Firm standards are what make a review yours rather than generic. Codes tell Pirros what the law requires. Your standards tell it how your firm does things.

You upload these once for the whole firm, and every project review checks against them from then on.

Most firms already have these documents. They are usually written for onboarding new staff or for project management, and they have simply never been machine-readable before.

QC checklists — what your QA/QC lead works through before a submittal. This is the most valuable single document you can upload, because it tells Pirros exactly what your reviewers already look for.

Drawing set standards — the package a new employee receives. How a set should be organised at each phase (SD, DD, CD), covering sheet organisation, sheet sequencing, formatting, and scale conventions.

BIM execution plan or template — the workflow guide every project starts from: software versions, standard templates, family and detail libraries, naming conventions, and general quality rules.

Standard operating procedures — any of the four levels are useful: policies (what the firm does and why), procedures (who does what and when), work instructions (how to perform a specific task), and the checklists and forms used at review gates.

That last step matters. It is how you confirm Pirros read what you think it read, and it takes a minute.

Codes. Pirros processes IBC, ADA, AISC and regional code books centrally, and you simply select which ones apply to each project. You never need to source or upload a code book yourself. You can do this if you are in a time crunch and need to run a review immediately wihtout waiting for the Pirros team to include the code (which will take about 1 hour).

Plenty of firms don't, particularly smaller ones. The standards exist — they are just in people's heads and in the way the work gets done.

Mira can read through your recent models and templates, work out what your firm does consistently, and draft a standards document you can edit and upload. See No standards document yet? Have Mira write one.

Q: Can I upload a Word document or a spreadsheet?

A: No. The Standards page accepts PDFs only. Export to PDF first — the content is what matters, not the original format.

Q: Can different offices or disciplines have different standards?

A: Standards can be chosen specifically for each project review. So you can upload any and all "Standard Documents" the Firm has and during each project review, the lead will choose the relevant standard to review.

Q: How do I update a standard when it changes?

A: Archive the existing document and upload the new version. There is no version history on standards documents, so there is nothing to roll back to — keep your own copy of the previous version if you need it.

Q: Do I upload code books here too?

A: No. Codes are processed centrally by Pirros and selected per project. This page is only for your firm's own documents. Speak with your CSM or our support chat ([email protected]) if you need a specific code added.

Q: How do I know Pirros actually read the document?

A: Open it after upload and look at the clauses that were extracted — you can see the exact text it pulled out. It is worth doing once per document. See Review the clauses Pirros extracted from your standards.

Q: We don't have any of these documents. Can we still use Project Review?

A: Yes. Code checks, constructability, default drawing rules and Mira reasoning all work without any firm standards uploaded. You just won't get findings specific to how your firm does things until you add them.

Q: How many documents should we upload?

A: Start with your QC checklist if you have one — it is the highest-value document because it encodes what your reviewers already check for. Add the others as you go.