Sending drawings without losing control of them

Sharing a drawing feels like the least consequential thing an architect does. It's a file, it goes to a person, the person opens it. And yet almost every awkward conversation a small practice ends up having — about fees, about scope, about a design turning up on somebody else's plot — starts with a drawing that went to the wrong person in the wrong format at the wrong moment.

The answer isn't paranoia. It's a protocol: a small number of decisions made once, in advance, so that at four on a Friday afternoon you're following a rule instead of exercising judgement.

What each recipient should actually get

Start from what the recipient has to do. A client has to understand and approve. A structural consultant has to build on top of your geometry. A contractor has to set out and price. A municipal office has to check compliance against a byelaw. Four different jobs, and they don't want the same file.

Before anything leaves the studio, strip what shouldn't travel with it. Model space clutter. The previous scheme on a frozen layer. The consultant's XREF you never unbound. Your fee note in a text box on the corner of the sheet. Files carry more than architects think, and a DWG in particular carries a great deal of history.

Why the default keeps failing

The default in most Indian practices is a shared Drive folder, a WhatsApp thread and email for anything formal. That's not a stupid arrangement. It's free, everyone already has it, and it works perfectly well right up until it doesn't.

• A shared link has no end date. It was created for a project in 2024 and it still opens today. Nobody revokes it, because revoking it requires remembering it exists.
• Forwarding is invisible. The client sends the folder to their brother-in-law who is "also building something". You will never know, and you will not find out until you see the plan.
• WhatsApp destroys drawings. Images are recompressed and line weights die. A hairline becomes invisible, a dimension becomes ambiguous, and somebody builds from it anyway.
• There is no record of receipt. Sent is not received, and "I never got it" is unanswerable when the only evidence is a blue tick.
• The wrong revision stays reachable. Drive shows the current file, but the version somebody downloaded in March is still on their laptop, and it looks exactly as authoritative.
• Sharing quietly bypasses the fee. A folder shared at concept stage keeps working through every stage after it, including the ones that have not been paid for.

That last one deserves more attention than it gets, because it's the one with money attached. Plenty of practices have a stage-wise fee schedule and still share a folder that ignores it entirely. The schedule says the working drawings are released at 45%. The folder says they're released the moment they're saved into it.

The title block does more than a watermark

Watermarking gets discussed a great deal and delivers less than people expect. A diagonal "DRAFT" across a plan is easily cropped, frequently ignored, and does nothing whatsoever to a DWG. It deters the casual and inconveniences the honest.

A disciplined title block does far more work. Revision, status, date of issue, the recipient, the project number, and a plain line stating the terms the drawing is issued on. It travels with every print, it survives being photographed, and it's the thing you point at when somebody says they didn't know a drawing was superseded or that it wasn't to be built from.

• Status, in words, large enough to read on a photograph: FOR INFORMATION, NOT FOR CONSTRUCTION, FOR CONSTRUCTION.
• Revision and issue date, so a print pinned to a site wall can be checked against the register at a glance.
• A short rights line, so the licence position is on the drawing rather than only in the appointment letter. What that line should say is covered in who owns the drawings.
• The recipient, where the sheet is issued to one party. It makes a forwarded copy self-identifying.

Expiry and revocation

The only sharing controls that change outcomes are the ones that act on their own. A watermark asks someone not to do something. An expiry just stops working.

So insist on two properties wherever you share from. A link should carry an end date by default, rather than as an option somebody has to remember to set. And access should be revocable after the fact, in a way that reaches the copies already handed out and not just the front door.

That's the reasoning behind expiring share links: a consultant or contractor gets a private link with an expiry you set, revocable at any moment, without you provisioning a login or opening up the rest of the project. The link is served through a short-lived signed URL minted only after the access check passes, so it can't be forwarded to live forever or hotlinked from somewhere else.

The corollary matters as much as the rule. If sharing a set can quietly skip a fee that hasn't been paid, then every share is a decision with money attached and you'll hesitate over each one. When the payment gate travels with the share, sharing goes back to being routine, which is the only way a protocol survives contact with a busy week.

A protocol you can actually keep

None of this requires distrusting your clients, and you should say so to them plainly. Practices that explain the protocol at the outset find that clients read it as competence rather than suspicion. The studio that knows which revision is on site, and can prove it, is the studio people recommend.

It does need somewhere to run from, though. If the drawings live in a folder that was shared in March and has been drifting ever since, none of the six steps above is available to you. That's a question about what the practice runs on, and it's easier to answer before the next project starts than during it.