How Corvus approaches data, reporting and deliverables

A Corvus deliverable is built to be acted on. Every report, plan, and dataset we ship is designed to drop into the contractor’s, engineer’s, or client’s workflow without translation. This article describes how we think about data, reporting, and deliverables — and why the discipline behind them matters more than any single feature of the output.

The starting point: the question

Every Corvus engagement starts with a question. Before any equipment is calibrated or any survey is planned, we want to know what decision the data will inform. A pre-drill scan is a different deliverable from a structural assessment input is a different deliverable from a heritage record.

The question shapes:

• The methods we choose.
• The density of survey work.
• The level of detail in the report.
• The format of the CAD or model output.
• The interpretation we provide.

A clear question produces a tight, useful deliverable. A vague question produces a vague deliverable. We invest more time in the briefing conversation than most surveyors precisely because the brief is what makes the rest of the work valuable.

On-site discipline

On site, Corvus surveyors operate to a documented method statement and risk assessment supplied before attendance. We turn up calibrated, prepared, and ready to work. Calibration is checked at the start of every session and recorded in the project pack.

Findings are marked up live on the slab, wall, or column as they are identified. We photograph the markings before leaving site. The surveyor walks the contractor or engineer through the markings before departure — the most valuable conversation in the whole engagement.

We do not leave site without a clear handover of what was found, what was inferred, and what additional verification (if any) we recommend.

Reporting

The standard Corvus report contains:

• A clear scope and brief, restated by the surveyor.
• The method, including equipment, frequency, and scanning pattern.
• The calibration record from the day.
• Findings: depth-accurate plans, photographs of markings, and tabulated data where appropriate.
• Statistical analysis where the data supports it (cover statistics, strength estimates, etc.).
• Limitations and assumptions, explicitly acknowledged.
• A recommendation, where one is appropriate.
• Signed off by the surveyor who did the work.

Every report is in plain English. Where technical language is necessary, it is explained. We write for the engineer or contractor who has to act on the data, not for the file.

CAD output

For most concrete scanning, ferro scanning, and large-scale GPR work, a CAD-ready DXF or DWG plan is part of the standard deliverable. The plan is:

• Drawn at a scale that overlays the project drawings.
• Referenced to the project coordinate system.
• Annotated with depths, IDs, and anomaly classifications.
• Layered cleanly so it integrates with downstream design work.

If the project uses a specific BIM environment, we deliver in that environment’s native format on request.

Point cloud delivery

For LiDAR work, the registered point cloud is the durable deliverable. We supply:

• The cloud in your preferred format (E57, RCP/RCS, PLY, etc.).
• A registration report showing achieved accuracy.
• A scan station log.
• Any drawn outputs (plans, sections, elevations) scoped in the brief.
• A BIM model at agreed Levels of Development if the brief calls for it.

The point cloud is the source of truth. Drawings and models are derived from it; the cloud remains the authoritative record.

NDT data

For concrete testing, deliverables include:

• A method statement and calibration record.
• Test logs with photographs.
• Raw test data.
• Statistical analysis.
• UKAS lab certificates for any cores.
• A characteristic strength estimate where the brief calls for one.
• An interpretation note tied to the engineering question.

We work closely with the structural engineer where one is involved, so that our deliverable feeds directly into the engineering analysis without re-interpretation.

Sign-off

Every Corvus deliverable is signed off by the surveyor who did the work. Named, dated, and accountable. We do not ship anonymous reports. The surveyor’s reputation is on the deliverable; the surveyor’s reputation is also why the deliverable is worth what it costs.

Limitations honestly stated

Every method has limits. Every Corvus deliverable acknowledges them. GPR has depth limits, ferro has shadowing effects, photogrammetry has lighting requirements, NDT has confidence intervals. Pretending otherwise is short-sighted; the moment a deliverable is queried, the limitations come out anyway, and a deliverable that did not state them up front is a deliverable that has lost credibility at exactly the wrong moment.

We state limits honestly because that is how defensible work is done.

Same-day, next-morning, no-drama

Routine deliverables come back fast. On-slab markings the same day. A written report and CAD plan the next morning. Larger or more complex jobs follow within a few working days. We do not slow-roll deliverables.

If the brief needs faster turnaround — same-day report, urgent dispute response — we flag that on the quote and price it accordingly. We do not promise turnaround we cannot deliver.

What we do not do

A few things, deliberately:

• We do not over-claim what GPR, ferro, or NDT can do.
• We do not promise definitive answers from techniques that produce estimates.
• We do not anonymise reports.
• We do not skip calibration or the calibration record.
• We do not bury limitations in fine print.
• We do not subcontract the survey to whoever’s free.

These are not branding statements. They are operational disciplines that produce defensible work.

The takeaway

A Corvus deliverable is not the cheapest in the market and is not designed to be. It is built to support the engineering, contracting, or client decision it informs — clearly, defensibly, and with the confidence that comes from a properly run engagement. If you have read a survey report that you couldn’t act on, you’ll know what we are trying to do differently. The deliverable is the product. We invest in it accordingly.