The problem
A month-end close depends on a long sequence of tasks that have to happen in a particular order, and much of the knowledge about how each one works tends to live with whoever normally performs it. When that person is unavailable, the close either slows down or the task gets done differently than it was last month. A static checklist records what must happen but not how, so it does not solve the underlying problem.
The approach
I built the close as an interactive dashboard rather than a document. Every task on the checklist is a live item with an owner, a due point in the close calendar, a status, and a direct link to the written SOP for that specific task. Completing an item requires the procedure to be in front of the person doing it. Because the checklist and the procedures are connected rather than stored separately, the documentation stays current: when a procedure changes, it changes in the place people actually open during close.
Tools
What it enables
- Any team member can complete a close task they have not performed before by following the linked procedure.
- Close status is visible in one place instead of being reconstructed from conversations.
- Cross training and coverage during absences no longer depend on one person being reachable.
- Procedures stay current because they are attached to the workflow rather than filed away from it.
My role
I designed the checklist structure and the task to SOP linkage, wrote the procedures, and built the dashboard.