Comparison
A shared folder link vs. a digital permit box
Taping a Dropbox or Google Drive link inside the box is the most common thing builders try before looking for anything else. It's free and everyone already has an account. This page is honest about where that holds up and where it quietly fails on site.
What a shared folder is genuinely good at
In its favour
This is the default for a reason. If your team already lives in Dropbox or Drive, taping a link inside the box is the obvious next step, and for plenty of jobs it's enough.
01
It's already free
If the office already saves plans to a Dropbox or Drive account, there's nothing new to buy and nothing new to cancel. Taping a link inside the box costs a sheet of paper.
02
Nobody has to learn a new tool
The files already live where your team already works. A shared folder doesn't ask anyone to change how the office operates — it just adds a link on a post.
03
You keep full control of the files
It's your account, your storage, your organization. No third party sits between you and the documents, and nothing about the arrangement depends on another company's product staying around.
04
Real version history, if you know where to look
Both Dropbox and Drive keep prior versions of a file. The capability is there — it's just a feature built for an office user, not a sub standing at a post.
05
One folder can do double duty
The same folder that's shared to the site can also be the actual working folder your team edits from, instead of a copy made just for the public.
06
Setup is instant
Right-click, share, copy the link, print it. There's no account to create for the job and no software to configure.
Where it fails on site
Against
None of this is a knock on Dropbox or Drive — they're built to be excellent team file storage. They just weren't built to be handed to a stranger standing outside in the sun with no account and no context.
01
A login wall waiting to happen
If the link isn't set to open for anyone, or a company account defaults to requiring sign-in, whoever scans it gets a request-access screen instead of the plans. On a phone in the sun, that's the whole interaction over.
02
Nothing enforces revision discipline
The folder holds whatever was put in it. Unless someone reliably deletes or renames the superseded sheet on every job, every time, the old and new revisions sit side by side and nobody can tell which is current.
03
Folder sprawl finds every job eventually
Subfolders inside subfolders, a file named 'FINAL v3 fixed used this one.' The link still resolves — finding the actual current sheet inside it is a separate skill from opening it.
04
Links break more often than you'd expect
Reorganize the parent folder, move it into a different workspace, have permissions change upstream, and the link on the placard can stop resolving. Nobody notices until a sub calls asking why it goes nowhere.
05
No sense of whether anyone opened it
Consumer sharing links aren't built to tell you who scanned a QR code and opened a folder. You don't get to know whether the plumber ever actually saw the approved set.
06
A folder browser isn't a job-site page
A shared-folder link opens whatever generic file-browsing UI the provider ships, in whatever order the files were last left. It wasn't designed to be read outdoors on a small screen by someone who doesn't work there.
Side by side
The table
Twelve rows. Three come out even — both need a data connection, neither satisfies a posting requirement, and both let you add a document from off site.
| Aspect | Shared folder link | DryPlans | Edge |
|---|---|---|---|
| Up-front cost | Free, assuming you already have an account and the storage to spare. | Free for one active job site. Pro is $19 a month for 10 of them. | Folder |
| Works with no signal | No — needs a data connection to load, the same as any web page. | No — needs a data connection to load, the same as any web page. | Even |
| Opening the link without an account | Works if it's shared as 'anyone with the link' and stays that way. If not, whoever scans it hits a sign-in or request-access screen instead of the documents. | No login, ever. The page is public by design and never asks for an account. | DryPlans |
| Keeping the current revision obvious | Whatever's in the folder is what's on site. Nothing stops an outdated sheet from sitting next to the current one unless someone removes it by hand. | Hide the old revision and it disappears from the public page immediately. | DryPlans |
| Finding the current sheet on a phone | A generic file browser, sorted however the folder was last left — great in an office, slower standing at a post. | One page, grouped by document type, built to be read outdoors on a small screen. | DryPlans |
| Reliability of the link over time | Can break if the parent folder moves, gets renamed, or permissions change upstream — and nothing on the placard tells you it happened. | One address for the life of the job, set once when the placard is printed. | DryPlans |
| Knowing anyone actually looked | Not built for this. Consumer sharing links don't report who opened them. | A scan count per job site, so you know whether the code is being used. | DryPlans |
| Storage included | Whatever your Dropbox or Drive plan already includes — often generous, and likely already paid for. | Counted per plan, separate from any storage you already pay for elsewhere. | Folder |
| Familiarity | Nearly everyone already has an account and knows the app. | A QR code, which most people scan without being told — but it's a slightly different habit than opening an app they already use. | Folder |
| A required physical permit posting | Doesn't satisfy it and was never meant to — you still post whatever your department requires. | Doesn't satisfy it either. Neither option replaces the posted permit card. | Even |
| Adding a document from off site | Yes — upload to the folder from wherever you are. | Yes — upload from wherever you are and it's on the page. | Even |
| Running several job sites | One folder per job, or subfolders under a parent — organizing them consistently is on you. | Every job gets its own page automatically; Pro covers 10 active sites at once. | DryPlans |
Swipe the table sideways
The honest cost comparison
Money
A shared folder is free if your team is already paying for the storage elsewhere, and for a lot of jobs that's genuinely the end of the analysis. A small crew running one site, disciplined about deleting old files, with subs who already have accounts — that setup works and doesn't need to change.
The cost shows up as friction rather than a line item: the sub who hits a sign-in screen and calls instead, the ten minutes spent hunting through subfolders for the current set, the link that quietly broke last month because someone reorganized the parent folder. None of that appears on an invoice, which is exactly why it's easy to keep paying.
DryPlans is free for one active job site, which is enough to test whether that friction actually goes away before paying anything. Pro is $19 a month for 10 active sites. Archived jobs stop counting toward the limit and their public pages keep working.
Who should use which
Verdict
Keep the shared folder and skip this
- You run one job at a time and the sub list barely changes between jobs.
- Everyone who needs access already has an account in your workspace.
- Someone reliably cleans up superseded files the moment a revision lands.
- The link has never broken and nobody has ever hit a sign-in wall.
- Cost is the deciding factor and the friction hasn't cost you real time yet.
Worth trying DryPlans
- Subs and inspectors aren't in your Google or Dropbox org and keep hitting login prompts.
- You've found an outdated sheet still sitting in the folder next to the current one.
- A placard link has broken before and nobody noticed until someone called.
- You want to know whether the code is actually being scanned.
- You're running enough sites that keeping folder structure consistent has become its own job.
Most builders end up running both
In practice
These solve different problems. The shared folder is your team's working file — the place plans actually get edited, organized, and archived internally. It doesn't have to stop being that.
The placard on the post is for a different audience: a sub or inspector who has never been added to your Dropbox, doesn't want an account, and just needs the current set on a phone in the sun. Point it at a public DryPlans page instead of the internal folder, and the two stop competing — one is where your team works, the other is what the site sees.
That split also fixes the specific failure this page spends the most time on: nobody outside your organization ever hits a login wall, because the public page was never behind one.
What we are not claiming
Limits
- That Dropbox or Google Drive are bad products. They're excellent at what they're built for — team file storage and collaboration — which is a different job than a public, no-login page for a job site.
- That every shared folder fails. Small, disciplined crews run this way for years without a problem. We're describing where it tends to break, not asserting that it always does.
- That it satisfies a posting requirement. It does not, and neither does DryPlans.
- That we have a customer count, a star rating or a case study to show you. When there are real ones they will appear here, with names on them.
Questions builders ask
FAQ
- Isn't a shared Dropbox or Drive link basically free already?
- Functionally, yes, if your team already pays for the storage. DryPlans is also free for one active job site, so the honest comparison isn't price on day one — it's what happens once a login wall, a broken link, or an out-of-date sheet costs you an afternoon.
- What if my subs already have the Drive link?
- Keep using it internally — nothing about DryPlans requires you to stop. Plenty of builders keep the working folder for their own team and point the public QR placard at a DryPlans page built for people who aren't in that folder.
- Does a shared folder link satisfy a physical posting requirement?
- No, and neither does DryPlans. Most building departments require the permit card itself to be physically posted and visible at the site. Rules vary by jurisdiction and permit type — check with your building department before you take anything down.
- What happens if someone reorganizes the folder later?
- With a shared-folder link, the placard can silently stop resolving — nobody finds out until a sub calls. A DryPlans job page keeps one address for the life of the job regardless of how you reorganize documents inside it.
- Do subs or inspectors need a Google or Dropbox account to open a DryPlans page?
- No. The page is public by design and never prompts for a sign-in, which is the specific failure mode a restricted shared-folder link can hit.
Keep reading
Elsewhere
Comparison
vs. the plastic permit box
The original job-site standard. Needs no phone and no signal — here's what it costs you once the weather turns.
Demo
See a real job page
The page a sub actually lands on after scanning. No login, no sign-up, no sales call.
Pricing
What it costs
Free for one active job site, $19 a month for 10. Every plan includes placards and unlimited scans.
Guides
Job-site document guides
What belongs on site, how to keep a revision from being built twice, and how to set a job up in ten minutes.
Comparing against something else? The other common answer is the plastic permit box on the post, which wins when there's no signal and loses the moment paper gets wet.
Give the site a page instead of a link
Create the job, print the placard, and stop fielding calls about login screens and old files. One active job site is free and there is no card to put in.
No card required · See the plans