Build a decision record, not a gallery
A folder of screenshots rarely explains why a location was shortlisted. Begin with a short record of the proposed scene use, the current decision status and the evidence supporting it. Name the unresolved conditions immediately. A producer should not have to inspect a model to discover that the equipment route is still unconfirmed. Keep the summary readable without specialist software, then link it to the deeper technical material.
Use a compact register for each source: creator, capture date, received date, file version, permitted use and known limitations. Capture date and file modification date are different facts. A recently exported model may depict a site from an earlier season or before a refurbishment. When dates are unavailable, write “not supplied” rather than filling the gap with the day the file arrived.
Give every important view a stable identity
Assign a view ID to each angle used in a discussion. Link that ID to a position on a simple plan and record camera height, orientation, focal length, active image area and aspect ratio where relevant. This allows camera, art and locations to refer to the same proposal. A view described only as “the window shot” becomes ambiguous as soon as the group considers another room.
Include a reference image beside a simulated frame when possible. Explain any deliberate alterations, such as removed furniture or a proposed wall extension. If the creative intention changes, preserve the earlier decision as superseded rather than silently replacing it. The purpose is not bureaucratic completeness; it is to stop a later department treating an obsolete image as the current plan.
Package for different readers
Keep a lightweight summary, still views and a text issue register alongside the interactive scene. A production manager may need the decision and constraints without opening a large environment. A technical artist may need source assets, unit conventions and import settings. A local scout may need a short list of measurements with annotated reference images. These are different reading tasks; forcing everyone through one complex viewer adds friction.
File formats help with exchange but do not erase interpretation. Khronos glTF is designed for efficient transmission and loading of 3D scenes. OpenUSD supports scene description and composition workflows. Autodesk FBX is common in content pipelines, while Alembic is used for baked geometry interchange. None guarantees that every camera, material or metadata field survives every application path. Test the actual transfer with the recipient and compare against a reference view.
Record the application and version used for the approved export, but avoid making an entire production record dependent on a single proprietary project. Keep plain-text notes and broadly readable images as a fallback. Where a PDF summary is used, preserve selectable text, meaningful headings and image descriptions. Accessibility is part of a useful handoff, not an optional finishing pass.
Make unresolved issues actionable
Each issue needs a location reference, an evidence request, an owner role and a status. “Check access” is too broad. “Confirm clear lift opening and usable car dimensions for the proposed equipment route” is actionable, provided the intended equipment envelope is also supplied. Do not insert guessed measurements just to complete a row. Mark assumptions and distinguish a reported answer from independently checked evidence.
| Field | What it should contain |
|---|---|
| Reference | Stable room, route or view identifier |
| Question | A specific unresolved production decision |
| Evidence | Requested measurement, observation or written confirmation |
| Owner and status | Responsible role; open, answered or verified |
| Decision effect | What can proceed, or what remains blocked |
Store approvals separately from review comments. A department saying a composition is promising is not approving fire access or electrical arrangements. Identify who has authority to make each kind of decision and retain the supporting correspondence under the production’s document policy. If a site condition changes, reopen the affected issues rather than assuming the original approval still applies.
Control distribution and revision
Private interiors, faces, vehicle registrations, security systems and access instructions can be sensitive. Share only what the recipient needs and use access controls appropriate to the production. Do not embed door codes in a widely circulated location deck. Confirm the rights to distribute scans, photographs and third-party assets; owning a working copy does not necessarily include redistribution rights.
Give the pack a clear revision identifier and state which previous release it replaces. Keep a short change log focused on decisions: updated loading route, corrected units, revised camera view or new permission condition. Archive superseded material where it cannot be mistaken for the current version. The final test is simple: can a recipient name the current decision, find its source and identify the next owner without phoning the author?
Expandable risk note: a portable file can travel too far
A downloadable scene may contain embedded textures, hidden objects or metadata beyond the intended view. Inspect the export and remove unnecessary sensitive content before sharing it outside the approved team.
Source desk
- Khronos glTF and OpenUSD — scene exchange and description references.
- Autodesk FBX and Alembic — interchange context; test your specific workflow.
Make the first record: use the local location-note tool to draft and save a plain-text question. It does not upload or send your information.