A project handoff from public documents.

Illustrative inputs: a fictional three-person team is preparing a handoff from a public project brief, public release notes and a public FAQ. This is a worked scenario, not a customer story or a tested result.

Try these task and priority choices

Two candidates with different jobs.

NotebookLM: build the evidence first.

The catalogue lists NotebookLM for reading across supplied documents. Start by identifying requirements and the passages that support them. Follow each reference back to the document before using it in the handoff.

Limitation to check: an imported document may be incomplete or out of date. A source reference does not settle conflicting requirements; compare document versions and leave unresolved differences visible.

Read the NotebookLM catalogue note · Official NotebookLM source

Claude: shape the reviewed evidence into a draft.

The catalogue lists Claude for drafting and reasoning through supplied written material. Give it the passages you have reviewed and a clear handoff structure. Use it to draft the explanation while keeping the source labels and open questions attached.

Limitation to check: a readable draft can still introduce unsupported details. Compare every requirement and promise with the supplied material; do not treat the draft as an independent fact check.

Read the Claude catalogue note · Official Claude source

A workflow the team can review.

  1. List the public documents, their versions and what the handoff needs to answer.
  2. Use the source-focused candidate to locate supporting passages. Record contradictions and missing information.
  3. If a writing pass is useful, give the drafting candidate the reviewed passages and ask for a one-page handoff.
  4. Check each claim against its source. Leave unanswered questions visible before sharing the handoff.

These are complementary roles to consider; you do not need to use both products. Check current access requirements and provider data practices before supplying material.

A starting prompt to adapt.

Prepare a one-page project handoff from the supplied material.

For each requirement, include the document name and supporting passage.
Separate agreed requirements, conflicting statements and unanswered questions.
Keep document versions visible. Do not invent owners, dates or commitments.
If the material does not support a statement, label it unresolved.

Suggested sections: purpose, supported requirements, conflicts, next questions.
Material: [add only documents or reviewed passages you are allowed to use]

Edit the starting prompt in your guided shortlist, then copy or export it with the candidate notes. Choose Save on this device if you want to return to that shortlist.

Provider references use the catalogue’s 11 October 2026 documentation baseline. This illustrative workflow has not been tested hands-on. See the project brief guide for the longer method.