Closing in five days: an orchestration playbook

A five-day close is not the product of working faster. It is the product of removing the things that make the close slow: serial dependencies, manual handoffs, and work that piles up waiting for month-end. Here is the playbook, in the order it matters.

Move reconciliation out of the close

If you reconcile continuously, the close inherits finished reconciliations instead of starting them. This single change does more for cycle time than any other, because reconciliation is usually the longest pole in the tent.

Treat the checklist as orchestrated software

A close is a dependency graph, not a list. Task B cannot start until Task A finishes, and someone has to know the moment it does. An orchestration layer tracks status in real time, chases owners automatically, and shows the critical path — so no task sits idle because nobody knew it was unblocked.

• Recurring journals — accruals, prepaids, allocations — are drafted automatically for one-click approval.
• Owners are chased by the system, not by the controller’s calendar reminders.
• Flux commentary is drafted against budget and prior period before the review meeting, not during it.

Make review the only human bottleneck

When preparation is automated, the only thing left for people to do is review and approve. That is the right place for human time. The controller spends the close looking at variances and judgment calls, not assembling schedules.

The result

Continuous reconciliation, orchestrated tasks, drafted journals, and pre-written flux turn a two-week scramble into a five-day confirmation. The team works normal hours, the numbers are trustworthy, and audit evidence is a by-product rather than a follow-up project.