Home | Contact

How to set up a NAS for construction project documents

A construction document NAS gives the project office a central, searchable home for drawings, site diaries, RFIs, subcontractor packages, safety records and handover files. It gives architects, estimators, site managers and engineers a controlled place to find the current issue instead of chasing renamed PDFs through email threads.

Setting one up means designing an information system, not simply installing drives. Decide what the NAS owns, who may change it, how it survives site conditions, and how it connects with the project tools already used across a busy Australian build.

Plan the document workflow

Start with a file map before buying hardware. Create one root folder for the project, then organise work packages, disciplines and document types beneath it. Give drawings, models, site records and photographs predictable homes, while keeping working native CAD or BIM files on licensed workstations, publishing locked PDFs for general review and backing up native files to the archive. A revision register should identify the current issue and preserve superseded versions as read-only files.

Next, decide where the master copy belongs. The site office may collect incoming photographs and marked-up drawings, but head office or the document controller can approve the official issue. Define which folders are append-only, which staff can edit and which external parties can read. Project platforms such as Microsoft 365, Aconex, Procore and Autodesk Construction Cloud can support collaboration, but they should not become the only place a record exists.

Australian projects vary sharply. A commercial fit-out in Melbourne might involve dozens of trades, while civil works in the Pilbara or a house build near Cairns can involve long distances and intermittent connectivity. For the latter, make local browsing and capture work without internet, then replicate when a link returns. Use the same folder rules on every site so records remain understandable after the project mob moves to the next job.

Choose hardware for the workload

Size the unit for current records plus expected growth from drawings, native models, site photographs and video. Allow roughly 30 per cent free capacity for revisions, indexing and temporary work, and check expansion options before the first major project. RAID provides drive redundancy, not protection from deletion, ransomware or a stolen device.

For one small project office, mirrored drives in a two-bay QNAP or Synology model can be enough. A four-bay system configured as RAID 6 offers useful tolerance for larger teams, while 10GbE networking makes browsing model-heavy folders more practical. NVMe caching can improve responsiveness for small-file workloads, but it should be treated as an accelerator rather than extra backup space.

Buy through an Australian channel so warranty claims, spare drives and replacement power supplies are straightforward. Confirm the supplied power unit supports standard Australian 230 V mains, and check local support for the specific NAS model before committing to a project deadline.

Keep the main NAS and UPS in a lockable, conditioned office rather than a hot, dusty site shed. Regional NSW sheds can reach damaging temperatures, and Far North Queensland’s wet season brings humidity, rain and power interruptions. If a site has no suitable room, use a small local appliance for capture and defer full replication to head office. A UPS should cover the NAS, router and network switch, with its runtime tested before a critical upload.

Secure access without slowing the site

Give each person an individual account and grant permissions by role: document controller, estimator, site manager, subcontractor and read-only reviewer. Where head office already uses Microsoft 365 or Active Directory, connect the NAS to its directory service to simplify onboarding and offboarding. Use a VPN with multi-factor authentication for remote access, disable unused administrator accounts and avoid shared logins, which destroy accountability when a marked-up drawing goes missing.

Never publish SMB or administrative interfaces directly to the internet, and avoid unsolicited port forwarding. An NBN or business fibre service does not make direct exposure safe, and some Australian sites have only fixed wireless or 4G/5G. Provide a managed VPN, keep external sharing limited to named users, and require multi-factor authentication wherever the client supports it.

Set retention and approval rules before the project begins. Where a file forms part of a regulatory approval, follow the sign-off requirements of the relevant state or territory building authority, council or private certifier. If files include personal information about workers or clients, assess the Privacy Act 1988 and applicable state or territory privacy laws, then keep only the data needed for the project. If the project also sends marketing emails or newsletters, check the Spam Act 2003 before adding recipients.

Make backups recoverable, not merely present

Apply the 3-2-1 rule: keep three copies of critical project records, on two types of storage, with one copy away from the site. A mirrored RAID array is still one logical copy. Keep a second copy at head office or in an Australian data centre, and protect portable backup media from ransomware by disconnecting it when not in use.

Schedule automatic backups and alert named staff when one fails. Keep at least one offline or immutable copy so a compromised account cannot erase every version. A snapshot on the same NAS is useful for recovering an accidental change, but it is not an independent backup.

Several practices make the difference between a backup and a usable recovery plan:

For a small project office, a workable starting pattern is incremental backups each working day, a weekly image and retention aligned with the contract and records schedule. Large native models and drone footage can change the storage and bandwidth requirements, so measure them rather than applying the same settings to every project.

Operate the NAS through project handover

Begin with the manufacturer’s guided setup: label the drives, create the intended volume, apply firmware updates, reserve a network address and create only the shared folders the project needs. Add a small test share before importing the full archive. Then name a person or IT provider as the NAS custodian and create a short operating procedure covering passwords, file naming, capacity checks, backup failures and offboarding a subcontractor.

Use Australian project terms such as RFI, variation, defect list, practical completion and handover in templates and folder names. That familiar language helps a site manager or tradie find material without a translation guide. Review the setup every month and after each major milestone. Check free capacity, UPS status, snapshot history, audit logs, account access and whether an off-site copy received the latest files. Compare file counts and folder sizes with the live share, since a backup can appear healthy while syncing only selected folders.

Start the rollout with a small test package this week: load a recent drawing set, a site diary, a marked-up subcontractor package and a folder of site photographs. Invite one internal user and one external consultant through the normal access route, then complete an off-site restore test. Once that path works, extend it to the remaining work packages and make the NAS custodian responsible for the next review.