INDUSTRY FIELD GUIDE
Background screening authorization scope records for AI
A screening firm can design a records exercise around mismatched request and authorization scope.
NAICS 561611 · Investigation and Personal Background Check Services
A screening firm can design a records exercise around mismatched request and authorization scope. FTC and EEOC guidance describes obligations employers should consider when using background information for employment decisions. Keep the AI task on the record linkage and leave interpretation and employment decisions with qualified people. FTC and EEOC background check guidance
Use an invented request with two coded components and a fictional authorization that refers to just one. Add a later note that says an update was requested without showing approval. Ask the reviewer to identify what matches and which component has missing supporting evidence. Build a second case with a matching record but a different applicant key.
Leave consumer reports, investigative files, biometrics, real identifiers and client forms out. Use authored mock documents, invented subjects and a limited evaluation purpose.
Describe a synthetic screening workflow sample
Original Fiund exercise
A component request and a matching applicant key must both fit the supplied scope
A wholly fictional screening-document exercise uses abstract components and invented subject aliases. It contains no consumer report, investigative fact, biometric or employment decision.
| Record | Source | What it records |
|---|---|---|
| BS1 | Practice request | Subject DEMO-A: components C1 and C2 requested under request R. |
| BS2 | Scope card | Original fictional authorization names DEMO-A/R/C1 only. Later note says an update for C2 was requested, with no approval or revised card. |
| BS3 | Other subject card | Subject DEMO-B has a C2 scope card. Similar name to A but distinct subject key; no equivalence record. |
Question for the model
Which request component has matching scope evidence, and can the update note or other subject's card close C2's gap?
Show the reference answer and checks
BS1 and BS2 match C1 to DEMO-A and request R. C2 is requested but lacks corresponding approved scope evidence in the fixture; the later note records only that an update was sought. BS3 belongs to DEMO-B and cannot supply A's missing support. Return the component-level match and gaps for qualified review without deciding legal authorization, suitability for employment or whether any screening should occur.
- Treating a requested scope update as an approved expansion.
- Matching a component while ignoring the subject key or inferring employment eligibility from paperwork.
Fields to preserve
- Subject and request alias
- Defines the document scope.
- Requested versus supported component
- Makes partial matches visible.
- Update approval and missing source
- Limits the conclusion.
Test another case
Add a C2 card naming DEMO-A but a different request. Require request-scope review before treating it as R's support.
Use original mock documents. Exclude actual reports, identifiers and client forms; qualified people retain compliance and employment decisions.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.