Delivery review summary01
Production review
Check completeness, classes and attributes against the guide. Record and address obvious issues first.
Record: self-review and open questions
DELIVERY & QUALITY
Delivery & Quality
Every data batch,backed by a clear record.
Connect guidelines, reviews, issues and revisions. Agree acceptance criteria first, then organize production into batches with a clear manifest, a defined quality scope and a path for unresolved issues.
Delivery review summary
QC-CAM-01
Image-annotation batch
- Guideline
- GUIDE-1.2
- Checked units
- 120 frames
Initial review passed114 / 12095.0%
Rework recheck passed6 / 6100.0%
Current sample passed120 / 120100.0%
QC-CAM-01 / 120 sampled frames / GUIDE-1.2
01 / DELIVERY WORKFLOW
Eight stages. One connected handover.
The same delivery workflow introduced on our homepage, with clear inputs, actions and records at each stage. Roles, cadence and review coverage are agreed at project kickoff.
- 01
Discovery
Understand objectives; Define data types.
Stage recordScope and deliverable list - 02
Assessment
Review data volume; Evaluate data quality.
Stage recordData assessment and risk record - 03
Guidelines
Define annotation rules; Break down tasks.
Stage recordGuideline and exception version - 04
Calibration
Run a pilot batch; Align interpretations.
Stage recordPilot and calibration record - 05
Qualification
Screen specialists; Train and assess.
Stage recordTraining and qualification record - 06
Production
Plan production; Assign and schedule.
Stage recordBatch plan and production record - 07
Quality control
Layered quality checks; Sample and full reviews.
Stage recordReview report and issue list - 08
Acceptance
Prepare deliverables; Check against criteria.
Stage recordAcceptance and version manifest
02 / QUALITY CONTROLS
Layered reviews. Shared criteria.
Separate review responsibilities while linking results to the same guideline and data version. Use automated checks and human judgment for the questions each can answer.
02
Team review
Cross-check ambiguous classes and boundary cases. Feed unclear definitions back into the guide.
Record: review notes and rule clarifications
03
Specialist QC
Review the agreed scope and dimensions. Record issue location, type, severity and affected units.
Record: issues and recheck results
04
Handover review
Check files, versions, formats, sample scope and open issues before a delivery decision.
Record: acceptance checklist and manifest
03 / REVIEW REPORT
Read the result. See the denominator.
Explore three fixed batches with separate initial, rework and current results. These rates describe the listed review units, not model accuracy or the status of unchecked data.
QUALITY REVIEWBatch review record
QC-CAM-01
Road-image annotation batch
- Review guideline
- GUIDE-1.2
- Checked units
- 120 image frames
- Review scope
- 120 frames sampled from a batch of 600. Initial and current results refer to the same checked sample.
- Sample composition
- Review composition: 40 frames each from urban, junction and tunnel scenes.
Initial pass rate
95.0%114 / 120
Initial passes / checked units
Rework recheck pass rate
100.0%6 / 6
Recheck passes / initial failures
Current sample pass rate
100.0%120 / 120
(Initial + recheck passes) / checked units
Review result counts
- Passed initially114
- Passed after rework6
- Still unresolved0
Each unit is grouped by one primary issue and counted once. Current sample pass rate = (initial passes + recheck passes) / checked units.
Sample recheck completeAll 120 checked units currently pass. The remaining 480 frames are outside this result. Delivery still requires agreed acceptance.
Issues and recheck records
Issue groups summarize scope and corrections. Detailed records link each unit to its location, guideline clause and revision.
| Primary issue | Affected units | Correction | Recheck result |
|---|---|---|---|
| Missing objects | 3 frames | Add objects and classes | 3 / 3 passed |
| Loose boundaries | 2 frames | Correct box boundaries | 2 / 2 passed |
| Occlusion inconsistency | 1 frame | Align the attribute to the guide | 1 / 1 passed |
From the issue to the revision
Keep a reference chain for every correction so a reviewer can return to the same data unit. List unresolved issues separately and agree whether to rework, exclude or defer them.
- 01
Locate
Unit ID + issue location
CAM-018 - 02
Record
Issue type + guideline clause
ISSUE-006 / §4.2 - 03
Correct
Change + data revision
r01 → r02 - 04
Recheck
Result + open issues
RECHECK-006
04 / ACCEPTANCE & HANDOVER
Prepare the evidence with the data.
A handover includes more than data files. Bring guidelines, versions, review scope and outstanding items into one manifest for verification, reuse and traceability.
Suggested acceptance checks
- 01
Scope and counts
Check batch IDs, file counts, valid units and exclusions.
- 02
Guidelines and versions
Align task rules, class lists, revisions and export versions.
- 03
Format and usability
Check directories, fields, references and sample readability.
- 04
Quality and issues
State the review scope, calculations, rechecks and open issues.
- 05
Receipt and acceptance
Record receipt, outstanding items and the agreed acceptance result.
PROJECT ARRANGEMENTS
Agree access and retention at kickoff.
These are proposed topics for project planning. The actual arrangements depend on the agreement and the operating environment.
Access scope
Define project roles, accessible data, allowed actions and authorization periods.
Data handling
Confirm provenance and permitted use; agree handling and masking of sensitive fields.
Retention and handover
Agree transfer, retention, receipt checks and recorded disposition at project close.
QUESTIONS
Delivery questions, answered
01How are quality criteria agreed?
Define review units, dimensions, sampling coverage, thresholds and acceptance at kickoff, then calibrate the rules in a pilot. Each report records results within its stated scope.
02Does a passing sample mean the entire batch passes?
No. A sample conclusion has a defined scope and method. The Camera batch covers only 120 reviewed frames; its rate does not establish an individual pass for every unchecked frame.
03What happens when a recheck still fails?
Keep the unresolved issue and its affected scope visible, then follow the agreed process. The LiDAR batch shows a delivery hold. A project may continue rework or agree an exclusion or phased delivery.
04Can you work with our guidelines and quality tools?
First assess whether rules, fields, review methods and export formats can be aligned, then confirm with a pilot. Tool access, permissions and the processing scope need project-specific agreement.
05What files are included in a handover?
Deliverables usually include data or labels, rule versions, batch manifests, quality reports and issue records. Agree formats, directories and acceptance materials before production.
START WITH THE ACCEPTANCE CRITERIA
Align on acceptance before production.
Start with the data type, expected volume and an existing guideline to shape review criteria and batch delivery.