Request a demo
Built for EPC and owner-operator teams

Spend more time engineering.Less time drafting, checking, searching, and coordinating documents.

Verno keeps P&IDs, spec sheets, line lists, and related engineering documents coordinated as your project changes. You make the engineering decisions. Verno handles the drafting, checking, and updates that follow.

Request a demoSee examples
Backed by Y Combinator
Verno in action

Adding a standby pump.

An example of how Verno coordinates engineering changes across related documents.

Verno drafts a standby pump on the P&ID and sends linked drafts to engineersA process engineer sketches the outline of standby pump P-101B and its branch in red on the PDF, with the note “Add P-101B — standby pump”. Verno AI replaces that rough markup with precise black CAD-style pump, piping and valve linework. A large green check means drafting is complete, not that the design is approved. Verno sends the equipment list to Process, the pump datasheet to Mechanical with Process duty input pending, and the load list and cable-schedule finding to Electrical. All human reviews remain pending. The draft load-list rating is pending and the cable schedule has no power-cable assignment. Verno proactively asks before drafting a cable entry. No updates are approved or issued automatically. Piping, valves, controls and electrical supply may also require review. This is an illustrative animation, not a live CAD or Bluebeam integration.Cross-drawing utility reference: The two P&IDs have a matching off-page utility connection; drawing titles alone do not establish a link.Line numbers on PID-001: The line register contains these drawing and line references.Valve tags on PID-001: The project valve register contains these tags.Instrument tags on PID-001: The instrument index references instruments on this drawing.Utility line numbers on PID-002: The line register covers the utility system too.Utility valve tags on PID-002: The valve register covers the utility system too.Piping class / specification code: The line record references the applicable piping class, not just a similarly named document.Valve specification / piping class: Applies to the piping valves covered by that class; not every control valve is a pipe-spec item.Control-valve tag / datasheet reference: This project register includes control valves. A manual-valve-only list would not establish this link.Shared proposed equipment tag P-101B: The draft register entry and datasheet refer to the same proposed pump.Motor / feeder reference: The load maps to a feeder on the SLD. Motor changes may require SLD and protection review too.Control-valve instrument tag: The datasheet describes a tagged control valve in the instrument index, not an arbitrary manual valve.Proposed equipment tag P-101B: Create a draft equipment record; tag allocation and project approval remain pending.Proposed pump P-101B / datasheet: Process confirms hydraulic duty; Mechanical reviews equipment specification. No vendor selection is implied.P-101B / associated motor: The proposed electrically driven pump maps to a draft motor consumer. Rating and operating-mode data require review.P-101B motor / missing cable assignment: Check the motor against the cable schedule. A draft entry is not a sized cable or an assigned feeder.P&IDPID-001 · Simplified excerptPDFExisting centrifugal pump P-101; axial inlet and tangential dischargeDischarge check valve; permitted flow to the rightSuction and discharge isolation valvesPiping continues beyond this simplified excerptP-101ExistingProcess engineer's red freehand PDF markup: proposed standby pump and branch outline, not finished CAD geometryAdd P-101B — standby pumpProposed standby centrifugal pump P-101B; separate isolation valves and discharge check valve, sharing the existing suction and discharge headersP-101BStandby · NewVerno draft · Process review pendingP&ID · UtilitiesPID-002Line listLST-LN-01Valve listLST-VV-01Piping specificationSPC-PP-01Equipment listLST-EQ-01 · XLSP-101B · Proposed standbyVerno draft · New equipmentEquipment registerP-101B addedSent to Process for review; not approvedSent to ProcessPump datasheetPDS-101B · PDFP-101B · Proposed standbyDraft · Process duty pendingPump specificationStandby pumpSent to Mechanical for review; not approvedSent to MechanicalSingle-line diagramSLD-001Load listLST-LD-01 · XLSP-101B · Proposed standbyVerno draft · Rating pendingMotor registerP-101B motorSent to Electrical for review; not approvedSent to ElectricalCable scheduleSCH-CB-01 · XLSP-101B · Proposed standbyP-101B motor · Power cableCable registerNo cable assignedSent to Electrical for review; not approvedSent to ElectricalControl valveCVD-201 · DatasheetInstrument indexLST-IN-01ProcessP&ID + equipment listReview pendingMechanicalPump datasheetReview pendingElectricalLoad list + cable scheduleReview pending

The engineer marks up the P&ID.

Process engineer · Add P-101B — standby pump
Markup
Markup · AI drafting · Document updates · Engineer reviewSkip to examples ↓
Ask it

What engineers put to Verno.

Check and audit

Start here. Verno reads, changes nothing.

List reconciliation

Audit the valve list against the P&IDs. Show me every row that does not match.

Cross-document consistency

Check the tie-in schedule and the electrical and I&C drawings against the P&IDs.

Tag traceability

Find every drawing and document where this tag appears.

Issue readiness

Every drawing in this package: right revision, right date, right stamp. Before I issue.

Update and revise

Proposed with reasoning. An engineer accepts.

Batch tagging

Replace the placeholder tags with final line and valve numbers, across the set.

Drawing edits

Delete this high-high level switch and the line it sits on.

Change propagation

Line 2101 went from 6 inch to 8 inch. Update everything downstream.

Revision management

Take these redlines and issue Revision 1, title blocks updated across the package.

Version control and audit trail

Show me everything that changed between Rev 0 and Rev 1, and who accepted it.

Generate and answer

Into your templates, not ours.

List build and update

Build the line, valve, instrument and equipment lists from the drawing set, or update the ones we already have.

Datasheet generation

Redo the control valve datasheets after this change.

Control system sizing

Build the I/O list from the instrument index. How many analogue and discrete points does the DCS need?

Project queries

How many 3 inch ball valves are on this project?

Standards lookup

Which clause covers this? Take me to the page.

How it works

You make the calls. Verno does the rest.

Verno is the executor. If it is work on your documentation, Verno does it.

You decide

The design, the spec, the judgment call stay yours. You make it, then say what needs to change.

Verno executes

One instruction, the whole set. Retags, transcribes, reconciles, cross-checks, and whatever else the job takes. Without ever getting bored.

You approve

Every change comes back with its reasoning. Nothing lands until an engineer accepts it.

Where it lives

On your files, in your systems.

Verno connects to your existing storage. It never becomes your system of record.

M-FilesProjectWiseSharePointOneDriveGoogle DriveWork network directories

And any other document management system. If your team keeps files somewhere else, Verno connects to it.

  • Native DWG/DXF edited in place
  • Lists written into your own Excel templates
  • Every revision retained with a full audit trail
  • Single-tenant, deployed where your policy requires
Integrations Security