How to Share Blueprints with Subcontractors Without Logins
Email bounces on 40MB plan sets. Drive needs an account. Texting screenshots leaves you blind. Here's the cleanest way to put blueprints on a sub's phone in 60 seconds.
Answer summary
The best way to share blueprints with subcontractors who will not create logins is to send each trade a private, per-recipient SMS magic link that opens the current PDF plan set in a mobile browser and keeps the site address, scope of work, and lockbox or garage code beside the drawings. Email attachments are familiar but break on large plan sets, forwarded files, stale versions, and permanent copies; Drive or Dropbox folders handle size but add account friction and folder confusion; screenshots are fast but lose zoomable detail; full project-management suites are powerful but ask one-off subs to install and learn another app. A magic-link workflow is the cleanest fit when the GC needs fast delivery, revocation, read receipts, offline access after first open, and enough context for a sub to show up ready to work.
You're a residential GC. You just got the latest set of plans from the architect — 12 sheets, 47 MB, PDF. By 7 AM tomorrow, four subs need to see them: the framer, the electrician, the plumber, and the HVAC guy. None of them will install an app.
Below: the five practical ways to do this, the trade-offs of each, and the one that actually scales when you're running more than two jobs at a time.
The five methods, ranked
#1 Email attachment
What works
- Universally familiar.
- No new tool to learn.
What breaks
- Gmail caps attachments at 25 MB. A full residential plan set is 30–80 MB.
- Subs forward and lose track of which version is current.
- No revocation — the PDF lives on their device until they delete it.
- No idea who opened it.
Verdict
Fine for a single sheet. Fails for plan sets.
#2 Shared Google Drive / Dropbox folder
What works
- Handles any file size.
- Free.
What breaks
- Subs need a Google/Dropbox account, or you mark folders public — which leaks the link.
- Subs forward the share link to other subs.
- No project context: just files in folders.
- No lockbox-code card, no address, no scope of work.
- Slow offline performance when subs lose signal in basements.
Verdict
Workable for tech-friendly subs. Mostly ignored by field trades.
#3 Text screenshots
What works
- Fast for the GC.
- Subs always open texts.
What breaks
- Screenshots lose the vector detail subs need for measurements.
- You can't zoom into a screenshot the way you can a PDF.
- No version control — sub holds the screenshot from week 2 in week 6.
- No revoke.
Verdict
Last resort. The thing you fall back to when everything else fails.
#4 Project management suite (Procore, Buildertrend, Fieldwire)
What works
- Powerful for office workflows.
- Full audit log.
What breaks
- Subs must download the app and create an account.
- Most field trades won't do it.
- Per-seat pricing adds up fast.
- Built for office, not job-site UX.
Verdict
Best for your back office. Rarely adopted by subs.
#5 Magic-link share (SubShare)
What works
- Sub gets a text with a link. Tap → see plans. Zero setup.
- Each link is per-sub and instantly revocable.
- Plans are cached on the sub's device for offline use.
- Includes the lockbox code, site address, and scope of work alongside the plans.
- See who opened the link and when.
What breaks
- Not a replacement for a full project management suite.
- Designed for the share-with-subs workflow only.
Verdict
The cleanest fit when the workflow is just "get plans + access info onto the sub's phone."
What we'd actually do
If you're running 1–2 jobs and your subs are tech-comfortable, a shared Drive folder works. If you're running 3+ jobs with rotating subs, the friction of accounts and folder navigation outweighs the cost of a purpose-built tool.
For GCs who want zero adoption friction — text a link, sub taps, sub sees plans, sub gets the lockbox code, GC sees a read receipt — a magic-link tool is the cleanest fit. It's what we built SubShare to do.
How to share a plan set by magic link, step by step
Here's the entire workflow in SubShare, start to finish — it takes about 60 seconds per project:
- 1
Create a project and upload the plans. Upload the PDF plan set — full multi-sheet sets are fine; there's no email-style attachment limit.
- 2
Add the site info subs actually need. The site address, the lockbox or garage code, and the scope of work — so everything lives in one place instead of a text thread.
- 3
Add each sub by name and phone number. Each sub gets their own private, revocable link — not a shared one.
- 4
Send — the sub taps the SMS link. They see the plans, address, and code in their phone browser. Plans cache on their device after first open, so they work offline. When the job ends (or a sub does), revoke their access in one click.
Worried about what happens if a link gets forwarded, or how revocation actually works under the hood? We answer that honestly in the magic-link security FAQ.
Frequently asked
What's the maximum file size I can email to a subcontractor?
Gmail caps attachments at 25 MB. Outlook caps at 20 MB. A full residential plan set is usually 30–80 MB. So email fails for anything beyond a single sheet. Use a link-based share instead.
Can I share blueprints with a subcontractor without making them sign up for anything?
Yes. A purpose-built magic-link tool (SubShare is one) sends the sub a text with a link. They tap it and see the plans in their phone browser. No account, no password, no app download.
Is sending blueprints via SMS link secure?
Each link is unique, signed, and revocable in one click. That is more secure than emailing a PDF (which never expires) or putting plans in a shared Drive folder (which the sub can forward).
What happens to the plans when the job ends?
On a link-based system you revoke access in one click and the cached copy on the sub's device stops working on the next attempt to view. On email or Drive, the file lives on their device forever.
Sources & notes
- Gmail's 25 MB attachment cap is documented in Google Workspace Help; Outlook.com's attachment limit is approximately 20 MB.
- The 30–80 MB range for a full residential plan set is typical for architectural PDF exports, not a fixed standard — your sets may vary.
- On why app-based methods fail with field trades: the annual JBKnowledge Construction Technology Report surveys consistently rank field-staff adoption among the top barriers to construction tech rollout. Specific comments on sub behavior here are internal observations from SubShare's work with general contractors.
About the author
James M. · Owner/Project Manager, JJB General Contractors
James M. is the owner and project manager at JJB General Contractors, where he runs jobs and coordinates subcontractors on site every day. That hands-on field perspective shapes what SubShare writes about getting plans, lockbox codes, and job info to the trades.
Connect with James M. on LinkedIn →Ready to stop texting passwords?
Free for 3 projects. No credit card. 60-second setup.