The product
Everything your project needs to stay structured.
Three core pillars. Four powerful secondary tools. One platform that replaces the chaos of emails, WhatsApp, and disconnected spreadsheets.
Requirements
Requirements Management
AEC requirements are not simple bullet points. A façade engineer's requirement is linked to an architect's brief, which is linked to a client performance spec, which is linked to a planning condition. Naavek models every layer.
Hierarchical branching
Requirements have parent/child relationships with full tree traversal. Any discipline can branch a top-level requirement into sub-requirements they own.
Discipline tagging
Architectural, Structural, MEP, Façade, Civil, Infrastructure. Every team filters their own live view.
Status lifecycle
Open → In Progress → Responded → Closed. Each step has an owner and a timestamp — no ambiguity about where something stands.
Formal responses
Companies assigned to a requirement can formally respond with text, files, and a disposition: accepted / rejected / clarification needed.
Priority flags
Critical / High / Medium / Low, visible at every level of the tree.
Direct attachments
PDFs, images, Excel sheets, CAD exports directly on the requirement record — not floating in a shared drive folder nobody can find.
Decisions
Decisions Log
Every AEC project makes thousands of design decisions. Most are undocumented. Naavek's decisions module creates a living audit trail so the reasoning behind every choice survives the project.
Decision authorship
Every decision is stamped with the user and company who made it. No more ‘I thought someone else agreed to that’.
Reasoning captured
The decision record includes what was decided and why — the reasoning that usually lives only in the head of the person who made it.
Linked requirements
Each decision can reference the requirements it responds to or constrains, building the traceability chain.
Formal approvals
Each decision has a list of named approvers. Every sign-off is timestamped. The approval state is auditable and exportable.
Status states
Draft → Final → Archived. Teams can work iteratively without polluting the formal record.
Attachments & priority
Sketches, calculations, meeting clips — all directly on the decision record with priority flags.
Teams
Cross-Company Coordination
AEC projects span multiple firms. A single project may involve an owner, an architect, a structural engineer, an MEP firm, a façade specialist, a principal contractor, and a dozen sub-trades. Naavek is built for this.
Multi-org workspaces
Each firm has its own organisation workspace with its own members, roles, and permissions.
Shared projects
Projects are shared between organisations. Visibility and access are controlled by role — owner, manager, editor, viewer.
Cross-org invitations
A project owner invites another org to collaborate on a specific project. The invite flow handles acceptance, auto-registration, and role assignment.
Join requests
Users can request to join an organisation by sharing an Org ID. The admin approves or rejects in the Team panel.
Pre-invite by email
Add a user by email before they have an account. When they sign up, Naavek detects the pending invite and routes them to the right org.
Real-time notifications
Live updates via Socket.io — every team member is notified instantly when a requirement changes or a decision is made.
More than the core
The full toolkit
Beyond the three pillars, Naavek adds the visualisation, collaboration, and compliance tools a complex project needs.
Collaborative Canvas
A Miro-style real-time whiteboard where teams workshop the brief. When a point is resolved, promote it directly to a structured requirement — connecting discovery to delivery.
Trace Graph
A D3.js-powered visualisation showing which requirements link to which decisions and where a change cascades. Before approving a change, see the full downstream impact visually.
BIM Viewer
An in-browser IFC model viewer. Navigate by storey, discipline, element type. Click a column in the model and see the requirement it was designed to satisfy — directly in Naavek.
Approval Panel
A formal sign-off workflow where requirements and decisions move through a named approval chain. Each approver, timestamp, and state is auditable and exportable for handover.
Built to scale
Modern stack. Enterprise rigour.
Production-grade full-stack application designed for real-time multi-org collaboration.
Ready to see it in your project?
Naavek is in early access. We’re onboarding AEC teams now.