Hand over who runs it, what was tested and what happens after a failure.
Use this pack when the automation is built and your client is taking over. Prepare a closeout record, account and dependency register, test evidence and agreed support ownership, so the receiving operator can look up what to check, when to stop and whom to contact.
US buyers · One payment · Applicable tax and final terms shown at checkout.
Your client is taking over. Can the operator find the next step?
A walkthrough can show the workflow. The receiving operator also needs the delivered revision, account owners, acceptance status and recovery limits in writing. Use the closeout to record those details and the support terms you actually agreed before the project closes.
- A client closeout with the workflow revision, actual test evidence, open issues and client acceptance decision.
- An account and dependency register with named owners and vault references, without storing credentials.
- Acceptance and recovery records showing the input, expected result, actual observation and reviewer.
- Agreed support ownership, coverage, escalation and the changes the operator may make.
Use the free example to inspect your handover.
The free two-page fictional handover shows one acceptance test, a recovery exercise, a safe-change boundary and support roles. Use it to check whether your own handover tells the next operator what to inspect, when to stop and who owns the next action. Its observations are simulated teaching material.
The paid pack adds editable client records, a complete fictional lead-routing handover and a client acceptance checklist. One agency license covers five distinct client projects.
In the fictional recovery exercise, a CRM failure happens before any write. The operator pauses the trigger, checks the CRM and event ledger, then replays the same lead ID once after connectivity returns. If a prior write or delivery state is unknown, replay stops and the issue is escalated.
Simulated teaching case, not proof from a running n8n instance or instructions to replay your production workflow.
Prepare the records your client will receive.
Complete the closeout with the actual workflow facts and support terms. Use the account/dependency workbook for owners and references, and the test workbook for plans, observations and evidence. The client checklist gives the receiving operator a small exercise before the acceptance decision.
Tested in WPS Writer and Spreadsheets 11.8.2.8498 on Windows. Microsoft Word and Excel themselves have not been tested. Files are provided as DOCX, XLSX and PDF.
- PDFSTART-HERE.pdf
- XLSXacceptance-and-recovery-tests.xlsx
- XLSXaccounts-and-dependencies.xlsx
- PDFclient-acceptance-checklist.pdf
- DOCXclient-closeout.docx
- PDFfictional-lead-routing-example.pdf
- TXTLICENSE.txt
- TXTVERSION.txt
A good fit if…
- You have built and understand the automation, and a client handover is due.
- You can name the receiving operator and run real acceptance and recovery exercises.
- You need editable closeout records for up to five distinct client projects.
Choose another route if…
- You need someone to install, debug or maintain the workflow.
- The automation is not ready for acceptance testing.
- You need certification, professional assurance or Shirasu to verify client evidence.
Complete the handover with the person taking over.
Your agency runs the real tests and supplies the evidence, recovery procedure and support terms. Use the files to record the work, then have the client separately record Accepted, Conditional or Not accepted.
- Read the fictional lead-routing handover and gather the deployed revision, account owners and support terms.
- Fill the closeout, account/dependency register and test plans with real project details.
- Run the acceptance and recovery exercises with approved synthetic inputs; record observations and evidence.
- Use the client checklist with the receiving operator, then record Accepted, Conditional or Not accepted.
Questions before you choose.
Does this include an n8n workflow or import file?
No. It supplies handover records and an n8n-oriented fictional example, with no running workflow, parser or connection to your tools. You can adapt the document structure for other automation tools.
Can I share the completed handover with my client?
Yes. Your agency may share completed client-specific outputs for each of the five licensed projects. The client may use those outputs to operate and manage its automation. Unfilled source templates and reusable blank libraries may not be redistributed or resold.
What counts as one client project?
One separately scoped client automation delivery. Revisions within that scope use the same project allocation. Further distinct projects require another pack license.
Does a complete workbook record mean the client has accepted?
No. Record-completeness checks do not validate evidence or accept the project. The reviewer checks actual results and the client separately records its acceptance decision.
How much can one workbook hold?
Each workbook copy has 12 record rows. For more records in the same project, use another whole workbook copy and list both in the closeout. Do not duplicate individual sheets without fixing cross-sheet references.
Does it include support for the client workflow?
No. Your agency and client name the workflow support owner and agree the actual coverage and escalation terms. Lattice provides AI product-use support for the pack; it does not operate, repair or maintain the workflow.
What does the license include?
One purchasing agency may use the files for five distinct client projects. Completed client-specific outputs may be shared with that client. Revisions inside the same separately scoped delivery do not consume another project. Unfilled source templates may not be redistributed or resold. Your purchase includes access to updates published for this product in the twelve months after purchase. No update schedule, new feature or future compatibility is promised. You may continue using the files received under the product license after that period. Read the full product license.
Which applications were tested?
Tested in WPS Writer and Spreadsheets 11.8.2.8498 on Windows. Microsoft Word and Excel themselves have not been tested. Files are provided as DOCX, XLSX and PDF.
What are the refund terms?
14-day full refund, including after download. Email lattice@shirasusystems.com with your order reference within 14 calendar days of successful payment. No reason required.
Two practical field notes.
Automation Project Closeout Pack
Automation agencies handing a built workflow to a client operator. The build is ready for acceptance or project closeout, and day-to-day operation is about to change hands.
$199 USD
One agency · Five client projects
US buyers · One payment · Applicable tax and final terms shown at checkout.
Still agreeing the scope or an added request? See the separate Automation Scope and Change Pack for scope, acceptance and change records. Each pack works independently.