Design an intake form from recurring requests

An intake form should ask for information needed to route and complete work. Avoid collecting fields simply because they might be interesting later.

Bound the operating task

Provide the relevant records and define what is a draft recommendation versus an approved action. Keep original records intact and ask for an output manifest so you can find the result. Start with file generation and human review before adding any external action through a connected tool. A useful operations deliverable should make exceptions and missing information visible.

Inputs for this workflow: Sanitized past requests and the team’s routing rules.

Work through the task

1. Identify missing information that delayed work.
2. Map each proposed field to a decision.

A brief you can adapt

Draft intake-fields.md with field, purpose, required status, example and handling note. Keep sensitive fields out unless necessary and approved.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Run several past requests through the draft form and check whether routing becomes clearer.

Where this approach can fail

The form should not imply a response-time promise that the team has not approved.

For the related desktop setup, see review results.