A SharePoint consultant for construction companies who starts with the drawing set and the RFI log

Why a job outgrows its folder before the slab is poured

The pattern is the same at almost every contractor we scope. There is a share with a folder per job, a folder tree inside it that was copied from the last job and then modified, a “Drawings” folder containing three revisions and a subfolder called “OLD”, and an RFI log in Excel that one project engineer maintains and everyone else asks about. It works while one person holds it in their head. It stops working the moment a foreman needs to know whether the sheet on the plan table is current, a sub asks for the latest addendum, or the owner asks for a closeout package for a job that finished eighteen months ago.

None of that is a discipline problem. A folder path is a location, not a record: it cannot carry a revision, a status, a due date or a permission boundary that survives someone dragging a file. The work is making the things a construction business already talks about — the job, the drawing set, the RFI, the submittal, the closeout package — into objects the platform understands, so the answers come from the system instead of from the person who set the folder up.

This page covers the document and collaboration half of a construction Microsoft 365 build. The other half — capturing what happens in the field on a phone — is a different engagement: site inspections, punch lists, daily logs and crew timesheets belong with our Power Apps consultant for construction companies service, which builds offline-capable field apps. The two fit together, and most contractors do the document side first, because an app that files its output into an unstructured share has just automated the mess.

What a contractor’s vocabulary becomes in SharePoint

This is the translation table we scope against. Your build takes the rows that match how you run work — a specialty trade running forty service jobs a month and a GC running four ground-up projects land in very different places — but the conversation is the same every time.

Version control that answers “is this the current sheet?”

Document control is the part contractors feel first, and it is mostly configuration rather than heroics. Versioning is enabled per library, and Microsoft’s guidance on enabling and configuring versioning (opens in new tab) covers the settings that matter here: major versions only versus major and minor drafts, whether draft revisions are visible to everyone, and whether check-out is required before editing. Requiring check-out matters more in construction than in most industries, because CAD and PDF files do not co-author the way a Word document does — two people editing the same DWG simply overwrite each other.

Version history is not free storage, and pretending otherwise is how a tenant fills up. Microsoft’s documentation on version history limits (opens in new tab) explains that limits can be set at organization, site or library level, either automatically or manually as a version count with an optional expiration period, and that content under a retention policy or hold is exempt from trimming until the retention period ends. For a drawing library that receives a hundred sheets per issue, those settings are a real decision, and we make it explicitly in the scope rather than leaving the default in place.

Around that, the working rules are ordinary information architecture: one library is the issued set and everything else references it, revision lives in a column so a view can show only what is current, superseded sheets get a status rather than a delete, and the link a superintendent has bookmarked always resolves to the current file. Where you need the question and the answer to travel together — an RFI, a submittal package, a change order — the container is a document set, which Microsoft describes in its introduction to document sets (opens in new tab) as a group of related documents managed as a single entity, with shared metadata applied across everything inside it and a welcome page summarising the set.

Provisioning the same project site for every job

The second thing contractors ask for is consistency: every job set up the same way, without a project engineer rebuilding it from a memory of the last one. SharePoint does this with site templates and site scripts. Microsoft’s site template and site script overview (opens in new tab) describes the mechanism: a script is a JSON list of actions — create these libraries, add these columns and content types, apply this navigation, set external sharing, add these groups — that runs when a site is created, and can even trigger a Power Automate flow for anything the built-in actions do not cover. Scripts are non-destructive and can be re-run, which is how a change to the standard reaches sites that already exist.

Two constraints belong in the plan rather than in a surprise later. Microsoft documents a tenant limit of 100 site scripts and 100 site templates, so the design is a small number of parameterised templates — ground-up, tenant improvement, service work — and not one per client. And provisioning is worth automating end to end only when the trigger exists: when a job number is created in your accounting or ERP system, a flow creates the site, names it, applies the metadata and adds the project team. Wiring that trigger is Power Automate approval and provisioning workflow work, quoted alongside the SharePoint build when it is worth doing.

Site sprawl is the honest risk on the other side. A site per job is clean while jobs are large and few; at forty service jobs a month it produces a governance problem nobody has time for. The usual answer for high-volume work is a site per division or region with a document set per job, which keeps the metadata and the closeout behaviour while collapsing the number of sites to govern. We pick based on job volume, job duration and who needs to be let in.

Letting subs and the design team in without opening the tenant

