Improving Project Information and Document Control

Project information does not originate inside your business. It arrives from architects, structural engineers, services consultants, surveyors, certifiers and clients. Each of those parties produces revisions, and each revision has to be incorporated, distributed and confirmed as the version people are working to. You are controlling information you did not create, in a system you do not fully own.

That information changes constantly. A drawing issued at tender is not the drawing issued for construction. A specification revised for a variation is not the specification the subcontractor priced against. RFIs generate responses that alter the design. Site instructions change details. By the time a package reaches site, it may have passed through several revisions, and the question is not whether a document exists but whether the person holding it has the right one.

The information is consumed on site, not at a desk. A foreman standing in the rain with a tablet, a subcontractor who was given a set at tender and never received the update, a site supervisor who last saw the drawings on a shared screen in a meeting — these are the people who build from the document. If the structure does not reach them reliably, they will work from what they have.

And every project starts the structure again from scratch. A new folder, a new sharing arrangement, a new set of permissions, a new way of naming files. The learning does not carry over because there is no standard to carry. Each project becomes its own experiment in document control, and the lessons from the last one are lost.

A drawing is emailed to one person — a project manager, a foreman, a subcontractor's office. It is forwarded, saved locally, printed and pinned to a wall. By the time a revision is issued, the original is still in circulation. Nobody is malicious, and nobody is careless in a way that would be obvious. The system simply has no way of recalling the old version or confirming that the new one has replaced it.

A link is shared that was current when it was sent. The file behind it is updated, but the link still resolves, and the person who opens it does not know whether they are looking at the latest revision or the one that was there when the link was created. SharePoint and OneDrive can solve this, but only if the structure is designed to make the current revision visible and the superseded one clearly retired.

A file is saved locally before a revision. A superintendent downloads a drawing set to a laptop, a tablet or a USB drive so they can work offline or on site. The revision is issued while they are away from their desk. They return and open the file they saved, not the one that was updated. The local copy is the wrong version, and there is nothing in the system that tells them.

A subcontractor works from the set they were given at tender. The tender set was complete and correct at the time. The construction issue has since revised several sheets. The subcontractor was not on the distribution list for the revision, or was on it but never opened it. They build from what they have, because what they have is what they were given.

Rework is the most visible cost. A wall built to a superseded grid line has to be demolished and rebuilt. A service penetration cut in the wrong place has to be patched and re-cut. Concrete poured against an outdated reinforcement detail may have to be removed entirely. The materials, the labour and the programme time are all lost, and the cost falls on whoever is determined to hold the wrong version.

Delay follows rework. The programme slips while the rework is scoped, approved, scheduled and completed. Following trades are held up. The critical path moves. A delay that started with a document control failure becomes a programming problem, and the recovery effort consumes the attention of people who should be building.

Variation disputes are the contractual cost. When the question is who held what and when, the answer depends on records that may not exist in a form anyone can rely on. If the superseded drawing was emailed and the revision was issued by a method that left no auditable trail, the argument is not about the design — it is about who can prove what was in their hands at the time the work was done. Those disputes consume management time, erode relationships and sometimes end in claims that dwarf the cost of the original rework.

None of these costs appear as a line item in a document control budget. They appear as rework, as programme extensions, as variation claims and as disputes. By the time they are visible, the document control failure that caused them is long past.

Every project has one authoritative location for its documents. Not a copy on someone's laptop, not a version forwarded by email, not a set printed and pinned to a site wall. One location, known to everyone on the project, that always holds the current version. A foreman or subcontractor who needs the latest drawing knows where to find it without asking.

The current revision is visible on every file. A person opening a document can see immediately whether it is the current issue or a superseded one, without comparing it against another copy or asking the person who sent it. The revision status is part of the file's identity, not something held separately in a register that may or may not have been updated.

Superseded versions are retained but clearly retired. They are not deleted, because they may be needed for a variation claim, a defect investigation or a contractual dispute. But they are marked, moved or labelled so that nobody mistakes them for the current version. A person who opens a retired drawing knows immediately that it is not the one to build from.

The structure is the same on every project. The same folder layout, the same naming convention, the same permission model, the same approach to external sharing. A project manager who moves from one project to another does not have to learn a new filing system. A subcontractor who has worked with you before knows where things are. The structure is a business asset, not a per-project invention.

And the information is reachable from site on a phone. Not a laptop tethered to site office wifi, not a printed set that lives in the site shed. A person standing at the work face can open the current drawing on the device in their pocket, confirm the detail, and get on with the work. That is what good looks like, and everything else in this discussion is in service of it.

