What lives in Excel
For half the trade, the project is a set of spreadsheets: a cable list with lengths, a points list with sockets and luminaires, an estimate with materials and labour. Excel honestly holds the arithmetic while the job is small: rows are visible, totals add up, the file goes in one email. Trouble starts with growth: spreadsheets multiply, and the links between them live only in the author's head.
The typical set: a “cables” tab with types and metres, a “points” tab tied to rooms, an “estimate” tab with prices, sometimes a “schedule” tab for the foreman. The plan exists separately — a scan, an image or a drawing — with no link between a spreadsheet row and a line on the plan. A moved socket never moves the row, and the mismatch surfaces at procurement.
- Cables, points and money — three tables living separate lives.
- The plan exists apart, unlinked to any table.
- Works while the job is small; falls apart as it grows.
What moves first: plan or schedule
The direct answer: the loaded plan moves first, not the estimate. The reason is simple — everything else, schedule, specification and estimate, derives from the plan. Moving money first produces handsome totals hanging in mid-air, unattached to routes and points. A plan with placed sockets, luminaires and the panel is the foundation everything else rests on.
The order: base drawing (scan or draft), then points and groups on it, then the panel and risers. The cable schedule is collected from routed runs, not typed by hand: lengths come off the plan, not out of someone's head. The estimate moves last — once quantities are counted by the model instead of copied from the old table. Whoever starts with the estimate counts everything twice.
- First the loaded plan — the foundation of everything.
- The schedule is collected from plan routes, not typed.
- The estimate moves last, once the model counts quantities.
Reconciling lengths and totals
Migration without reconciliation is faith, not accounting. There are three checkpoints: cable lengths, point and device counts, money totals. Lengths are checked along routes: take the three to five longest runs from the old table and measure them on the new plan. A deviation within the stripping and sag allowance is normal; a multiple-times gap means a lost route or a duplication.
Counts are checked room by room: sockets and luminaires per room must match the table one to one. Money is checked last, and only after counts match: if metres and pieces agree but money does not, the issue is prices, not the design. Every discrepancy is written down, never “kept in mind” — memory fails exactly on procurement day.
| What | How | Pass bar |
|---|---|---|
| Cable lengths | 3–5 longest runs off the plan | Within allowance |
| Counts | Points and devices room by room | One-to-one match |
| Totals | Only after counts match | Difference in prices only |
Classic migration mistakes
Mistake one: dragging the spreadsheet into CAD as is, crutches and all. Temporary “to check” columns, hidden rows and monster formulas are garbage, not data. The table is cleaned before migration: only what describes the building stays, the rest goes to archive. Garbage moved into a new system becomes garbage with a residence permit.
Mistake two: running both systems in parallel “to be safe”. Parallel books double the work and guarantee divergence: within a month nobody remembers which version is master. The rule is hard — a cutover date after which only the new system is edited and the old table is frozen as archive. Mistake three: skipping the base scale check. An unscaled scan yields lengths out of thin air, and the whole reconciliation collapses.
- Do not drag crutches along: clean the table before migrating.
- No parallel books: cutover date, old table frozen.
- Verify the base scale before moving any lengths.
When Excel stays alongside
Moving to CAD does not mean killing spreadsheets: Excel stays right where it beats the model. First — commercial ballparks at the “roughly how much” stage: sketching three fit-out options is faster in a table than building three models. Second — non-standard items outside the design: hire, delivery, subcontractors with their own arithmetic.
Third — exchange with people outside the project: sometimes sending the client one table beats teaching them to open the set. The boundary rule is simple: everything describing the building — cables, points, devices — lives in the model and exports from it; everything describing the deal — discounts, payment stages, third-party work — lives in the table. Mixing both worlds in one file returns the chaos you left.
- Keep for ballparks, non-standard items, outside exchange.
- In the model: everything describing the building.
- Never mix building books and deal arithmetic in one file.
The payoff: schedule and estimate from the model
The finish line of migration is when tables become reports instead of sources. The cable schedule is collected from the model: every run knows its start, end, type, cross-section and length, and the schedule forms itself instead of being stitched from three tabs. A socket moved on the plan moves its schedule row by itself — a link Excel never had.
The estimate in GorkyCAD builds from the same single canon: materials, labour and VAT, an “Estimate” sheet in the PDF set plus XLSX export, with prices kept honestly fresh on a 14-day cycle. Change the model and the schedule, the estimate and the specification all recalculate at once. That is the whole point of moving: one edit instead of three unlinked files.
- Schedule and specification are model reports, not hand tables.
- Estimate: materials, labour, VAT, 14-day price freshness.
- One model edit refreshes every document at once.
The way back: tables out of CAD
Migration runs both ways: CAD data must return to tables for people who cannot work without them. The foreman needs the cable schedule in familiar form, the buyer needs the specification for suppliers, the accountant needs the estimate broken down. So tabular export is not a luxury but the condition for peaceful coexistence with the outside world.
GorkyCAD Pro lists XLSX export in the Pro plan — verify the export on your own data in the /cad/ editor before relying on it. The PDF set stays the master carrier for site work: plan, single-line diagram, panel schedule, specification, cable schedule and estimate in one file that never falls apart. Tables are for working the numbers; PDF is for working the site.
- Tabular export for buyers and accountants, PDF for the site.
- XLSX is a listed Pro export — verify it in /cad/ first.
- The master site carrier is the single PDF set.
FAQ
What moves out of Excel first?
The loaded plan: base drawing, points, groups, panel and risers. Schedule, specification and estimate derive from the plan and move after it, once quantities are counted by the model. Starting with the estimate means counting everything twice — first in the old table, then in the new system.
How to reconcile lengths and totals?
Three checkpoints in order: lengths along the three to five longest runs, counts of points and devices room by room one to one, money last and only after counts match. If metres and pieces agree but money does not, the issue is prices. Write every discrepancy down.
Will any data be lost?
No — if the table is cleaned before migration and frozen after the cutover date. Cleaning removes temporary columns and formula crutches; freezing forbids editing the old table past cutover, or the two systems diverge. Parallel books “to be safe” are the top cause of loss: within a month nobody knows the master.
Keep Excel for the estimate?
For deal arithmetic — yes: ballparks, discounts, payment stages, third-party work. For building books — no: cables, points and devices live in the model after the move and export from it. Never mix both worlds in one file — that is the chaos you left.