Floor plans
The working drawing is on an architect's laptop, the 'as-built' is a PDF in the site hut, and fire plans on the wall are two revisions behind. Contractors work from the wrong floor number.
Hypervault stores building, floor, plan type, and drawings in an encrypted EU vault, with permissions for architects, clients, and the contractors who are allowed that revision.
Why store Floor plans in a digital vault
As-built and design intent share a filename
Plan type is not labelled. Design, fire, and as-built as a field stops a contractor printing the wrong sheet.
Floor number is in the title block only
Search cannot filter. Floor number and building name as fields make a multi-building archive usable.
The architect's local file is newer than the issued set
Date created and a named architect on the vault item show which issue is current.
Site copies are unmarked printouts
They outlive a revision. A permissioned vault share replaces the hut binder as the issued set.
Who uses this template
Architects and technicians
Issue floor plans with building, floor, and plan type instead of another unmarked PDF.
Project clients
Hold the current drawings in an EU vault they control after the job closes.
Contractors and facilities
Open the issued revision under permissions, not a WhatsApp photo of the print.
Fields in this template
Keep every record complete and easy to find. Existing fields stay as they are; extras are added only when a vault item would otherwise be incomplete.
- Building name
- Floor number
- Plan type
- Date created
- Architect
- Attachments
- Notes
How it works in Hypervault
Create from the template
Add an item from the Floor plans template in your workspace.
Fill and attach
Complete the fields and attach supporting files where needed.
Share with the right roles
Give access only to the people who maintain or use this record.
Store it in a vault, not a spreadsheet
Create a workspace, pick this template, and keep credentials and supporting files encrypted in the EU.