Statutory deadline tracking
A determination date passed and nobody noticed.
- HUMAN STEPS
- 1
- AUTOMATED
- 5
- RECLAIMED
- ~9 hrs/month
WF-01 — Statutory deadline tracking. 1 human step, 5 automated steps, about 9 hours a month reclaimed.
- Step 1. Application validated (PLANNING PORTAL). Watches every live application
- Step 2. Arm the determination clock. Target date recorded against the project
- Step 3. Poll for consultee comments. Daily, logged as published
- Step 4. Track conditions for discharge. Each condition its own item
- Step 5. Determination window closing. Escalates before the date, not after it. This is the point of the whole workflow.
- Step 6. Agree extension or push. A judgement call, surfaced early
- Step 7. Application register updated. Every live application, one view
Risk points in this workflow:
- Determination window closing. Escalates before the date, not after it. This is the point of the whole workflow.
Steps you still do:
- Agree extension or push
What it actually does
- 01Application validatedWatches every live application
- 02Arm the determination clockTarget date recorded against the project
- 03Poll for consultee commentsDaily, logged as published
- 04Track conditions for dischargeEach condition its own item
- 05Determination window closingEscalates before the date, not after it. This is the point of the whole workflow.
- 06Agree extension or pushA judgement call, surfaced early
- 07Application register updatedEvery live application, one view
The risk this covers
Determination window closing
Escalates before the date, not after it. This is the point of the whole workflow.
What you still do
- Agree extension or pushA judgement call, surfaced early
Everything else runs without you.
- WORKFLOW
- WF-01
- BAND
- CORE
- REV
- 03