Operations requires verified drivers, but the product has only a boolean flag and no traceable submission, review, rejection, or audit workflow.
Source alignment
Every quote below is an exact substring of its linked fixture source and is checked against stable chunk offsets.
“Only drivers verified by operations may participate in the pilot, and finance must be able to reconcile every wallet credit, debit, and adjustment each week.”
MetroMove pilot management requirements
Open complete source“They could not see whether a document was received, under review, rejected, or approved, and they did not know who to contact when verification stalled.”
Driver discovery interview notes
Open complete source“Document submission, review states, reviewer assignment, rejection reasons, and verification audit history are not implemented.”
Current architecture and feature summary
Open complete sourceOperational / business
Operations cannot demonstrate a consistent approval process, and eligible drivers may remain blocked without a visible resolution path.
Technical
A single mutable flag cannot represent review state, evidence, reviewer accountability, or decision history.
Define verification states and ownership, then implement document metadata, reviewer assignment, decisions, reasons, and audit events.
Acceptance criteria
Linked deployment workstream
Align authentication cost, verification decisions, and driver-facing review status.