// Plan Review for Civil Engineering
QualRivu brings plan review for municipalities and civil engineering firms across Canada, with the discipline high-consequence work demands. The AI reads the drawings. Deterministic code computes and cites. Your licensed engineer or designated reviewer holds every determination.
A 40-sheet set is flagged in less than 10 minutes.
Next: product// Product
The AI pass is one step. Standards intake, workflow management, deterministic verification, collaboration and export are the rest - all in the browser.
The AI only extracts: lengths, counts, spacing, clearance and verdicts are computed in code, and citations resolve to a verified section.
The AI turns manuals, bylaws, and specs into structured, reusable audit rules: a living library of your jurisdiction's requirements.
Cross-references resolve across the submission, and structures and pipe runs shown on multiple sheets are reconciled; mismatches surface as findings, not surprises.
QualRivu flags deviations from bylaws and standards and places spatial markups on your drawings, with every finding engineer-verified before sign-off.
A high-performance canvas renders full-resolution sheets at any zoom, with measurement tools that snap to the drawing's CAD vectors - real linework, not a pixel estimate.
Create teams with defined roles, assign drawings, track review status in one submission-to-decision pipeline; live dashboards roll up progress. A traceable record holds every verified review action.
Work the same drawing with live cursors or on your own; add markups and submit comments for review. Built for iPads and tablets. Lose your connection with a sheet open and your markups queue on the device, then sync when you reconnect.
Ask the AI about anything on the drawing; answers cite the exact standards section. Where a sheet cross-references detail sheets, the AI reads those, so the answer carries the full design context.
Drawings, audit records and project data stay in Canada (Azure Canada Central), application and database in the same region. Zero AI training, data encrypted in transit and at rest. Built for FIPPA and PIPEDA, SOC 2 on the roadmap. On a dedicated deployment, storage and database run on your servers or cloud account.
// How It Works
From defining your standards to exporting results: four steps that replace weeks of manual back-and-forth.
A submission arrives as an attachment. Comments come back as a marked-up PDF export. Questions live in reply-all threads. Three weeks later, nobody can say which version was actually reviewed, or whether comment #14 was ever resolved.
One place, one version: reviewers, submitters and PMs work the same sheets, with roles deciding who can flag, resolve or approve. Questions attach to the markup they're about. Every item carries a disposition, so review state is a fact you read, and the memorandum and marked-up package assemble themselves from the record.
The AI transforms engineering manuals into structured audit rules, building a digital library of your jurisdiction's unique requirements.
Upload the set. QualRivu reads what is printed, measures what is drawn, computes each verdict in code, and places a markup at the station where it applies, with the clause it checked and the action the standard requires.
Your team works the same drawing, together or on their own time. Live sessions share cursors, so you can point at what you mean. Verify flagged findings with measurement tools, accept, reject or discuss each one, then clear the Design Checklist to catch what the AI missed. The reviewer holds every determination.
Export drawings with markups to PDF, readable as real comments in Acrobat or any PDF reader, alongside a memorandum and design data tables linking every finding to its drawing. Release the review to the submitter as Revisions Required, Approved or Rejected - markups land on their drawings, and the record is read-only.
// Why it holds up
Pointing a capable AI model at a drawing produces a demo, not a review tool. What makes it one is everything built around the model. Two failure modes we engineered out, and what happens instead:
What happens
A vertical curve is annotated K=4.1, and the AI model reports the finding against "section 4.1" (a sanitary sewer clause) because the number looks like one. Nothing looks wrong until someone opens the standard.
How it's handled
Every citation must resolve to a real section of the jurisdiction’s own standards before it is shown - and to the right discipline: a road finding cannot carry a sanitary clause.
What happens
A construction note - “REMOVE AND DISPOSE OF EX. HYDRANT” - mentions a hydrant, and the model counts one. Six mentions become six hydrants where the drawing shows two.
How it's handled
Counts are reconciled against the drawing's own CAD layers, where each hydrant has an exact position - prose can confirm attributes but never invent a feature. Sheets without those layers say their counts are model-only.
What happens
A pavement resurfacing sheet is sent the watermain, storm and sanitary detail sheets on every model call - details for trenches it does not cut. Beyond their cost, irrelevant references invite irrelevant findings.
How it's handled
Which reference sheets accompany a drawing is decided by what that drawing actually does. A pavement-restoration sheet gets the utility details, because it repairs a trench; a resurfacing sheet does not.
What happens
A standards library states three minimum widths for a cycling facility - painted, one-way protected, two-way protected. A drawing naming none of them can be judged against any; choosing one is a coin-flip.
How it's handled
Where the drawing does not say which sub-type applies, the check uses the most lenient candidate limit, so it can only fail a design that fails under every reading - and the finding states that the requirement varies and names what the reviewer must confirm.
None of this was fixed by a better model. Each case is a decision the model does not get to make.
Next: who we are// About
QualRivu was founded to fix one of the most persistent bottlenecks in Canadian infrastructure development: the design review process. What should take days routinely takes months, stalling projects and adding unnecessary cost to municipalities and developers alike.
We are building the review layer that sits between a submitted drawing set and a signed decision: the standards a jurisdiction actually enforces, the arithmetic that proves compliance, and the record of who decided what.
Headquartered in British Columbia, QualRivu Inc. is federally incorporated and built to serve municipalities and civil engineering firms from coast to coast.
The Founding Team
Alex
Co-Founder
George
Co-Founder
Dre
Co-Founder
// FAQ
The questions municipalities and consultants ask first.
// Contact
Book a 30-minute demo to see QualRivu in action with your team's real workflow.