In 30 seconds

A reliable intake form replaces "however the request happens to arrive" with a consistent starting point that already contains the information the workflow needs. It is one of the highest-value, lowest-cost improvements you can make.

Why this comes up

When requests arrive as free-form emails or verbal messages, every downstream step has to chase missing details. Half the work becomes asking for information that should have come in the first place.

An intake form fixes the input once, so the rest of the workflow starts from something complete and consistent. This is the structured intake pattern in practice.

Design the form around the decisions

The fields on the form should be the information the workflow actually needs to make its decisions. Work backwards from your map: for each decision, what does it require? Those requirements become your fields.

Avoid asking for information nobody uses. Every extra field lowers completion and adds noise.

Make required information actually required

If a field is needed for the work, make it mandatory and validate it at submission. It is far cheaper to reject an incomplete request at the door than to discover the gap three steps later.

  • Require the fields the workflow cannot proceed without.
  • Validate format where it matters: a real order number, a valid email, a date.
  • Use choices instead of free text where the answer is one of a known set. This turns messy input into clean structured data.

Plan for incomplete and unusual submissions

Even a good form gets imperfect submissions. Decide in advance:

  • What happens when a required field is missing or clearly wrong?
  • Where does an unusual request go that the form does not fit?

A "something else" path that routes to a person prevents the form from forcing bad data just to get through.

A small example

An IT team took requests by email and spent hours asking for device names, error messages and urgency. A short intake form with those as required, validated fields cut the back-and-forth sharply. Requests arrived ready to act on, and the exceptions that did not fit the form went to a triage queue instead of forcing bad answers.

What this does not solve

A form improves the input; it does not fix a workflow nobody understands, and it cannot capture genuinely unstructured cases well. Keep a path for the requests that do not fit, rather than distorting the form to cover everything.

Good enough to move on when

  • The fields match the decisions the workflow makes.
  • Required fields are validated at submission.
  • Choices replace free text where the answer is from a known set.
  • Incomplete and unusual submissions have a defined path.