A DrChecks-Style Review Workflow for the Projects You Can't Run in ProjNet

DrChecks — the Design Review and Checking System — is the design review module of ProjNet, a suite owned by the U.S. Army Corps of Engineers' Engineer Research and Development Center (ERDC) and sold to owner organisations by the National Institute of Building Sciences. Engineer Regulation 1110-1-8159 made it mandatory for USACE design reviews from FY02, and ProjNet's published client list today spans GSA, NASA, NAVFAC, the Department of State's Overseas Building Operations and the VA. If your contract specifies DrChecks, this page is not an argument to do otherwise: it is the system of record, and your comments belong in it.

The Problem Isn't DrChecks. It's Every Review DrChecks Doesn't Cover.

Firms that run federal work know the rhythm well — a reviewer raises a comment, the designer evaluates and responds, the reviewer backchecks it and closes it, and nothing disappears in between. Then the same firm opens a private, state or commercial job, or needs an internal review before anything gets posted to the agency, or has to coordinate three subconsultants — and the whole discipline collapses back into a spreadsheet and an email thread.

That gap is structural, not accidental. ProjNet access is granted by the owning agency, per project, on the agency's subscription: you cannot extend it to a client who isn't a subscriber. And the published NIBS guideline pricing — $31,049 a year for 1–20 projects, $62,094 for 41 or more, plus a one-time $5,000 setup fee (rates published as valid through December 2026; actual subscriptions are quoted per customer) — is priced for an agency programme, not for a design office that wants the same rigour on its own work.

What Contrat.io Keeps From the DrChecks Model

• The comment–response–backcheck record. Every comment keeps its own identity, its response, its history and an explicit close — the structure described in What Is a Comment Resolution Sheet?.

• Roles that mean something. Authors, Reviewers and Document Controllers each see and do exactly what their role allows, rather than everyone editing the same file.

• Revision discipline. Freeze the cycle, issue a revision, and open comments carry over instead of being retyped or quietly lost between issues.

• An audit trail you can hand over. Who said what, when, and how it was closed — exportable at close-out.

• Reviewers you can actually invite. Free Collaborator roles mean the cost of adding one more reviewer is never the reason a comment ends up in an email.

What It Deliberately Isn't

Contrat.io is one tool, not a suite. ProjNet's bidder inquiry, submittal register, plan room, RFI and criteria-management modules have no counterpart here, and Contrat.io is not accredited to host federal Sensitive But Unclassified information. If your requirement is a federally accredited programme platform, DrChecks is the right answer and this is not a substitute for it.

Most firms asking about a DrChecks alternative are not trying to leave DrChecks. They are trying to stop running two standards: a disciplined, auditable loop on federal work and a spreadsheet on everything else. Framed that way, the comparison that matters isn't Contrat.io vs DrChecks — it's Contrat.io vs the Excel-and-email process you fall back on the moment a project isn't federal.