Quality method
How Morvio measures quality, and what we report.
Version 1.0 · 11 November 2026
Production workflow: what happens to each batch
Each settled question becomes a guideline update for the whole team.
Diagram: ingest, guideline, annotate, review and adjudicate, deliver, with settled questions looping back into the guideline.
guideline update
What happens at each stage
- Ingest
- Data arrives in your tool. We check it against the specification and log what arrived.
- Guideline
- The agreed guideline version is fixed for the batch.
- Annotate
- Annotators recruited for the language and domain work in your tool or a widely used open-source one.
- Review and adjudicate
- QA reviewers check items against the guideline. The team leader settles disagreements and logs each decision.
- Deliver
- Data, delivery notes and the QA report.
Review layers
Each project has its own team: a team leader, annotators recruited for the task, and dedicated QA reviewers. Each language on a project has a named lead reviewer.
How we workSelf-check
- Who
- Annotator
- Checks
- Their own items against the guideline
Review
- Who
- Dedicated QA reviewer
- Checks
- Items against the guideline
Adjudication
- Who
- Team leader
- Checks
- Disagreements
Final audit
- Who
- Project lead
- Checks
- Sample before delivery
Metrics
Targets are agreed with you before the pilot and reported in every QA report.
Transcription
- Metric
- Word error rate (WER)
- How it is calculated
- (substitutions + deletions + insertions) ÷ words in the reviewed reference
Boxes, masks, cuboids
- Metric
- IoU
- How it is calculated
- Overlap ÷ union, against the reviewed shape
All tasks
- Metric
- Gold accuracy
- How it is calculated
- Share of gold items (items with a known correct answer) labelled correctly
The QA report
Every delivery includes a QA report.
What our QA report contains:
- sample size and how it was drawn
- results against the agreed targets, metric by metric
- error types, with examples
- adjudication notes: reviewer role, qualification and guideline version
The report also gives the batch ID and guideline version, the volume delivered, and the guideline questions and answers.
A sample batch gives you a real report on your own data.
Request a sample batchMethod changes
v1.0 · 11 November 2026 · First published version.
Engagement steps: how we work with you
Five steps, the same for every service. You see results before you commit to volume.
- 1
Scope
A call or a written brief. We agree the task, volume, languages, deadline and how quality is measured. You do not need to send any data.
- 2
Guideline and calibration batch
We write or adapt the guideline with you, then run a short calibration batch to settle edge cases.
- 3
Pilot
A fixed-price batch of your real task, with acceptance criteria agreed in writing.
- 4
Scale up with QA
We grow the team to your volume and deadline. QA reviewers check every batch, and disagreements are settled before delivery.
- 5
Delivery notes and QA report
Each delivery lists guideline changes and reports results against the agreed targets.
Discuss your project
Two ways to start. Both reach Khaled Zerouki.
Book a call. Pick a time in your own time zone.
Book a callRequest a sample batch. A batch of your own data, returned with a QA report, on terms agreed before work starts.
Request a sample batchWant a price first?
Get an estimateWe reply within 1 business day.¹ NDA on request. We can plan and price your project without seeing your data.
¹ Business days are Monday to Friday, UK time, excluding public holidays in England and Wales.