The engineering markup & design workflow
Less searching.
Clearer redlines.
Faster review.
Automatically build the markup. Give the designer the exact drawing, WBS and revision to use. Bring the baseline, redline and completed work together for the engineer’s final decision.
Workflow efficiency begins with the handoff. Smart Drawing Assist adds another layer of review support.
Actual SVS authoring output
Enter the change.
The markup takes shape.
Boxes, entered text, leader arrows and colors are generated from the authored request, reducing repeated graphic assembly.
- 01 / ENGINEERAuthor the redline
- 02 / DESIGNERConfirm the intent
- 03 / DESIGNERComplete the CAD work
- 04 / ENGINEERReview the evidence
- 05 / ENGINEERApprove and issue
Where the time comes back
Recover the hours lost
between engineering
and design.
A markup is more than a graphic. It is a request that someone must understand, locate, execute and review. Redline connects those steps so the team can spend more time on the engineering.
Stop assembling each graphic by hand.
The engineer enters the change. Redline generates the boxes, instruction text, connector arrows and colors, keeping the request attached to its drawing location.
Give the designer a precise starting point.
Drawing ID, WBS/project number and revision travel with the instruction. The designer can find the intended source without reconstructing what the engineer meant.
Put all three drawing states together.
Baseline, redline and completed work provide shared review context. The engineer can inspect the requested change, record the outcome and return missing or incorrect work.
These workflow benefits do not depend on training a model. The engineer remains responsible for the technical review and final release.
A reference the designer can actually find
The drawing number
is only part of the answer.
The same drawing can appear under different projects and revisions. Recording the engineer’s intended source at authoring time reduces avoidable searching, guessing and clarification loops.
- Identify the exact source
Drawing ID, WBS / project number and revision / version are required for each added reference. Sheet / detail provides optional additional context.
- Carry it into the visible markup
The generated instruction callout, instruction ledger and designer handoff retain the reference details. One markup can include up to five references.
- Keep ordinary markups quick
Markups that do not refer to another drawing need no reference fields. An incomplete added reference must be completed before saving.
Illustrative reference • not a platform screenshot
Use the relay detail from this exact source.
- Drawing ID
- DEMO-C-102
- WBS / project
- WBS-2048.03
- Revision / version
- C
- Sheet / detail
- Sheet 2 / Detail B
A useful handoff gives the designer all four pieces together.
The engineer–designer handoff
Keep the process visual.
Keep the work moving.
Start with an authored redline or an existing marked-up PDF. Follow the request through understanding, design, review and release in one connected process.
The engineer defines the change.
Create structured instructions in Redline or attach an existing redline binder. Define additional graphical expectations when the selected checking route needs them.
The designer confirms understanding.
Review the baseline and engineer’s redline together. Acknowledge clear intent or request clarification. Routine confirmation does not require retyping every markup.
Design work stays in CAD.
Revise the source drawings in the existing design application. Return a completed PDF binder for comparison with the controlled baseline and redline.
The engineer sees the evidence.
Inspect supported machine checks and aligned drawing views. Resolve exceptions or send incorrect and missing work back for correction and another review cycle.
The engineer owns the final decision.
Resolve required review items, approve the exact revision, apply the project’s seal/signature requirements and prepare the controlled release and handoff.
Acknowledge the request.
Preserve the engineer’s intent.
Visual binder review remains a practical route for legacy redlines. Structured expectations add checking precision where useful or required by project policy.
Understanding the instruction, observing a change and accepting the completed revision are distinct events in the record.
Existing redlines: the drawing and its identified markup regions
Engineering review, with context
What was requested.
What changed.
What still needs attention.
Bring the baseline, redline and completed drawing together. Supported checks help focus the review; the engineer can inspect the evidence and resolve the work.
A supported result is review evidence.
The engineer compares what was requested with what the designer delivered. Machine findings help focus that review. The engineer resolves required items, including checks that cannot conclude, and makes the final decision on the revision.
Expected state observed
The supported check found the declared condition within its scope.
Discrepancy found
The evidence indicates a missing or incorrect requested condition.
Review required
Ambiguity, limited evidence or unsupported work remains visible to the engineer.
A common workflow across engineering disciplines
Built around the handoff.
Flexible across sectors.
Engineering teams share the need to request a drawing change, confirm it, complete the design and review the result. Redline’s PDF workflow is designed around that common process.
Core workflow
Start with the drawings and tools you use.
Author or attach PDF redlines, confirm designer intent and return completed PDFs for engineer review. Native design work stays in MicroStation, AutoCAD or the team’s existing CAD application. This workflow does not require a sector-specific trained model.
Specialized verification
Qualify the checks for the drawing family.
Symbols, conductor relationships and design conventions vary. Automated interpretations and checks need supported input quality, defined rules and evaluation for their intended use. Broad workflow applicability does not mean every sector’s technical checks are already qualified.
The current Redline workspace
Real screens.
Connected capabilities.
Explore the current navigation, including Smart Drawing Assist and the direct Engineer Review & Release route. Select a view to see the actual software.
Explore the workspace
Actual application images.Select Enlarge for readable detail.
Projects, inputs and designer intent
Attach baseline, redline and completed PDFs to controlled revisions. Engineers author or define the request; designers confirm understanding. Binder review provides a visual route for existing markups.
Intake, verification and correction cycles
Check input prerequisites, run supported checks, inspect three-way evidence and record outcomes. Corrections return through another review cycle; changed inputs invalidate prior evidence. Selective reruns require their unchanged-input and runtime conditions to hold.
Engineer Review & Release, PE Signing Setup and handoff
The responsible engineer resolves the required review work and approves the revision. Project requirements determine seal artwork and any additional certificate/timestamp route. Signed issue and handoff preserve the relationship to the exact artifact.
Smart Drawing Assist, Profiles & Standards and help
Smart Drawing Assist brings together local readers, the private learning library, reviewed datasets, training jobs and candidate comparisons. Profiles & Standards manages versioned configuration and context. A reference pack does not itself train a model or qualify an executable check.
Administration, Jobs & Audit and advanced Authority Review
Administrators manage Windows account enrollment and assigned responsibilities. Job state, review history and integrity records support operations and audit. Running a background job does not give the operator engineering approval authority. Advanced Authority Review governs technical configuration separately from the engineer’s final drawing decision.
PE approval, signing and issue
The engineer’s approval.
The project’s release rules.
Connect the final decision to the drawing revision, credential records and release requirements. Add certificate signing when the project calls for it.
Engineer approval + seal artwork
A familiar sealing route, with a recorded decision.
The engineer can save authorized, undated seal-and-signature artwork for their own licence and apply a separate typed release date. Each issue still requires personal page review and authorization. Project policy sets the required placement and release controls.
Certificates when required
Add cryptographic signing and trusted time.
A project can require certificate signing, accepted certificate trust, revocation evidence and a trusted timestamp. Enrollment, renewal and suspension controls support the credential lifecycle.
A workflow for the whole team
Clear responsibilities.
Connected project history.
People see the work through their assigned responsibilities. Account administration, operational support and audit remain distinct from the engineer’s final drawing decision.
- Engineer
- Authors redlines, resolves returned-work findings, requests corrections, and approves, seals and issues the drawing revision.
- Designer
- Confirms markup intent, flags questions, completes external CAD work and returns the completed drawing package.
- Administrator
- Enrolls and manages user accounts, enables or disables access, and assigns the responsibilities needed by the team.
- Project Manager
- Follows project status, handoffs and outstanding work without becoming an additional drawing approver.
- Auditor
- Inspects the review history and evidence through assigned access without changing the engineer’s decision.
- Technical Operator
- Supports controlled jobs and platform operations. Worker execution carries no engineering approval authority.
- Profile Manager
- Manages approved configuration and recorded license/trust requirements separately from accepting the drawing.
Infrastructure data controls
Keep the drawings
within the chosen boundary.
Local processing, enrolled Windows identities and controlled workspaces support a deliberate approach to engineering information.
Local document processing
PDFs and verification evidence can remain in the selected local or shared workspace. There is no automatic cross-customer training service.
Defined user access
Registered Windows identities and assigned roles govern platform responsibilities. Administrators control enrollment; engineers retain drawing authority.
Controlled shared storage
Workspace identity checks protect the selected shared-folder route. The Windows sharing setup uses encrypted SMB with offline caching disabled.
Controlled execution
Pinned dependencies and runtime integrity checks prevent automatic installation of unapproved versions. Approved verification jobs can run headlessly.
Customer IT governs storage encryption, backup, endpoint security and corporate identity policy. Enterprise SSO/MFA and each VDI or multi-workstation deployment need environment-specific qualification. A screenshot or crop retains the confidentiality of the drawing it depicts.
Large files, revisions and concurrent work
Keep the review tied
to the right revision.
The platform records which inputs were checked, which job produced the evidence and which revision the engineer reviewed.
Reject stale updates.
Stale-save checks prevent an older editor state from silently overwriting a newer saved revision.
Keep job ownership visible.
Durable job status and ownership, plus recoverable attachment commits, support a controlled processing history.
Recheck changed inputs.
Changes to the drawing inputs invalidate earlier review evidence so it cannot silently stand in for the new revision.
External integration hooks and enterprise qualification
Current Redline uses controlled PDF handoffs and approved headless verification jobs. Direct connections to CAD, document-management and issue systems are proposed integration work.
A connector should preserve file/revision identity, input hashes, instruction and profile versions, findings, engineer decisions and the exact issued artifact. It must respect source-system permissions and locks, handle retries and interrupted transfers, and revalidate the revision before returning results.
Shared-workspace support does not establish qualification for every corporate network. Representative concurrent users, network interruptions, recovery, VDI and large-binder throughput require environment-specific acceptance work. Automated jobs cannot approve or release drawings on behalf of the engineer.
Deterministic checks, with defined scope
Repeatable checks.
Inspectable evidence.
The same controlled input, expectation and rule version should produce the same result. Supported checks help the engineer focus attention while uncertainty remains explicit.
Text and values
Declared native-PDF text targets and bounded offline English OCR routes.
Selected symbols
Defined jumper, ground and 52a/52b contact patterns within supported limits.
Vector connectivity
Selected endpoint, branch, junction and crossing checks on native-vector drawing geometry.
Drawing details
Specific relay/panel, terminal-caption, orientation and dimension routes.
Visual reconciliation
Controlled baseline, redline and completed evidence for targeted engineer review.
Smart Drawing Assist & private improvement
Learn from the work.
Keep control of the result.
Local drawing assistance and controlled learning add support to the core workflow. Firm-specific examples remain within the authorized workspace and local learning environment.
Build examples from real work.
Enable private workflow capture, inspect source-linked examples and record reviewed expected answers. Designer intent confirmation and final approval remain separate from correct-answer labels.
Evaluate a candidate against the current model.
Prepare frozen datasets, run supported local training jobs and compare current and candidate answers against the same reviewed cases. Inspect errors and regressions alongside improvements.
Keep new behavior deliberate.
A comparison does not activate a candidate. Independent evaluation, approved deployment and task-specific rule qualification are distinct steps. No learning process grants engineering release authority.
What is implemented, and where the learning scope ends
The development platform includes a private reference library, workflow learning inbox, reviewed source examples, frozen datasets, supported local training and current-versus-candidate comparisons. Current task coverage is bounded; these tools do not establish whole-drawing understanding.
There is no automatic promotion from a review decision to the live model or verification rules. Production model promotion and rollback remain further work. Previously used examples are development evidence, not an unseen accuracy benchmark.
Private drawings, excerpts and learning examples are not a public starter dataset. A crop can still reveal sensitive engineering information. Customer data rights, access controls and retention requirements continue to apply.
Recorded software evidence
A substantial
regression record.
Test results are tied to a specific build and method. They support a serious technical discussion about the product.
Tests passed in a full regression
Complete installed-platform reference run on Redline 0.15.7 build H, recorded September 21, 2026. Zero failures, errors or skipped tests.
A traceable software baseline
The result belongs to that tested build. Later development updates have separate evidence; this count is not a claim that the newest build received the same complete rerun.
What the testing proves, and what remains to qualify
Regression checks exercise software behavior. They do not establish a real-project accuracy percentage, validate the 50% workflow estimate, or qualify every engineering discipline.
Unseen drawing evaluation, representative large-file and multi-workstation deployment, and live PE/provider workflows require their own acceptance evidence. A technical evaluation can inspect the relevant build records and agreed workflow cases.
Strategic acquisition opportunity
Connect the change record
to the design ecosystem.
SVS offers an existing product foundation for engineering markup, designer confirmation, completion evidence and engineer-authorized release.
Autodesk
Extend design-to-delivery continuity.
Explore a completion record alongside AutoCAD design and connected document workflows.
Request the Autodesk packet ↗Bluebeam
Carry markup intent through completion.
Build on the role of PDF markup and review with a focused link between requested changes, returned-work evidence and the engineer’s disposition.
Request the Bluebeam packet ↗Bentley Systems
Keep design in MicroStation.
Explore controlled PDF handoffs and potential ProjectWise/iTwin connections around infrastructure and substation drawing work.
Request the Bentley packet ↗Strategic proposals only. These companies already provide design, markup and review capabilities. No affiliation, endorsement, delivered native connector or commercial partnership is implied.
Official ecosystem context
Ecosystem sources reviewed September 14, 2026. The proposed fit is SVS’s assessment; the linked companies have not committed to an SVS integration.
Direct answers
A practical route from
demonstration to evaluation.
Where does the estimated 50% time saving come from?
It is an experienced designer’s assessment of time spent assembling markups, finding drawing references, clarifying intent and comparing returned work. Redline addresses those specific steps. It is not a controlled measurement of total engineering effort; the result should be measured against the customer’s own baseline.
Do we need to train a model before using the workflow?
No. The core PDF authoring, visual intent confirmation, drawing-reference handoff and engineer review workflow does not depend on model training. Smart Drawing Assist and automated checks add task-specific support with their own coverage and qualification requirements.
Does the designer have to retype every markup?
No. Routine designer confirmation is a visual acknowledgment of understanding or a request for clarification. Structured expectations can be added for stronger checking or made mandatory by project policy.
Who gives the final approval?
The responsible engineer. They resolve required review work, including checks that cannot reach a conclusion, then approve the revision. Administrators, project managers and auditors do not add an approval above the engineer.
Can we use scanned PDFs or existing redlines?
Existing PDF binders can support visual review. Selected text extraction and offline OCR routes have defined limits. Native-vector connectivity checks need suitable vector content; a scan cannot provide that same evidence simply by being uploaded or traced.
Does SVS edit or certify native DGN or DWG files?
Design work remains in the CAD application. Current Redline reviews the supplied PDF representation and records the engineering workflow. Native CAD editing and direct Bentley or Autodesk adapters are separate proposed integration work.
Is a digital certificate required for every project?
The default route uses authenticated engineer approval with seal artwork. A project can additionally require certificate signing, accepted trust, revocation evidence and a timestamp. A cryptographic signature and state/client acceptance are different matters; the selected release workflow needs qualification.
Can we evaluate the software before an acquisition?
Yes. SVS operates demonstrations and agreed technical test cases and provides results and explanations. No trial deployment, downloadable application or repository/source access is provided before purchase. Agreed software and source assets transfer at closing against the purchase payment.
Private, SVS-operated technical evaluation
See the request.
Follow the evidence.
Evaluate the opportunity.
Review the working platform, challenge agreed cases and assess the workflow against your engineering and product priorities.
Marc Smith · Founder
Standard Validation Systems Corporation
- See the complete workflow.
Follow authoring, designer intent, returned-work evidence, engineer approval and release controls.
- Agree the evidence to evaluate.
Use authorized cases and clear acceptance criteria. Measure review effort, misses, false alarms and abstentions by drawing family.
- Define the acquisition scope.
Software and source-code handover occurs at purchase closing. The standards Validation Platform remains a separate product.
SVS retains the application and source during evaluation. No 30- or 90-day trial deployment or pre-purchase code access is offered.