Your submittals and RFIs are buried in email

Construction administration runs on two document types more than any other: submittals and requests for information. Every material approval, every clarification about a detail, every product data sheet and shop drawing passes through this machinery. And in most firms, that machinery is email.

The volume is staggering. A mid-size commercial project can generate hundreds of submittals and dozens of RFIs over its lifetime. Each one involves multiple parties: the contractor sends a submittal, the architect reviews it, the engineer weighs in, the architect returns it with a stamp, and the contractor distributes the approved version to the relevant subcontractors. Every step produces an email. Every email has attachments. And every attachment lives in someone's inbox, filed according to whatever personal system that person happens to use.

The inbox as filing cabinet

Email was never designed to be a document management system, yet that is precisely how most construction teams use it. A project architect's inbox becomes the de facto record of every submittal review. An engineer's sent folder holds the only copy of their comments on a hardware schedule. The project manager's email threads contain the approval chain for a curtain wall system that will cost six figures to install.

This arrangement works tolerably well when the project is small and the team is tight. Everyone knows who reviewed what, and finding a specific submittal means scrolling back a few weeks. But projects grow. Teams change. And the problems compound.

When a contractor asks whether a particular tile was approved, someone has to search through months of email to find the response. The search might turn up three threads: the original submittal, a resubmittal after the first was returned for revision, and the final approval. Figuring out which version was approved, and whether the approval had conditions attached, requires reading through all three threads and checking the attachments on each. If the person who handled the review has left the firm, the search becomes archaeological.

The cost of scattered records

Disputes in construction often come down to documentation. When a subcontractor installs a product that differs from what was specified, the question becomes: was it approved? If the submittal record is scattered across inboxes, answering that question takes hours rather than minutes. In some cases, the answer is simply lost.

The financial consequences are real. A missing submittal approval can leave a firm exposed during a claim. An RFI response that contradicts the drawings, buried in an email thread nobody can find, can become a liability. Construction lawyers know this; they ask for email records precisely because they know how disorganised those records tend to be.

Beyond disputes, there is the daily friction. A site superintendent needs the approved shop drawings for a steel connection. The drawings were attached to an email sent to the project architect four months ago. The superintendent was copied on the email, but has since changed phones and lost access to the old email archive. So they call the office, someone searches, someone forwards the attachment, and twenty minutes have passed for a document that should have been accessible in seconds.

Dedicated platforms and their trade-offs

The construction industry has recognised this problem, and a number of platforms have emerged to solve it. Procore, PlanGrid (now Autodesk Build), Submittal Exchange, and others offer structured submittal and RFI workflows. They provide numbering systems, approval chains, automatic logs, and centralised document storage. For large projects with the budget to support them, these tools are excellent.

But they come with weight. Licensing costs can be substantial, particularly for smaller firms or those working on projects where the owner has not mandated a specific platform. The learning curve is real; getting an entire project team, including subcontractors, to adopt a new system mid-project is a considerable undertaking. And for firms that work on a mix of project sizes, maintaining subscriptions to enterprise construction management software for every project may not make financial sense.

There is a middle ground that many firms occupy, often without naming it: they need better document access and search without a full construction management platform. They need to find submittals quickly, share approved documents reliably, and maintain a record that does not depend on any single person's inbox.

Centralising documents without the overhead

Fabric approaches this problem from the document side rather than the workflow side. The cloud drive at https://fabric.so/features/your-cloud provides a place to store submittal and RFI documents that is accessible to the entire team without consuming local storage on anyone's machine. Files stream on demand, so a 200-page submittal package does not need to download fully before someone can check a single page.

The organisational structure can be as simple or as detailed as the project requires. A folder per CSI division, a folder per submittal number, a flat collection with consistent naming, whatever suits the team's habits. The point is that the documents live in one place rather than in fifteen inboxes.

This is a deliberate trade-off. Fabric does not provide submittal workflows, RFI numbering sequences, or automated approval routing. Those features belong to dedicated construction management platforms, and firms that need them should use those platforms. What Fabric provides is a lighter layer: a place for documents to live, a way to find them, and a way to share them.

Finding documents by description

The semantic search feature at https://fabric.so/features/search changes the way teams locate construction documents. Instead of searching by submittal number (which requires knowing the number) or by file name (which requires consistent naming conventions that rarely survive contact with a real project team), semantic search lets people describe what they are looking for.

A search for "approved ceiling tile for the second floor lobby" will surface relevant documents even if the file is named "SUB-0847-Rev2-Armstrong.pdf". A search for "the RFI about the waterproofing detail at the plaza level" will find that document regardless of how it was titled or where it was filed. This is particularly useful for team members who joined the project mid-stream and do not have the institutional memory of how documents were organised.

For construction administration, where the same material might be referenced by a product name, a specification section number, a submittal number, and a colloquial description ("the grey tile"), this kind of search is more forgiving than exact-match alternatives.

Reviewing and annotating in place

Submittal review involves markup. Architects stamp submittals, add comments, circle items that need revision, and note conditions of approval. Traditionally, this happens on printed copies or in PDF markup tools that may or may not preserve annotations when the file is forwarded.

Fabric's annotation features at https://fabric.so/features/annotations allow reviewers to mark up PDFs directly. Comments can be placed on specific pages, and the annotations stay with the document. When the reviewed submittal is shared back to the contractor, the markup is part of the record.

