Blog

Working on site with no access to the office server


How construction teams access project files in the field without VPNs or local downloads



The office file server holds everything: drawings, specifications, submittals, RFIs, meeting minutes, schedules. It is the single repository for the project. And it is completely inaccessible from the construction site.

This is a routine problem across the construction industry. Site managers, engineers, superintendents, and inspectors all need project documents in the field. The documents live on a server in the office, behind a firewall, connected to a network that the construction site cannot reach. The gap between where the information lives and where the information is needed has existed for as long as digital project files have been the norm.


The VPN that almost works

The standard solution for remote file access is a VPN. Connect to the office network from the field, and you can browse the server as if you were sitting at your desk. In theory.

In practice, VPN connections on construction sites are unreliable. Cellular coverage varies across a site and throughout the day. Bandwidth is often limited, shared among multiple users, and subject to interference from the physical environment. Steel structures, concrete walls, and heavy equipment all affect signal quality.

When the VPN does connect, large files transfer slowly. Opening a drawing set over a mobile connection can take minutes, during which the connection may drop and the transfer restarts. The experience is frustrating enough that people develop workarounds, and those workarounds usually involve downloading files in advance.

Some firms invest in dedicated site internet connections, which helps considerably. But the cost and logistics of provisioning reliable broadband to a temporary construction site, particularly in early phases before permanent services are installed, can be significant. And even with a decent connection, VPN performance over distance and through firewalls introduces latency that makes interactive file browsing impractical.


The tablet full of downloads

The alternative to remote access is local copies. Before heading to site, you download the drawings you think you will need to a tablet or laptop. The files are available regardless of connectivity, and they open quickly from local storage.

The problems with this approach are predictable. Storage on tablets fills up quickly when you are carrying dozens of high-resolution drawing sheets, specification documents, and submittal packages. A single project can generate gigabytes of documentation. An iPad with 64GB of storage starts to feel cramped after a few projects' worth of downloaded files.

More importantly, downloaded files are snapshots. They reflect the state of the project documents at the time of download. If a drawing is revised after you download it, you are looking at a superseded version and may not know it. The site team and the office team can end up working from different versions of the same document, which is precisely the kind of disconnect that causes construction errors.

Managing which files are current across multiple tablets and laptops is a document control problem in its own right. Someone needs to push updates, or everyone needs to remember to re-download periodically. In practice, neither happens reliably.


What site teams need from their files

The requirements are specific. A site engineer checking a detail during a concrete pour needs to pull up the relevant structural drawing within a few seconds. A superintendent responding to an RFI needs to find the specification clause being referenced. An inspector reviewing a submittal needs to compare what was approved with what has been installed.

These interactions are typically brief and targeted. Someone needs one specific document, or one specific detail within a document, at a particular moment. They are not sitting down for a long design session. They need fast, reliable access to the right file, and they need to be confident it is the current version.

The challenge is that "the right file" is not always easy to identify. Project documentation is extensive and its organisation can be opaque, particularly to people who were not involved in creating the folder structure. Site staff who need to find a specific submittal or a particular drawing detail may not know the file name or the folder path. They know what they are looking for in conceptual terms: "the waterproofing detail at the podium level" or "the approved colour schedule for level 12."


Streaming files without filling up storage

Fabric's cloud drive (https://fabric.so/features/your-cloud) takes a different approach to the remote access problem. Rather than downloading files to a device or connecting to a remote server through a VPN, files are streamed on demand from the cloud. You access a file when you need it, and it does not consume permanent local storage on your device.

This distinction matters for construction site use. A site manager can carry access to the entire project document set on a phone or tablet without worrying about storage limits. There is no need to choose in advance which files to download, no need to manage local storage, and no need to periodically clean up old downloads to make room for new ones.

Because files are accessed from a single cloud location rather than downloaded as copies, the version problem diminishes. When you open a drawing on site, you are looking at the same file that the office team is working with. There is one copy, in one place, accessible to everyone. The drift between site copies and office copies that plagues the download-and-carry approach does not arise.

