Drawing and report review / Interface design

Compare the revision.
Record the receipt.

We designed the drawing-review workspace around a plan comparison, a review history and a transmittal register.

A reader can inspect the changed drawing while retaining the record of how it reached the reviewer.

Original illustration · Drawing and report review

PROJECT TYPE: Interface design & front-end development
DOMAIN: Drawing and report review
DESIGN FOCUS: Separating drawing revisions, receipt and approval

01 / THE DESIGN DECISION

Receipt is not approval.

We separated revision, receipt and approval states. A file being delivered does not establish that it has been accepted, so the transmittal and review have distinct jobs. The project focuses on document control rather than locating design issues within a building.

02 / THE BUILD

The pages we designed.

The build brings project document index, a–102 drawing review, revision B to C comparison, drawing review history and drawing transmittal register into one workspace.

01 / Screen

Project document index

View the screen ↓

02 / Screen

A–102 drawing review

View the screen ↓

03 / Screen

Revision B to C comparison

View the screen ↓

04 / Screen

Drawing review history

View the screen ↓

05 / Screen

Drawing transmittal register

View the screen ↓

03 / PROJECT NOTES

Project scope.

We designed and built 5 pages for this self-initiated project, including the layouts, responsive behaviour and front-end interactions. The interface uses sample business records.

The screenshots show authored interface states. Live accounts, operational integrations and production transactions are outside this portfolio build.

The gallery shows our rendered pages with identifying details masked.

06 / ON SCREEN

A closer look.
Page by page.

Start with the overview, then explore the details. These are screenshots of the original interface, with names, contact details and identifying information blurred for privacy.

5 views Select any view to explore