Key takeaways
- A playbook coordinates finite change. A recurring workflow must handle each new case after the workstream has closed.
- The failure usually sits at the handoff: task marked complete, but trigger, evidence, authority, exception ownership or verification is missing.
- Do not discard project tools. Add a process acceptance record beneath material tasks and test it with live normal and imperfect cases.
- If every acquisition requires hidden local workarounds, the reusable artifact is too abstract. Preserve explicit parameters and branches.
The project clock ends; the operating clock starts again tomorrow
| Layer | Unit of work | Useful status | Finish |
|---|---|---|---|
| Integration playbook | Milestone, decision or change task | Owner, due date, dependency, risk | Deliverable accepted |
| Recurring workflow | One customer, report, exception or request | State, evidence, decision, effect | Business result verified |
| Process handoff | Transfer of the recurring job | Procedure, authority, test cases, successor | Successor runs and repairs it |
DealRoom and Ansarada correctly present workstreams and checklists as ways to organize integration. The missing layer is not an indictment of those tools. It appears when a team interprets “transfer dispatch complete” as proof that tomorrow's dispatch case can run without the seller.
Five gaps hide behind a green task
| Gap | Symptom | Repair |
|---|---|---|
| Event | Nobody knows a new case has started | Observable trigger and unique business key |
| Evidence | Successor searches messages or asks seller | Approved source map and freshness rule |
| Decision | Procedure says “use judgment” | Criteria, examples, refusal and authority |
| Exception | Normal work passes; backlog grows invisibly | Classes, clocks, owners and escalation |
| Verification | Task ran but final state is unknown | Destination check and reconciliation |
Add a process acceptance record beneath material workstream tasks
- 01Name the recurring jobTriggerUse a verb and object with a real event, such as “reconcile Friday branch pack.”
- 02Link the current procedure and authorityHuman approvalName the effective version, process owner and decisions the successor may make.
- 03Attach test casesAI judgmentInclude one normal case, two contrasting exceptions and one recovery case with expected states.
- 04Run with the successor in controlHuman approvalLog every intervention and question. A corrected result can still be a failed transfer.
- 05Close on reconciled evidenceCodeVerify the final record, exception destination and procedure maintenance owner.
The workstream closes before the first imperfect case appears
Northline marks “transfer weekly reporting” complete after access, training and a successful Friday pack. The next week, one branch submits a late correction after the cut-off. The successor cannot tell whether to reopen the pack or carry the correction.
The project task had valid completion evidence, but the recurring process lacked an exception rule. The team reopens only the process acceptance record, adds cut-off authority and a correction ledger, then tests both routes. The integration tracker remains the coordination system.
Reuse the skeleton and preserve the variation
- Common: event envelope, evidence contract, state model, exception record and verification.
- Parameterized: thresholds, clocks, calendars, source mapping and approval role.
- Local branch: customer promise, physical condition, jurisdiction-specific duty or relationship judgment.
- Never hidden: an unknown owner, unsupported connector, private credential or consequential decision without authority.
The workflow mapper is the fastest way to expose whether a green task has an executable path beneath it.
Limitations and when not to use this
- A playbook remains useful for integration governance and project coordination. This guide does not claim project software is unnecessary.
- A process acceptance test supports one bounded handoff. It does not certify the company, integration or workflow as complete.
- Consequential financial, employment, legal, safety or security work still needs qualified review and accountable human decisions.
- Northline is simulated. No product, connector, transaction or customer outcome is represented.
Sources
- M&A Integration Playbook — DealRoom Accessed 9 August 2026
- Post-Acquisition Integration Checklist — Ansarada Accessed 9 August 2026
- Eliminating Toil — Google, The Site Reliability Workbook Accessed 9 August 2026
Map the recurring work beneath one task
Turn the project handoff into an explicit process acceptance record.
Map the recurring work beneath one taskUli Prantz
Builds and operates all-agents
Uli Prantz builds all-agents, the process-automation platform this site documents. He writes about the operational side of automating recurring business work: where deterministic code beats model judgment, where it does not, and where a human still has to approve.