Define the monitoring question before the first flight
Decide whether the record supports general progress communication, earthwork review, installation verification, design coordination or a combination. Each use needs different capture coverage, frequency, control and acceptance. A visual overview for a weekly meeting is not automatically suitable for quantity certification or as-built acceptance.
Document the authoritative design files, survey reference, responsible reviewers and formal approval route. PIX4Dcloud is the shared spatial environment; it does not replace the project’s contractual progress and quality-assurance procedures.
Make each capture repeatable
Use a consistent site boundary, naming convention, horizontal and vertical reference, capture perspective and processing configuration. Drone flight plans should provide suitable overlap and cover changing areas, while terrestrial captures should preserve sufficient visual texture and observation angles.
- Retain stable control and independent checkpoints appropriate to the required comparison.
- Record weather, active work areas, occlusions and inaccessible zones.
- Keep consistent site, folder and dataset names.
- Use a documented processing-output selection and review each result before issue.
- Flag scope changes that prevent like-for-like comparison.
Use Pro functions with their dependencies visible
Pro sites and timelines organise recurring datasets. Volume comparison can help review change where surfaces and boundaries are suitable. DXF/IFC overlays provide design context, and annotations collect observations around a common record. Gaussian Splatting and AutoGCP support are also plan-specific functions in the current comparison, but their availability does not remove dataset-specific QA.
Design overlays must use the correct revision and coordinate reference. A visual mismatch is an investigation trigger, not automatic proof of construction error; model alignment, design exports and capture accuracy must be checked before issuing a conclusion.
Review, annotate and close the loop
A practical review cycle assigns each observation an owner and a next action. Annotate the location, attach the relevant project reference and distinguish field observation from design interpretation. Export or record the agreed report and retain the underlying dataset version.
- Field observation: what is visible in this capture?
- Spatial comparison: what changed relative to the selected reference?
- Interpretation: what might that mean for the works?
- Verification: who checks it on site or against authoritative records?
- Disposition: what action, approval or follow-up capture is required?
Limitations to include in the monitoring plan
Cloud review cannot see concealed work, reconstruct unobserved surfaces or certify progress by itself. Changed shadows, vegetation, standing water, stockpile movement and machinery can affect reconstruction and comparison. Restricted project information requires an approved hosting and sharing route.