--- Skip to content
Business2026-10-245 min read

Design revisions: numbering, change logs and reissue rules

Three things keep order: continuous revision numbering, a change log with the date and reason of every edit, and an archive where the latest version is found in a minute.

Author:GorkyCAD Team

Where changes come from

Design changes arrive from three places, and they must not be confused. The client moves layouts and wishes: sockets shifted, underfloor heating added, the kitchen rethought. The site brings facts: a wall turns out load-bearing, a route does not fit, the panel does not fit the niche. Standards and review add a third source: check comments, a revised code edition, utility requirements.

Each source has its own pace. Client wishes can be batched weekly and issued as one revision, otherwise the drafter reprints the set every day. Site facts cannot wait: an unrecorded rerouted run becomes an as-built nobody drew. Review comments are closed as a checklist, item by item, with a mark in the change log.

  • Client: batch weekly, issue as one revision.
  • Site: record immediately, or the as-built diverges from the design.
  • Standards and review: close comments as a checklist.

Numbering and file names

A revision is the number of an issued set, not a save counter. Same-day drafts get no numbers; only an issued set — to the client, to site, to review — earns one. The working scheme is simple: first issue is Rev 0 or P01, then the number grows by one with each issue. Letters can mark stages, digits mark revisions within a stage.

The file name must carry three things: project code, stage and revision. Example: EOM-12-R-Rev03.pdf. A file without a revision in its name is a disaster candidate: the site will always find an old printout, and nobody will prove which is newer. A date may be added to the name, but it never replaces the number — one date can host three different builds.

  • Only an issued set gets a number, never a save.
  • File name must include code, stage and revision.
  • A date complements the revision number, never replaces it.

Change log contents

The change log is one table at the front of the set, and everyone reads it: client, foreman, reviewer. Minimum columns: revision number, date, sheet, what changed, reason. The reason is short and honest: “per client letter of 12 March”, “site fact: beam”, “review comment No. 4”. Without a reason the entry is useless — in six months nobody will recall why the group moved.

Log only what affects the work: routes, groups, breakers, loads, the bill of materials. Cosmetics — shifted callouts, re-split sheets — stay out, or the table bloats and nobody reads it. The rule is simple: if a change can affect procurement, installation or acceptance, it goes in the log; if not, it is fixed silently.

ColumnWhat to write
RevisionIssued set number
DateIssue date
SheetChanged sheet numbers
ChangeExactly what changed
ReasonClient, site, or review

Reissue vs cloud-mark

Reissuing the whole set every week is a reliable way to bury the site under paper. Only changed sheets are reissued: they get the new revision number in the title block, the rest stay valid under old numbers. The cover sheet or transmittal note lists which sheets are replaced and which remain valid from earlier revisions.

Changed spots on a sheet are ringed with a revision cloud — a wavy frame — with a triangle carrying the revision number beside it. The cloud is not removed at once: it stays for one or two revisions until eyes adjust, then it is taken off while the change log entry remains. The site always receives the full set even if one sheet changed — the foreman must not assemble a mosaic of sheets of different dates.

  • Changed sheets are reissued; the site still gets the whole set.
  • Changes are ringed with a revision cloud and number.
  • Clouds stay one or two revisions, then come off.

Archive and finding latest

An archive is not a dump folder but a structure where the latest version is found in a minute. A working skeleton: project folder, inside it issued revisions by number (Rev00, Rev01…), a drafts folder and a client-inputs folder. Each revision folder holds exactly the set that was issued, plus the change log. Drafts never leak into an issue.

On top of that, keep an issue register: who received what and when. “Sent the foreman via messenger” is not an issue until recorded: which set, which revision, which date. The register wins arguments: when a client claims “I never approved that”, a dated entry with the set contents closes the question. Keep the archive at least until the warranty period of the building ends, client letters together with the project.

  • Structure: revisions by number, drafts and inputs kept apart.
  • Issue register: to whom, when, which set and revision.
  • Keep at least until the building warranty expires.

One model instead of scattered files

The classic source of revision chaos is scattered, unlinked files: the plan in one editor, the scheme in another, the schedule in a spreadsheet. An edit lands in the plan while the scheme and the estimate stay old, and every revision falls apart. A single engineering model fixes the root cause: plan, single-line diagram, panel, specification, cable schedule and estimate are views of one model, not separate documents.

GorkyCAD Pro is built exactly this way: a browser CAD for electrics where one model produces the plan, the single-line diagram, the panel, the specification, the estimate and the PDF set. An edit is made once — in the model — and the whole set regenerates from it; the single-line diagram is generated automatically rather than drawn by hand. A revision in this scheme is simply the state of the model on the issue date, and “plan versus scheme” mismatch disappears as a class.

  • Plan, SLD, panel, specification, schedule, estimate — one model.
  • One edit in the model, full set regenerated.
  • A revision is the frozen model state on the issue date.

Issue checklist for the next revision

Run a short checklist before every issue — ten minutes that catch most blunders. First: every client-requested change from the batch is in, nothing lost in transit. Second: the change log is filled, reasons stated, sheet numbers matching the title blocks. Third: revision clouds sit on the changed spots, old clouds removed.

Fourth: title-block revision numbers on changed sheets are updated, the cover reflects the issue contents. Fifth: the set is assembled whole, not “changed sheets separately”. Sixth: the issue register entry — to whom and when it was sent. Seventh: an archive copy of the issued set sits in the revision folder. Seven items — and there is nobody left to blame for version confusion.

  • Changes in, change log filled, clouds in place.
  • Title blocks updated, set assembled whole.
  • Issue register and archive copy — immediately, not later.

FAQ

How to number revisions?

Only an issued set gets a number: first issue is Rev 0 or P01, then plus one per issue. Letters can mark stages, digits mark revisions within a stage. Draft saves are never numbered. The file name must include project code, stage and revision — a file without a revision in its name will surely be confused with an old printout on site.

What goes in the change log?

Five columns: revision number, date, changed sheet numbers, exactly what changed, and the reason. The reason is short and verifiable: a dated client letter, a site fact, a review comment number. Log only changes that affect procurement, installation or acceptance; cosmetics stay out so the table keeps being read.

Reissue the whole set?

No. Only changed sheets get the new revision number; the rest stay valid under earlier revisions, with the mix fixed in a transmittal note. But the site always receives the full set, not loose sheets — the foreman must not assemble a mosaic of different dates. Changed spots are ringed with a revision cloud carrying the revision number.

Where to archive?

Structure: project folder with issued revisions by number, plus separate drafts and client inputs. Each revision folder holds exactly the set that was issued. Add an issue register — to whom, when, which set was sent. Keep everything at least until the building warranty expires, client correspondence together with the project.

Single-model workflow in GorkyCAD

Build plan, panel and single-line from one model — open the editor

Open GorkyCAD