Research and Source Management

Research Handoff Packet

Transfer findings, source context, evidence limits, unresolved questions, restricted material, and verification priorities from researcher to writer.

Free editable Markdown · Research teams, writers, and editors · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Assignment orientation

Project and deliverable: [Name and format]
Primary reader: [Role, need, and knowledge]
Research question: [Final bounded question]
Scope and exclusions: [Population, period, geography, and omitted areas]
Definitions: [Terms the writer must use consistently]
Research cutoff: [YYYY-MM-DD]
Expected publication date: [YYYY-MM-DD]
Suggested structure: [Evidence-led outline, if helpful]

Findings and files

Finding 1: [Bounded conclusion] — **Source IDs:** [IDs] — **Confidence:** [Reason]
Required qualification: [Limit that must remain]
Finding 2: [Bounded conclusion] — **Source IDs:** [IDs] — **Confidence:** [Reason]
Contradictory evidence: [Sources and treatment]
Approved quotation log: [Link and attribution rules]
Calculations or data: [Versioned location]
Approved assets: [Files and permission]
Restricted materials: [Access path and prohibited use]

Open work and acceptance checks

High-consequence and volatile claims are marked.
Every finding links to source context.
Interpretation is distinguished from source language.
Open questions have owners, dates, and fallback wording.
Pending source responses are not treated as confirmation.
Restricted information is not duplicated into unsafe locations.
Claims that evidence cannot support are listed explicitly.
Writer, researcher, and editor agree on the continuing update channel.

How to use this template

Restate the audience, assignment, research question, scope, definitions, and delivery constraints.
Summarize each major finding with confidence, source IDs, and mandatory qualifications.
Link approved notes, evidence, calculations, quotations, assets, and permission records.
Assign open questions, contradictions, pending responses, and prohibited claims clear treatments.
Conduct the handoff, confirm understanding, and name the ongoing question and update channel.

Orient the writer to the assignment

Begin with the reader's need, primary research question, scope, important definitions, and publication constraints. Summarize what changed during research: a question that narrowed, an assumption that failed, or a source that redefined the outline. Include a suggested evidence-led structure only when it follows the findings. The handoff should prevent the writer from restarting discovery, but it should not lock them into a narrative that contradicts the available evidence.

Deliver findings with provenance

For each major finding, state the bounded conclusion, confidence, source IDs, and qualifications that must remain with it. Link to the source inventory, citation records, synthesis, interview notes, calculation files, and approved assets. Distinguish exact quotations, close paraphrases, data outputs, and researcher interpretations. Flag facts that are volatile or high consequence. If a source is confidential, explain permitted use and provide access only through the approved system rather than copying sensitive content into the packet.

Make unfinished work actionable

List contradictions, missing evidence, pending responses, fact-checking priorities, legal or specialist reviews, and claims that must not be written. Give each item an owner, status, deadline, and fallback treatment. Schedule a short verbal handoff for complex work and invite the writer to repeat the main limits in their own words. After drafting begins, record new questions and decisions in the shared trail so research context does not fragment across private messages.

See the fields in context

Fictional example: market shelter renovation explainer

Dovetail Market and all project documents are invented for this handoff demonstration.

Finding: The fictional renovation schedule has three approved phases; source is the invented council plan, revision B.
Qualification: Dates are planning targets rather than guaranteed completion dates.
Open question: Accessibility review comments are pending; the writer must not claim final compliance.
Restricted material: Vendor contact details remain in the approved project drive and are not copied into writing notes.
Fallback: If no response arrives, describe only the published design stage and note that final review was not available by cutoff.

Frequently asked questions

Should the packet include every research note?

Link complete notes for traceability, but foreground the material findings, limits, and decisions the writer needs. An undifferentiated note dump is not a handoff.

Who owns fact-checking after handoff?

Define responsibility explicitly. Researchers can clarify sources, while the writer and editor still need an agreed verification and approval process for the final wording.

What if the writer discovers new evidence?

Add it to the shared source trail, assess how it changes the synthesis, and notify the responsible researcher or editor rather than silently replacing context.

Can a handoff packet be generated automatically?

Automation may assemble links or fields, but a knowledgeable person must verify findings, restrictions, uncertainty, and the relationship between evidence and claims.