Forms, Templates, and Intake
Structured intake
Forms turn requests into tasks with consistent fields. A form is attached to a project; each submission creates a task in that project. Form questions can map to task name, description, assignee, due date, and custom fields. Because form fields map to project fields, the project must already have those fields for the mapping to work. Forms let you standardize what requesters provide, reducing back-and-forth.
Templates for repeatable work
Templates capture a project's structure - sections, tasks, subtasks, fields, and sometimes rules - so repeatable work starts consistent. Project templates can be created from an existing project. Understand that a template copies structure, not necessarily the people or dates, depending on settings. Templates pair naturally with forms: a form triggers a task, and a template defines the project skeleton that task lands in.
Traps in questions
Common traps: assuming a form can set a field the project doesn't have (it can't), or that editing a template updates projects already created from it (it doesn't - changes apply to future instantiations). Another is confusing task templates with project templates. Also watch for questions implying forms can route to multiple projects automatically without rules.
Worked example
An IT intake form asks for request type, urgency, and description, mapping urgency to a drop-down field. A rule on the project then assigns the task based on urgency, and a project template supplies the standard sections (Triage, In Progress, Resolved).