Workflows · GL and close · Tier 2 · the long tail
The close calendar as an eight a.m. status note
Tasks by month and quarter, owner, force-check flag, timing, responsibility, kept by hand. Vendors sell task managers; nobody sells the agent that reads yours and writes the morning note.
By hand: Daily during close, two to four hours a month · Every finance team.
The card, as it runs by hand
- Input
- The close task schedule (task, action, type, force-check, time, responsibility, timing) and the day's completion status.
- What I do to it
- Each morning during close: read what is done, what is late, what is blocked; reschedule on slips; nudge owners.
- Output
- A short status note to the close lead and each owner's items for the day.
- Who checks
- The close lead reads it daily; owners tick off their tasks.
- How often
- Daily during close.
- How long
- Two to four hours a month by hand.
- How long now
- Measured in the course after the first governed run, per card. Not estimated here.
As a governed workflow
- Stays in code
- Dates, dependencies, and what counts as late.
- The AI does
- The daily digest in plain language, the reschedule suggestions, and the nudges.
- A person still
- The close lead decides what moves. The agent only proposes.
- The log
- Each day's digest and what changed.
AI does the preparation. A named person approves it. Nothing posts to the books without that approval, and every run is recorded.
Where it goes wrong
Letting the agent move dates. It proposes; the close lead disposes.
Why it lands in a room
The control model already exists in the schedule. The digest is the missing piece.