The problem
Every certificate passed through several people, each keeping their own record. Nothing was wrong on paper, but answering a simple question — who checked this, and against what — meant reconstructing a story from three inboxes.
The team was not asking for automation. They were asking to answer that question in front of an auditor without preparing for a week.
What we built
One flow that follows a certificate from registration to issuance and transfer, with each step recorded as it happens rather than reconstructed afterwards.
- 01
Registration with the checks that used to live in someone's head written down as rules.
- 02
Verification queues, so work is assigned rather than negotiated by email.
- 03
Issuance and transfer with the record of who approved what, captured at the moment of approval.
- 04
A view built for the auditor, not adapted for them afterwards.
How it fits together
Deployed in the client's own environment, as their data policy required.
What changed
Issuance stopped being a project each time. The audit question is now answered from the screen while the auditor is still in the room, and the people who used to chase approvals spend that time on the cases that need judgement.
<< published figures to confirm with client >>