When you upload a standards document, Pirros reads it and pulls out the individual clauses — the specific, checkable statements buried in the prose.
You can see exactly what it extracted, and you should look at least once per document.
Why bother
Two reasons.
First, it is how you confirm the thing is working. Reviews check against these clauses and nothing else from that document. If a rule you care about was not extracted, it is not being enforced — and the extraction view is the only place you would find that out.
Second, it turns an abstract claim into something concrete. You are not taking on trust that Pirros "understands your standards." You can read the actual sentences it took from your actual document.
How to look
Go to the Standards page.
Click the document you want to inspect.
You will see the clauses extracted from it, along with the source text each one came from.
Read down the list and ask one question: are the things my reviewers actually check for in here?
If something is missing
Extraction works best on documents written as rules. A checklist with clear, discrete items extracts cleanly. A narrative policy document written in flowing paragraphs gives it less to work with.
If a rule you care about did not come through, the usual causes are:
It was implied rather than stated. If the document says "sheets should follow our usual sequence" without saying what that sequence is, there is no checkable rule there.
It lives in a table or diagram rather than in text.
It is in a different document that has not been uploaded yet.
The fix in each case is to state the rule explicitly in a document and upload it. Since standards have no version history, that means archiving the current document and uploading the revised one — see Upload your firm standards.
Frequently Asked Questions
Q: A rule I care about wasn't extracted. What do I do?
A: Check how it is written in the source document. Rules that are implied rather than stated — "follow our usual sequence" — have nothing checkable in them. State the rule explicitly, then archive the old document and upload the revised one.
Q: Can I edit the extracted clauses directly?
A: No. The clauses come from your document, so you change them by changing the document and re-uploading it. That is deliberate — it keeps your standards document and what Pirros checks against in step with each other.
Q: What kind of document extracts best?
A: Anything written as discrete rules. A QC checklist is close to ideal. A narrative policy document written in long paragraphs gives extraction much less to work with, and you will see that in the results.
Q: Do I need to check every document?
A: Once per document is enough, when you first upload it. After that it does not change unless you replace the document.
Q: The extraction looks wrong and I can't see why. Who do I ask?
A: Email [email protected] with the document and tell us which rules you expected to see. That feedback is genuinely useful to us as well as to you.