A vehicle 360 delivery is more than an image that opens successfully. It includes the source coverage, processed views, interactive behavior, supporting descriptions, and files intended for publication. Review these layers separately before judging the package as a whole. A smooth interface can hide a missing angle, while a sharp source image can still be published in a confusing or inaccessible way.
Begin with the agreed scope
Compare the delivery with the capture brief. Identify the vehicle, the required viewpoints, and any documented exclusions. Check that interior and exterior sets belong together and represent the agreed configuration. If doors, roof, or accessories differ between sets, the difference should be intentional and explained. Do not infer complete coverage merely because a file or viewer is labeled 360.
Keep a simple issue log with the affected file or view, the observed problem, and the proposed action. Distinguish capture faults from processing faults and publishing faults. A missing photograph may require recapture; a file-order error may not. This separation makes corrections clearer and helps avoid repeatedly exporting material that cannot solve the underlying problem.
Inspect image integrity
For interior panoramas, look around the full view rather than staying at the opening angle. Inspect pillars, steering wheels, seat edges, roof lines, and the area around the camera support. Check for duplicated controls, broken lines, stretched textures, and abrupt exposure changes. Compare suspicious areas with source photographs when available. The interior guide explains why nearby objects are frequent trouble spots.
For exterior spins, step through frames individually and then run the sequence. Look for changes in scale, drifting alignment, cropped mirrors, altered wheel position, and inconsistent color. Check the transition between the final and first frames. Confirm that the direction of movement matches the controls and labels. A misplaced frame can look like a software problem even when the viewer is functioning as configured.
Use a decision table for corrections
| Finding | Likely next step | Publication consideration |
|---|---|---|
| Important viewpoint absent | Compare with the brief and assess recapture | State the coverage limit if unresolved |
| Broken or duplicated cabin feature | Review sources and stitching | Do not present a misleading structure |
| Exterior sequence jumps | Check order, framing, and replacement frames | Review the assembled sequence again |
| Private detail remains visible | Hold affected publication files for correction | Check all related derivatives |
| Essential control cannot be operated | Correct the implementation or provide a usable alternative | Do not rely on the interactive view alone |
Review privacy and supporting text
Inspect delivered files for personal documents, reflected people, identifiers, and unnecessary location information. Include preview images and alternative stills. The privacy guide provides a broader review process, including metadata and file naming. Treat an unresolved privacy concern as a publication decision, not a minor image-quality note to be buried in a handoff.
Read descriptions against the images. Do they identify the correct viewpoint? Do they distinguish visible features from unverified claims? Remove statements implying a mechanical inspection, verified provenance, or complete condition assessment when the photography cannot support them. Text should explain unseen areas rather than suggest that missing detail confirms the absence of a problem.
Test the delivered experience
Open the actual publication package, not only an editor preview. Check navigation, loading feedback, keyboard operation, visible focus, and the way movement can be stopped. Test whether supporting stills and descriptions remain available if the interactive element fails. The accessible publishing guide expands these checks. For image-alternative guidance, use the W3C images resource as a place to verify current considerations.
Record which files are approved and which remain drafts. Keep a clear distinction between originals, working files, and public exports so an older uncorrected version is not accidentally reused. After corrections, repeat the affected checks and review neighboring content for unintended changes. Approval should describe the reviewed package and remaining limitations, not promise that every possible defect has been found.
Frequently asked questions
Should every exterior frame be reviewed?
Yes. Individual frames can contain privacy, framing, or continuity problems that are easy to miss during playback.
Can sharpening fix missing detail?
Not reliably. Sharpening cannot establish information that the source capture did not meaningfully record.
When is a delivery ready to publish?
When it matches the agreed scope, significant issues are resolved or clearly limited, and the actual publication package has been checked.