A document structure invented fresh for each project cannot be learned. The first week of every job is spent working out where things are, who has access, what the folders are called and how revisions are labelled. By the time the team has figured it out, the project is already underway and the early documents have already been filed inconsistently. The next project starts the same cycle again.

The same structure every time is what makes it work for people who move between projects. A site supervisor who has used the SharePoint project site template on one job recognises it immediately on the next. A subcontractor who received drawings through a controlled Teams channel last time knows where to look this time. The cognitive cost of finding information drops, and the risk of looking in the wrong place drops with it.

Consistency also makes the business governable. If every project uses the same permission model, you can answer the question of who has access to commercial information across the whole business, not just on one project. If every project uses the same retention approach, you can be confident that superseded drawings are being retired rather than quietly remaining in circulation. A standard that is applied everywhere is auditable. A standard that is invented per project is not.

The objective is not to constrain how projects are run. It is to give every project a running start. The structure is proven once, refined, and then replicated. Each new project inherits the learning from the last, instead of repeating its mistakes.

Construction sites are not offices. Connectivity is variable — a basement car park, a remote subdivision, a high-rise floor where the mobile signal drops out. Devices are mixed: a company-issued tablet, a subcontractor's personal phone, a site office laptop that is shared between three people. The people using them are wearing gloves, standing in weather, and trying to get an answer quickly so they can keep building.

This is why access design matters as much as storage design. A document control system that works perfectly on a desktop in the head office but is unusable on a phone on site has solved only half the problem. The drawing that reaches site late or with the wrong revision is the one that causes rework, regardless of how well the head office system is organised.

Practical access design means the current drawing is available offline or on a weak connection, not only when the site office wifi is working. It means the interface on a phone screen shows the revision status clearly, not buried in a file property that requires three taps to reach. It means a subcontractor can be given access to the documents they need without being given access to the whole project's commercial information.

It also means the device itself is managed. A phone or tablet that is lost, stolen or left in a site shed should not expose the project's drawings, correspondence and commercial details to whoever picks it up. Device encryption, remote wipe and conditional access are not optional extras on a construction site — they are part of making the information reachable without making it exposed.

The following questions are diagnostic. A director or construction manager can answer them without a consultant, and the answers reveal whether the business has a version control problem that is worth addressing before the next project starts.

LOOKUP works on the Microsoft 365 environment around the specialist systems. That means designing SharePoint project sites with a consistent folder structure, revision visibility and permission model that can be replicated across every project. It means configuring Teams channels for project communication so that drawings, RFIs and site instructions are shared through a controlled environment rather than ad-hoc email. It means managing permissions so that external consultants, subcontractors and clients can reach the documents they need without being given access to commercial information they should not see.

It means managed devices — encryption, remote wipe, conditional access — so that the phones and tablets on site can reach project information without exposing it if they are lost or stolen. It means configuring offline access so that a foreman in a basement or a remote site can open the current drawing without a live connection, and sync the latest revision when they return to coverage.

LOOKUP coordinates with estimating, project management and drawing platforms. Microsoft 365 is not a replacement for a construction document management system or a CAD platform. It is the environment that connects those systems to the people who need their output, controls who can reach what, and ensures that the current version is the one that is visible. LOOKUP works alongside those platforms, not instead of them.

The work includes Microsoft 365 environment design, SharePoint and Teams project structure, identity and permissions, device management, and access from site. It also includes managed IT services that keep the environment running, supported and secure across every project and every office.

Construction and property development — the industry page for builders, developers, head contractors, architects, engineers and project teams, covering managed IT, cyber security, Microsoft 365 and AI services.

Securing external collaboration — how to give consultants, subcontractors and clients controlled access to project information without exposing commercial detail or losing control when the project ends.

Building a technology roadmap — what order to do things in, from securing what you have to standardising, automating and preparing for AI.

Frequently asked questions

Sources & Further Reading

The following primary and authoritative sources support the research, guidance and industry context discussed on this page:

Evidence Standard

LOOKUP references recognised industry, government, professional and technology sources when discussing research, regulation and industry trends. Research findings are paraphrased and linked to their original sources wherever practical. LOOKUP's professional observations and recommendations are presented separately from third-party research.

Is everyone on your site building from the current drawing?

If your project information is scattered across email, shared drives and local laptops, the answer is probably no. LOOKUP helps construction and property development businesses build a governed Microsoft 365 environment where the current drawing is visible, reachable from site and controlled. Book a strategy session to assess your current environment and build a practical path forward.