This is simpler than a full submittal review workflow, and that simplicity is intentional. For firms that do not need a formal digital stamp and routing process, the ability to annotate a PDF and share it covers the essential need: communicating review comments clearly and keeping them attached to the document they reference.

Sharing approved documents cleanly

One of the persistent frustrations in construction administration is sharing approved submittals with the people who need them. The approved shop drawing needs to reach the fabricator, the site superintendent, and sometimes the owner's representative. Forwarding email attachments works, but it creates multiple copies with no way to ensure everyone has the current version.

The publish feature at https://fabric.so/features/publish allows teams to create shareable pages with approved submittal documents. A published page can contain the approved submittal, any relevant annotations, and supporting documents. The link can be shared with anyone who needs it, and the analytics show whether recipients have viewed the documents. When an approved submittal is revised, the published page can be updated, and everyone with the link sees the current version.

This does not replace the formal transmittal process that some projects require, but it provides a reliable way to share documents without the version confusion that comes from emailing attachments back and forth.

Connecting existing storage

Many construction teams already have documents spread across Google Drive, Dropbox, or other cloud storage services. Fabric's connections feature at https://fabric.so/connections can bring those existing repositories into one searchable view. Rather than moving everything to a new location, teams can connect their current storage and gain the benefit of unified search across all of it.

This is useful for firms that inherit document sets from other teams or that work with consultants who use different storage platforms. The RFI responses from the structural engineer on Dropbox and the submittal logs from the MEP coordinator on Google Drive become searchable from one place.

What Fabric does and does not do

Clarity about scope matters when discussing construction document management. Fabric is a document storage, search, and sharing tool. It handles the "where is that document and how do I get to it" problem well.

It does not handle submittal workflow automation, RFI tracking with sequential numbering, spec section linking, or the other structured processes that platforms such as Procore provide. It does not generate submittal logs or track response times. It does not integrate with construction scheduling tools.

For firms that need those capabilities, the dedicated platforms remain the right choice. For firms that need to get their submittals and RFIs out of email and into a place where anyone on the team can find them, Fabric handles that with considerably less setup and cost.

The AI assistant at https://fabric.so/features/ai-assistant can help team members locate documents through conversational queries, which can be useful when someone is on site and needs a quick answer about whether a particular product was approved. Smart organisation at https://fabric.so/features/smart-organization helps keep the growing collection of project documents structured without requiring constant manual filing.

Frequently asked questions

Can Fabric replace Procore or PlanGrid for construction document management?

No. Fabric is a document storage, search, and sharing tool. It does not provide submittal workflows, RFI numbering, automated approval routing, or the other structured features that dedicated construction management platforms offer. It solves the document access problem, which is a different (and often complementary) problem.

How does semantic search help with construction documents?

Semantic search at https://fabric.so/features/search finds documents based on meaning rather than exact keywords. You can search for "approved light fixture for the conference rooms" and find the relevant submittal even if the file name contains only a submittal number and manufacturer code. This is useful on projects where naming conventions are inconsistent or where team members are unfamiliar with the filing system.

Can I annotate submittal PDFs in Fabric?

Yes. The annotation features at https://fabric.so/features/annotations allow you to mark up PDFs with comments and drawings. The annotations stay with the document and are visible when the file is shared.

Does Fabric support offline access to construction documents?

No. Fabric requires an internet connection to access files. For site visits where connectivity is unreliable, you would need to download relevant documents beforehand.

How large can submittal files be in Fabric's cloud drive?

Fabric's cloud drive at https://fabric.so/features/your-cloud is designed to handle large files, including multi-page submittal packages and high-resolution shop drawings. Files stream on demand, so you do not need to download an entire package to view a single page.

Can I share approved submittals with external parties like subcontractors?

Yes. The publish feature at https://fabric.so/features/publish lets you create shareable pages with submittal documents. You can share a link with subcontractors or other external parties, and the link analytics show whether they have viewed the documents.

Can Fabric connect to documents already stored in Google Drive or Dropbox?

Yes. The connections feature at https://fabric.so/connections lets you link existing cloud storage accounts so that documents stored there become searchable alongside files stored directly in Fabric.

Is Fabric suitable for very large construction projects?

Fabric works well as a document access and search layer for projects of any size. However, very large projects with complex submittal workflows and formal RFI tracking requirements will likely need a dedicated construction management platform for those processes, potentially using Fabric as a complementary tool for document search and sharing.

How does Fabric handle version control for resubmittals?

Fabric stores files as they are uploaded, and you can organise revisions using folders or naming conventions. It does not have built-in version tracking tied to submittal numbers the way a dedicated construction management platform would. For formal version control of submittals, a dedicated platform remains the better choice.

Can the AI assistant help find specific construction documents?

Yes. The AI assistant at https://fabric.so/features/ai-assistant can respond to conversational queries about your stored documents. You can ask it to find a specific submittal or RFI, and it will search across your stored files using semantic understanding of your query.

Related pages

• https://fabric.so/features/your-cloud

• https://fabric.so/features/search

• https://fabric.so/features/annotations

• https://fabric.so/features/publish

• https://fabric.so/connections

• https://fabric.so/features/ai-assistant

• https://fabric.so/features/smart-organization