Hand off a research question with evidence and a clear next action
A research handoff should tell the next reader what question to answer, what has already been checked, and what remains to do. Attach source identities and locators, not just a conclusion. Define acceptance criteria so the recipient can complete a concrete task without reconstructing a long conversation.
W3C provenance provides background for identifying objects and activities. Library of Congress format resources support thinking about readable material. The handoff sheet below is an original workflow suggestion, not an assertion that a shared task has been sent or that an external reviewer has approved anything.
Lead with the unfinished question
Write the question in one sentence, naming entity, period, and event where relevant. State the current status: unresolved, partially answered, or ready for a specific review. A generic instruction to “check the research” leaves the recipient guessing about scope and may produce duplicated work.
Then list inspected sources and actions. Separate available-but-unread files from checked evidence. Explain unsuccessful searches that matter, including filters and access failures. This context prevents the recipient from repeating failed paths or assuming that a collected source was already evaluated.
Hypothetical handoff sheet
Assume fictional North Meadow’s contract-party question is being handed to a colleague. This is an invented scenario, and no message is being sent by this article.
| Field | Hypothetical content |
|---|---|
| Question | Which legal entity signed the facility agreement? |
| Checked | Issuer notice names subsidiary; cover identity verified |
| Available, unread | Agreement exhibit downloaded, not inspected |
| Limit | Parent support terms not established |
| Next action | Read agreement parties and signature section |
| Acceptance | Exact entity name, locator, and remaining limitation recorded |
The recipient can act without guessing whether the task concerns financial terms, project viability, or entity identity. If the agreement does not settle the question, the handoff can close with a documented unresolved result rather than an invented answer.
Include reasoning only where it guides action
A short explanation of why the question matters can help. For example, two similar legal names may have caused an earlier mismatch. Include that ambiguity and the evidence already checked. Do not bury the next action beneath pages of speculative interpretation or unrelated company history.
Link the source packet and its manifest. Ensure the recipient can identify which version each locator uses. If access depends on an account, state that constraint and provide a public route where available. A handoff with inaccessible evidence is a partial handoff and should be labeled accordingly.
Verify with a recipient simulation
Read only the handoff and try the next action. Can you find the correct source, locate the target section, and tell what counts as completion? If not, add the missing identity, path, or acceptance condition. This tabletop check does not substitute for actual substantive review; it tests whether the instructions can be followed.
When the work returns, record what was checked and the outcome. Distinguish reviewer observations from your later interpretation. If scope expanded, update the handoff rather than presenting the result as if it answered the original narrow question unchanged.
Limits and common mistakes
A handoff does not transfer certainty. The next researcher inherits a task and evidence trail, not a guaranteed conclusion. It also does not authorize communication to others by itself; actual sharing should follow the human’s instruction and relevant access expectations.
Common mistakes include sending only a summary, failing to mark unread attachments, leaving acceptance vague, and omitting historical cutoff information. Another is asking a reviewer to confirm a preferred answer. Frame the task as an open check with a bounded output so disagreement can improve the record.
A final record check
Add a return format when coordinating review: answer, source locator, action performed, and remaining limit. This avoids receiving an unqualified approval when the task required a precise evidence check. The recipient can disagree with the preliminary interpretation while still completing the handoff correctly. Record that disagreement as a research result, not as failure to follow instructions.
FAQ
Should I include every note in the handoff?
No. Include the material needed for the defined question and link background separately. The recipient should see the next action immediately.
What counts as a successful unresolved handoff result?
A clear account of sources checked, the exact remaining gap, and the evidence needed next. An honest unresolved result can satisfy the task without establishing the underlying fact.