Best-Practice Form Templates
Last updated: July 21, 2026
Starting a subtask from a blank canvas is slow, and it's easy to miss best practices like layout structure, masking, or pre-filled dropdowns.
Form templates solve this: pick a starter, drop it in, and customize from there.
What Are Form Templates?
A form template is a pre-built subtask — already laid out with layout containers and best-practice fields — that you insert instead of building from scratch.
Templates come pre-configured with things like:
Layout containers (Group, Columns) already structured
Masking applied where relevant (e.g., phone, sensitive fields)
Pre-filled reference dropdowns (states, countries, dialing codes) where relevant
Once inserted, a template is fully yours to edit — add, remove, or rearrange fields freely.
Where to Find Templates
The template gallery appears at the empty-state / "new subtask" entry point in the task builder — the same place you'd otherwise start from a blank canvas.
Starter Templates Available
Contact / Company Info – Name, company, role, phone, email
Address Block – Street, city, state, zip, country
Document Collection – File upload with instructions
Kickoff Questionnaire – Common project-kickoff questions
💡 Tip: Templates are a starting point, not a final product — always review and adjust fields to match what you're actually collecting.
Using a Template
Open the task builder and go to add a new subtask
Choose a template from the gallery instead of starting blank
The template populates the canvas fully laid out
Edit freely — add/remove fields, adjust layout, rename labels
Why Use a Template Instead of Building From Scratch
If the goal is speed…
Start from a template and edit only what's different.
If the goal is consistency…
Templates enforce the same layout-first structure and validation patterns across your org's tasks.
If the goal is learning the builder…
Templates model the best-practice assembly order (layout first, then fields) better than a blank canvas does.
Best Practices
✔ Start from the closest matching template, even if you'll change most of it
✔ Don't skip the layout containers a template gives you — they exist for a reason
✔ Review masking and dropdown settings a template includes — confirm they match your use case
✔ Rename generic template labels to match your specific task language