Exit interview records

Name: Exit interview records
Creator: TestPattern Community
License: https://opensource.org/licenses/MIT

Detects exit interview, exit survey and separation interview records for an identified departing employee, with reasons for leaving, last day or resignation date, rehire eligibility or satisfaction scores.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: Medium: the primary phrases also appear in policies, guidance, blank forms and news, so enforce tiers require a populated person field and 85 adds a record-specific populated detail plus independent corroboration. Person values are customer-defined (employee IDs, position numbers), so the field regexes use labelled loose values with a placeholder guard. 85/75 are heuristic evidence tiers, not measured accuracy.
Detection quality: Topic false positive
Jurisdictions: global
Regulations: Fair Work Act 2009 (Cth), Privacy Act 1988 (Cth), Information Privacy Act 2009 (Qld), NDB Scheme (Cth), GDPR
Frameworks: ISO 27001, ISO 27701
Data categories: pii, employment
Scope: wide
Risk rating: 8
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?i)\b(?:exit\s+(?:interview|survey|questionnaire|feedback)|separation\s+interview|departure\s+interview|resignation\s+feedback)\b

Corroborative evidence keywords

workload, culture, career, new employer, flexibility, remuneration, bullying, wellbeing, confidential

Proximity: 300 characters

Should match

Exit interview Departing employee: Avery Teston Position title: Field Technician Last day: 26/09/2026 Primary reason for leaving: Workload and lack of flexibility with the roster. Eligible for rehire: Yes. Comments on team culture recorded confidentially. — 85: Exit interview with employee, last day, reason and rehire
Separation interview notes Employee: Jordan Staffson Resignation date: 2026-09-12 Satisfaction: 2/10 Leaving for a new employer offering better career progression. — 85: Separation interview with resignation date and satisfaction
Exit survey response Employee ID: 5520117 Free text: felt unsupported after the team restructure. — 75: Exit survey naming an employee ID, no dated detail

Should not match

Exit interviews help us understand why people leave. This procedure explains who conducts the exit survey and how results are reported. — Procedure text - must stay below 75
Exit interview form Departing employee: __________ Last day: ___/___/____ Reason for leaving: __________ — Blank form - must stay below 75
Our annual exit survey results show 38% of leavers cited workload, according to the workforce report media release. — News / aggregate statistics - must stay below 75
unrelated generic text without domain phrases — No relevant topic phrases present
placeholder value 12345 — Random text should not match topic-specific regex
employee interview — Generic word pair from old broad template should not match

Known false positives

Policies, directives, fact sheets, guidance and training material that name the record type. Mitigation: Enforce tiers require a populated person field; guidance text has labels without values and guidance/training/media-release framing is excluded.
Blank forms, templates and HR system configuration. Mitigation: Blank lines, square- and angle-bracket placeholders, XXX and n/a/tbc values are rejected by the placeholder guard; template/fixture words are excluded.
Aggregate statistics and news reporting. Mitigation: No populated person field, so these stay at 65 discovery.
Records that identify the person only in free text (no field label) fall to 65. Mitigation: Accepted precision trade-off; extend the person-field regex with the customer employee-id format to recover recall.