Make research easier and faster to launch with vetted, preconfigured templates. Decide when to stick with the baseline, when to create something new, and how to manage access.

Template Types

Rally supports the ability to create templates across a variety of types to enable re-use and consistency. The template types covered in this guidance include:

• Study Templates: Create these so study creators have a pre-configured study set with the right email, screener, and consent to speed creation, maintain consistency, and leverage best practices.

• Question Templates: Focus on the "Screening Baseline." Create templates for standard demographic questions (Age, Role, Tools Used) so data is collected consistently across all studies, making CRM filtering easier later.

  • Map the answers to these questions to database properties if you want to hold on to these self-reported values beyond a specific study to help with future recruiting efforts.

  • See Screener Best Practices for more details around how questions work when they are used in screeners and surveys.

• Email Templates: Differentiate by Engagement Type.

  • Internal: Plain text, "colleague-to-colleague" tone.

  • External: Branded, professional, clear value proposition, and "official" company voice.

• Branding: Create specific sets for different sub-brands or specialized programs (like a "Beta Research League" which might have its own logo and/or email domain).

Additional templates for consent and custom incentives are covered in other modules.

Access Control: Who Needs What?

Managing access prevents clutter and protects sensitive processes.

• Workspace-Wide (default): Use for "Universal Assets" like standard company branding, common screening questions, basic GDPR consent, and "Thank You" email templates.

• Team-Specific Access:

  • Internal Teams: Give them access to "Employee-only" incentives and "Internal" study templates.

  • Specialty Product Teams or Research Programs: If the "Mobile App" team has a unique beta program, restrict their specific branding and NDAs to just that team to avoid confusing the "Web App" researchers.

  • Ops & Admins: Only these roles should have "Create/Modify" permissions to maintain the integrity of the baseline templates.

When to Create a Template

A common mistake for new users is "template bloat"—creating a new template for every single study scenario. Don't build a template for the sake of building. Build a template when you find yourself doing the same manual task repeatedly, or when you need to ensure a study creator follows a specific legal, compliance, or brand standard.

Ask these three questions before you create a new template variation:

Guardrails vs Guidance

Guardrails are the “must-haves” that protect the company—like your legal NDAs and branding. Guidance Guidance is the “nice-to-haves” that you can teach through documentation. If you create a new template for every “nice-to-have,” your team may struggle to use the templates because they won’t be able to find the right one to use or find them too rigid to be useful.

If a request doesn't fall into the "Guardrail" column, it should likely be handled through "Guidance" or a modular baseline.

Strategies to Reduce Template Sprawl

Standardize Templates by Study Type

You likely do NOT need separate templates if:

• The core research technique is the same

• Email copy is the same

• Only schedule/duration, incentive type/amount changes

Instead:

• Use a core set of templates that have the best preset values for most decisions, including:

  • Default brand

  • Default consent

  • Core compliance questions for screeners with logic and property mapping

  • Default messaging

• Take advantage of personalization tokens in participant-facing elements like emails, welcome pages, etc to tailor the copy to a specific participant and a specific study without creating another template.

• Provide guidance and documentation around what to change when creating a study from a template through a playbook

80/20 Rule for Modular Templates

Instead of creating a specific template for every research scenario (e.g., "Mobile Usability," "Desktop Usability," "Tablet Usability"), create a Modular Baseline template to cover 80% of the decisions pre-set and pair it with guidance to cover the remaining 20% of decisions that might be study-specific.

• Guardrail: A Usability Testing study template with the correct consent form, base email communication, required screener questions, etc.

• Guidance: Notes around adding relevant screener questions, choosing the appropriate incentive amount, and adding any study-specific language or expectations into the email communication.

Integrated Guidance

Use the template’s description field to direct study creators on when to use this template and where to find guidance on what to change.

• Example: Use this for all customer interviews. If you are in the Fintech pod, remember to swap the logo in the branding tab. Refer to this guidance on other changes you should make for your study - https://link.com/rallytemplateguidance

Use placeholder text (e.g., [INSERT PRODUCT NAME HERE]) to signal when something needs to be changed manually.

Leverage Personalization Tokens

Personalization tokens in Rally help you dynamically tailor personalized email messages, calendar invites, and study registration screens for a specific participant within a specific study. 

• Participant Tokens (Available across most email types)

  • Participant First Name

  • Participant Last Name  

  • Participant Email

• Interview-Specific Tokens (Available for Interview templates)

  • Interview Start Date

  • Interview Start Time

  • Interview Length

  • Study Start Date

  • Study End Date

• Study-Level Tokens

  • External Study Name

  • Study ID

• Sender Tokens

  • Username ← Rally user’s name when sending messages to participants

• Custom Properties

  • Any custom properties you create can also be used as personalization tokens

  • Keep in mind that not all participants will always have a value stored for all custom properties, making it highly likely that this information might be empty

Template Review & Sunset

Treat templates like product features, review them regularly for usage and effectiveness. Sunset ones that are no longer beneficial.

• Quarterly or Bi-annual Audits: If a template hasn't been used in 90 days, archive it.

• One-In, One-Out Rule: For every new global template created, identify one that can be retired or merged.

References

https://help.rallyuxr.com/collections/7532906214-templates

https://help.rallyuxr.com/articles/6471072345-study-templates

https://help.rallyuxr.com/articles/9615867376-question-templates

https://help.rallyuxr.com/articles/9825183946-email-templates

https://help.rallyuxr.com/articles/1892854849-branding