The trade-off is that you need an internet connection. This is worth addressing directly: Fabric requires connectivity to access files. It does not offer an offline mode. For sites with no cellular coverage at all, this is a limitation. For most urban and suburban construction sites, and increasingly for regional sites, basic cellular coverage is available. The bandwidth required to stream a document for viewing is modest; you do not need a fast connection, just a present one.


Finding files by description rather than folder path

The other persistent friction point for site teams is findability. Office-based staff who created and organised the project files may navigate the folder structure by memory. Site staff often cannot. They know what they need but not where it lives within the folder hierarchy.

Fabric's semantic search (https://fabric.so/features/search) allows you to find files by describing what you are looking for rather than knowing its file name or folder location. A search for "the structural detail for the third-floor beam connection" will return relevant results based on the meaning and content of the files, not just their names.

This is particularly valuable in the field, where searches happen quickly, on a phone screen, often while standing on a scaffold or in a partially enclosed space. Typing a long file path on a mobile keyboard is slow and error-prone. Describing what you need in plain language is faster and more forgiving.

Semantic search also helps when project documentation uses naming conventions that are clear to the design team but opaque to others. A file named "S-301-D42" means something specific to the structural engineer who created it. A site superintendent looking for "the connection detail at gridline 7" should be able to find the same file without knowing the naming convention.


Bringing files together from multiple sources

On many projects, documents are scattered across multiple platforms. The architect's drawings might be in one cloud storage service, the engineer's calculations in another, and the contractor's submittals in a third. The specifications might live on a project management platform, while the meeting minutes are in a shared email folder.

Fabric's connections feature (https://fabric.so/connections) allows you to bring files from Google Drive, Dropbox, and other cloud storage services into a single searchable space. For site teams, this means that a search for a particular document can surface results from across all project sources, rather than requiring you to remember which platform a particular discipline or consultant uses.

This consolidation is especially useful during the construction phase, when the number of parties contributing documents to a project is at its peak. Subcontractors, suppliers, consultants, and the client may all be using different storage platforms. Having a unified view of project documentation, searchable from a phone on site, reduces the time spent hunting for files.


Reviewing and marking up on site

Site inspections generate observations, defects, and queries that need to be linked back to the relevant drawings or specifications. The traditional approach is to mark up a printed drawing, photograph it, and email it back to the office. The markup then needs to be reconciled with the digital file, which is another manual step that can introduce errors or delays.

Fabric's annotation features (https://fabric.so/features/annotations) allow markup directly on files within the platform. A site engineer can annotate a drawing on a tablet, and the annotation is immediately visible to anyone accessing that file. For images and visual documentation, annotations can be drawn directly onto the content. For video recordings of site conditions, timestamps can be added to reference specific moments.

This keeps observations anchored to the documents they relate to, rather than floating in email threads or sitting on printed sheets in a site office filing cabinet.


Using AI to answer project questions

When a site team member needs to understand a specification clause or find related information across project documents, Fabric's AI assistant (https://fabric.so/features/ai-assistant) can help. Rather than manually searching through lengthy specification documents or cross-referencing between drawings and schedules, you can ask a question and receive an answer drawn from the project's documentation.

This is useful for the kinds of quick reference questions that come up constantly on site. What is the specified concrete strength for the podium slab? What finish is called for on the level 3 corridor walls? Which submittal covers the curtain wall gaskets? These questions have definitive answers buried somewhere in the project documentation. Finding those answers quickly, from a phone on a scaffolding platform, saves time and reduces the risk of proceeding on the basis of memory or assumption.


Sharing site documentation back to the office

Communication flows in both directions. Site teams generate documentation that the office needs: progress photos, inspection records, test results, as-built markups. Getting this information from the field back to the project file in an organised way is its own challenge.

Fabric's publish feature (https://fabric.so/features/publish) provides a way to create shareable pages from project content, with link analytics that show who has accessed the shared information. This can be useful for site reports, progress updates, or issue documentation that needs to be distributed to multiple parties. The analytics provide a basic record of who has viewed the content, which is helpful when you need to confirm that a particular notice or report was received.


