Drafting services: the whole drawing set, issued and controlled.

The drawing set is the deliverable, not the drawing

Individual drawings are easy to get right. Sets are hard. A set fails when a detail callout points at a sheet that was deleted, when two drawings show the same slab at different levels, or when the schedule on sheet 41 was updated and the plan on sheet 12 was not. Nobody drew that error; the set grew it.

A drafting engagement is therefore scoped around the whole set:

• General arrangement drawings — plans, elevations and sections with setting-out, grids and levels.
• Details — typical and specific, drawn once and referenced properly rather than copied around the set.
• Schedules — doors, windows, finishes, columns, beams, foundations, or whatever the discipline schedules.
• Notes, legends and key plans, consistent across every sheet that carries them.
• The drawing register — the list of what exists, at what revision, at what status, issued to whom.

The disciplines a set has to carry

A construction set is rarely one discipline, and the sheets that cause trouble are the ones where two of them meet. Drafting is scoped across the disciplines the project needs rather than around whichever one is easiest to staff.

• Architectural — floor and roof plans, elevations and sections, reflected ceiling plans, door and window schedules, room data, as-built records and the shop drawings that come back for review.
• Structural — general arrangements, foundation and framing plans, connection sketches, shop and fabrication drawings, erection drawings, anchor bolt plans and single-part and fitting drawings.
• MEP — power and lighting layouts, containment and cable tray routes, plumbing and drainage plans with invert levels that agree between sheets, HVAC ductwork and its fabrication drawings, and piping isometrics with spool references the fabricator can order against.
• Façade — curtain walling, structural glazing, unitised and rainscreen panel details, cladding and composite panel setting-out, canopies, skylights and louvres, with movement joints, thermal breaks and tolerance take-up drawn rather than assumed.
• Millwork and joinery — custom shop drawings, assembly and installation details, bills of material and modular or furniture drafting, dimensioned for a workshop rather than for a site.
• Mechanical — component and assembly drafting, sheet metal design, exploded views, and the fabricated ancillaries that every industrial project turns out to need.

They travel together for one reason: the interfaces. A ceiling void where ductwork, containment, sprinkler pipework and a structural downstand all have a claim is not resolved by six correct drawings produced independently. It is resolved by one set, drawn to one setting-out, checked against itself.

Drafting from whatever you actually have

Work rarely arrives as a clean brief. It arrives as a designer's sketch on a section print, a calculation package with the sizes in it, a model that is complete for three floors, a supplier's product drawing, a point cloud, and a set of markups on last month's issue.

All of those are valid inputs. What matters is that the ambiguities in them are surfaced early rather than drafted around. At intake we read the source material and come back with the list of things that are undefined, contradictory or dimensioned two different ways — before three weeks of drafting is built on top of them. That conversation is short, and it is the difference between a first issue that gets comments and a first issue that gets rejected.

How a drafting package runs

Intake fixes the standard, the title block, the numbering, the sheet list and the issue programme. The sheet list is agreed as a document, so progress is a count of drawings at a status, not a percentage someone estimated in a meeting.

The AI-driven part of the work is the volume of the set: producing sheets, laying out views, dimensioning, annotating, applying the standard notes and building the schedules. Senior engineers spend their time on the drawings that carry judgement, on the coordination between sheets, and on reading the set the way a site engineer will read it.

Every issue is a decision. Drawings go out under a revision, against the register, with a change list. Comments come back into the register and are shown as actioned. Superseded revisions are marked superseded, not deleted, because a site needs to know what it was building to last month.

Revisions, issues and the register

Document control is not administration bolted onto drafting. It is the part that decides whether the site is building to the right drawing.

We run the set with revision clouds and deltas that show what actually changed, status and suitability codes that mean the same thing on every sheet, transmittals that record who received which revision and when, and a register that reconciles against the files issued rather than against someone's memory of them. Where the project runs a common data environment, the set lives in it and the register mirrors it. Where it does not, we run the exchange and hand over a complete issue history at the end.

Two mechanisms carry most of that weight and are worth naming, because they are the ones that go wrong quietly. A transmittal is the record that a specific revision left this office for a specific recipient on a specific date, and it is the document that answers the question nobody wants to ask two years later. A submittal log is the same discipline pointed the other way — what has gone for approval, what has come back, in what state, and what is now blocking fabrication. Both are maintained as part of the set rather than by somebody's spreadsheet, and both are reconciled against the files actually issued.

The practical test is simple: at any moment, you should be able to answer what is current, what changed, and who has it. A drafting service that cannot answer those three questions has not finished the job.

Machine-checked across the set before issue

The automated checks run over the whole set, which is where set-level errors live:

• every detail and section callout points at a sheet and a detail that exists;
• drawing numbers unique, and the issued files reconciled against the register;
• the revision on the sheet equals the revision in the register and in the transmittal;
• title block fields complete — status, scale, originator, date, revision;
• scales, north points and scale bars consistent between related sheets;
• symbols used on the drawings all present in the legend, and legend entries that are never used flagged;
• standard notes matching the current approved wording rather than an older copy;
• schedules reconciled against the drawings they describe.

A senior engineer reviews the set with those results in front of them and signs the issue. The check record goes out with the register.

Drawing conventions and standards

Drawings are read by people who were not in the design conversation, so convention is not pedantry. We draft to your standard where you have one, and otherwise to the recognised conventions: ISO 128 for the presentation of technical drawings, ISO 7200 for title block data, ISO 19650 naming where the project runs a formal common data environment, AS 1100 for Australian work, and the AISC and Eurocode drawing conventions where the set feeds fabrication.

Sector matters more than it looks. An airport drawing set is read under a phasing and possessions regime; a residential set is read by trades on a repetitive floorplate; an industrial set has to agree with equipment supplier drawings that arrive late and change. The set is structured for how it will be used.

One partner, one signature

BuildTwin produces the set, checks it, controls it and signs it. One delivery lead, one register, one issue programme, one company answerable for what is on the sheet — not a pool of people you have to manage.

Taking over a set mid-project is normal work: we audit what exists, reconcile the register against the files, list what is missing or inconsistent, and agree a recovery position before drafting anything new. When the programme accelerates, the system produces more sheets per week; the review and the signature stay with the same senior engineers.