How to Return an Incomplete Project Request Without Starting a Fight

An incomplete request needs a question, not a verdict.

Name the missing fact

Say: “I can see the proposed dashboard, but I cannot yet tell who uses the current report or what goes wrong.” Do not send a generic rejection or the full form instructions.

Explain why the fact matters: “We need this to compare impact and identify the right owner.” That turns the return into progress instead of a compliance exercise.

Ask one question at a time

Use requirements gathering software to keep the question beside the original request. Ask what happens today, who is affected, what the consequence is, or what outcome would prove success.

The form diagnosis is in why stakeholders hate your intake form. Once the missing fact arrives, return the request to software project intake without translating the requester into somebody else.

One requester labeled difficult because she ignored three returned forms. A ten-minute conversation revealed she did not control the budget field we kept requiring. The conflict belonged to the template.

Preserve the requester’s words

Do not rewrite the answer into project language and ask for approval. Review for understanding, then let the original witness remain visible.

Use the free Project Intake Evaluation Worksheet to test whether your minimum-data rule asks for facts requesters can honestly know.