Planning around the connectivity requirement

Fabric's cloud-based approach eliminates the storage, versioning, and synchronisation problems that come with local file copies. The trade-off is that you need a connection.

For most construction sites in populated areas, this is manageable. Cellular data coverage is widespread, and the bandwidth required to view documents (as opposed to streaming video or making large uploads) is modest. A 4G connection is generally sufficient for pulling up drawings and specifications.

For sites in remote areas with very limited connectivity, you will need to plan accordingly. This might mean downloading critical files before travelling to the site, which brings back some of the version management challenges. It might mean investing in a portable hotspot or satellite internet terminal for the site office. The right approach depends on the project and the location.

The broader trend is clear: cellular coverage is expanding, connection speeds are improving, and the proportion of construction sites with adequate connectivity for cloud-based file access is growing. The offline limitation is real today and worth acknowledging, but it affects a shrinking share of projects.


Smart organisation for project files

Keeping project documentation well organised benefits everyone, but it is especially important for site teams who need to find things quickly under time pressure. Fabric's smart organisation features (https://fabric.so/features/smart-organization) help maintain a coherent file structure without requiring the rigid hierarchical folder systems that tend to become unwieldy as projects grow.

Combined with semantic search, smart organisation means that files can be structured in ways that make sense for the project without sacrificing the ability to find specific documents quickly. A drawing does not need to be in the "correct" folder to be findable; it just needs to be in the system.


Frequently asked questions

Does Fabric work on phones and tablets?

Yes. Fabric's cloud drive is accessible from any device with a web browser and an internet connection, including phones and tablets. Files are streamed rather than downloaded, so they do not fill up device storage.

Can I use Fabric without an internet connection?

No. Fabric requires an internet connection to access files. It does not currently offer offline support. For construction sites with limited connectivity, this is a consideration to factor into your planning.

How much bandwidth does Fabric need to view files on site?

The bandwidth required to stream documents for viewing is modest. A standard 4G cellular connection is generally sufficient for pulling up drawings and specifications. You do not need a high-speed broadband connection.

Does Fabric replace our office file server?

Fabric can serve as your primary file storage through its cloud drive (https://fabric.so/features/your-cloud), or it can work alongside existing storage through its connections feature (https://fabric.so/connections). It connects to Google Drive, Dropbox, and other cloud storage services to provide a unified view of project files.

Can I search for files by describing what I need?

Yes. Fabric's semantic search (https://fabric.so/features/search) lets you find files by meaning rather than file name. You can search for "waterproofing detail at podium level" and find relevant results regardless of the file's naming convention.

Is Fabric a project management tool?

No. Fabric is a cloud drive with semantic search, annotations, and file streaming. It is not project management software, and it does not replace tools used for scheduling, budgeting, or task management.

Can site teams annotate drawings within Fabric?

Yes. Fabric's annotation features (https://fabric.so/features/annotations) allow markup directly on files, including drawing tools for images and timestamped annotations for video and audio. Annotations are visible to anyone accessing the file.

How does Fabric handle large drawing files?

Fabric's cloud drive streams files on demand rather than requiring full downloads. Large CAD drawings and PDF drawing sets can be accessed without consuming local storage on the viewing device.

Can I share site documentation with external parties through Fabric?

Yes. Fabric's publish feature (https://fabric.so/features/publish) lets you create shareable pages with link analytics, so you can distribute site reports, progress photos, and other documentation while tracking who has accessed it.

Does Fabric work with files from different cloud storage services?

Yes. Fabric's connections feature (https://fabric.so/connections) supports Google Drive, Dropbox, and other cloud storage services. Files from multiple sources can be brought into a single searchable space, so site teams do not need to check multiple platforms to find a document.


Related pages

The workspace that thinks with you.

Ready when you are.

The workspace that thinks with you.

Ready when you are.

The workspace that thinks with you.

Ready when you are.