Set default content for form fields
Default content automatically pre-fills form fields with values when a task or kick-off form opens. It’s a real time-saver - reducing data entry and keeping things consistent across your processes.
You can use static text, dynamic variables, or system-generated values like today’s date. And yes, users can still change these pre-filled values whenever they need to.
- Faster form completion: Users spend way less time typing the same info over and over.
- Reduced errors: Pre-filled content keeps formatting consistent and cuts down on typos.
- Better user experience: Let’s be honest - forms feel so much easier when they’re already partially filled.
- Dynamic information: Variables automatically pull in relevant data from earlier steps. No more copy-paste.
- Smart defaults: Set the most commonly selected options to help people decide faster.
Not all form field types support default content. Here’s what works:
Text fields give you the most flexibility - they’re the workhorses of default content.
- Static text: Pre-fill with standard phrases, instructions, or helpful examples.
- Variables: Pull data from previous form fields or system variables.
- Mixed content: Combine static text with variables (like “Request from
{{customer_name}}
”).
Want to speed things up? Pre-select the options people pick most often.
- Default selections: Choose the most common option and save everyone a click.
- Multiple defaults: For checklists, you can pre-check several items at once.
Date fields are smart - they calculate deadlines and timestamps automatically.
- Current date/time: Sets to today’s date. Simple.
- Relative dates: Need something due next week? Use “today + 7 days”.
- Variable dates: Pull date values from earlier form fields.
Some field types can’t have defaults - mostly for technical or security reasons. Here’s why:
- File upload: Can’t pre-populate files (security thing - and honestly, would you want random files appearing?).
- Table: Can’t pre-fill table rows, though you do set up column headers during configuration.
- Assignee picker: Can’t pre-select specific users here, but don’t worry - you can set default assignments at the step level instead.
- Open your template in Edit mode.
- Click on the step containing the form field you want to configure.
- Go to the Form Fields tab in the details panel.
- Click on the specific form field to open its settings.
- Look for the Default Value or Default Content field in the settings.
- Enter your default text or click the button to insert variables.
- Save your changes.
- Open the form field settings (same process as above).
- In the Options section, enter your list of choices - one per line.
- Find the Default or Default Selection option.
- Pick which option should be pre-selected when the form loads.
- Save your changes. Done!
- Open the checklist field settings.
- In the Options section, type your list of items (one per line).
- Find the Default or Pre-checked items options.
- Select which items should already be checked when someone opens the form.
- Don’t worry - users can still uncheck these if they need to.
- Hit save and you’re all set.
- Open the date field settings.
- Look for Default Date or Default Content options.
- Pick what works best:
- Today: Automatically uses the current date.
- Today + X days: Perfect for deadlines (like “Today + 7 days” for next week).
- Custom date: Set a specific date that never changes.
- Variable: Pull a date from another form field.
- Need time too? Date/time fields let you set default times as well.
- Save your changes.
Variables are where things get really interesting. They pull information from other parts of your process and drop it right where you need it.
Form field variables: These grab data that someone entered in earlier steps.
- Example:
{{customer_name}}
pulls in the customer name from a previous field. No retyping needed.
Kick-off form variables: Info that was entered when the process first started.
- Example:
{{request_type}}
shows whatever type was selected in the kick-off form.
System variables: Tallyfy generates these automatically - they’re always current.
{{DATE}}
: Today’s date{{TIME}}
: Current time{{TEMPLATE_NAME}}
: The template you’re using{{PROCESS_NAME}}
: This specific process instance’s name
Customer communication: Here’s a template that practically writes itself:
Dear {{customer_name}},
Thank you for your {{request_type}} request submitted on {{DATE}}.We will process this within 5 business days.
Reference numbers: Need unique IDs? Create them automatically:
{{TEMPLATE_NAME}}-{{DATE}}-{{customer_id}}
Follow-up dates: Keep track of deadlines without thinking:
Follow up with {{customer_name}} by {{deadline_date}}
- Pick the options people actually select 80% of the time for dropdowns and radio buttons.
- Set default dates that match your real process timeline - not wishful thinking.
- Pre-fill text fields with genuine examples or formats people can actually use.
- Users will change defaults if they need to - that’s the whole point. Don’t box them in.
- Think of defaults as helpful suggestions, not rules.
- Test with real users. If they’re constantly changing your defaults, you’ve got the wrong defaults.
- Mix static text with variables - you get consistency AND personalization.
- System variables are perfect for timestamps and tracking info.
- Reference earlier form fields to keep everything connected. Context matters.
- Internal forms: Your team knows the jargon. Use shortcuts and abbreviations they understand.
- External forms: Customers need clarity. Spell everything out.
- Repetitive processes: If people do this 20 times a day, load it up with smart defaults. Save them time.
- Check your defaults every few months. Things change.
- Listen when users complain - they’re telling you what needs fixing.
- If everyone’s changing a default, just delete it. It’s not helping.
Want faster response times? Default content is your secret weapon.
- Default priority: Set to “Medium” - let’s be honest, most requests aren’t actually urgent.
- Default category: Pre-select whatever 60% of your tickets are about. Saves time.
- Response template: Drop in a friendly greeting with the customer’s name already filled in. Personal touch, zero effort.
Nobody likes waiting for approvals. Smart defaults keep things moving.
- Default reviewer: Match the reviewer to the request type. Finance requests go to finance team - simple.
- Due date: “Today + 3 days” gives reviewers breathing room without dragging forever.
- Approval notes: Give reviewers a template so feedback stays consistent and useful.
Starting new projects? Stop reinventing the wheel every time.
- Project prefix: Combine template name + today’s date. Instant project codes that actually make sense.
- Default team members: Pre-select your usual suspects for each project type. They know they’re on it.
- Timeline defaults: Standard milestones based on the start date. Realistic timelines from day one.
Here’s where default content really shines - automated documents that don’t feel robotic.
- Document title: Mix project name + document type + date. Clean, searchable, organized.
- Author information: Pull requestor details straight from the kick-off form. No more “who wrote this?”
- Version numbering: Start everyone at “v1.0”. Consistency across the board.
The bottom line? Default content turns empty forms into smart, helpful starting points. Your team saves time, makes fewer mistakes, and still has total flexibility to customize when they need to. That’s a win.
How To > Build effective forms
- 2025 Tallyfy, Inc.
- Privacy Policy
- Terms of Use
- Report Issue
- Trademarks