Templates
Last updated: November 17, 2026
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.
Studies Start from Templates for Many
Researchers working in Rally can use a study template or start from scratch. Through the Rally Agent and MCP, a study template is required, and the study takes everything that template carries: consent form, brand, default incentive, screener questions and their property mappings.
Your template library therefore sets the limits of what AI-assisted research can produce. If a team is missing a template for a specific study type or scenario, they won’t be able to build that study through an agent.
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 Configuration Guidance 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 standard email templates.
Team-Specific Templates
Internal Teams: Give them access to "Employee-only" incentives and "Internal" study templates.
Specialty Product Teams or Research Programs: If a Beta Program needs to specific branding, different consent, modified email templates, and their own population, assign these only to the team that's using a beta program so as not to confuse other teams.
Management & Override Permissions
Be selective about which roles have the permission to create and modify templates to maintain the integrity of the baseline templates.
Some elements in study templates can be locked for most study creators. The permission to override locked template elements should be limited to trusted individuals that understand the implications of changing those elements. A lock holds only as far as the list of people who can bypass it.
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 questions before you create a new template variation:
Factor | Ask Yourself... | Decision |
Audience | Is the participant internal (employee) or external (paying customer/prospect)? | Create New if the tone, legal consent, or branding must differ significantly. If the change is minor (e.g., changing one sentence in an email), use guidance over another template to instruct study creators to modify the version within a specific study. |
Frequency | Will this specific workflow (e.g., a "Monthly Pulse Survey" or "Standard Usability Test") be repeated by multiple people? | Create New to ensure consistency and save time for non-UXR teams. |
Compliance | Does this study type require specific legal "guardrails" (e.g., an NDA vs. a standard GDPR consent)? | Create New to pre-set key settings or lock certain capabilities into the workflow. Use caution since this will increase template change management and confusion at the time a study creator selects a template. |
Translation | Will the study be facilitated in more than one language? | Create New to support specific translations of your studies and communication since only one language can be selected for a study at the time of creation. |
Guardrails vs Guidance
Guardrails are the “must-haves” that protect the company—like your legal NDAs and branding. 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.
Feature | Guardrails Use templates when... | Guidance Use documentation when... |
Legal/Privacy | NDAs, GDPR consent, or specific data-sharing agreements are required. | Minor phrasing tweaks are needed for a specific study. |
Data Integrity | Standardizing CRM fields (e.g., "Job Role" dropdowns) is critical for filtering. | Asking open-ended discovery questions. |
Brand/Image | Using a specific sub-brand logo or a highly formal executive tone. | Choosing between "Hi" or "Hello" in an email greeting. |
Incentives | Budget caps or specific payout methods must be enforced for a team. | Deciding the specific dollar amount (within a range). |
Guidance can be built into Rally by creating skills. See Skills & Workspace Knowledge.
When to lock a template element
A locked element in a study template cannot be changed in the Rally interface or through an AI assistant unless the user has permission to bypass as part of their role.
Every locked element removes a decision someone (or the agent) would need to make, but it can also unnecessarily restrict decisions that just need guidance over enforcement. Lock what carries real consequence. Leave the rest to guidance or preset values.
How Templates are Found
You decide what a template contains. The person using it decides which one to take, and that person usually did not build it. The match is made from how your templates present themselves: a study template chosen by name and description, an email or question template pulled from a library the same way.
Name and describe them in the words your researchers use. A template named after the project or quarter that produced it stops being findable once that context fades, and an unfindable template gets replaced by whichever one looks closest.
Library size affects which template gets chosen. Each near-duplicate adds another chance for the wrong one to be taken, and the person choosing has no way to know they chose wrong.
Make the cost visible in the name. A study template that recruits through an external panel provider draws from the provider’s pool and charges per participant. That should be clear before anyone selects it.
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
Use skills in Rally to guide other decisions that may need additional context to set well.
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.
Where Guidance Belongs
Guidance covers what a template deliberately leaves open: what to adjust for a specific scenario, which incentive amount fits, what to add to a screener.
Keep it out of the description, which is read when someone is choosing a template rather than configuring one. Hold it in a research playbook your team maintains, or in custom skills that state your standards at the moment the decision is being made. Skills can do what a static document cannot, which is present the open choices during study creation and editing.
Placeholder text inside a template’s preset values is not guidance. It may reach a participant without someone catching it first.
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.