Time every step of the current close
Backlog·Research
Ready — every dependency closed
Unlocks 1 task
Software DevelopmentSoftware Development template
Month-end close automation
DraftNormalComposed but not released to the departments.
0progress
progress: 0 out of 100Take the month-end close from five days to one, starting with the agent spend attribution that currently blocks it.
Next
Not released. Publish it to route work to the first department.
Discovery
Current stage
5
Stages
6
Tasks
0 closed
3
Open gates
5
Ready now
1 waiting
6 weeks
Planned
Ready to start5
1 waiting- Time every step of the current closeResearch
- Identify the agent spend attribution gapResearch
- Size the automatable shareResearch
- Define the attribution data contractEngineering
- Estimate and sequence the buildEngineering
Held behind a dependency
- Draft the technical spec×3
Assigned teams3
Departments, in routing order
Accountable
Executive Dai OkonjoManagers Anselm Reyes, Aris Vandel, Edda Lindqvist
AI agents on this workflow
No named agents yet. A freshly built workflow assigns work to departments — naming agents is a scheduling decision the orchestrator makes when it staffs the stage.
Stage timeline
- STAGE 1
Discovery
Pending40h plannedEstablish which close steps actually cost the five days.
ResearchManager Anselm Reyes0 of 3 tasks0% - STAGE 2
Specification
Pending56h plannedTurn the finding into something engineering can build.
EngineeringManager Aris Vandel0 of 3 tasks0%Manager approvalPending30 Jul 2026Clear Specification before work routes onward.
Held by Aris Vandel
- STAGE 4
Quality assurance
Pending64h plannedProve the numbers match a manual close.
EngineeringManager Aris VandelQA approvalPending30 Jul 2026Confirm the automated close matches a manual one to the penny.
Held by Probe
- STAGE 5
Release
Pending32h plannedRun it alongside a manual close before trusting it.
FinanceManager Edda LindqvistExecutive approvalPending30 Jul 2026Authorise running the automated close as the source of record.
Held by Dai Okonjo
Dependencies
Discovery
3Identify the agent spend attribution gap
Backlog·Research
Ready — every dependency closed
Unlocks 1 task
Size the automatable share
Backlog·Research
Ready — every dependency closed
Unlocks 1 task
Specification
3joins from Discovery
Draft the technical spec
Backlog·Engineering
Waiting on 3: Time every step of the current close; Identify the agent spend attribution gap; Size the automatable share
Define the attribution data contract
Backlog·Engineering
Ready — every dependency closed
Estimate and sequence the build
Backlog·Engineering
Ready — every dependency closed
Build
0joins from Specification
No tasks
Quality assurance
0joins from Build
No tasks
Release
0joins from Quality assurance
No tasks
One column per stage, in routing order. Tasks inside a stage run in parallel; the first task of each stage joins from every task of the one before it, which is the hand-off between departments made explicit.
Board6
Backlog
6Time every step of the current close
research
Research6 weeks
Identify the agent spend attribution gap
research
Research6 weeks
Size the automatable share
research
Research6 weeks
Draft the technical spec
engineeringwaiting ×3
Engineering6 weeks
Define the attribution data contract
engineering
Engineering6 weeks
Estimate and sequence the build
engineering
Engineering6 weeks
To do
0Empty
In progress
0Empty
Review
0Empty
Blocked
0Empty
Completed
0Empty
Approval gates3
3 openManager approvalPendingNot reached30 Jul 2026
Month-end close automationClear Specification before work routes onward.
QA approvalPendingNot reached30 Jul 2026
Month-end close automationConfirm the automated close matches a manual one to the penny.
Executive approvalPendingNot reached30 Jul 2026
Month-end close automationAuthorise running the automated close as the source of record.
Deciding a gate writes the decision and nothing else. The status change, the release of downstream stages and the “ready to close” state are all derived from it on the next render — which is why an approval here is one field rather than a transaction.
Messages0
No conversation yet. Messages appear here when a stage raises something in a department channel.
Related projects0
Not linked to a department project. Projects appear here when a stage’s work is tracked on a department board as well.
Performance
392h planned · 96h remaining0%
Progress
0 of 6 tasks
0/5
Stages closed
0/3
Gates cleared
0
Blocked tasks
3
Departments
routed through
0
Agents
named on the work
96h
Remaining
from the breakdown
-296h
Estimate variance
296h under
Task completion0%
Task-weighted, not stage-weighted. A two-hour approval stage and a two-hundred-hour build stage are not half the work each, and treating them as such is the usual way a project dashboard reports 50% before anything has been built.
Completion rule · All stages complete
Closed when one full close runs automated and reconciles against a manual run.
Every stage reaches complete or skipped.
Automation7
1 would fire · 0 willNext routing decisionHeld
3 open tasks in Discovery.
Computed by engine.peekAdvance(), which returns the next stage rather than moving to it. The Task Orchestrator owns the write; keeping this side pure is what lets a card show “next: Engineering” with no risk that rendering a page advances a workflow.
- Advance stage on completion
- WHEN
- Every task in the active stage reaches a terminal column and the stage carries no pending gate.
- THEN
- Mark the stage complete and route work to the next stage in the chain.
- NOW
- 3 tasks still open in Discovery.
- Notify approver on gate open
- WHEN
- A stage with a gate becomes active and the gate is still pending.
- THEN
- Raise a workflow notification addressed to the named approver in the Communication Hub.
- NOW
- No gate is currently open.
- Escalate a stale gate
- WHEN
- A gate has been pending longer than its stage's estimate.
- THEN
- Escalate one authority level up and notify the accountable executive.
- NOW
- Needs a real clock. Placeholder timestamps are relative strings.
- Release dependent tasksWould fire
- WHEN
- A task reaches a terminal column and other tasks depend on it.
- THEN
- Move every newly-ready dependent from backlog into to-do.
- NOW
- 5 backlog tasks have all dependencies closed.
- Write outcome to memory
- WHEN
- The completion rule is satisfied.
- THEN
- Write a project-scope memory record summarising the outcome and link it back.
- NOW
- Completion rule is not satisfied yet.
- Auto-approve low-risk gatesHeld for a human
- WHEN
- A QA or manager gate carries no rejection history and sits under the risk threshold.
- THEN
- Nothing. Recorded so the policy is visible and reviewable — a gate an agent can clear is not a gate.
- NOW
- Held for a human by design.
- Stand down a stalled workflowHeld for a human
- WHEN
- No activity for longer than the estimated duration and no open gate explains it.
- THEN
- Nothing automatic. Surfaces the workflow for a human decision.
- NOW
- Held for a human by design.
Nothing here executes. There is no scheduler, no queue and no writer — these are evaluations of the current state, refreshed on every render. Adding a trigger is one row in AUTOMATION_TRIGGERS; it appears on every workflow immediately so a rule can be checked against real data before anything is built to act on it.
Activity log1
- 1d ago
CEO Opened from the Software Development template — 5 stages, 3 approval gates. Not yet released.