Skip to content
Sunbeam
Open menu

Technology for Engineering and construction consultancies

A consultancy should be able to say which revision was issued, to whom, and on which date.

Direct answer

Document control fails in small and mid-sized consultancies when the drawing register is a spreadsheet and the transmittal is an email attachment. Sunbeam builds a drawing register, a transmittal record and a query log sized to the way the office actually issues work. A heavyweight document system is the wrong first step if the team cannot keep a register current.

Where the work breaks

The problems we expect to hear.

The register and the drawing do not match

Revision C is in the email, revision D is on the server, and the spreadsheet still says B. Site then builds, or prices, from the file that was easiest to open. The consultancy cannot show which revision was the one it issued.

Transmittals are unsearchable

A transmittal sent as a zip file to a contractor answers today's question and disappears into a mailbox. Six weeks later, 'what did they receive' is a search through sent items, and the answer is only as good as the person who sent it.

RFIs and site queries have no owner

Questions from site arrive in a group chat shared with people who are not on the project. Some are answered in the group, some in email, and some not at all. There is no due date and no record that the reply was against a particular drawing.

The same drawing number means different things on different jobs

Without a project boundary, a register search returns the wrong sheet. Superseded drawings stay in circulation because nothing marks them as replaced in the place the team actually looks.

What we would build

A first system sized to the actual work.

  1. 01

    A drawing register with a real status

    Project, discipline, number, title, revision, date, and a status the office already uses — for review, issued, approved, superseded. The current revision is obvious. The previous ones stay available and are marked as not current.

  2. 02

    Transmittals tied to that revision

    Issuing a set creates a record of what was sent, to which party, and when. The register entry points at the transmittal. 'Which drawing did the contractor have' becomes a lookup.

  3. 03

    A query log with an owner and a due date

    Requests for information and site questions sit against the project, and where it matters against the drawing. Someone owns the reply. The log is the record, even if the conversation still happens on email or in chat.

  4. 04

    A document workspace for the office, not an enterprise suite

    Submittals, method statements and client comments can live in the same project space when the register is in place. We size this to the consultancy. A full enterprise document system is a later decision, made once the register is a habit.

How the system has to behave

Practical constraints, decided before the build.

  • Project boundaries so drawing numbers do not collide across jobs
  • A simple rule for who may issue a revision and who may only view it
  • Exports a client or contractor can receive without needing an account on day one

Answers that sit behind this work

FAQ

Questions from Engineering and construction consultancies teams.

What is a drawing register, in practice?

A list of the drawings on a project with the current revision, the status, and the date it changed. The useful version also records who it was issued to. A spreadsheet can do this until more than one person needs to issue work at the same time.

Do you replace our CAD tools?

No. Drawings are still produced in the tools the engineers use. The system holds the register, the issued file and the record of who received it.

We already email transmittals. Why change that?

Email can stay as the notification. The change is that the list of what was sent is stored against the revision, so it can be shown later without searching a mailbox.

Is this only for large EPC contractors?

It is most useful for consultancies that issue drawings to clients and contractors and feel the pain in revisions and queries. A three-person office with one live project may still be fine with a disciplined sheet. The system earns its place when two jobs, or two people, can no longer share one file safely.

Not every operational issue needs custom software. See when Sunbeam is not the right fit, compare practical options in our decision guides, or .