Missing Piece
The file becomes a jigsaw: one glowing gap, one photo, resubmitted without restarting.
The job
End document ping-pong: rank every document requirement by the holds, rejections and 'asked me twice' contacts it causes, priced in citizen-days; give each requirement an owner and a fix-by date; let applicants supply the missing piece in chat and resubmit in place; and retire requirements that never change a decision.
The moment
An applicant rejected twice for the same stamp sees the one glowing piece, sends one photo and reads Complete. Resubmitted. No need to start again. Back in OnClarity the requirement's card flips from red to Improving, and a new headstone appears in the Graveyard: Here lies the second copy of the lease. Cost citizens 4,120 days. Changed 0 decisions.
What it does
- Assign requirement owner and fix-by date
- Edit applicant-facing piece copy
- Request the missing piece and resubmit (applicant side)
- Try a stuck resubmission again
- Propose a requirement for cancellation and bury it
- Send the zero-bureaucracy review pack
What you see
Two faces: an applicant-facing jigsaw of their own file with one glowing gap (AI agent chat widget, WhatsApp) and an internal requirement kill-list that ends in a Requirements Graveyard of headstones
What it moves
Resubmissions accepted without restart per month and citizen-days returned; 'asked for the same document twice' contacts per 1,000 applications
Built for
- Citizens & customers
- Operations
