Layer
Layer is a web and mobile workflow platform for buildings that ties field photos and structured data to drawings and Revit models, then generates shareable reports and templates for surveys, punch lists, RFIs, and facility workflows.
Field teams often collect photos and notes in one app while design data lives elsewhere, which slows audits and closeout. Layer combines capture on iOS and Android with desktop and web access, then links records to locations, sheets, or model elements. The homepage states the product powers hundreds of teams on major building projects, giving a sense of adoption scale even though it is not an audited census (Layer homepage, 2026).
Integrations include a Revit connection so owners, architects, and contractors can anchor data to model elements instead of only folders. Template galleries cover door surveys, room data sheets, punch lists, RFIs, safety inspections, property assessments, and historic building workflows, which spans design through operations.
Reporting features include a document builder for PDF layouts, collaborative views, automations, and APIs documented for customers who need custom integrations. Enterprise pricing is quote-based on the public pricing page, so budget conversations start with a demo.
Because Layer spans design, construction, and owner operations, governance matters for photo storage, retention, and access control. Review the security page and contract terms if you handle sensitive owner or patient environments.
Specifications
Pricing
Platforms
Used for
Used by
Tasks
Pros and cons
Pros
- Cross-platform coverage (web plus iOS and Android) suits mixed field and office teams.
- Revit integration aligns field observations with authored models for many AEC workflows.
- Large template library speeds pilots for common owner and contractor processes.
Cons
- Public list pricing is not posted; enterprise quotes take time for smaller teams.
- Breadth across lifecycle phases means you must scope which modules you will adopt first.
- Heavy photo and file usage may need a clear retention policy with IT.
Key features
Field capture: Native mobile apps for photos and structured data tied to building locations.
Revit link: Model viewer and add-in messaging on the marketing site for BIM-connected workflows.
Templates: Prebuilt workflows for surveys, punch lists, RFIs, FF&E, CMMS, and preservation.
Document builder: PDF report layouts fed from captured data instead of manual copy and paste.
Collaboration: Shareable views and controlled links for owners and partners.
API access: Public API documentation for integrations and automations.
Pricing
Enterprise (quote)
Free
layer.team/resources/pricing lists request-quote flow. Confirm fees after demo.
Frequently asked questions
Do I need Revit to use Layer?
- The marketing site states Revit is not strictly required because Layer can attach data to drawings and locations. If you want model-linked workflows, plan for supported Revit versions and ACC permissions.
Which devices support Layer?
- Layer advertises desktop or web plus native iOS and Android apps. Confirm offline behavior, photo limits, and MDM requirements with the vendor for your sites.
How is Layer priced?
- The pricing page points to enterprise quotes with custom onboarding. Ask for a written scope that names user counts, projects, and template packs.
Can Layer handle owner-operated buildings after turnover?
- Templates include CMMS, warranties, spare parts, and asset registers, which target operations teams. Validate integrations with your CMMS or IWMS roadmap.
Does Layer support APIs and automations?
- Marketing lists automations and links to API documentation. Have your integration partner review rate limits, auth modes, and webhook options.
Is Layer only for construction, or also for design surveys?
- Workflow pages cover both construction administration and design-phase surveys such as room data sheets and door hardware. Pick templates that match your deliverable set.