Assign responsibilities before sending a link
Identify the dataset owner, processing operator, technical reviewer and person authorised to issue information externally. Separate routine project reviewers from administrators. Enterprise access, SSO, API or custom integration requirements should be scoped separately from the core Starter and Pro plans.
Classify the information in the project
Review imagery, coordinates, utility details, building interiors and design overlays for contractual or security sensitivity. Choose who may view, annotate, download or reshare according to the owner’s policy. Where the approved route is unclear, pause external sharing and use the controlled project process.
- Authorised audience and organisation
- Permitted actions: view, measure, annotate, download or administer
- External share-link approval and expiry practice
- Retention period and archival export responsibility
- Removal of access when a person leaves the project
Keep collaboration separate from authoritative records
Annotations are useful for questions, observations and assigned actions. They should include an author, date and context. Before an annotation becomes a design change, GIS update or acceptance record, it must pass the relevant project verification and approval route.
Plan the export and retention route
Decide which files constitute the issued record: source imagery, point cloud, mesh, orthomosaic, annotations, reports or a defined subset. Test the export in the recipient system and retain coordinate, design-revision and QA metadata. Do not rely on indefinite browser access as the only archive.
A simple review-state convention
Use explicit states such as Processing, Internal QA, Review, Issued and Superseded. Only the appropriate state should be visible to each audience. When a new capture or corrected model replaces an earlier one, preserve the relationship rather than silently deleting the project’s review history.