Client handoff template
A handoff explains how the recipient can continue. The template keeps actual delivery state, access and pending decisions easy to find.
How to use this file
- State version, included scope and actual review status.
- Verify the evidence and authorized access needed to use the delivery.
- Separate pending validation from decisions requiring client input.
- Review the final document and agree on follow-up for unresolved items.
Open the file in an ordinary editor or spreadsheet. It is a manual resource, usable with or without FlowSight. It does not imply automatic agent import or integration.
A worked example
Fictional example: documentation delivery is reviewed for one environment, with another environment's validation explicitly pending.
Template preview
# Client handoff Project: [project] Delivery: [name and version] Date: [date] Recipient: [authorized audience] ## Scope and delivery state - Included: [scope] - State: [reviewed / pending validation / delivered] - Evidence: [authorized reference] - Excluded: [scope outside this delivery] ## Access and starting point - Location: [authorized link] - Prerequisites: [required access or setup] - Access owner: [role] - Never include passwords or secrets here. ## Pending validation - [check, owner and condition] ## Decisions required - [question, consequence, owner, date] ## Next action - [action and responsible person] Check the final file, links, recipient and unnecessary information before sharing. Published by Manuel Castillejo / FlowSight, https://flowsight.site
Review before sharing
Check outcomes against evidence, preserve uncertainty and remove details the reader does not need. Review connected services separately if they process the document. The worksheet itself is a drafting aid, not a guarantee about privacy or compliance.
Read the supporting workflow · Check FlowSight documentation