AutoArchWorkflowsWF-01

Sanction + statutory deadline tracking

The sanction file moved and nobody in the office knew.

HUMAN STEPS
1
AUTOMATED
5
RECLAIMED
~9 hrs/month

WF-01 — Sanction + statutory deadline tracking. 1 human step, 5 automated steps, about 9 hours a month reclaimed.

  1. Step 1. File accepted for scrutiny (OBPAS). Watches every live sanction file
  2. Step 2. Arm the approval clock. Statutory timeline recorded against the project
  3. Step 3. Poll for departmental objections. Daily, logged as raised
  4. Step 4. Track NOCs and clearances. Fire, AAI height, environment, lift — each its own item
  5. Step 5. Approval window closing. Escalates before the date, not after it. This is the point of the whole workflow.
  6. Step 6. Resubmit, revise or follow up. A judgement call, surfaced early
  7. Step 7. Sanction register updated. Every live file, one view

Risk points in this workflow:

  • Approval window closing. Escalates before the date, not after it. This is the point of the whole workflow.

Steps you still do:

  • Resubmit, revise or follow up

What it actually does

  1. 01File accepted for scrutinyWatches every live sanction file
  2. 02Arm the approval clockStatutory timeline recorded against the project
  3. 03Poll for departmental objectionsDaily, logged as raised
  4. 04Track NOCs and clearancesFire, AAI height, environment, lift — each its own item
  5. 05Approval window closingEscalates before the date, not after it. This is the point of the whole workflow.
  6. 06Resubmit, revise or follow upA judgement call, surfaced early
  7. 07Sanction register updatedEvery live file, one view

The risk this covers

Approval window closing

Escalates before the date, not after it. This is the point of the whole workflow.

What you still do

  • Resubmit, revise or follow upA judgement call, surfaced early

Everything else runs without you.

Part of

All fifteen workflows →
WORKFLOW
WF-01
BAND
CORE
REV
03