Our story
Building-code review should start while the Revit model can still change.
CodeGuardian started from a problem experienced firsthand in architecture and VDC work: potential code and documentation issues are often found after a team has already invested time coordinating the design.
Founder insight
Built from the workflow, not outside it.
Founder Adedayo Otitolaye encountered the same pattern across architecture, VDC, freelance, and Revit-based project work: code knowledge was critical, but review often happened through manual checklists, scattered references, senior staff bottlenecks, and late permit comments.
The core insight behind CodeGuardian is that advisory review becomes more useful when it is connected to the live model. A warning should identify what deserves attention, show its priority, and help the user locate the affected element while the design can still change.
CodeGuardian turns that insight into a Revit-native workflow for model, documentation, coordination, and permit-readiness review.
The bigger vision
From earlier design review to clearer permitting.
Today, CodeGuardian helps designers review advisory risks inside Revit. The longer-term vision is a shared compliance workflow that helps design teams submit clearer projects and helps municipalities organize review more consistently.
One platform, two sides of the same problem.
- Designers catch code issues before submission.
- Reviewers evaluate plans with clearer issue tracking.
- Cities reduce repetitive manual review work.
What we believe
Compliance should be earlier, clearer, and easier to act on.
Building code compliance will always require professional judgment. CodeGuardian is not replacing architects, engineers, code officials, or licensed reviewers. It is giving them a better way to see risk earlier.
Our goal is to help designers catch issues early and help cities review plans faster.