Maker-checker governance, end to end

Submit, review and approve with verifiable dual control.

A focused workflow platform where applicants submit requests and reviewers move them through a strict state machine — every approval requiring two different people, every action sealed in a tamper-evident audit trail.

How the workflow works

Each application flows through six stages. Status only ever changes through the authoritative state machine, so the pipeline can never be skipped or forged.

Draft

An applicant drafts and refines a request.
Submitted

Handed in and waiting for a reviewer to pick it up.
Under Review

A reviewer is actively assessing the request.
Pending Approval

A maker has proposed approval; awaiting a checker.
Approved

Confirmed by a second reviewer — final and positive.
Rejected

Declined with a recorded reason — final.

Maker-checker dual control

High-value approvals demand two distinct reviewers. One reviewer (the maker) proposes approval; a different reviewer (the checker) must confirm it. Segregation of duties is enforced in the database under a row lock, so a reviewer can never confirm their own proposal — even under a concurrent race.

Built for trust and speed

Tamper-evident audit trail

Every transition is hash-chained, so any altered, inserted or deleted record is detectable end to end.

Realtime dashboards

Queues, stage funnels and activity feeds update live over PubSub the instant anyone acts — no refresh.

Scheduling & calendar

Reviewers schedule future reviews and see what's due across a full calendar and agenda.

Bulk operations

Act on many applications at once, with every per-item guard and segregation-of-duties rule still enforced.

Role-based access

Applicants, reviewers and admins each get a tailored, server-gated experience and dashboard.

Maker / checker insight

Per-reviewer profiles surface proposed, confirmed, rejected and reviews-started at a glance.