Every project answers to a different set of codes. You tell Pirros which ones apply, and reviews check against exactly those.
You do not upload code books
Pirros processes code documents centrally — IBC, ADA, AISC, and regional codes. They are already in the system, already broken into clauses, and maintained by us.
Your job is selection, not sourcing. You never need to find a PDF of a code book, buy one, or upload one.
This is the opposite of how firm standards work, where you upload your own documents. Codes come from us; standards come from you.
Selecting codes
Code selection is part of configuring a review. You can select more than one — most projects need several, and a project spanning jurisdictions may need more still.
Every issue raised from a code check is labelled with the code it came from and links to the specific clause, so you can always see which book and which section a finding rests on.
Choosing well
Select the codes that actually govern the project. Selecting everything available is not a safer choice — it produces findings against codes that do not apply, which your team then has to dismiss one by one.
If a code you need isn't there
Tell us. Reach out to [email protected] to input a new code into Pirros and our team will take care of it within the hour! Which code, which edition, and which jurisdiction — that is what we need to add it, and it is the single most useful piece of feedback we get about coverage.
Frequently Asked Questions
Q: Do we need to buy or upload the code books?
A: No. Pirros processes them centrally and maintains them. You select which ones apply to each project.
Q: Can we select more than one code?
A: Yes. Most projects need several, and a project spanning jurisdictions may need more.
Q: Should we just select everything to be safe?
A: No. Codes that don't govern the project produce findings your team then has to dismiss one at a time. Select what actually applies.
Q: Is code selection per project or firm-wide?
A: Per project, because every project answers to different codes. Firm standards are the firm-wide input; codes are the per-project one.
Q: The code we need isn't in the list. What now?
A: Email [email protected] with the code, the edition, and the jurisdiction. That is exactly what we need to add it, and coverage requests are the most useful feedback we get.
Q: How do I know which code a finding came from?
A: Every code-check issue is labelled with its source and links through to the specific clause, so you can read the exact text a finding rests on.