Illustrative report structure

Internal Blade Inspection Report

This page demonstrates an illustrative information structure without publishing field or customer imagery. It is not a customer report, a field-case record, an independent validation or a diagnosis of any asset.

Download blank report CSV

Illustrative layout · no inspection data

How the evidence fits together

Asset and record reference

Asset ID · component · capture reference · inspection context

Original capture belongs here

No customer image or defect finding is shown.

Location: Reference linked to the capture and agreed coordinate convention.
Observation: Describe what is visible; keep interpretation separate.
Human review: Reviewer, review status and limitations.
Traceability: Original file, annotation reference and procedure revision.

A field arrangement for discussing report requirements, not a completed report or a software screenshot. Final fields and exports require project confirmation.

Blank template · UTF-8 CSV

Define the record before collecting the evidence.

The download contains 26 column headers and no inspection rows, measurements, customer details or asset results. It is an illustrative planning template, not a completed report, an approved procedure or a statement of WIT-BR60 export compatibility.

How to use the fields

Open the CSV in a spreadsheet using UTF-8. Keep identifiers as text and use one row per observation.
Record asset context and location first. Link original capture files and separate annotation files by their identifiers.
Add measurements only when supported by a documented method and unit. Leave unavailable values blank and describe limitations; blank does not mean zero.
Have the responsible reviewer add classification, criteria and review state. Record the asset owner’s decision separately from a recommendation.

Download the field-by-field guide (CSV)

Agree the required outputs

Asset and coordinate conventions, units, required fields and missing-data handling.
Original images or video, annotation references, filenames and access permissions.
Measurement method, uncertainty and capture limitations.
Project taxonomy, acceptance-criteria references and reviewer responsibility.
Requested export format, revision history, retention and approval workflow.

Confirm which outputs the proposed configuration can provide before approving a project. The browser PDF saves this illustrative page; the CSV is the editable blank record.

01 · Scope

Asset and inspection context

Turbine / bladeIllustrative asset · Blade A

Inspection areaInternal cavity and documented path

Operating stateStopped and mechanically locked

Review statusHuman verification required

02 · Capture

Make source-file requirements explicit.

These code-native placeholders show where original files and their references belong in a controlled report. They do not depict a blade, product, defect or inspection result.

Context file

Required

No field image includedOriginal context frame would be retained here.

Reference: Original file ID
Purpose: Access and geometry context

Review file

Required

No observation image includedOriginal and annotation layers remain separate.

Reference: Capture + annotation IDs
Purpose: Human review trail

03 · Observation record

Separate capture from judgement.

Illustrative inspection-record fields and their review state
Field	Illustrative content	Review state
Position	Blade / cavity / distance from root / image reference	Captured
Observation	Visible surface feature and measurable dimensions	Human verification
Classification	Project defect taxonomy and applicable acceptance criteria	Engineering review
Next action	Monitor, re-inspect, evaluate or plan repair	Asset-owner decision

Field: Position
Illustrative content: Blade / cavity / distance from root / image reference
Review state: Captured

Field: Observation
Illustrative content: Visible surface feature and measurable dimensions
Review state: Human verification

Field: Classification
Illustrative content: Project defect taxonomy and applicable acceptance criteria
Review state: Engineering review

Field: Next action
Illustrative content: Monitor, re-inspect, evaluate or plan repair
Review state: Asset-owner decision

Illustrative-content limitation

The reference, asset fields, observation fields, source-file slots and review states are constructed examples and do not come from a customer case. No product, field, customer or defect imagery is presented on this page. Actual report content depends on the approved inspection procedure, asset information, capture quality, project taxonomy and human engineering review.

Build the right record

Define the required review record.

We’ll map capture views, location fields, review states and export requirements to the documented configuration.