Engineering Workspace / Design Workflow
IIDesign control

The Design Workflow

The deliverables list is the backbone of design management — here it is alive: every row knows its chain, its dates, and who is sitting on it.

1:31 · WATCH600 drawings, real approval chains, zero spreadsheet wars
90 seconds of the real workflow: chains, codes, escalation, transmittals.

The EDL — 5,300 rows, no sweat

Filter by discipline and status, import the list you already have in Excel, export the view you are looking at. Every row shows its pending step and who owes it — overdue in red, not in a report next week.

Import maps your existing columns automatically
Pagination proven at 5,300+ rows — capacity to 20,000
Pending step + owner on every row
The EDL — 5,300 rows, no sweat
A revision's whole life on one card

A revision's whole life on one card

P01 ran the full chain and was issued; the consultant returned Code C, the chain reopened itself, and P02 now waits on DC & issue with a working-day due date — the admin acting for an absent approver, stamped on the record.

Originate → check → approve → DC → issue
Substitutions stamped: who acted for whom
Codes A–D; C and D reopen the chain automatically

“My actions” — each engineer's personal queue

Everything waiting on you across every deliverable, with batch approve when it is a stack and a 'While away' delegation so leave never stalls a chain.

Batch actions up to 100 at once
Delegation with an end date
Automatic escalation after 2 working days
“My actions” — each engineer's personal queue
As-builts ride the same rails
An as-built AB01 on its full chain, cropped from its revision card.

As-builts ride the same rails

AB revisions run on the same chains and the same evidence trail, without ever disturbing the issued status of the design record — coverage reported per discipline.

AB01… labels on the same deliverable
Issued status never regresses
Every capability, declared

The complete list.

The full sign-off machine — built inside a mega-project's delivery, not a demo.

The EDL

Excel import with auto-mappingBring the list you already keep; columns map themselves; re-import updates in place.
CapacityTested end-to-end at 5,300 rows with 14 engineers acting in parallel; engine reconciled to the row. Handles 20,000.
View = exportThe filtered view you are looking at exports to Excel exactly as filtered.
Planned vs actual datesPlanned issue per row; actual stamped on issue; variance feeds the S-curve.
Stage-weighted earned valueEach status carries a percent — progress is earned, not guessed.

Chains & steps

Five step kindsOriginate, discipline check, approve, DC check, issue — per-discipline templates, editable per project.
Template wizardOne press creates a default sign-off chain for every discipline.
Working-day deadlinesStep durations count working days on YOUR weekend — deadlines never land on Friday.
Named accountabilityEvery step assigned to a person; 'anyone' steps eliminated by design.
The chain, drawnEvery step a station on one rail, marked with what happens there: gold where documents wait, red where one is late, one bracket over steps that run side by side. A revision shows the same rail, so where it stands and who holds it is read at a glance.

Acting on work

Batch actionsApprove or return up to 100 waiting steps in one confirmation.
Delegation'While away' hands your steps to a colleague until a date — every act stamped '[delegate — acted for X]'.
Admin substitutionAn admin can unblock a chain, transparently: '[admin — acted for X]' in the trail.
ReassignmentMove a single step to another engineer without touching the template.

The loop closed

Escalation engineDue today: nudge. Two working days over: escalate to the next in line. Every three: re-nudge. Automatic, hourly.
Response codes A–DRecord the consultant's code per revision; C and D reopen the chain by themselves.
TransmittalsIssued deliverables get transmittal records with per-project numbering.
Auto visual compareEach new revision is diffed against the last — removed in red, added in teal — before reviewers open it.

Document control

Numbering disciplineEnforce your document-number pattern (or raw regex); filenames checked on submission.
Title-block readingThe sheet's title block is read and checked against the EDL row — scanned sheets included, via vision.
As-built familyAB01… revisions on the same deliverable; issued design status protected; coverage report per discipline.
Full auditWho submitted, who acted, who was acted-for, when — permanently on the record.
Against the field — design workflow
Sign-off chains with delegation, escalation and response codes
Generic 'review status' fields; chasing lives in someone's memory
Working-day clocks on a Fri–Sat weekend
Calendar-day durations, if durations exist at all
As-built revisions on the same record, issued status protected
As-builts as a separate folder, disconnected from the trail
5,300-row EDL exercised with 14 parallel actors — reconciled
Row limits nobody has tested against a real mega-project list

"The field" is the usual toolchain — the per-user construction cloud and the separate applications around it. Good tools; the difference here is one integrated record, on your own server.

Install it and begin — free for 14 days.

Nothing to request and nobody to wait for: download it, install it, and the 14-day evaluation starts by itself the first time it opens.
Download and install →
← DashboardRegisters & Claims →