AI Bias Assessment Template
AI BIAS AND IMPACT ASSESSMENT WORKSHEET
INTERNAL WORKSHEET — NOT A CERTIFICATION OR DEPLOYMENT APPROVAL
1. Assessment Control
| Field | Entry |
|---|---|
| Organization | [________________________________] |
| System / model / version | [________________________________] |
| Assessment ID | [________________________________] |
| Product owner | [________________________________] |
| Assessment lead | [________________________________] |
| Independent reviewer | [________________________________] |
| Assessment date | [__/__/____] |
| Evidence cutoff | [__/__/____] |
| Decision requested | [pilot / deploy / expand / renew / investigate / retire] |
| Prior assessment and open conditions | [________________________________] |
2. System and Decision Context
| Issue | Verified description | Evidence |
|---|---|---|
| Intended purpose | [________________________________] | [________________________________] |
| Prohibited or out-of-scope uses | [________________________________] | [________________________________] |
| Decision, recommendation, ranking, generation, or other output | [________________________________] | [________________________________] |
| Person or process receiving the output | [________________________________] | [________________________________] |
| Consequence of the output | [________________________________] | [________________________________] |
| Population and geography | [________________________________] | [________________________________] |
| Deployment channel and environment | [________________________________] | [________________________________] |
| Human role and override | [________________________________] | [________________________________] |
| Vendor, foundation model, or external dependency | [________________________________] | [________________________________] |
| Change since prior version | [________________________________] | [________________________________] |
3. Current-Authority and Obligation Register
Counsel must complete one row for every potentially applicable jurisdiction, sector, contract, program, decision type, and population.
| Authority / obligation | Scope and trigger | Required assessment or control | Official source | Checked on / reviewer |
|---|---|---|---|---|
| Employment / worker decision | [____] | [____] | [____] | [____] |
| Housing / credit / insurance / benefit decision | [____] | [____] | [____] | [____] |
| Education / healthcare / public service | [____] | [____] | [____] | [____] |
| Consumer / privacy / biometric / child data | [____] | [____] | [____] | [____] |
| Accessibility / disability accommodation | [____] | [____] | [____] | [____] |
| Procurement / customer / platform contract | [____] | [____] | [____] | [____] |
| Other jurisdiction or sector | [____] | [____] | [____] | [____] |
This worksheet does not state that any named legal category, test, threshold, notice, audit, retention period, appeal, or remedy applies.
4. People and Impact Mapping
| Group or role | How affected | Benefit | Harm scenario | Severity | Evidence / consultation |
|---|---|---|---|---|---|
| [________________________________] | [________________________________] | [________________________________] | [________________________________] | [____] | [________________________________] |
| [________________________________] | [________________________________] | [________________________________] | [________________________________] | [____] | [________________________________] |
| [________________________________] | [________________________________] | [________________________________] | [________________________________] | [____] | [________________________________] |
Include direct subjects, applicants, users, workers, customers, nonusers, bystanders, reviewers, operators, and people affected by feedback loops.
5. Data, Labels, and Representation
| Control | Assessment |
|---|---|
| Data sources and collection periods | [________________________________] |
| Sampling and inclusion / exclusion | [________________________________] |
| Missing populations or contexts | [________________________________] |
| Target, label, proxy, or ground-truth definition | [________________________________] |
| Labeler instructions and disagreement | [________________________________] |
| Historical process embedded in data | [________________________________] |
| Measurement and recording error | [________________________________] |
| Protected or sensitive attributes available for evaluation | [________________________________] |
| Proxy and correlation review | [________________________________] |
| Synthetic, augmented, or generated data | [________________________________] |
| Data drift and refresh plan | [________________________________] |
| Documentation and lineage | [________________________________] |
6. Evaluation Design
| Item | Approved method |
|---|---|
| Primary performance measures | [________________________________] |
| Harm-relevant error measures | [________________________________] |
| Comparison groups and intersections | [________________________________] |
| Reference or benchmark | [________________________________] |
| Minimum sample / uncertainty treatment | [________________________________] |
| Threshold selection | [________________________________] |
| Calibration analysis | [________________________________] |
| False-positive / false-negative analysis | [________________________________] |
| Ranking, allocation, or exposure analysis | [________________________________] |
| Language, accessibility, geography, and device slices | [________________________________] |
| Stress, edge, and adversarial tests | [________________________________] |
| Independent replication or review | [________________________________] |
A missing difference does not prove fairness. A measured difference does not by itself identify its cause or legal significance.
7. Results Register
| Slice / scenario | Population count | Measure | Result | Uncertainty | Practical impact | Reviewer conclusion |
|---|---|---|---|---|---|---|
| [________________________________] | [____] | [____________] | [____] | [____] | [________________________________] | [________________________________] |
| [________________________________] | [____] | [____________] | [____] | [____] | [________________________________] | [________________________________] |
| [________________________________] | [____] | [____________] | [____] | [____] | [________________________________] | [________________________________] |
Attach code, data version, queries, test output, and reproducibility instructions.
8. Cause and Control Analysis
| Finding | Possible cause | Evidence | Proposed mitigation | Owner | Due date |
|---|---|---|---|---|---|
| [________________________________] | [________________________________] | [________________________________] | [________________________________] | [____] | [__/__/____] |
| [________________________________] | [________________________________] | [________________________________] | [________________________________] | [____] | [__/__/____] |
Potential controls to assess include data changes, label review, feature restrictions, model changes, thresholds, uncertainty handling, human review, documentation, user interface, access limits, appeal or correction processes, monitoring, and retirement.
9. Human Review and Contestability
| Question | Verified answer |
|---|---|
| Who reviews outputs | [________________________________] |
| Training and authority | [________________________________] |
| Information available to reviewer | [________________________________] |
| Time and workload | [________________________________] |
| Automation-bias control | [________________________________] |
| Override and escalation | [________________________________] |
| Person notice or explanation | [________________________________] |
| Correction, complaint, or appeal path | [________________________________] |
| Response tracking and quality review | [________________________________] |
| Accommodation and language access | [________________________________] |
Do not claim that human involvement cures a system risk without testing the actual workflow.
10. Monitoring and Change Control
| Monitor | Metric / trigger | Frequency | Owner | Escalation |
|---|---|---|---|---|
| Performance drift | [________________________________] | [____] | [____] | [________________________________] |
| Group / intersection difference | [________________________________] | [____] | [____] | [________________________________] |
| Complaint / override / appeal | [________________________________] | [____] | [____] | [________________________________] |
| Data or population shift | [________________________________] | [____] | [____] | [________________________________] |
| Vendor or model update | [________________________________] | [____] | [____] | [________________________________] |
| Incident or new use | [________________________________] | [____] | [____] | [________________________________] |
Reassessment triggers: purpose, population, geography, data, label, model, threshold, vendor, interface, human workflow, law, contract, complaint pattern, incident, or material performance change.
11. Decision Record
| Decision | Select |
|---|---|
| Approve limited test | ☐ |
| Approve with conditions | ☐ |
| Require remediation and retest | ☐ |
| Reject or pause | ☐ |
| Retire or roll back | ☐ |
Scope and conditions: [________________________________]
Known limitations: [________________________________]
Residual risks and rationale: [________________________________]
Required notices, documentation, or contractual controls: [________________________________]
Next review date / trigger: [________________________________]
12. Final Review Gate
☐ Intended and prohibited uses are documented.
☐ Affected people and harm scenarios were reviewed.
☐ Current legal and contractual obligations were entered from official sources.
☐ Data, labels, representation, proxies, and lineage were assessed.
☐ Evaluation slices, measures, uncertainty, and reproducibility are documented.
☐ Mitigations were tested rather than merely proposed.
☐ Human review, correction, complaint, and accessibility processes were evaluated.
☐ Monitoring, escalation, change, rollback, and reassessment controls are assigned.
☐ No unsupported fairness, compliance, certification, safety, or legal conclusion remains.
Product owner: [________________________________]
Data-science reviewer: [________________________________]
Legal reviewer: [________________________________]
Domain / affected-community reviewer: [________________________________]
Approving executive: [________________________________]
Approval date: [__/__/____]
About this template
- Last updated
- August 31, 2026
- Citations checked
- August 31, 2026
- Jurisdiction
- All states
- Category
- Compliance & Regulatory
Compliance documents are what regulated businesses use to prove they follow the rules that apply to their industry, whether that is privacy, anti-money-laundering, consumer protection, or sector-specific requirements. Regulators look for consistent policies, up-to-date records, and clear evidence of employee training. The cost of getting compliance paperwork right is almost always smaller than the cost of an enforcement action, fine, or public disclosure.
Not legal advice
This template is provided for informational purposes. We recommend having an attorney review any legal document before signing, especially for high-value or complex matters.
Checked against the law it cites
A reviewer verified this template's legal citations against the official source on August 31, 2026.
Draft your AI Bias Assessment Template in the editor
Answer a few questions, let the AI editor draft each section from your answers, review it, and download Word and PDF. $99 one time, or $249 per month for every document and every Ezel app.