Operators routinely include 'QA pack' as a single line item in a quote — sometimes priced separately, sometimes bundled into 'processing and reporting'. The pack a buyer actually receives at this line item varies enormously between operators: a two-page 'accuracy achieved: ±X mm' summary vs a 30-page compliance-grade pack with independent reviewer sign-off. Both are honestly called QA packs; one cost the operator $0 to produce, the other $8,000. The pricing rarely reflects the difference. Buyers who want the comprehensive pack should expect to specify it and pay for it; buyers who specify nothing get whatever the operator's default is.
If you've ever received a LiDAR deliverable with a thin "QA pack" — accuracy number quoted, no analytical depth behind it — and wondered whether that was the standard or whether you should have expected more, you've met the QA-pack-pricing problem. The pack you receive reflects what the operator's default QA workflow produces; the default varies wildly between operators; pricing doesn't typically reflect the difference.
A reputable operator producing a comprehensive compliance-grade QA pack invests $5,000-12,000 of processor time in it for a typical project. An operator producing a minimal pack invests $300-800. The deliverable cost difference often isn't visible in the quote — the comprehensive operator bundles it into processing cost; the minimal operator skips most of it; both can call the output a "QA pack" honestly.
This article walks through what each of the ten QA pack sections actually costs to produce, the three-tier pack hierarchy with realistic price ranges, why buyers default to under-priced packs, and the brief language that scopes pack content honestly rather than letting it default invisibly.
(See QA report article for what's actually in a proper 10-section pack, and acceptance criteria article for what makes a pack contractually acceptable.)
The standard 10-section QA pack, with what each section costs the operator to produce:
Project identification, dates, client reference, operator details, sensor model and serial, capture parameters summary.
Production cost. Almost zero. Auto-populated from project management system. $0-100.
Flight pattern, altitude AGL, ground speed, swath width and overlap, point density target, weather conditions during capture.
Production cost. Auto-populated from flight planning system. $0-200.
PPK covariance plot through the flight, position solution quality vs time, satellite count, PDOP record.
Production cost. Generated as standard output from PPK processing software (POSPac MMS or equivalent). $100-300 to extract and format for inclusion.
Per-strip-pair alignment residuals, alignment method documentation, residual trend analysis.
Production cost. Generated by TerraMatch or equivalent during processing. $200-500 for extraction, interpretation and presentation.
Per-checkpoint comparison against control, stratified by cover class, statistical summary (RMSE, mean, max, distribution).
Production cost. Modest if the control was captured and processed correctly upstream; substantial if proper independent-checkpoint methodology wasn't designed in (see residuals article). $400-1,500.
Per-class precision and recall against independent validation, classification scheme documentation, manual cleanup methodology if applied.
Production cost. Depends entirely on whether manual cleanup was scoped (see quality vs speed classification article). Auto-only classification documentation: $200-400. Tier 2 targeted cleanup documentation: $600-1,500. Tier 3 full cleanup with per-class validation: $1,500-3,500.
Per-cell density raster across the project area, with statistical summary (mean, percentiles, minimum), edge zone identification.
Production cost. Generated from point cloud in routine processing. $200-500 for extraction, presentation, and analysis.
DTM and DSM quality validation — visual inspection summary, identified artefacts, hydro-enforcement documentation if applicable, contour validation.
Production cost. $400-1,200 depending on project complexity. Hydro-enforcement documentation adds further if structures are enforced.
Itemised deliverable list with file paths, formats, sizes, SHA-256 checksums, classification scheme, attribute schema.
Production cost. Mostly automated from deliverable structure; format and documentation quality matters. $200-500.
Review and validation by a senior processor or external reviewer separate from the project processor, with documented assessment and named sign-off.
Production cost. $500-2,000 for the reviewer's time. This is the section most operators skip in their default pack.
Combining the section costs produces three practical pack tiers:
Sections 1, 2, and a basic version of 5. Effectively "here's what was captured and what accuracy we hit". No deeper analytical content.
What you get. Project summary, capture parameters, headline RMSE number with checkpoint locations.
What's missing. Trajectory quality documentation; strip alignment analysis; classification quality; density analysis; surface QA; manifest detail; independent sign-off.
Appropriate for. Planning-grade work where the deliverable supports broad decisions rather than engineering or compliance use.
Sections 1-9 with reasonable depth. Manual cleanup documentation if Tier 2 classification was scoped. No independent reviewer sign-off beyond the project processor's own attestation.
What you get. Full analytical content across all standard sections; documented capture and processing chain; defensible accuracy reporting; deliverable manifest with proper detail.
What's missing. Independent reviewer sign-off; the more demanding compliance items (detailed methodology documentation, audit-defensible processing trail).
Appropriate for. Most engineering work where the deliverable supports design decisions or asset management.
All ten sections at maximum depth. Full classification cleanup documentation per class, independent reviewer sign-off, methodology documentation suitable for regulatory filing or expert-witness use.
What you get. Pack defensible against regulatory audit; per-class validation documentation; independent professional sign-off; complete processing chain audit trail.
Appropriate for. Compliance work (regulator filing, expert witness, audit-defensible documentation), high-stakes engineering, programme work where pack quality matters across cycles.
Three structural reasons:
1. Procurement template defaults. "Include QA pack" gets in the brief without specification; operator's default version is whatever they produce by default; buyer gets the cheap version without realising the comprehensive version was an option.
2. Operators don't surface the tiered choice. Operators quoting against vague briefs assume the cheap version is acceptable and price accordingly; the buyer doesn't know to ask for something different.
3. The pack difference is invisible at quote time. Two operators quoting "QA pack included" look comparable on quote, deliver wildly different packs at delivery. The buyer who took the cheaper quote got the cheaper pack and didn't see the difference until handover.
(See reading the project brief article for the broader brief-interpretation problem this sits within.)
For a Tier 3 compliance-grade pack at $8,000 typical, the cost breakdown is roughly:
The biggest line item is typically the classification cleanup documentation that goes with Tier 3 manual classification work. The second biggest is per-class validation against independent samples. The independent reviewer is the third biggest, and the section most operators skip entirely.
The cost ranges above scale somewhat with project size and complexity:
Small projects (under 50 ha). Pack production cost is largely fixed (most sections are per-project, not per-area); under-100 ha projects can have QA pack at 15-25% of total project cost.
Mid-size projects (50-500 ha). Pack cost is proportionally smaller — 5-15% of total project cost. Most economic case for comprehensive QA.
Large projects (over 500 ha). Pack cost proportionally smaller again — 2-8% of project cost — but the absolute number is larger because some sections (density coverage, surface QA) scale with project area.
Multi-cycle programme captures. First-cycle pack costs more (establishes baseline); subsequent cycles cheaper (variance against baseline rather than full analysis). Per-cycle pack cost can drop 40-60% from cycle 1 to cycle 3+.
(See annual capture programmes article for the programme-level pack economics.)
Three sentences in the brief that pin down pack expectations:
"QA pack tier: [Tier 2 engineering-grade / Tier 3 compliance-grade]. All ten standard sections present with [tier-appropriate] analytical depth.
Specific tier-3 items required if applicable: per-class classification validation against independent samples; independent reviewer sign-off; methodology documentation suitable for [intended use — regulator filing / expert witness / audit].
Pack format: [PDF for archive / JSON manifest for ingestion / dual]. Per-class accuracy targets and acceptance criteria per attached reference."
That paragraph specifies pack tier, identifies the high-cost items if Tier 3, and pins down format. Prevents the operator defaulting to their cheapest interpretation.
Three patterns we see when QA pack scope goes wrong:
Specifying "comprehensive QA pack" without tier specification. Comprehensive means different things to different operators; the quote varies accordingly; the deliverable varies accordingly.
Over-specifying Tier 3 for projects that genuinely need Tier 2. Compliance-grade pack overhead on a project that doesn't need it inflates cost by $3-8k without adding what the deliverable depends on.
Skipping the pack scope conversation entirely. Operator's default pack tier is applied; buyer gets whatever that is; potentially either too much or too little.
Four diagnostic questions about pack scope at quotation:
1. "What tier QA pack is included in your quote — basic, engineering, or compliance?" Forces explicit tier identification rather than generic "included" language.
2. "Will the pack include independent reviewer sign-off?" This is the most diagnostic single item — operators with mature QA include it; those with informal QA don't.
3. "What per-class classification validation is documented?" Tests whether the pack contains actual analytical depth or just a list of classes.
4. "What's the additional cost to upgrade from your default tier to the next?" Surfaces what the operator's default actually is and what the upgrade costs.
QA pack production cost varies enormously: $500-1,500 for a basic accuracy summary up to $5,000-12,000 for a compliance-grade pack with independent reviewer sign-off. Most quotes don't distinguish between the tiers; buyer gets whatever the operator's default is.
The ten-section pack breaks down by per-section cost — auto-populated sections (metadata, capture parameters, density) cost $0-500; analytical sections (classification quality, surface QA, alignment) cost $400-3,500 depending on depth; independent reviewer sign-off costs $500-2,000 and is the section most operators skip.
Three pack tiers: Basic ($500-1,500, planning work), Engineering ($2,500-5,500, most engineering work), Compliance ($5,000-12,000, regulator filing / expert witness / programme work where pack quality matters across cycles).
Three reasons buyers default to under-priced packs: procurement template defaults, operators not surfacing the tiered choice, invisible difference at quote time.
Pack cost scales with project size but largely as fixed cost for small projects (15-25% of total), proportionally smaller for mid-size and large (2-15%). Multi-cycle programmes get cheaper per-cycle after baseline.
Three-sentence brief language pins down tier, specific tier-3 items, and format. Four diagnostic questions surface what the operator actually includes. Three common scoping mistakes — vague "comprehensive" specification, over-specification of Tier 3, skipping the scope conversation.
If you're scoping a project and want to specify the QA pack at the tier your deliverable actually needs — without over-paying for compliance-grade when engineering-grade is right, or under-paying for engineering when compliance is needed — send through the project shape. We'll quote against the tier-appropriate pack with itemised cost so you can see exactly what each section contributes.
The ten-section pack structure this article costs. Useful prerequisite for understanding what each section contains before evaluating what each costs.
What makes a pack contractually acceptable. Pairs with this costing piece — the contract language and the cost picture together let you specify and budget the pack honestly.