Write the handover and usage note
Drafts the short accompanying note confirming what the client now holds, how to access and use it (especially for interactive or model formats), and what they can do with it — so ownership transfers cleanly.
In / outFinalised artefact details + client context → handover and usage note
You might say…
“I don't want to send a file and have them message me a week later asking what they're supposed to do with it.”
What it does
Draft the short accompanying note that confirms what the client now holds, how to access and use it (especially for interactive or model formats), and what they can do with it — so ownership transfers cleanly rather than leaving them with a file and no orientation. Used once at hand-over.
Trigger: Use once per handover to accompany the final delivered artefact.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation