Working rule
Track LOD by element or system. Do not describe the full model as LOD 300 or 350 unless every required scope has passed the same evidence and approval gates.
LOD 300
Specific geometry
An element can reach LOD 300 when its quantity and dimensions are based on approved design information. Its shape, location, and orientation must use the same source. The model geometry must be suitable for measurement at that stated level.
LOD 350
Interfaces with adjacent systems
An element can reach LOD 350 when the model also shows the parts needed to coordinate its connection; support; access; clearance; penetration; or other interface with nearby systems.
Required evidence
Advance one element or system at a time
- Identify the source: field measurement; survey; approved drawing; trade model; equipment submittal; or licensed design document.
- Record the responsible trade or designer. Include the date and revision. State the remaining assumptions.
- Model the required dimensions; elevation; orientation; slope; access; support; and clearance data.
- Check clashes and interfaces where they apply. Include architecture; structure; plumbing; HVAC; electrical; fire protection; kitchen equipment; and owner program.
- Run a second measurement and visual check. Keep the earlier release available for comparison and rollback.
- Mark the element LOD 300 or 350 only after the party responsible for that scope accepts the source and geometry.
Object status
Keep provenance visible
Each developed object should state its system; floor; source; responsible party; design status; field-verification status; LOD; revision; and unresolved issue IDs. Keep scan/reference geometry separate from design intent. Also distinguish trade-supplied geometry from approved construction geometry.
Authority
Zach and Tread run the coordination lane
Zach can direct model development and page updates. He can also direct release decisions, resource sharing, and routine subcontractor coordination. Tread can inspect; model; measure; package; publish; verify; and roll back the project files.
Licensed design and code interpretation stay with the qualified people responsible for that work. The same boundary applies to sealed documents; permit submission; trade means and methods; fabrication approval; contracts; bid awards; cost commitments; and field safety.
Release gate
Every public model release
- Starts from the saved Greenfield working blend.
- Creates a source checkpoint and SHA-256 manifest.
- Exports a fresh GLB and checks structure; units; names; bounds; metadata; and file references.
- Loads all eight views in a browser. It checks desktop and phone layouts plus console errors, failed requests, and external requests.
- Snapshots the current live release before promotion.
- Publishes only after the gates pass. A failed build stays offline.