How It Works
Each stage below shows who acts, why it matters to you, and what stays on record.
-
Stage 1 of 6
Controlled intake
Your data is stored as an immutable ORIGINAL dataset with a checksummed copy of the file you sent.
- Who acts
- Our system administrator, the only role that can upload client files.
- Why it matters to you
- Every later step works from this untouched copy, so the delivered file can always be compared with what you sent.
- Kept on record
- The ORIGINAL dataset and the checksum of the file you sent.
-
Stage 2 of 6
Deterministic detection
Configured detectors raise findings against defined reason codes. No model decides what is wrong.
- Who acts
- Configured detectors, set up for your project’s fields.
- Why it matters to you
- A field is sent for review only for a stated reason, never on a hunch.
- Kept on record
- Each finding with its detector and reason code.
-
Stage 3 of 6
Qualified verification
Tasks reach only workers qualified for that task category and authorised on that project.
- Who acts
- One reviewer qualified for the task category and authorised on your project. They see the product identifier, the field, its current value, your field definition and the evidence you allow.
- Why it matters to you
- The reviewer answers Supported, Mismatch, Cannot determine or Request reviewer help, and must give a reason for every answer except Supported. Cannot determine is paid, so nobody is pushed to guess.
- Kept on record
- The task, who it was assigned to, and the decision they submitted.
-
Stage 4 of 6
Independent reverification
Where policy requires it, a different reviewer sees the same case without the first answer.
- Who acts
- A second qualified reviewer, never the first, where your project’s policy requires it.
- Why it matters to you
- The second reviewer never sees the first answer, so agreement means two independent judgements.
- Kept on record
- The second reviewer's answer, kept apart from the first.
-
Stage 5 of 6
QA adjudication
Disagreement and escalation go to an independent reviewer who is neither of the first two.
- Who acts
- A QA reviewer who is neither of the first two.
- Why it matters to you
- QA must record a rationale. It keeps the current value, accepts a correction, confirms a mismatch, or records that the evidence cannot resolve the case. It never averages two answers.
- Kept on record
- The QA decision and the rationale behind it.
-
Stage 6 of 6
Verified delivery
A FINAL snapshot is generated only when the work behind it has actually concluded, then exported and delivered.
- Who acts
- Our system administrator generates the package, and only they can download it. Each download is logged.
- Why it matters to you
- You receive the file and, for a check-only project, a check report. The export package is recorded with a checksum. In your client area you can acknowledge, accept or request a revision, and a revision arrives as a new version.
- Kept on record
- The FINAL snapshot, the export package and its checksum.