Illustrated workflow
Keep DNO comments with the job.
From a marked-up drawing to a response an engineer can review, with the original comments beside the work.
Illustrated engineering workflows, with current product capabilities and the decisions for your people shown on each page.
The example
A network operator returns comments on a submitted drawing. This example follows the comments through review and a proposed response.
The illustrated steps
Confirm the job
A person checks which job the email and attachments belong to before filing them.
Keep the original comments
Keep the marked-up drawing with the correspondence. Comments that need manual entry are flagged for an engineer to read.
Record the drawing and query
Put the drawing revision and the technical query beside the original source.
Review the response
The responsible engineer checks each comment and the proposed drawing change.
Approve the exact issue
The authoriser checks the response, revision and intended recipients together.
Send and keep the record
An authorised person sends through the existing manual process and keeps the issue record.
What is built, and where it stops
The full incoming-comment-to-response journey is not available. Automatic project filing, response drafting and delivery are not promised by this illustration.
Current product scope recorded 28 October 2026. Built, switched off means it is not switched on for customers yet. Coming means it is planned and not yet available.
- Robert: Drawing registers, revisions and transmittals
- Built, switched off
Keeps the drawing register with its revisions and numbers each transmittal issued.
- Robert: Technical queries and drafted RFI responses
- Coming
Logs technical queries and RFIs and drafts responses for an engineer to review.
The RFI register is built, but sending is switched off; response drafting, closure and chasing are unproved. Engineer review required.
These scope statements use the same source as the Feature List in the procurement pack. Read the OpsWork specification →