Construction is unusual in how much of the document flow crosses the company boundary: architects, engineers, owners, subs and suppliers all need part of the set and none of them should see the rest of your business. Microsoft’s external sharing documentation (opens in new tab) sets out the model: sharing is controlled at the organization level and then per site, a site can never be more permissive than the tenant setting, and guests can be required to sign in with their own account rather than receiving an anonymous link.

Configured properly, that produces the behaviour a project manager wants. One project site allows named guests while every other site stays internal. A sub sees the current drawings and their own submittals, not the buyout file or the other trades’ pricing. Access is removed when the trade demobilises, and the audit log records who opened what — which matters more than anyone admits until there is a dispute about whether an addendum was issued. We also set the boring guardrails at the same time: link defaults that do not silently create anonymous links, expiry on guest links, and a review of which sites are allowed to share externally at all.

Closeout, warranty and how long you keep it

Closeout is where document control either pays for itself or embarrasses you. The package the owner is owed — as-builts, O&M manuals, warranties, test and balance reports, permits, lien releases — is assembled far more cheaply as a document set that fills up while the job runs than as an archaeology exercise three weeks after substantial completion. Making the job’s status a real field is what enables the rest: when it flips to closed, the handover copy is produced, the library drops to read-only for everyone who no longer needs write access, and a retention label is applied.

Microsoft’s documentation on retention policies and retention labels (opens in new tab) covers the distinction that matters: a policy applies broadly to a location, while a label attaches to the content itself and travels with it. Contractors generally need both — a baseline across project sites, and labels for the categories your schedule treats differently, since project records, safety records and employment records rarely share a period.

A necessary line: this is configuration work, not legal advice. Retention periods for construction records depend on your contracts, your insurer, your state’s limitation and repose periods and your own counsel’s reading of them — we do not set them and we do not opine on them. You decide the schedule; we configure the tenant so the schedule is actually enforced, and we document what was configured so your risk manager can review it. Anyone selling you a compliance guarantee attached to a SharePoint build is selling something they cannot deliver.

Where SharePoint stops and a construction platform starts

Plenty of contractors already run Procore, Autodesk Construction Cloud, Newforma or similar, and the honest question is not which tool wins but which documents belong where. We do not resell any construction platform and take no commission either way. The pattern that holds up: the construction platform is the system of record for the drawing set, RFIs and submittals on projects that use it, and SharePoint owns everything the platform was never meant to hold — contracts and subcontracts, prequalification and insurance, safety and training records, estimating and buyout files, HR and equipment documents, and the jobs too small to justify a platform seat.

Two practical notes. Very large model, point-cloud and scan files are a poor fit for library sync and belong in the platform or a dedicated store; SharePoint holding a link to them is usually the right answer. And where both systems are in play, decide the boundary explicitly and write it down — the failure mode is not choosing wrong, it is having drawings in both places with no rule about which is current.

Who this fits

General contractors and specialty trades roughly between fifteen and three hundred people, already paying for Microsoft 365, still running jobs off a server share or a tangle of OneDrive folders. The trigger is usually one of four things: a dispute where nobody could prove which drawing was issued when, an owner or auditor asking for a closeout package that took three weeks to assemble, a server refresh quote, or a new project executive who will not accept “it’s in the job folder” as an answer. It is a poor fit for contractors who have not settled how jobs are numbered, because structure built on an undecided convention gets rebuilt.

This page is the construction-shaped version of our wider SharePoint intranet and document management consulting, which covers intranets, governance and migration across any industry — same engineering standards, different vocabulary. The same exercise for practices that organise around a client and a matter is our SharePoint consultant for law firms engagement. If the job files are still on a file server, sequencing matters, and our file server to SharePoint migration playbook explains why the structure gets designed before anything moves. Once the documents carry job metadata, the reporting side gets easier too — job cost, WIP and change-order dashboards are what our Power BI consultant for construction engagement builds on that data. We work with contractors in all US states remotely from our Orange County, CA base.

What the engagement covers

Three shapes cover most requests from contractors. Every fee is fixed and put in writing after your free consultation — the table shows scope and typical timeline, because an honest number needs to see your job volume, your current share and your licence position first.

Whatever the shape, you own everything: the sites, the templates, the metadata, the scripts and the documentation stay in your Microsoft tenant from the first day, and nothing we build depends on us to keep running.