ARTICLE
The Comprehensive Guide to Scoping a Drafting Service Engagement
A drafting engagement is easy to under-scope and hard to recover once it is running. Here is what a drafting package should actually deliver, and how to define one before a single sheet is produced.
What a drafting package actually delivers
Individual drawings are easy to get right. Sets are hard. A set fails when a detail callout points at a sheet that no longer exists, when two drawings show the same element at different levels, or when a schedule is updated and the plan referencing it is not — and nobody drew that error, the set grew it.
A drafting engagement should therefore be scoped around the whole set, not a drawing count: general arrangement drawings with setting-out, grids and levels; details drawn once and referenced properly rather than copied around the set; schedules for whatever the discipline schedules — doors, windows, finishes, columns, beams, foundations; notes, legends and key plans consistent across every sheet that carries them; and a drawing register that states what exists, at what revision, at what status, issued to whom. The register is not paperwork attached to the deliverable. It is part of the deliverable, and a package scoped without one is a package scoped around the wrong unit of work.
Scoping the brief before drafting starts
Work rarely arrives as a clean brief. It arrives as a sketch on a section print, a calculation package with sizes in it, a model complete for three floors out of ten, a supplier's product drawing, a point cloud, and a set of markups on last month's issue — and all of those are valid inputs.
What matters is that the ambiguities in them are surfaced before drafting starts, not discovered partway through it: which standard governs, what the title block and numbering convention are, and which dimensions in the source material actually agree with each other. The sheet list should be agreed as a document at intake, with each drawing given a target issue date and a status, so progress is a count of drawings at a status rather than a percentage estimated in a meeting. Where two sources genuinely disagree — a dimension on the sketch that does not match the calculation package — that conflict is exactly what intake exists to surface, not something to resolve quietly in whichever direction looks more likely to be right. A short intake conversation that surfaces contradictions early is the difference between a first issue that gets comments and one that gets rejected outright.
Revision control and the drawing register
Document control decides whether a site is building to the right drawing, which makes it closer to the core of a drafting service than an administrative add-on to it.
Every drawing should be issued under a revision against the register, with clouds and deltas that show what actually changed, and a transmittal recording who received which revision and when. Status and suitability codes need to mean the same thing on every sheet — shared should never be confused with published. Comments return into the register and are shown as actioned, and superseded revisions are marked superseded rather than deleted, because a site needs to know what it was building to last month, not only what is current today. Where several parties issue into the same set — a structural engineer, an architect, a specialist subcontractor — the register is what stops one party's revision silently overwriting another's understanding of what is current. The practical test is simple: at any moment, someone should be able to state what is current, what changed, and who has it.
Verifying a set before it is issued
Quality control on a drawing set is a set-level activity, not a sheet-by-sheet one, because that is where the costliest errors live.
- Every detail and section callout points at a sheet and a detail that actually exists.
- Drawing numbers are unique, and the issued files reconcile against the register.
- The revision on the sheet matches the revision in the register and in the transmittal.
- Title block fields are complete: status, scale, originator, date, revision.
- Symbols used on the drawings all appear in the legend, and unused legend entries are flagged.
- Schedules reconcile against the drawings that describe the same elements.
A named, qualified engineer should review the set against those results and sign the issue — not sign off on the assumption that the checks were run, but review what the checks actually found.
Drawing conventions and standards to specify
Drawings are read by people who were not in the design conversation, so convention is not a formality. A scope should name a drawing standard explicitly rather than leaving it to be inferred: your own standard where you have one, or the recognised conventions where you do not — 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, and the relevant regional convention, such as AS 1100 in Australia, alongside the AISC or Eurocode drawing conventions where the set feeds fabrication directly.
Sector shapes the set as much as the standard does. An airport drawing set is read under a phasing and possessions regime; a residential set is read by trades working a repetitive floorplate; an industrial set has to agree with equipment supplier drawings that arrive late and change. Where a project runs a mixed portfolio of legacy and current drawings, the convention in force has to be stated per set rather than assumed to be whichever one is most recent. A scope that does not account for how its set will actually be read is missing half the brief.
A short checklist before commissioning a package
Most drafting disappointments trace back to a handful of things left unstated at the start, and each one is cheap to fix in advance and expensive to fix mid-package.
- Name the drawing standard and title block precisely, not just the code family.
- Agree the sheet list as a document, with a target issue date and status for each drawing.
- Define the review and comment cycle: who reviews, how comments return, how many rounds are budgeted.
- Name who signs the issue, and what they are actually checking when they do.
- Agree what “current” means on this project, and how a revision reaches everyone who needs it.
- State which source document governs when two of them disagree, before that conflict is discovered mid-package rather than at intake.
None of this takes long to write down. It takes considerably longer to reconstruct after a set has already gone out inconsistent, which is the ordinary cost of skipping it, and it is cheaper still when it is agreed before the first sheet is opened rather than after the first dispute over which revision is current. A scope this specific reads like caution to someone who has not run a drafting package before, and like the only sensible way to start one to someone who has.