Settings → Analysis rules lets you layer your firm's standards on top of the platform's defaults, for every project in your workspace.
What rules are for
- Thresholds you hold to. If your firm treats any dependency more than two major versions behind as a Warning, say so once here rather than correcting it in every report.
- Vocabulary. House terms for ratings and severities, so the draft arrives in the language your committee reads.
- Emphasis. Sectors and mandates differ. A regulated target needs the control environment weighted more heavily than a seed-stage one.
- Things to always check. A question your firm asks on every deal, added to every project's question set.
What rules cannot do
Rules change how evidence is weighed and how findings are worded. They cannot change what the evidence is. A rule cannot make a finding assert something the project's material does not support, and it cannot switch off the citation requirement or the review gate — those are not preferences.
Precedence
Platform defaults sit underneath, your workspace rules layer on top, and a project can override for its own scope. The narrowest applicable rule wins.
After changing a rule
Existing drafts are not rewritten — a finding an analyst already reviewed is not silently altered under them. Re-run the affected review areas to draft against the new rules. If a rule changes what counts as evidence, use full re-analysis so cached extraction is not reused.
Availability
Analysis rules are part of the higher plans. Without them, projects run against the platform defaults, which are maintained by the Percomb diligence team.