Behind every building permit, BlinKode brings the requirement that applies to your building and its source. The decision stays yours.

I’d been an architect and construction manager for eight years when I came to Canada. I knew how buildings are designed, and I knew what a misread requirement costs once it’s found on site. Then I opened the Ontario Building Code and started again from the first page.

Not because the code is badly made. It’s exact for a reason: behind every sentence is someone’s safety. But it’s written to be precise, not to be found. A single design decision can depend on a definition in one part, a table in another, an exception a few articles away, and a standard the code only names. You read, follow the reference, come back, and read again.

Preparing for my exams made that very clear. I passed them. What stayed with me was how long it took to see the requirement behind the text, and that the time didn’t end with the exam. On every project in my two years of design and permit work here, the book came back out.

I thought that was because I was new. Then a building official I know told me something I haven’t forgotten: “I know the whole book, but I check it for every project. Trusting memory only increases the risk.”

That changed how I saw it. Going back to the book isn’t a sign that someone doesn’t know the code. It’s part of the work, and the most experienced people I know do it on every project. The question was never whether we should check. It was why a check still comes back with a page instead of the requirement, what it means for this building and its source.

Everything else in our work has moved on: how we draw, how we coordinate, how we share. The way into the code has barely changed. There are good books that explain parts of it, some with diagrams, but none I found that go through the whole code, article by article.

So I started with a simple idea: make the code visible. Each article’s plain meaning next to its original text, a diagram of what it asks of the building, and the articles it connects to, the ones it points to and the ones that point back. I tested the idea and talked it through with designers, and, before I started building, with three building officials. They told me the gap was real, from both sides of the counter.

They also showed me the idea was too small.

A building permit draws on more than one kind of expertise, and two of them I kept turning to. One reviews the work against the code and names each requirement not met: where it is, and the source that says so. The other advises on the code: what applies to this building, and why. Usually they live in different people and different offices, and what one knows reaches the other as a comment to be worked out again. As a designer, I didn’t want one more tool beside the many already open on my screen. I wanted both at my side, standing on the same understanding of the code and the building.

That’s what BlinKode is. CodeEase advises: the code, article by article, read the way I wished I could have read it, with an assistant that works from your project and asks before it assumes. Codiag reviews and reports, coming soon: each requirement not met on your drawings, with its source.

What BlinKode doesn’t do matters as much. It doesn’t approve anything; that stays with the building official. It doesn’t decide; that stays with you. You’re the one who designs, signs and answers for the building. BlinKode carries the legwork, so your judgment gets the time it deserves.

So here’s what I commit to. Every answer comes with its source, so you can check it the way that building official checks the book. When BlinKode can’t check something, it says so. And we build it with the people who do this work every day. If it falls short on your project, I want to hear about it.

Mehran Doulatabadi, CEO & Founder, Ontario Registered Designer (BCIN)