The One-Page Brief That Turns a Research Handoff Into an Answer

You know the handoff. A colleague asks you to 'look into' a vendor, a competitor, a policy change, or a conference. Two days later you get a document with 34 links, three screenshots, and no clear answer. Everyone involved feels busy. Nobody feels helped.

The problem is rarely laziness. It is that the original request was a topic, not a search task. A topic invites a tab dump. A task invites an answer. At ExpressSeek, we think the fix is a one-page search brief — short enough to write in ten minutes, specific enough that the person doing the searching knows when to stop.

Why tab dumps happen

A tab dump is what you get when the searcher has no definition of done. They do not know which question matters most, which sources count, or how much time is reasonable. So they collect everything that looks relevant and hand it back. The reviewer then has to do the actual search work: sort, compare, and decide.

That is a double handoff. The first person hands off the searching; the second person hands off the judgment. A brief collapses those steps. It tells the searcher what decision the research supports, what constraints apply, and what evidence would be good enough to stop.

The five fields of a search brief

A useful brief does not need to be long. One page is plenty. It needs five fields.

1. The real question

Write the question the answer will inform, not the topic. 'Look into project-management tools' is a topic. 'Which of these three tools can import our current tickets without losing attachments, and what would it cost for 40 users?' is a question.

If you cannot phrase it as a question, you are not ready to hand it off. Ask yourself what decision will change based on the answer. That decision is the real brief.

2. The constraints

List the boundaries that should shape the search: deadline, budget range, geography, date range, must-have features, and anything that is explicitly out of scope. If the answer has to be US-only, say so. If the research should cover the last 18 months, say so. If a particular vendor is already ruled out, say that too — it saves everyone a wasted hour.

Constraints are not restrictions on curiosity. They are search filters. They make the difference between a broad scan and a useful result.

3. Acceptable sources

Name the kinds of sources you will trust. For a vendor comparison, that might mean the vendor's own documentation, security pages, pricing pages, and at least one independent review. For a policy question, it might mean the primary government document, not a summary of it. For a market question, it might mean recent filings, earnings calls, and reputable trade press.

Be explicit about what does not count as evidence. AI-generated summaries can be a starting point, but they are not a source. Neither is a random listicle with no author or date. If you want the searcher to use forums, say so and explain how to weigh them.

4. Stop conditions

This is the field most people skip, and it is the one that prevents the tab dump. A stop condition tells the searcher when they have done enough. Examples: three independent sources agree on the core fact; the shortlist is down to two options; the deadline arrives; or the searcher has spent 90 minutes and should report what is still missing.

A stop condition is not a guarantee of certainty. It is a boundary. It lets the searcher return an answer with a confidence level instead of an endless pile of links.

5. The verification step

Ask for one deliberate check before the handoff comes back. That could mean confirming a price on the vendor's own page, checking the date on a policy document, or cross-referencing a claim with a second source. The searcher should note what they verified and what they could not.

Verification is what separates research from aggregation. A link is not proof. A checked claim is closer.

A brief you can paste into a message

Question: Which of the three shortlisted vendors can meet our security requirements and stay under $18,000 per year for 40 users?

Decision this supports: whether to request demos from all three or narrow to two.

Constraints: US data residency, answers by Friday at noon, current pricing only, exclude vendors without SOC 2 Type II.

Acceptable sources: vendor security pages, pricing pages, and one independent review per vendor. No AI summaries as final evidence.

Stop when: two vendors clearly qualify, or all three are documented with gaps. If pricing is not public, say so and stop.

Verify: check the SOC 2 claim on the vendor's own trust page and note the date.

That brief takes less time to write than one meeting about the meeting. It also gives the searcher a way to succeed.

How to review the handoff without drowning

When the results come back, read the one-paragraph answer first. Then look at the evidence map: claim, source, date, confidence. If there is no answer, ask for the missing field in the brief rather than asking for 'more research'.

Spot-check two claims. Not all of them. Two is enough to see whether the searcher understood the standard. If the citations are stale, vague, or circular — three articles quoting the same press release — send it back with a specific note.

And if you get a tab dump anyway, do not just accept it. Reply with the question and the stop condition. 'This is useful background, but I still need a yes or no on whether Vendor B meets the security requirement. Can you answer that in one paragraph?'

A search handoff is not about transferring tabs. It is about transferring a question clearly enough that someone else can close it. The brief is the bridge.