Building documentation usually starts in pieces: site photos, 360 imagery, laser scans, floor plans, Revit files, PDFs, inspection records and handover documents. The problem is not creating those files. It is keeping them connected to the building after the project team moves on.
OcuMap is designed to organize visual documentation around the physical asset itself. A building project can begin from a floor plan or drawing, then add media, point clouds, design references and documents as the record grows.
What building documentation should include
- Existing-condition photos and 360 imagery
- LAS, LAZ and E57 point clouds
- Floor plans and PDF drawings
- DWG, RVT, FBX, OBJ and GLB references
- Videos, reports and supporting documents
- Historical captures from renovations, inspections and operations
Organize by building context
Instead of treating every file as an isolated upload, OcuMap lets teams organize documentation around buildings, floors, plans, locations and Features. That makes it easier to understand where a record belongs and what it describes.
Measure without returning to site
Supported flat photos can be calibrated for length and area measurements. Point clouds can be viewed and measured natively. These tools help teams answer many existing-condition questions remotely while respecting the accuracy of the original source.
Compare before, during and after
Historical comparison can show documentation from the same location side by side across dates. For renovation and facility workflows, that creates a visual history of what changed rather than a series of disconnected project folders.
Share a client-ready view
Published Viewers provide a curated, read-only experience for owners, consultants and stakeholders. The working project remains separate from the material selected for delivery.
Preserve the record beyond the project
Original uploaded files remain preserved alongside optimized viewing copies. That makes the documentation useful for future renovations, maintenance, due diligence and ownership transitions.
Start documenting with OcuMap →
Practical checklist
- Define the building, floor and floor-plan context before organizing files.
- Capture both broad context and targeted details.
- Use point clouds when dense 3D geometry is required.
- Keep drawings and design references with field documentation.
- Retain a pre-project baseline for later comparison.
- Plan the owner handover before the project ends.
Related resources
Common questions
Can one building project include photos, point clouds and Revit references?
Yes. OcuMap is designed to keep multiple documentation types in one project.
Do users have to start from a floor plan?
No. Floor plans are a natural starting context for buildings, but file-first and map-based workflows are also supported.
Can the record continue after construction?
Yes. The platform is designed for long-term documentation across operations, renovation and future ownership.