Start the current run
Set the trigger, checklist, source records, owners, deadlines, and expected result.
Lodge for operations teams
If the runbook only works in one person’s head, it is not a runbook.
Keep the current runbook, owners, source records, exceptions, approvals, outcome, and next-cycle improvement together. Operational systems still execute the transactions.
The tools already in the job 
Asana
monday.com
Microsoft Planner
Asana monday.com Microsoft PlannerPut every exception in front of an owner
Missing information and blocked steps return to the person who can resolve them.
Fix the runbook while the lesson is fresh
Keep the outcome, failure points, and next-cycle change with the completed work.
One Lodge project
The systems execute the transaction. Lodge runs the job around it.
The runbook, files, owners, exceptions, approvals, and post-run improvement stay connected without replacing systems that move money, change access, or track inventory.
- Run Vendor renewal · Q3
Current checklist, records, owners, and deadlines
- Exception Insurance document missing
Blocker, impact, and the person resolving it
- Improve Renewal runbook v4
Outcome, failure point, and next-cycle change
What it looks like
Take a vendor renewal from first notice to recorded outcome.
Operations, finance, legal, security, and the vendor owner follow one current run instead of five private checklists.
- 01 · Start
Open this cycle’s runbook
Add the vendor, records, owners, deadlines, and checks required for this renewal.
- 02 · Resolve
Return every exception
People and AI prepare routine work while each unresolved item goes to a named owner.
- 03 · Close
Record the outcome
Operations confirms completion and updates the runbook with what this cycle taught.
Where people decide
AI can run the routine. Operations owns the exception.
Lodge does not move money, change access, renew a vendor, or alter an operational system. The responsible person resolves and approves those actions.