Uploading plans for trade quotes looks like a single action: you send one CAD set and the trades price from it. What decides whether the quotes come back comparable is what you do in the hour before the upload.
Units, external references, layer names and revision labels all travel with the file. Each one changes how a trade reads your scope, and each one is easier to fix on your machine than in a pricing conversation three weeks later.
This guide covers the actual upload process for an Adelaide project. It sets out what to check in the drawing, and how to clean and package it. It then covers the formats that survive the trip, revision control from planning consent through building consent, and what you should receive back.
Key Takeaways
- Upload the native DWG or DXF set, not a flattened PDF. AutoCAD model space is normally drawn at full size, so an estimator can measure quantities directly from the geometry (Autodesk).
- Check the drawing unit with the
-DWGUNITScommand and confirm one known dimension before you send anything (Autodesk). - Clean the file first: detach unneeded xrefs, run
OVERKILLon duplicate geometry and purge unused layers and blocks (Autodesk). - Email is not the delivery method. Gmail caps attachments at 25 MB for Business and Education accounts (Google Workspace).
- In South Australia, development approval includes one or more consents. The current names are planning consent and building consent (PlanSA).
What You Upload, and What You Get Back
You upload the native drawing set, not a picture of it. A DWG or DXF file keeps the geometry, the layer structure and the drawing units. A print PDF keeps only the appearance.
That difference decides how a trade measures your job. Model space in AutoCAD is normally drawn at full size. Autodesk's support guidance states that "AutoCAD 2D drawings are commonly drawn in model space at a 1:1 scale (full-size)", and that the drawing is only resized when it is "plotted or printed at a plot scale" (Autodesk). One-to-one geometry lets an estimator measure a wall run or a slab area directly instead of inferring it from a scale bar.
What you get back is a comparison, not a single number. Each trade package returns pricing against the same scope, with the inclusions and exclusions that trade has assumed. Two quotes become comparable when the scope behind them is the same. That is the point of uploading one set rather than slicing sheets into separate emails.
Step 1: Check Units, Scale and Drawing Integrity
Start with the drawing unit, because everything else scales from it. Autodesk recommends drawing "in actual size (or in 1:1 scale)" and verifying the current unit with the -DWGUNITS command before plotting or issuing (Autodesk). A set drawn in millimetres and read as metres is out by a factor of 1,000, and the error follows every quantity taken from it.
If a model is not at full size, Autodesk points to "user errors, inaccurate scanning, and faulty exporting of data" as the usual causes, and documents the reference-length method for correcting it (Autodesk). Before upload, measure one grid line that carries a known dimension and compare it with the number on the drawing.
Then check file integrity. AUDIT "evaluates the integrity of a drawing and corrects some errors", while RECOVER "repairs and then opens a damaged drawing file" (Autodesk). A file that opens with errors on your workstation will behave worse in a browser viewer, and worse again in a takeoff tool.
Scale error compounds with distance. On a 20 m grid dimension, a 1 per cent linear error is 200 mm, which is enough to move a brick count or a flooring order. That figure is arithmetic on a stated assumption, not a measured benchmark. The practical point is to verify the reference dimension rather than trust the title block.
Step 2: Clean the File So It Travels
Send a stripped, self-contained file rather than the working model. Autodesk's guidance on reducing DWG size recommends detaching unneeded xrefs, running OVERKILL on duplicate geometry, and clearing registered applications with -PURGE. It also lists purging unused items, resetting the scale list and deleting layer filters (Autodesk).
Bound Set or Attached Set
Two xref strategies work for trade pricing:
- Bound set. Bind or insert the xrefs so that one file carries all geometry. Trades see the whole drawing in one open.
- Attached set. Keep architectural, structural and services files separate and attach them, so a trade loads only what it needs. Autodesk notes that a large drawing can be "divide[d] into multiple smaller drawings and then attach[ed] ... into a master drawing". Child drawings can then be loaded or unloaded as required (Autodesk).
What Clean-Up Does Not Fix
Size reduction is not guaranteed. Autodesk's own caveat is that "the amount of data in a drawing (used and unused), object types, and complexity all attribute to the size of a DWG file". It adds that "some drawings may not reduce very much in size while others may show a significant change" (Autodesk). The goal is a clean file, not the smallest possible one.
| Check before upload | Why it matters for pricing | How to do it |
|---|---|---|
| Drawing unit | Millimetres read as metres multiplies every quantity by 1,000 | Run -DWGUNITS and confirm the unit for length |
| Full-size geometry | Takeoff measures the model, not a scale bar | Measure one known grid dimension against the drawing |
| Xrefs resolved | Missing grids or levels hide part of the scope | Detach unneeded xrefs, or send the attached set together |
| Duplicate geometry | Overlapping lines inflate linear takeoffs | Run OVERKILL, repeating it if needed |
| Unused layers and blocks | Clutter slows the layer filtering a trade needs | Run PURGE with all options, and -PURGE for RegApps |
| File integrity | Errors surface as missing or shifted elements | Run AUDIT and fix the reported errors |
| Revision label | Trades need to know which issue they are pricing | Put the revision and issue purpose in the file name and title block |
Step 3: Name Layers and Files for the Trade Reading Them
A trade should be able to isolate its own scope in seconds. That is a naming problem, not a software problem.
Keep one discipline prefix per layer group, and use it consistently across every sheet in the set. If your office already works to a layer standard, keep those names in the upload instead of renaming for the platform. If the layer names change from sheet to sheet, a filtered view will not line up.
Name the files the same way. A file name that carries project, discipline, sheet and revision lets a trade confirm it is holding the current issue without opening the drawing. Use the same revision code in the file name, the title block and the upload note. If they disagree, the trade will price the one they opened.
Step 4: Package the Set by Trade, Not by Sheet
You do not need to cut the drawing into trade slices yourself. Upload the whole set, and let the intake process separate the packages. What you do need is to make sure a trade can price each package on its own.
Boundary and setout information usually sits with the surveyor rather than the architect. If the groundworks package depends on boundary dimensions, check what a cadastral map shows before the package goes out. The trade can then price against the same boundary as the survey.
| Trade package | What it needs from the set | What is commonly missing |
|---|---|---|
| Groundworks, excavation and slab | Site plan, levels, slab and footing layout, soil report | Finished surface levels and retention detail |
| Structural steel and timber framing | Structural layouts, beam and column schedules, tie-down details | Connection details and bracing certification |
| Roof carpentry, roofing and cladding | Roof plan, truss or rafter layout, fascia and flashing details | Custom flashing profiles and fall direction |
| Hydraulic, drainage and stormwater | Hydraulic plan, sanitary and stormwater layouts, on-site detention requirements | Invert levels and connection points |
| Electrical, data and mechanical | Electrical and reflected ceiling plans, schedules, switchboard location | Ceiling grid heights and equipment loads |
| Waterproofing, tiling and flooring | Wet area details, floor finishes schedule, membrane specification | Fall to waste details and substrate type |
| Linings, joinery and finishes | Elevations, sections, joinery details, inclusions schedule | Appliance and fixture models, wall lining types |
Two omissions are worth designing around. A package sent without its schedule produces a quote full of exclusions, because the trade can see the layout but not the fittings. A package sent without the consultant's xrefs produces a quote with a caveat about grid and level information.
Step 5: Choose Formats That Survive the Trip
Not every consultant works in AutoCAD, so the accepted formats matter at upload time.
- DWG and DXF. Native vector formats. Geometry, layers and units all survive, which is what makes measurement and layer isolation possible.
- Vector PDF. An acceptable fallback when a consultant cannot release the model. Plotted from the model it keeps vectors; scanned from paper it does not.
- IFC. An open, vendor-neutral exchange format published as ISO 16739, with the
.ifcSTEP physical file format recommended for exchange (buildingSMART). Useful when a consultant works outside AutoCAD but can still export a coordinated model. - Schedules and specifications. Send them as PDF or spreadsheet with the drawings. A finishes schedule attached to the plan removes a whole class of exclusion.
Then check how the file is going to arrive. Gmail caps attachments at 25 MB for Business and Education accounts, with 50 MB available only on Enterprise Plus in the web version (Google Workspace). A multi-sheet DWG set with xrefs will exceed that ceiling. Upload the set to the coordination service, or use a bulk transfer link, rather than exporting a flattened PDF for each trade.
Step 6: Hold Revision Control from Planning Consent to Building Consent
Use the current South Australian consent names, because they are what appears on the portal and in correspondence. Development approval "consists of one or more types of consent granted during the assessment process". Under the Planning, Development and Infrastructure Act 2016 it may require planning consent, building consent and land division consent (PlanSA). Label each upload with the consent stage it supports, and keep those names consistent in the file name and the issue note.
The Two Revision Waves
Revisions arrive in two predictable waves. The first follows planning consent, when conditions, setbacks, materials or access change. The second follows building consent, when structural and compliance detail firms up. Treat each wave as a numbered issue rather than an update to a file.
Where to Check Zoning and Mapping
If a condition turns on zoning or mapping, checking a site in SAPPA confirms what the current Planning and Design Code says for the allotment. For projects outside South Australia, planning map viewers by state lists the equivalent viewer.
How a Late Revision Affects the Statutory Clock
The statutory clock rewards sending a complete revision once. PlanSA publishes the assessment timeframes. "All types of assessment have a five business day verification period at the start and two business days at the end for the decision to be issued". For performance assessed development, "time limits can be suspended" when the authority or a referral agency asks for more information. "The assessment clock restarts when the information is received" (PlanSA). Drip-feeding sheets invites exactly that request.
| Revision stage | What usually changes | What to re-upload | What to tell the trades |
|---|---|---|---|
| Tender issue | Scope and inclusions settled for pricing | Full coordinated set plus schedules | The issue purpose, and the closing date for questions |
| After planning consent | Conditions, setbacks, materials, access | Only the affected sheets, with a new revision code | Which sheets the new revision replaces, and which package they affect |
| After building consent | Structural and compliance detail | Structural and services sheets, updated schedules | That the revision is not yet a construction issue |
| Construction issue | Approved for construction | The complete current set | That earlier revisions are withdrawn from pricing |
What Comes Back After the Upload
A coordinated upload returns a single comparison rather than a folder of attachments. For each package you should receive the priced scope on common terms, so that inclusions and exclusions sit side by side instead of in three different formats.
Ask for four things with every comparison:
- Scope inclusions and exclusions, written against the package you sent.
- Lead time and availability for the trade, not just a price.
- A query log showing the questions raised and the answer given to every trade at once, so no trade prices a different scope.
- Licence and insurance details for the quoting entity, so you check credentials before award rather than after. This guide to licensed and insured trade quotes sets out the verification steps developers use.
The service described here approaches up to three licensed trades for each package, follows the quotes up, and returns that comparison. That is what the upload is for: the comparison is only meaningful if every trade looked at the same drawing.
Where Uploads Go Wrong
| What the trade reports | Usual cause at upload | Fix before sending |
|---|---|---|
| Quantities out by a factor of 1,000 | Drawing units misread between millimetres and metres | Confirm the unit with -DWGUNITS, then check one known dimension |
| Grid or level information missing | Xrefs unresolved on the recipient's machine | Bind the xrefs, or send the attached set together |
| Scope filtered incorrectly | Layers renamed or exploded sheet by sheet | Keep one discipline prefix and one layer standard across the set |
| Quote priced from a superseded revision | No revision code or issue purpose on the upload | Label every upload with its revision and purpose |
| Quote full of exclusions | Schedules or specifications left out of the package | Attach the inclusions and finishes schedules with the drawings |
| Two trades measuring different areas | A scanned or flattened PDF sent instead of the vector set | Upload the DWG or DXF, and keep the PDF for viewing only |
If the problem is not the drawing but the availability of trades, the recovery sequence is different. This playbook covers finding backup trades for a delayed project, including how to document the stage reached before a replacement trade prices the balance of the work.
Frequently Asked Questions
What File Formats Can I Upload for Trade Quotes?
Prefer native DWG and DXF files, because they keep vector geometry, layers and drawing units. A vector PDF plotted from the model is an acceptable fallback. IFC is useful when a consultant works outside AutoCAD, and schedules and specifications should travel with the drawings as PDF or spreadsheet.
Do I Need to Separate My Drawings by Trade Before Uploading?
No. Upload the complete architectural and engineering set. The intake process separates the trade packages, so you do not need to slice sheets or export a separate PDF for each trade. What matters is that each trade's package includes the schedule that goes with it.
Do I Need to Draw at 1:1 Scale?
Yes. Model space is normally drawn at full size and resized only when plotted. If a model is not at full size, Autodesk lists user errors, inaccurate scanning and faulty exporting as the usual causes. You can rescale the drawing with the reference-length method before upload.
What Is the Maximum File Size I Can Upload?
There is no single answer, because the limit belongs to the receiving platform rather than to the drawing. The practical constraint to plan around is email: Gmail allows 25 MB of content and attachments for Business and Education accounts. Anything larger should go through the coordination service or a bulk transfer link.
What Happens If My Plans Change After I Upload Them?
Upload the changed sheets as a new numbered revision, name the sheets it supersedes, and ask for repricing on the affected trade packages. Keep one current set as the single source of truth, so no trade prices a withdrawn revision. If a development application is under assessment, send the revision complete. A request for further information can suspend the assessment time limits.
Does Uploading Plans Commit Me to a Construction Contract?
No. Uploading plans starts a pricing exercise and does not commit you to any trade. You do not form a construction contract until you sign one. What you get is comparable pricing and a documented scope to take into subcontract negotiation.
Next Step
If your drawings are ready and the revision label is current, upload the DWG or DXF with its schedules attached. The DDDI Group research team publishes this article. The quoting service described here is run by Cyberate Technologies, an independently owned company built with the DDDI method, on its trade and supplier network, and it returns licensed Adelaide trades' pricing side by side.
Submit your architectural and engineering plans at Get Started. If you are weighing how South Australia's consent steps compare with other states, the NSW and SA planning system comparison for developers sets out where the pathways diverge.

