How to Share Project Plans With Subcontractors Without Opening the Whole Folder

When you share project plans with subcontractors, the easy mistake is sending a link from wherever the files already live. That folder may sit beside estimates, contracts, other projects, internal notes, or a newer drawing set that has not been issued.

The safer workflow is simple: create a separate external workspace, put only the material that recipient needs inside it, choose whether they can view, edit, or upload, and test the link as an outsider. The software matters, but the folder boundary matters first.

This guide uses Microsoft 365 and common construction platforms as examples. The same questions apply in another system: who can open it, what can they do, which version do they see, and when does access end?

Start with the job the link must do

"Send the plans" can mean three different things. A subcontractor may need to view an issued plan set, work with your team on a live document, or upload a submittal, photo set, quote, or closeout package. Those jobs should not receive the same permission.

For an issued package, view access is usually enough. For a document that both companies must change, use an edit space with version history and a named owner. For incoming files, use an upload-only request when the platform supports it. Granting full folder edit because it is convenient gives the recipient far more power than the task requires.

Also decide whether the link should always show the newest version or preserve the exact package sent that day. A living link can keep the field current. A fixed issue package can preserve what was distributed for a particular decision. The project manager should name which behavior is intended.

Share project plans with subcontractors from a separate workspace

Microsoft's OneDrive sharing guide gives the most useful structural advice in this whole topic: if a recipient should see only certain files, put those files in a separate folder and share that folder.

For an active job, the external workspace might contain a current issued-plan folder, a clearly labeled reference folder, and a separate upload destination. Internal estimating notes, bid comparisons, payroll, contracts, and unrelated projects stay elsewhere. Do not rely on a recipient to ignore material they should never have received.

Keep folder names plain. Include the project, package purpose, and issue date where that helps. If a folder contains working documents rather than issued documents, say so. A file called FINAL-v7-new.pdf is a process problem no permission setting can solve.

For broader construction technology, use the platform that already owns the project record when it gives you the right controls. Creating a second unofficial file system can make version confusion worse.

Choose recipient identity before convenience

In Microsoft 365, a Specific people link limits use to the people named in the invitation, subject to any access they already hold elsewhere. The recipient may need to sign in or verify identity under the tenant's guest-sharing settings. An Anyone link trades that accountability for less friction. Whoever receives a forwarded Anyone link can use it.

Microsoft's external-sharing guidance says authenticated guests are the better choice for sensitive or proprietary information, while Anyone links cannot reliably tell you who has access. That does not make a named link a secrecy guarantee. An authorized viewer may still download when allowed, take a screenshot, photograph the screen, or redistribute information outside the platform.

Autodesk Docs makes the same public-link tradeoff explicit. Its sharing documentation says anyone who receives a public link may access, download, or further share the content. Public links can expire and be revoked, but they are still public links.

The safest shared folder contains nothing you would have to explain if the link reached one person too many.

View, edit, and upload are different permissions

View access is a good default for issued plans. If the platform offers a download block, use it only when online viewing is workable. Do not describe it as perfect data-loss prevention. Platform, file type, app behavior, and a viewer's ability to capture what is on screen all limit the promise.

Edit permission is much broader. Microsoft says an editor of a shared folder may copy, move, rename, share, and delete items in that folder. Use it for a real collaboration area, not the issued set. Keep one person accountable for changes and confirm that version history is on.

For incoming documents, Microsoft's file-request feature lets a recipient upload without seeing, editing, downloading, or deleting the destination contents. There is a catch: anyone with that request link can upload, and a name typed by an unauthenticated sender is not verified identity. Match a sensitive submission through a separate known contact path.

Construction platforms offer their own permission models. Autodesk can grant folder access by user, role, or company. Procore's Documents permissions depend on the user's project-tool access and the private folder or file settings. Creating a folder with a promising name does not make it private by itself.

Decide what happens when a drawing changes

A subcontractor needs to know whether the link opens the package as issued or the newest current file. Autodesk public sharing lets the sender choose a version fixed at the time of sharing or always the latest current version. That is an operational decision, not a cosmetic setting.

For a live folder, keep the current file in one predictable place and use the platform's version history instead of appending random suffixes. Microsoft's version-history guide says OneDrive and SharePoint can restore earlier versions of Microsoft 365 files, PDFs, CAD files, photos, videos, and other file types.

Version history helps with mistakes. It is not the independent backup or the contractual record. Retention depends on the platform and configuration, and a formal issue may need its own fixed package or transmittal under the project's document-control rules.

Test how you share project plans with subcontractors

The owner of a folder often sees more than a guest, so opening your own link proves very little. Use a controlled external test account that has no other project access. Do not test with a real subcontractor's identity or ask someone to expose their password.

Check these behaviors before distribution:

• Can the test recipient browse above or beside the intended folder?
• Can they see only the right project and package?
• Can they download, edit, rename, delete, or reshare?
• Does an upload request hide existing files?
• Does a forwarded named invitation fail for an uninvited test user?
• Does the expiration or revocation setting behave as expected?

Open several file types, including a large plan sheet from a normal field connection if practical. A secure link that nobody can load in the field will push people back to email attachments and personal file apps.

Review access while the job is active

Access should change with scope. Review it when a subcontractor is awarded, when its package finishes, when a superintendent changes, and when the project moves from construction to warranty. Microsoft provides Manage Access to remove a person or link, and site administrators can generate a sharing report showing files, users, permission types, and links.

Assign one project owner to run that review. IT can show the permissions, but the project manager knows whether the concrete sub still needs the current civil sheets or whether a consultant's work is over.

At final completion, move to the separate project-closeout process for archive, ownership, service cancellation, and warranty exceptions. Active collaboration and final retention are connected jobs, but they are not the same job.

Give the recipient one clean door

A good sharing setup is boring. The subcontractor opens one known link, sees the current material for its package, and has only the actions the work requires. The project team can identify every outside person with access and remove that access without reorganizing the company library.

GTZ Integrations can help Southern Colorado contractors structure Microsoft 365 and project access as part of managed IT. The result should make collaboration easier for the field while keeping internal material out of the shared path.