How the problem develops
A new project reaches the delivery team with a contact name but no usable brief, service location or agreed output. The coordinator asks for one missing item at a time. The client sees repeated chasing rather than one clear request.
What to check first
- Compare the intake form with what the receiving team actually needs to start the agreed work.
- Separate essential starting information from details that can be gathered later.
A better process
- Define a minimum complete intake for each service type.
- Show a single missing-information list with examples of acceptable answers.
- Keep a visible waiting state and identify which work, if any, can start safely.
What a system can do
Check required fields and formats, compile missing details and send a bounded follow-up using approved wording.
Where people stay in control
A completed form is not proof that a request is suitable. Unusual scope and sensitive information need human assessment.
Benefits and tradeoffs
The useful outcome
The client gets one coherent request and the delivery team sees what is ready.
The tradeoff
Requiring every possible detail upfront increases friction. Only block a start for genuinely necessary information.
Test before going live
Submit complete, partly complete and irrelevant answers. The system must distinguish an empty field from a superficially filled but unusable response.