Reject Unanswerable Research Requests at Intake

Some research requests cannot be completed because they ask for knowledge the available evidence cannot supply. Find their exact budget, tell me why they ignored us, and prove they need our service may all look like assignments. Each can instead invite speculation presented as fact.

A useful intake process does not merely collect required fields. It tests whether the question is answerable through permitted methods and whether the answer would change a legitimate decision. Reject the unsupported premise while helping the requester find a better question.

Use four intake outcomes

Accept for research when the entity, decision, and evidence route are sufficiently clear. Return for clarification when a missing definition prevents a reliable answer. Route for an owner decision when the issue is policy, authority, or commercial preference rather than a missing fact. Mark cannot determine when the requested conclusion exceeds what the permitted evidence can establish.

The GOV.UK Service Manual: Plan user research for your service recommends turning unfounded assumptions and opinions into research questions and choosing methods suited to the answers needed. Its context is service user research. The intake method here adapts that principle to account research rather than treating every seller hypothesis as established reality.

Do not make cannot determine a permanent claim about all possible knowledge. State the boundary: cannot determine from the supplied and permitted sources, or cannot establish without information the organization has not provided.

A filled fictional intake board

Imagine four requests arriving at an internal research desk:

• Request A: find the purchasing budget of fictional Vale Components. Decision unclear; no budget statement supplied. Outcome: clarify the intended decision and explain that an exact budget cannot be inferred from company size. Possible replacement: identify published project scope and the budget question for an appropriate future conversation.

• Request B: confirm whether Vale's East Yard is an operating repair site. Entity reference and service-coverage decision supplied. Outcome: accept a bounded operating-status check using company and relevant official sources.

• Request C: decide whether we should serve a site outside our normal area. Facts about location already established. Outcome: route to the commercial owner for an exception decision, not another research ticket.

• Request D: explain why a contact has not replied. No explanation from the person exists. Outcome: cannot determine motive; offer a factual review of delivery status, relevance, prior interaction, and applicable stop rules instead.

The examples are fictional. They demonstrate different intake decisions, not findings about a real account or person.

Ask the smallest clarification that unlocks the task

For A, ask what decision requires the budget figure. Perhaps the requester only needs to know whether a published procurement process exists. That is a different, potentially answerable question. Do not ask for twenty background fields when one clarification changes the assignment.

For B, confirm what operating means for this decision. A planned opening and a current service location may both matter, but they must remain separate. Define the relevant date and geographic boundary before beginning.

For D, preserve the distinction between observable silence and an explanation of intent. A factual communication review does not justify repeated follow-up or private-person inference. It may conclude that no further action is appropriate.

Record the rewrite, not just the final status

Keep the original request, the accepted replacement question, the requester who agreed to it, and the excluded claims. Otherwise a later reader may believe the narrower deliverable answers the original broad question.

The intake record for A might say: exact purchasing budget not established; revised task is to check for a published procurement notice relating to the named project; absence of a notice will remain inconclusive about budget. That last condition prevents a new unsupported inference from replacing the old one.

If clarification never arrives, return the task with its blocking question. Do not let it occupy an active research slot indefinitely or silently choose a convenient interpretation.

Protect the boundary when urgency increases

An urgent deadline changes priority, not what evidence can establish. A manager can authorize a narrower internal decision with uncertainty, but cannot make a guessed fact verified by asking for it sooner.

End intake with a question the researcher can execute, a controlled route for the decision owner, or an honest explanation of what cannot be determined. Rejecting an unanswerable request is useful service when it prevents confident nonsense and gives the team a better next decision.

Continue with Plan a First Sales Hire's Research Training or Create a Useful Sales Research Service-Level Agreement.