Team Intake

A Request Form That Produces Actionable Tasks

Ask for the few fields that turn a request into work, then test how incomplete responses reach a human.

“Please fix the dashboard” gives a team a subject and little else. Ask where the failure appears and who needs the result before the requester closes the page. Those two fields give the team enough to route a first look.

Design the opening question around the choice the intake owner needs to make. The receiver should be able to assign the job, ask a specific question, or send it to a different queue without reading an old email chain. For software requests you could use structured controls like those in GitHub issue forms, including required inputs. Pick controls to match the answer you need.

Compare a request and a problem report

Field Design request example Fault report example
What should happen? Update the contact panel on the partner page The billing graph should show this month's labels
Where? Partner page link Dashboard link and selected reporting period
Who needs it and when? Events team before Friday's email Finance needs this data for its Monday review
Who can answer questions? Name or reachable address Reporter or affected teammate

A fault report also benefits from steps to reproduce the problem and a description of what actually happened. A design request benefits from a clear approval contact and any constraints on copy or artwork. Let the request type open the right extra questions. A required field should change the next person's decision. Making every field mandatory encourages people to enter dummy text when they lack the answer.

Put a person between intake and the queue

In Google Forms, responses can be collected in the form or linked to a Google Sheet. Give the intake owner a place to mark “ready”, “need detail” and “rerouted”. Provide the receiver with enough context to ask for one missing piece at a time. Check who can see the responses and remove any collection of personal data that the task does not need.

On the confirmation screen, say what happens to the request and who answers it. A requester who knows when to expect follow-up can avoid sending a second copy by email. Give a reachable contact for genuine corrections to a submitted request.

Make it possible to route an ordinary request

Suppose a finance team asks for a dashboard change. The intake owner needs to know whether the graph is broken for a configured period or the requester wants a new view. An early choice between reporting a fault and requesting a change can decide which follow-up fields appear. For a fault, ask for the screen, a short description of the observed result and the expected one, and an approved route for any useful screenshot. For a change, ask what decision the new view should support and who can approve its definition.

Read the form as a person who cannot supply an exact date. “Before the Monday finance review” is useful even if the requester does not know the meeting time. Give an optional field for the full deadline alongside a brief explanation of what will happen at that date. Ask for a contact who can check the time. A required date picker can prompt a guess, which makes a vague request look more precise than it is.

Some requests are deliberately confidential. Put an example under the attachment or details field that tells users to use test data and omit employee details, tokens or billing records. Where an attachment really is required, give the requester the organisation's approved upload route and check the sharing settings before linking it in a task. Let the receiver know how to ask for missing evidence without copying a confidential attachment across systems.

Run a two-response rehearsal

Send two example requests from an account with the permissions a requester will have. The first should point to the right dashboard and identify who needs help. The second should contain “soon” and have no clear location. Let the intake owner review both before seeing the original examples. Record the decision their task record enables, and the first detail they have to ask for.

Observed result Change to consider
Both requests appear identical in the queue Preserve the request type and original description when creating the task.
The second is impossible to route Require an affected service or offer a department choice with an “unsure” route.
The first works but the approver cannot see the screenshot Check the attachment sharing and the authorised place for evidence.
A second copy arrives by email Give a clear receipt and a contact for corrections to the existing request.

Follow those examples from form to queue. If dispatching creates a title and drops the original report, create a link an authorised receiver can use. Ask how the reviewer will know if a task has already been created. Give both test submissions a different internal reference, then reopen the first through the link a teammate will receive. That check is especially helpful when a form has an automation that writes to another app.

Make room for exceptions in the queue

Decide where work sits when it needs one more answer. A separate waiting status keeps it out of the ready column while the owner follows up. Give the owner a date to ask again. If requests regularly wait because a project field is missing, test different wording with one requester before adding a field to every form.

Agree on how to handle an exception, such as a billing report due today. Write the manual route in the receipt, and make clear which team should use it. When you review results, use the overloaded Kanban board example to distinguish requests waiting for information from active work waiting for someone to finish it. Keep the intake fields that change dispatch decisions, including how to reach the requester for an unusual case.

Rerun the incomplete example after each change to the form. A new field may improve a careful submission and make the quick one worse. If a requester picks an unrelated value just to finish the form, give them an honest option for uncertainty and send that answer to a human review task. Preserve the original wording alongside any classification so the reviewer can correct a bad guess without contacting the requester again. When the form asks for an account name, state which account it means and supply an example that contains no real account data.

Sources