Architects should attach only what someone needs to read on their own, like a single sheet, a sketch or a marked-up detail. A full drawing set goes as a link to a dated issue folder. Put a transmittal in the email body saying what’s in the link, which revision it is and why it’s going. Put the project number and revision in the subject line and the filename. Then file what arrives to the project record the day it lands, with the email that carried it. That’s the whole answer. The rest of this page is the detail behind each step, for a small practice running projects out of one inbox.
- The size limit that bounces a set is usually the recipient’s, and encoding makes your file about a third bigger on the way.
- A DWG or a Revit model rarely travels alone. Its references have to go with it.
- A link shows whatever is in the folder now. An attachment is a fixed copy of what you sent. The record needs to know which one it holds.
- Most version mix-ups start with an old attachment forwarded in good faith.
How architects should send large drawing attachments by email
Start with what the person on the other end is going to do with the file. That decides attach or link better than the file size does.
| What you’re sending | How it goes | Why |
|---|---|---|
| One sheet, a sketch (SK) or a marked-up detail | Attach as a PDF | It gets read on a phone at site, often with no login handy |
| A response to an RFI with a sketch | Attach, in the RFI thread | The answer and the drawing stay together in the record |
| A full issue: permit, bid or construction set | Link to a dated issue folder, transmittal in the body | Too big for most mailboxes, and everyone should pull the same copy |
| DWG backgrounds for a consultant | Packaged with eTransmit, then linked | The references and plot styles have to travel with the drawing |
| A Revit model | Linked, through whatever channel your agreement names | Models are large, and they often carry linked consultant models |
| Specifications | Link with the set, or attach a single section | A project manual is long, and one section is usually what’s asked about |
| Returned submittals and shop drawings | Attach if small, link if not, with the action stamp visible | The contractor needs your marking, not just the file |
A practice that sends everything as a link makes life hard for the superintendent on a phone. A practice that attaches everything bounces sets and scatters copies across twenty inboxes. The table above is the middle path most small firms settle into.
The size limit that bounces a set
Two numbers matter, yours and theirs. The smaller one wins.
- Personal Gmail allows 25 MB. Over that, Gmail swaps the attachment for a Google Drive link on its own (Gmail Help).
- Google Workspace limits are set by your administrator, so ask whoever runs your account.
- Microsoft 365 defaults to 35 MB to send and 36 MB to receive. Administrators can set anywhere from 1 MB to 150 MB (Microsoft).
- Outlook for iOS and Android has a 33 MB message limit on the same Microsoft page. That’s the phone your contractor reads on.
- Older Outlook setups on an IMAP or POP account stop you at 20 MB by default (Microsoft).
Then there’s the part that catches people out. A file grows when it’s packed into an email. Microsoft’s limits page puts it plainly:
Messages that are routed outside of the Microsoft datacenters are subject to an additional 33% translation encoding increase, in which case the maximum message size is 112 MB.
So a 28 MB PDF on your desktop arrives at about 37 MB. That’s over a consultant’s default 36 MB receive limit, and the message bounces. The rough rule is to keep attachments under two-thirds of the smallest limit on the thread. On a thread with any Microsoft 365 default mailbox on it, that’s around 23 MB.
A bounce isn’t always loud, either. The non-delivery report lands in your inbox, often hours later and easy to miss. If a set matters, a link avoids the question.
DWG and Revit files travel with their references
A DWG sent on its own often opens with missing backgrounds, wrong lineweights and substituted fonts. The drawing depends on files that live in your folders, not in it.
AutoCAD’s eTransmit is built for this. Autodesk’s help describes it simply:
The Electronic Transmittal (eTransmit) feature helps to package your drawings and any support files required to display and print them accurately.
The package picks up xrefs, plot style tables (CTB and STB) and plotter configuration files on its own. It also writes a transmittal report listing what went in and what was left out. Keep that report with the email. It’s the record of exactly what the consultant received. One caution from the same page: if you include fonts, the people receiving them might need their own license to use them.
A Revit model has the same shape of problem. Linked models from your structural and MEP consultants sit outside the file. Agree how models move before the first one goes out.
That agreement often already exists. If your contract carries AIA’s E203-2013 exhibit, the AIA’s summary says it sets up the process for protocols that:
will govern the development, use, transmission and exchange of digital data and BIM on the project.
The protocols themselves get written into G201 and G202. If they name a shared platform for models, email isn’t the channel. The email that goes out is the note saying a new model is posted.
A transmittal someone can find a year from now
The transmittal is the part of the email that becomes the record. The AIA’s G810-2001 transmittal letter exists for this:
AIA Document G810-2001 allows for the orderly flow of information between parties involved in the design and construction phase of a project.
You can attach the G810 or your own form as a PDF. Either way, put the same facts in the email body too. That’s the text a search will find. A transmittal written into the email looks like this:
Subject: 2417 Maple Street Library · Construction set Rev D · Transmittal 027
To: Dana Whitcomb, Ridgeline Builders. Cc: Priya Nair, Halvorsen Structural
Date: October 13, 2026
Sent: Architectural set A-001 to A-602, Rev D, dated October 12, 2026. Link to the Rev D issue folder below.
Purpose: For construction.
What changed: Stair 2 moved 2 feet north (A-201, A-501). Storefront head height revised (A-401). No other sheets changed.
Supersedes: Rev C, dated September 18, 2026. Please mark Rev C superseded on site.
Action: Confirm receipt and that pricing is on Rev D by Friday, October 16.
Seven lines, and every question a contractor or a lawyer asks later is answered in it. The subject line does the most work. It carries the project number, the issue and the revision, so a search for any of them finds it.
Keeping one version in play
Most version trouble starts with a kind act. Somebody forwards “the drawings” from an email six weeks old, and Rev B goes out again.
A few habits keep the current set the only one anyone reaches for:
- Link to a dated issue folder, not a “current” folder. A link shows whatever is there now. A folder called “Rev D, October 12” stays Rev D. Your record then matches what was actually sent.
- Say what’s superseded, every time. One line in the transmittal saves a call from site.
- Never forward an old attachment. Send from the issue folder, even when the old email is right there.
- Reply on the latest issue thread. The newest revision then sits at the bottom of the conversation.
- Ask for the revision back. When a contractor prices or a consultant comments, ask which revision they used. It takes one line.
- Keep the revision in the filename.
2417-A-201-RevD-2026-10-12.pdfsurvives being saved to a desktop. “Plans final v2.pdf” doesn’t.
There’s one real risk with links worth naming. A link isn’t a copy. If someone moves the folder, changes the sharing or leaves the firm, the link in a two-year-old email can stop working. For anything the record depends on, keep the issued PDF in your own project folder as well. The link is how you sent it. Your folder is what you sent.
Filing what arrives to the project record
Drawings also come in: consultant backgrounds, shop drawings, survey files, site photos, a client’s markup on a printed sheet. The inbox is where they land, but it’s a poor place for them to live.
A simple routine for a small practice:
- Save the file to the project folder the day it arrives. Rename it to your convention on the way in, with the project number, the sender’s discipline, the sheet and the revision.
- Keep the email with it. Save the message as a PDF beside the file, or note the sender and date in your received log. The email often holds the caveat the file doesn’t, like “this is preliminary, final Friday.”
- Log it. A received-documents log lists date, sender, item, revision and what you did with it. It’s the inbound twin of your transmittal log.
- Reply with what you received. “Got S-101 to S-301, Rev 3, thanks” confirms the version for both of you.
If you run project software like Newforma, or a shared project drive, that’s where the record lives. Email is what arrives around it. If you’re on Microsoft 365, Power Automate can save attachments to SharePoint by subject keyword, which suits a firm that’s strict about project numbers in subject lines.
How long to keep it all is a question for your contracts, your state’s statute of repose and your professional liability insurer. The answer is usually longer than the mailbox keeps things by default.
Finding the drawing that came by email
Months later, the question is usually “what did Halvorsen send us before the beam change?” A few things make that answer quick:
- Search by sheet number and revision. That works when the filename carries them, which is one more reason for the naming habit above.
- Search by file type. Gmail’s
filename:pdffinds attachments of a type, andlarger:10Mfinds the heavy messages (Gmail search operators). Outlook’shasattachment:yesnarrows to messages with files (Microsoft). - Search the transmittal, not the file. A sentence like “Stair 2 moved 2 feet north” is something you’ll remember, and it lives in the email body.
Finding a decision years later, rather than a file, has its own page. The practice inbox covers it, along with the size-limit table for each mailbox.
What Point does with the drawings in your inbox
Point is an email client that runs on your existing Gmail or Microsoft 365 mailbox. Drawings that come in by email gather into one documents list as they arrive. Each one is named, dated and one click from the thread that carried it. Nothing is filed for you, and nothing about your project folders changes.
Here’s what that looks like on the Maple Street job:
- Rev D lands in the list. Priya’s structural backgrounds arrive Tuesday at 8:40. They’re in the list with her name and the date, and her note about the preliminary beam sizes is one click away.
- You ask the PDF a question. “What size is the beam at gridline C on Halvorsen’s S-201?” The answer comes back with a link to the spot in the sheet it was read from. Check that link names the revision you meant. Ask a question, get the answer out of the attachment shows how that works, and where scans and handwritten markups get thin.
- One search covers it all. Mail, tasks, calendar and files sit in one search box. “Maple Street stair” brings up the RFI, the transmittal and the sheet together. Searching your inbox by meaning has the detail.
- A new set lines up the next step. Tell Point once: when Halvorsen sends a revised set, give me a task to issue the transmittal. When the set lands, Point catches it and has the task ready. Nothing is created yet. One click is your go. A watch that lines up the work shows it.
- The transmittal reply comes back drafted. Point drafts the email in your voice, with the revision and the superseded line in it. Getting AI replies that sound like you wrote them covers how it learns.
Two things stay outside the list. A link to a shared folder stays a link, because the file lives in someone else’s system. And a DWG or a Revit model opens in your own software. Point keeps the email and the file together, and your CAD tools do the drawing.
By default, Point waits for you before anything goes out. You set that per action type, so drafting can be automatic while sending stays yours. Turn a kind of action all the way up, and Point does it without asking first. Setting how much your inbox does on its own walks through it.
The set that arrived overnight shows up in a daily email briefing for architects. If a contractor’s question came with the drawing, a long RFI thread, in a paragraph picks it up from there. For the wider picture, see Point for architecture practices and the benefits page.
Common questions
How should architects send large drawing files by email?
Attach single sheets, sketches and marked-up details as PDFs. Send full sets as a link to a dated issue folder, with a transmittal in the email body that lists the sheets, the revision, the purpose and what’s superseded. Package DWGs with eTransmit so their references go along. Keep attachments under about two-thirds of the smallest mailbox limit on the thread.
Why did my drawing bounce when it was under the size limit?
Email encoding makes a file about a third bigger on the way out. Microsoft documents a 33% increase for messages that leave its datacenters. A 28 MB PDF can arrive as about 37 MB and hit a 36 MB receive limit. The recipient’s limit counts as much as yours.
What’s a good professional email signature for an architect?
Keep it short and in text. Your name, title, firm, phone, and the firm’s address or website is enough. Add the project number only in the subject line, where search can use it. Keep any logo small, or leave it out. A heavy image rides along on every reply in a long drawing thread.
Should I send DWG files to a contractor?
Check your agreement first. Many owner-architect agreements and the AIA’s E203 exhibit set out how digital files move and who can rely on them. Where you do send CAD, send it packaged, with a transmittal that says it’s for coordination and which issued PDF set governs.
Is a link to a shared folder enough for the project record?
Not on its own. A link shows what’s in the folder today and can break when sharing changes. Keep the issued PDF set and the transmittal in your project folder as well, so the record holds exactly what went out.
Is this page about buying architect email lists?
No. This page is about the drawings moving through your own practice inbox. Buying contact lists to market to architects is a separate question, and the practice inbox points to the rules for that.