Objective
Create a controller playbook that turns close from heroic effort into a repeatable operating rhythm.
Case study 17
Portfolio knowledge project
Month-End Controller Playbook
A dependency-based month-end playbook for controllers — task owners, gates, evidence, escalation paths, and a reporting pack that makes close status visible.
Knowledge / portfolio case study only. Not employment history, not a named client engagement, and not a certification claim.
Context
Close delays usually come from unclear ownership and hidden dependencies, not lack of effort.
Scope
Close calendar, RACI, evidence checklist, escalation rules, and status dashboard outline.
Approach
Map dependencies → assign owners → define done criteria → set escalations → run a mock close → refine timings.
- 01Dependency mapWhat blocks what.
- 02RACIOwner and backup per task.
- 03Evidence standardWhat 'done' means.
- 04Mock closeFind the real bottlenecks.
- 05Steady-state rhythmCadence + continuous improvement.
01Dependency map
02RACI
03Evidence standard
04Mock close
Month-End Controller Playbook
Key design decisions
- Visible status beats private spreadsheets
- One close board.
- Backups for every critical owner
- Protect vacation risk.
- Timebox investigations
- Escalate early.
Walkthrough
Start close day -2 checklist → clear AP/AR gates → run depreciation & reval → lock periods → publish TB pack → hold close readout.
Controls
No soft close without evidence; blockers logged same day; post-close review within five business days.
Oracle modules in focus
GL
AP
AR
Assets
Cash
OTBI
Deliverables
Close calendar
RACI
evidence checklist
status board wireframe
mock-close findings log.
Outcomes
A recruiter-readable close leadership artifact grounded in process design.