Requirements
Define the task, use case, risk, labels or scoring dimensions, and acceptance criteria.
Quality
Marka’s quality process starts before the first item is reviewed. The instructions, reviewer requirements, checks, and handling of uncertainty are part of the project scope.
Scope a pilotDefine the task, use case, risk, labels or scoring dimensions, and acceptance criteria.
Write examples, edge cases, evidence rules, and a clear path for uncertainty.
Test reviewers on representative cases before production work begins.
Use project-specific checks, hidden quality items, and confidence signals.
Route uncertain or conflicting decisions to a more qualified review step.
Check output format, quality findings, corrections, and documented limitations.
Projects can require language proficiency, domain experience, prior role experience, or formal credentials. The actual requirement is agreed with the customer.
Reviewers work through representative examples and receive feedback before production access is granted.
Agreement, correction rate, hidden quality cases, confidence, and pattern-specific performance can be monitored during delivery.
Reviewers should see only the data needed for their assigned task and only for the required period.
The final schema is project-specific. These fields show the type of provenance Marka is designed to preserve.
| Input and output | The original item, model response, trace, or source record. |
| Instruction version | The exact rubric or annotation guidance used for the decision. |
| Reviewer decision | Label, score, correction, confidence, and written explanation. |
| Supporting evidence | Policy passage, tool result, source text, or expected outcome. |
| Quality history | Second review, correction, disagreement, and final approval status. |
| Dataset version | The delivery batch and change history in which the item belongs. |
Send a sample and the standard you currently use. Marka will identify what needs to be clarified before a pilot begins.
Start a pilot