CAD Tools

Revision Control: Why Your Reports Drift After Every Change

The device changed, but the BOM still shows the old part. In a revision, the real cost is the manual work between drawing and list. With one data source, a change updates the drawing and every list — no forgotten rows.

This article: Türkçe · Deutsch

Revisions are a normal part of any project: the client changes a parameter, a supplier updates a part number, an unexpected situation turns up on site. The problem is not the revision itself — it starts afterwards. The change in the drawing does not make it into the lists.

Why do reports drift?

In most offices, the data lives in two places: the schematic in a drawing file, and the lists in a spreadsheet. Those two copies are independent; when one changes, the other is forgotten. The outcome is usually the same:

  • The BOM still lists the old part number; the order goes out with the wrong material.
  • The terminal schedule is two revisions behind when the installation crew gets it.
  • Nobody notices — the inconsistency is too small to be spotted by eye.

The root cause is the same every time: the lists are a separate, manual job from the drawing.

One source: a change updates the lists too

In EupCAD, devices, terminals and cables are not drawing objects — they are the project's data, and the drawing is their view. So when you make a change:

  1. You update the device or connection in the drawing.
  2. You re-download the report (CSV).
  3. The new list matches the drawing exactly.

There is no "I should update that row too" step in the flow, because there is no separate data to update.

Practical scenario: a change requested during installation

During installation, the client wants a motor with a higher power rating. In the classic flow: the drafter updates the drawing, the office updates the BOM, and the terminal schedule is remembered at the next meeting. It takes hours, and the risk is a forgotten row.

In the EupCAD flow:

  1. The motor is updated in the drawing (label and parameters together).
  2. The BOM and terminal schedule are re-downloaded.
  3. The installation crew gets the new CSV — same moment, same data as the drawing.

A version is just a drawn version

The lists are downloaded as CSV and open in any spreadsheet, so versioning stays clean: each revision is a separate file, and nothing is overwritten. "Which BOM did we order with?" has a clear answer — it is the file in front of you.

Next step

In the demo project (ZONE1_PUMPS), change a device and re-download the BOM: watch the lists change in the same step as the drawing.

Open EupCAD and try a revision →

Try EupCAD now

No install, no license key — open it in the browser, browse the demo project and move on to your own schematic.

Open EupCAD