Roles: who draws, who calculates, who approves
A classic small-office split needs only three hats, even if one person wears two of them on small jobs. The drafter builds the plan: walls, rooms, socket and lighting layouts, cable routes. The engineer sizes cables, sets protective devices, balances phases and runs the calculations. The approver — a senior engineer or principal — reviews the set against the check report and signs it.
The key rule is that drawing and approving never sit with the same hands on one issue. Even in a two-person office, the second pair of eyes reads the single-line diagram and the panel schedule before release. GorkyCAD Pro is a browser CAD where a single engineering model feeds the plan, the single-line diagram, the panel, the 3D view, the specification, the estimate and the PDF set, so each role works on the same data instead of three divergent files.
- Drafter: geometry, layouts, routes, title blocks.
- Engineer: loads, short-circuit currents, voltage drop, selectivity, panel build.
- Approver: review, verdicts on warnings, signature and stamp.
Templates: title blocks, frames, document sets
Every repeatable job starts from a template, not a blank sheet. A good office template pack includes title blocks with the company stamp field, standard sheet frames, a layer and colour convention, a default panel range with incomer and RCD layout, and a prefilled document set: plan, single-line diagram, panel schedule, cable schedule, bill of materials and estimate.
Keep templates versioned like code: one master folder, a change note for each edit, and a sample project that proves the template still builds a clean PDF set after every change. New staff learn the office standard by copying the sample, not by reading a fifty-page manual. The payoff is boring in the best sense — every issue from the office looks like it came from one hand.
- Sheet template: frames, stamps, revision table.
- Panel template: incomer, metering, RCD groups, spare ways.
- Document template: which sheets every issue contains.
Review: a human plus 25 automatic checks
On the English-language side GorkyCAD runs 25 automatic checks against IEC 60364: protection coordination, cable sizing and heating, voltage-drop limits, RCD coverage and similar routine points, each with a PASS, WARN or FAIL verdict. Treat them as a tireless junior reviewer — they never sleep, but they do not understand context, so every WARN needs a human decision recorded next to it.
Build the review into the schedule, not into overtime: drafter self-check against the checklist, engineer review of calculations and selectivity, approver sign-off of the full set. The /* checkout */ rule is simple — no PDF leaves the office with an unreviewed FAIL, and every accepted WARN carries a name and a reason. That discipline is what clients actually buy when they hire a bureau instead of a lone drafter.
- Self-check: geometry, labels, completeness of the set.
- Engineering review: calculations, breaker curves, phase balance.
- Sign-off: verdicts closed, stamp applied.
One model instead of realtime myths
Clients often ask whether the whole team can edit one project at the same time. Be honest: GorkyCAD Pro does not provide realtime multi-user teamwork as a tariff feature, and promising it creates chaos at handover. The reliable pattern is sequential ownership — one editor at a time — on top of a single shared model, so the plan, the single-line diagram and the panel schedule can never drift apart.
Agree simple ownership rules: the drafter owns geometry until the layout freeze, then the engineer owns devices and calculations, then the approver locks the issue. Pass the project with a short handover note — what changed, what is still open, which warnings are accepted. Sequential work on one model beats parallel work in five files every time.
Versions and archive: naming and storage
Use revision codes that anyone can read a year later: P01, P02 for preliminary issues sent for comment, C01, C02 for construction issues, plus a date in ISO format in the file name. Every issued PDF keeps its code in the title block revision table together with a one-line note of what changed.
Keep the change log short and factual: added, removed, resized, relocated — with the reason in half a sentence. Store superseded issues read-only in an archive folder and never overwrite them; when a dispute arrives two years later, the archive is your memory. Local project data lives in the browser store with offline PWA support, so the office keeps working through network outages and syncs later.
- File name: project code, revision, date.
- Change log: what, where, why — one line each.
- Archive: old issues read-only, signed PDFs separate.
Handover and liability: where the line is drawn
The handover pack is the plan, the single-line diagram, the panel schedule, the cable schedule, the specification, the estimate and the check report — the full PDF set the bureau actually produced. Before the client's signature, all calculations and AI suggestions are preliminary materials; responsibility for the design decisions sits with the engineer or principal who approves the set, as the licence and the calculation methodology state plainly.
Write the boundary into the contract: which revisions the price covers, how many comment rounds are included, what counts as a change order, and who answers for site deviations. For kindergartens, schools and hospitals, remind the client early that independent expert review is mandatory — it protects both sides. A clean handover letter with the issue codes and the acceptance signature closes the project and opens the next order.
Where a small team starts this week
Do not rewrite the office in one go — pick one live project and run it through the new flow. Freeze roles on paper, copy the closest old project into a template, run the 25 automatic checks and hold the first real review meeting with verdicts. The gaps you find become next month's template update.
Price the experiment honestly: a monthly Pro subscription costs €40, and token top-ups run €2, €15 and €60 — one small job pays for the whole workflow upgrade. Start free in the editor, and move to Pro when the pipeline, not the curiosity, demands it. Full terms and what's included live on the pricing page.
FAQ
Who signs the design?
The person who takes professional responsibility: a licensed engineer or principal who verifies calculations, checks and drawings and puts a signature and stamp on the set. Automatic checks and AI hints are advisory only — see the liability note in the EULA and the calculation methodology.
What goes to review?
The complete set as issued: plan, single-line diagram, panel schedule, cable schedule, bill of materials, estimate and the check report with PASS/WARN/FAIL verdicts. Attach the list of open warnings and who accepted them.
How to archive versions?
By revision code in the file name and title block (P01, P02 for preliminary, C01 for construction issue), plus a change log noting what changed and why. Keep superseded issues read-only and store the final PDF set with the signed approval separately.
Expert review for small jobs?
It depends on the jurisdiction and the building class: small fit-outs usually pass the client's technical review, while new builds and capacity upgrades may need formal expert review and utility sign-off. Clarify the route before pricing the job.
Related articles
- Design review checklist before issue
- Electrical project stages
- Electrical drawing checklist
- GorkyCAD for companies
Templates, roles and review in one model — open the editor
Keep one engineering model for plan, panel, single-line diagram and documents, and run the 25 IEC 60364 checks before issue. Start free in the browser — Pro at €40/mo when the office grows.
Open GorkyCAD