NOC + clearance tracking
Applied for, but has it actually come back? All of them?
- HUMAN STEPS
- 1
- AUTOMATED
- 4
- RECLAIMED
- ~3 hrs/month
WF-08 — NOC + clearance tracking. 1 human step, 4 automated steps, about 3 hours a month reclaimed.
- Step 1. Clearances identified for the project (PROJECT)
- Step 2. List every NOC the file needs
- Step 3. Track each application separately
- Step 4. Log issue dates and validity
- Step 5. NOC register (REGISTER)
Risk points in this workflow:
- NOC pending or lapsed. An expired fire NOC is not a held NOC, and the programme assumes it is. Sanction stops at the weakest one.
Steps you still do:
- Decide the next step
What it actually does
- 01Clearances identified for the project
- 02List every NOC the file needs
- 03Track each application separately
- 04Log issue dates and validity
- 05NOC register
The risk this covers
NOC pending or lapsed
An expired fire NOC is not a held NOC, and the programme assumes it is. Sanction stops at the weakest one.
What you still do
- Decide the next stepFollow up, or refile
Everything else runs without you.
- WORKFLOW
- WF-08
- BAND
- CORE
- REV
- 01