Close timeline
Eight working days, one deadline
Each mark is a task due that day, coloured by its status at the 09:00 stand-up. Tap one to see its chain.
Computed, not written
Today's three actions
Rule: the blocked root cause first, then late tasks, then tasks due today. Ties go to the task with more work waiting downstream.
Task board
24 tasks, one owner and one due day each
The blue bar marks the critical path, from the ERP load to the management pack. Tap any task to see what it waits on and what waits on it.
Critical path
Reconciliations
Seven accounts
Open data issues
Approvals queue
Waiting for a named role
Manual journals above EUR 100,000 need the Controller. Drafts go nowhere until the person named approves them.
Replicate it
Take the board to your own close
One copy gives you the task list template, the rules the board runs on and a controlled prompt for the first draft. Plain text, no tool required.
The lesson
Chase the chain, not the list
- The close is a dependency graph, not a checklist. At WD2 a checklist shows one late item. The graph shows eight more tasks waiting on it, the management pack included.
- An AI can only chase what has an owner and a date. Every task here has one owner role and one due day. Without them there is nothing to flag and nobody to ask.
- Sign-offs stay with people. The draft, the chaser and the flag are starting points. Journals, reconciliations, commentary and the pack are approved by a named role.
Where to start
List your close tasks with one owner, one due day and one upstream dependency each. Then trace the chain from your first data load to the pack. That chain is what you chase first.
Free series
AI in FP&A, the controlled way
Short, practical tools that show finance teams where AI really helps, without losing lineage, approvals or the controller's trust. Follow me on LinkedIn for the next one.