Design validation reports
Identifies documents containing references to design validation reports in Australian contexts. Higher confidence denotes reports of performed design validation (executed tests with observed results, pass/fail outcomes, deviations, conclusions, or approval), not plans or protocols; validation/review/protocol vocabulary alone remains discovery-only.
- Type
- regex
- Engine
- boost_regex
- Confidence
- medium
- Confidence justification
- category-aware structural regex with anchor and context constraints replaces phrase-only detection. Added context gating and exclusion rules improve precision and reduce incidental matches.
- Detection quality
- Topic false positive
- Jurisdictions
- global
- Regulations
- AML/CTF Act (Cth), HRIPA (Cth), IPA 2009 (Qld), My Health Records Act 2012 (Cth), NDB Scheme (Cth), Privacy Act 1988 (Cth), TIA Act 1979 (Cth), GDPR
- Frameworks
- ISO 27001, ISO 27701
- Data categories
- intellectual-property
- Scope
- wide
- Risk rating
- 7
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported
Pattern
(?is)\b(?:design\s+validation|validation\s+report|design\s+review|product\s+validation|verification\s+testing|test\s+protocol|acceptance\s+criteria|design\s+output|qualification\s+report|conformance\s+assessment)\b
Corroborative evidence keywords
design validation reports, design, validation, reports, product, quality, safety
Proximity: 300 characters
Should match
design validation— Primary topic phrase matchvalidation report— Case-insensitive topic phrase matchdesign review— Alternative topic phrase matchproduct validation— Additional topic phrase matchDV-330 executed 12 Jul; expected 50 N, observed 43 N; FAIL; deviation DEV-19; conclusion: redesign latch; approved by M. Chen.— Executed test with expected/observed values, outcome, deviation, conclusion, and approval (enforces at 75/85)
Should not match
unrelated generic text without domain phrases— No relevant topic phrases presentplaceholder value 12345— Random text should not match topic-specific regexproduct failure— Generic word pair from old broad template should not matchTest protocol and acceptance criteria for the upcoming review.— Planning material without results — discovery only, must not enforceThe theatre design received favourable reviews.— Design/review in an arts meaning must not matchTraining sample DV-001 observed 10, PASS.— Training/sample indicates a fabricated report — suppressed from enforcementvalidation report— Report label alone does not prove execution — discovery only, must not enforce
Known false positives
- Common words and phrases related to design validation reports appearing in policy documents, training materials, HR templates, or compliance guidelines without actual personal data. Mitigation: Require corroborative evidence keywords within the proximity window to confirm sensitive data context rather than general discussion.
- In Australian English, similar terminology used in formal or administrative contexts (education, professional documentation) that does not constitute sensitive data collection. Mitigation: Layer with additional contextual signals such as structured identifiers, form fields, or database column headers to distinguish sensitive records from general references.
- High-frequency pattern matches in large document corpora due to broad regex anchors. Expected match rate is significantly higher than specific identifier patterns. Mitigation: Tune confidence thresholds for bulk scanning. Consider using this pattern primarily as a pre-filter with secondary validation.
References
- https://www.safeworkaustralia.gov.au/doc/model-code-practice-how-manage-work-health-and-safety-risks
- https://www.productsafety.gov.au/product-safety-laws