HR Record Taxonomy and Documentation Architecture

Introduction

Human resource records are not merely administrative by-products. They are organizational evidence: evidence of decisions, employment relationships, legal compliance, compensation, capability development, workplace safety, and organizational accountability. A well-designed HR record system enables authorized users to locate reliable information, reconstruct decisions, protect sensitive data, and dispose of records lawfully. A poorly designed system creates duplication, contradictory versions, privacy risks, weak audit trails, and costly disputes.

HR record management therefore requires more than scanning documents into folders. It requires a taxonomy, a file plan, metadata, naming conventions, version controls, retention rules, access restrictions, and explicit rules concerning which source is authoritative. These components form a documentation architecture: the designed structure through which HR information is created, classified, stored, used, shared, preserved, and destroyed.

The subject is especially important in contemporary organizations because HR records exist across human resource information systems (HRIS), applicant-tracking systems, payroll platforms, learning-management systems, occupational-health systems, collaboration tools, email, paper files, and employee self-service portals. The challenge is not simply volume. It is the need to preserve context, authenticity, integrity, confidentiality, availability, and accountability across interconnected systems.

Learning Objectives

By the end of this chapter, students should be able to:

1. Explain the purpose and principles of HR record taxonomy and documentation architecture.
2. Classify major categories of HR records and distinguish records from transitory information.
3. Design a practical HR file plan for a complex organization.
4. Develop naming conventions and metadata schemas that support retrieval, governance, and auditability.
5. Apply version-control and authoritative-source rules to resolve conflicting records.
6. Evaluate privacy, security, retention, legal-hold, and ethical implications.
7. Recommend improvements to an HR documentation architecture in an applied organizational case.

1. Records as Organizational Evidence

A record is information created, received, or maintained as evidence of an activity, transaction, decision, obligation, or relationship. In HR, a signed employment contract, approved salary change, interview evaluation, payroll register, performance review, safety investigation, or termination notice may all be records. By contrast, an informal duplicate, an obsolete draft, or a personal convenience copy may not need to be retained as an official record, although its status must be determined through policy rather than assumption.

The distinction between data, documents, and records is useful:

• Data are individual facts or values, such as an employee identifier, salary amount, or training date.
• Documents are organized expressions of information, such as a policy, letter, form, report, or spreadsheet.
• Records are documents or data preserved because they provide evidence of an activity, decision, right, obligation, or event.

A record may be structured, such as a payroll database entry, or unstructured, such as an email approving a promotion. It may be digital, paper-based, audio-visual, or generated automatically by a system. Its evidential value depends not only on content but also on context: who created it, under what authority, when, for what process, and whether it has been altered.

1.1 Core quality characteristics

A defensible HR record system seeks the following qualities:

These qualities may conflict. For example, broad availability improves operational access but can weaken confidentiality. Strong confidentiality controls may reduce usability if authorized managers cannot obtain information promptly. Documentation architecture is therefore a governance problem involving risk-based trade-offs.

2. Principles for HR Documentation Architecture

2.1 Classification by business function

Records should first be classified according to the HR activity they support, not according to the software in which they happen to reside. A recruitment record remains a recruitment record whether it is stored in an applicant-tracking system, email, or a shared drive. Functional classification improves consistency when technology changes.

2.2 One record, one accountable process

Each official record should have a defined process owner. The process owner is responsible for accuracy, access rules, retention, and disposition. Ownership does not necessarily mean that the owner physically stores the record. For example, payroll may own wage calculations while an enterprise records team manages the repository.

2.3 Minimum necessary collection and access

Organizations should collect and expose only information necessary for a legitimate purpose. This principle reduces privacy risk and supports responsible use of employee information. A manager may need confirmation that an employee is medically fit for a role, but may not need access to a diagnosis or clinical report.

2.4 Lifecycle orientation

A record has a lifecycle: creation, active use, semi-active storage, archival preservation or destruction. Lifecycle rules should be designed before records accumulate. Retention periods must be based on applicable law, regulatory requirements, contractual needs, limitation periods, operational value, and litigation or investigation risk.

2.5 Context before convenience

A file name such as “final_review_new.docx” provides little reliable context. A good architecture preserves the relationship among the employee or position, process, event date, status, and source. Convenience for the person saving a file must not undermine retrieval and evidential value for the organization.

2.6 Controlled change

Policies, forms, procedures, job descriptions, and templates change over time. The system must show which version was effective at a particular date. Current documents should not overwrite historical evidence where the prior version affected an employment decision or obligation.

3. HR Record Taxonomy

A taxonomy is a controlled classification scheme that groups records according to shared characteristics. The following taxonomy is a practical enterprise-level model. Organizations should adapt it to their legal environment, workforce structure, and operating model.

3.1 Personnel and employment records

Personnel records document the employment relationship and its administrative history. Typical records include:

• employment applications and employment agreements;
• offer letters and contract amendments;
• job title, position, department, location, and reporting-line records;
• identity and right-to-work evidence, where legally required;
• emergency-contact information;
• probation or introductory-period decisions;
• employee acknowledgements of policies;
• authorized changes to personal or employment data;
• correspondence concerning employment status.

Personnel records should be separated from highly restricted categories such as medical records, investigation files, and payroll banking information. A “master personnel file” should not become an unrestricted container for every document concerning an employee.

3.2 Recruitment and selection records

Recruitment records document workforce acquisition and selection decisions. They may include workforce requisitions, approved job descriptions, advertisements, sourcing records, candidate applications, screening results, interview schedules, structured evaluation forms, assessment results, reference checks, selection rationales, offer approvals, and unsuccessful-candidate communications.

A major governance issue is the distinction between candidate records and employee records. When a candidate is hired, selected recruitment records may become part of the employment record, while other records remain subject to recruitment-specific retention and privacy rules. Access should be role-based: recruiters and selection panel members may require access that line managers do not.

Structured evaluation records are particularly important because they demonstrate whether selection decisions were based on job-related criteria. Free-text notes should be governed carefully because informal comments may introduce bias, disclose protected information, or undermine the defensibility of a decision.

3.3 Payroll and time records

Payroll records document compensation obligations and payments. They may include salary and wage rates, payroll registers, deductions, tax or social-insurance information, time records, overtime approvals, expense reimbursements, bank-payment instructions, garnishments, and payroll reconciliation reports.

Payroll records frequently contain high-risk personal and financial information. Access should normally be segmented among payroll processors, finance personnel, HR administrators, managers, auditors, and employees. A manager may see approved hours and departmental labor costs but should not automatically see bank details or tax information.

Payroll systems often generate authoritative transactional records, whereas an HRIS may contain a reference copy of compensation data. The architecture must explicitly identify which system controls each field.

3.4 Benefits and leave records

Benefits records document eligibility, enrollment, elections, claims administration, leave entitlements, and communications. Examples include benefit elections, beneficiary designations, insurance enrollment, pension or retirement records, leave requests, leave approvals, accommodation-related documentation, and vendor correspondence.

Benefits information can reveal health, family, financial, or religious information. It should therefore be segregated according to sensitivity. Leave administration requires particular care because the fact of leave may be operationally necessary for a manager, while the underlying medical or personal justification may be restricted.

3.5 Performance and conduct records

Performance records include objectives, performance reviews, feedback, improvement plans, recognition records, disciplinary notices, attendance-related actions, and performance-related correspondence. They should distinguish routine performance management from formal disciplinary or investigation records.

A performance record should identify the relevant review period, criteria, reviewer, employee response, approval status, and effective date. Organizations should avoid changing an approved evaluation without preserving the original and documenting the reason for amendment. Employee comments and acknowledgement should be retained as part of the evidential record, without treating acknowledgement as proof of agreement.

3.6 Learning and development records

Learning records document capability development and compliance training. They include training needs analyses, course approvals, registrations, attendance, assessments, certifications, licenses, learning plans, development objectives, and training evaluations.

The authoritative source may differ by field. The learning-management system may be authoritative for completion status, while an external licensing body may be authoritative for license validity. A manager’s spreadsheet may be a planning aid but not the official certification record.

3.7 Health, safety, and occupational records

Health and safety records include incident reports, hazard assessments, inspection records, safety training, workers’ compensation documentation, exposure monitoring, fitness-for-duty determinations, and workplace accommodation information. Medical records and clinical details require especially restricted access and, in many jurisdictions, separate storage from general personnel records.

A useful separation is between:

1. operational safety records, such as an incident date, location, hazard, corrective action, and status; and
2. confidential medical or clinical records, such as diagnoses, test results, and treatment information.

The first may be needed by safety managers and operational leaders. The second should be limited to authorized occupational-health or legal personnel.

3.8 Employee-relations and investigation records

Employee-relations records include grievances, complaints, investigations, mediation records, workplace-conduct reports, findings, corrective actions, and appeal outcomes. These records are often sensitive because they may contain allegations, witness statements, personal data, and legally privileged material.

Investigative records should preserve procedural integrity. The file should identify the allegation, mandate, investigator, evidence reviewed, interviews conducted, findings, decision authority, and actions taken. Draft interview notes should be managed according to policy; destroying drafts simply because they are inconvenient may be improper, while retaining every informal note indefinitely may create unnecessary risk.

3.9 Separation and post-employment records

Separation records document resignation, retirement, redundancy, dismissal, final pay, exit obligations, return of property, benefits continuation, references, appeals, and post-employment restrictions. The separation event should be clearly distinguished from the reason recorded in a confidential investigation or medical file.

Retention must account for possible claims, benefit obligations, tax requirements, reference requests, intellectual-property protection, and legal holds. A terminated employee’s records should not disappear from operational systems before payroll, access control, audit, and legal processes are complete.

4. Designing a File Plan

A file plan is a controlled map of record categories, subcategories, owners, locations, access rules, retention requirements, and disposition actions. It translates the taxonomy into an operating structure.

A useful file-plan entry contains:

4.1 Hierarchical and faceted classification

A hierarchical file plan places records in levels, such as HR → Recruitment → Requisition → Candidate evaluation. It is intuitive and useful for browsing. However, hierarchy alone can be limiting because a record may need to be found by employee, location, legal matter, process, or date.

A faceted approach supplements the hierarchy with metadata. For example, an investigation record may be classified by function, case number, employee identifier, location, allegation type, confidentiality level, and status. The combination improves retrieval without forcing one folder to represent every relationship.

4.2 File-plan design principles

A professional file plan should:

• use stable business functions rather than temporary project names;
• avoid excessive depth and ambiguous catch-all folders;
• distinguish official records from working material;
• identify system-of-record status;
• support records generated by automated workflows;
• include exceptions, such as legal holds and investigations;
• accommodate reorganizations without changing historical meaning;
• map each series to a retention and access rule.

A folder named “Miscellaneous HR” is a warning sign. It usually indicates that the taxonomy is incomplete or that staff have not been trained to classify records.

5. Naming Conventions

Naming conventions improve retrieval, reduce duplication, and support automated processing. A naming standard should be short enough to use consistently and precise enough to distinguish records.

A practical pattern is:

[RecordClass]_[SubjectID]_[Process or Event]_[EffectiveDate]_[Status]_[Version]

For example:

PER_004582_EmploymentAgreement_2025-07-01_Approved_v03.pdf

Recommended rules include:

• use a stable employee or case identifier rather than a full name where possible;
• use the ISO date format YYYY-MM-DD to support chronological sorting;
• use controlled terms for status, such as Draft, Review, Approved, Superseded, or Cancelled;
• use a consistent version pattern, such as v01, v02, v03;
• avoid unexplained abbreviations, spaces, emojis, and punctuation that may fail across systems;
• do not place sensitive information, such as diagnoses, in file names;
• do not use “final” as the only indicator of approval;
• preserve the original file format when authenticity or editability matters.

Names should not carry every possible attribute. Excessively long names become difficult to read and may exceed system limits. Metadata should hold information that does not belong in the file name.

6. Metadata Schema

Metadata is structured information about a record. It supports discovery, access control, retention, audit, interoperability, and automated workflows.

A core HR metadata schema may include:

Metadata should be governed as carefully as document content. Incorrect metadata can expose restricted records, trigger premature destruction, or cause an authorized user to rely on the wrong version.

6.1 Controlled vocabularies

Terms such as “approved,” “closed,” “active,” and “superseded” should have defined meanings. A controlled vocabulary prevents one team from using “complete” to mean “approved” while another uses it to mean “uploaded.” Where multiple systems exchange records, code lists and data dictionaries should be aligned.

6.2 Identifiers and privacy

Stable identifiers improve matching, but identifiers can themselves be personal data. Access to cross-reference tables should be restricted. A record architecture should not assume that pseudonymization eliminates risk; re-identification may remain possible when datasets are combined.

7. Version Control and Document Status

Version control establishes the history of changes and identifies the version that should be used. It is essential for policies, employment contracts, job descriptions, forms, procedures, compensation schedules, and approved assessments.

A simple status model is:

1. Draft: being developed and not authorized for operational reliance.
2. Under review: submitted for designated review or consultation.
3. Approved: authorized by the responsible authority and effective on a stated date.
4. Superseded: replaced by a later approved version but retained for historical evidence.
5. Withdrawn or cancelled: removed before or after implementation for a documented reason.

Version control should record the author, reviewer, approver, approval date, effective date, change summary, and reason for change. An approved document should not be silently overwritten. If an error is corrected, the correction should generate a new version or an amendment record.

The distinction between version and copy is important. A version represents a controlled change in content. A copy is the same version stored or transmitted elsewhere. Multiple copies do not become multiple authoritative versions merely because they exist in different locations.

8. Authoritative-Source Rules

An authoritative source, sometimes called a system of record, is the designated source whose value or document controls when duplicates conflict. Authority should be assigned at the field or record-series level, not assumed for an entire system.

For example:

Authority rules should specify:

• the source system or repository;
• the responsible owner;
• the fields or record series covered;
• synchronization frequency and direction;
• conflict-resolution procedures;
• audit requirements;
• what happens during system failure or migration.

An authoritative source is not necessarily the oldest, most convenient, or most frequently accessed copy. It is the source designated by governance and supported by controls for accuracy and integrity.

9. Retention, Disposition, and Legal Holds

Retention schedules define how long records are kept and what happens afterward. A retention period should be expressed clearly, including its trigger. “Seven years” is incomplete unless the organization states seven years from what event: creation, last action, separation, contract expiry, or case closure.

Retention decisions should consider:

• employment and labor law;
• tax, payroll, benefits, and safety requirements;
• discrimination, wage, injury, and contract limitation periods;
• regulatory or accreditation obligations;
• business and historical value;
• privacy and data-minimization principles;
• cross-border transfer and localization requirements;
• litigation, investigation, audit, or regulatory holds.

A legal hold suspends ordinary disposition for potentially relevant records. It should identify the matter, custodians, record categories, scope, start date, instructions, and release authority. A retention schedule cannot authorize destruction while a valid hold applies.

Disposition must be authorized and documented. The organization should be able to show what was destroyed, under which rule, when, by whom or by what process, and whether exceptions applied. Secure deletion must address accessible copies, backups, exports, and replicated systems according to the organization’s technical capability and legal obligations.

10. Privacy, Security, and Ethical Governance

HR documentation architecture is inseparable from privacy governance. Employee records often include identity data, financial information, health data, family information, biometric information, performance judgments, and allegations. Ethical management requires respect for dignity, fairness, proportionality, transparency, and purpose limitation.

Key controls include:

• role-based access and least privilege;
• segregation of medical, payroll, investigation, and general personnel records;
• multi-factor authentication for sensitive systems;
• encryption in transit and at rest where appropriate;
• access logging and periodic review;
• secure transmission and approved collaboration tools;
• data-quality correction procedures;
• privacy notices explaining collection and use;
• breach-response procedures;
• controlled vendor access;
• staff training and sanctions for misuse.

Access should be based on role and purpose, not merely organizational seniority. A senior executive does not automatically require access to every employee record. Nor should HR professionals browse records simply because the system permits it.

10.1 AI and automated processing

AI may assist with classification, duplicate detection, redaction, search, retention labeling, and anomaly identification. However, automated classification can misidentify sensitive records, infer protected characteristics, or apply retention rules incorrectly. AI-generated summaries may omit uncertainty, reproduce bias, or create a misleading impression of the underlying evidence.

Organizations should maintain human oversight, document model purpose and limitations, validate outputs, restrict training use of confidential records, and preserve the original source. An AI-generated summary should not replace the authoritative record when the original is needed to establish what was said, decided, or observed.

11. Implementation Framework

A documentation architecture can be implemented through the following sequence:

1. Inventory existing repositories, record series, data flows, owners, and duplication.
2. Map processes such as recruitment, payroll, performance management, and separation.
3. Assess risk according to sensitivity, legal significance, volume, access, and operational dependency.
4. Design the taxonomy and file plan using stable functions and record series.
5. Assign authority to systems, repositories, owners, and fields.
6. Define metadata and naming standards with controlled vocabularies.
7. Create retention and disposition rules with legal and privacy review.
8. Configure technology for access, versioning, audit trails, holds, and workflow.
9. Migrate and cleanse records, preserving provenance and documenting transformation.
10. Train users and monitor compliance through audits, quality metrics, and corrective action.

Migration deserves special attention. Moving files from a shared drive to a records platform may change names, formats, permissions, or timestamps. The organization should preserve original metadata where possible, document transformations, identify duplicates, and avoid treating migration itself as proof that a record is authentic.

Useful performance indicators include retrieval time, percentage of record series with assigned owners, metadata completeness, duplicate rate, unauthorized-access incidents, overdue disposition actions, and percentage of systems with documented authoritative-source rules. These measures should be interpreted cautiously: a high metadata-completion rate is not useful if the metadata is inaccurate.

Applied Case: Northbridge Health Systems

Background

Northbridge Health Systems is a fictional regional healthcare organization with 4,500 employees. Its HR information is distributed across an HRIS, payroll platform, learning system, applicant-tracking system, occupational-health service, shared drives, and email. Each business unit has developed local folders and spreadsheets.

Problem

During an employment dispute, HR discovered three different salary records, two versions of the employee’s job description, and an interview evaluation stored only in an individual recruiter’s mailbox. A manager had access to a medical accommodation document, while payroll staff could view investigation correspondence. The organization could not determine which salary record was authoritative or whether a retention period had expired.

Analysis

The problem was not simply poor filing. It reflected four architectural failures:

1. classification followed storage location rather than business function;
2. no field-level authoritative-source rules existed;
3. naming and metadata were inconsistent;
4. access and retention rules were not linked to record categories.

Approach and solution

Northbridge formed a cross-functional governance group involving HR, payroll, legal, privacy, information security, occupational health, and records management. It inventoried record series and designed a functional taxonomy. It designated the payroll platform as authoritative for payment transactions, the HRIS as authoritative for approved employment status and base salary, and occupational health as authoritative for clinical records.

The organization introduced a naming standard based on record class, stable identifier, event date, status, and version. It separated medical records from general personnel files, restricted investigation cases, and configured audit logging. A retention schedule was approved after legal review, and an electronic legal-hold process prevented disposal of relevant records. During migration, original file names and source locations were preserved in metadata so that provenance could be reconstructed.

Outcome

Retrieval of approved employment documents became faster, unauthorized access was reduced, and HR could explain which source controlled each disputed field. The organization also identified that some historical records lacked sufficient provenance; those records were retained with a documented reliability limitation rather than being silently treated as authoritative.

Learning points

The case demonstrates that documentation architecture is a governance system, not a folder redesign. It must connect classification, authority, metadata, access, retention, and accountability. It also shows that uncertainty should be recorded honestly. A record with a known limitation is safer than a record presented with unjustified certainty.

Challenges and Limitations

No taxonomy perfectly represents every HR activity. Reorganizations, mergers, remote work, multiple jurisdictions, contractors, and outsourcing create classification complexity. The same event may generate records in several systems, and synchronization may introduce timing differences.

Over-classification can make systems difficult to use and encourage workarounds. Under-classification can expose confidential information and weaken retention control. Automated tools may improve scale but cannot eliminate the need for accountable human decisions. Retention schedules may also conflict across jurisdictions; organizations should identify the applicable legal basis rather than applying the longest period automatically, because indefinite retention can itself create privacy and security risks.

A further limitation is that records cannot guarantee that an underlying decision was fair. Accurate documentation may preserve evidence of a biased process. Record management supports accountability, but it must operate alongside fair HR policies, structured decision-making, anti-discrimination controls, and substantive managerial responsibility.

Best-Practice Checklist

An HR documentation architecture is generally defensible when:

• every major record series has an owner;
• the taxonomy follows HR functions and processes;
• sensitive categories are segregated;
• each critical field has an authoritative source;
• naming and metadata standards are documented;
• approved versions cannot be silently overwritten;
• retention triggers and legal holds are explicit;
• access is role- and purpose-based;
• audit logs are reviewed;
• migration and destruction are documented;
• employees can correct inaccurate personal information through a defined process;
• AI and automation are subject to human oversight.

Chapter Summary

HR record taxonomy and documentation architecture provide the structural foundation for reliable, secure, and accountable HR information management. A record is evidence of an activity, decision, obligation, or relationship, and its value depends on authenticity, reliability, integrity, usability, availability, confidentiality, and traceability.

The principal HR record classes include personnel, recruitment, payroll, benefits, performance, learning, health and safety, employee relations, investigations, and separation records. These categories should be organized through a functional file plan supported by facets such as employee or case identifier, date, owner, status, sensitivity, retention trigger, and authoritative source.

Naming conventions improve consistency, while metadata supplies context that should not be forced into file names. Version control distinguishes draft, reviewed, approved, superseded, and cancelled content. Authoritative-source rules resolve conflicts among HRIS, payroll, learning, occupational-health, and document repositories. Retention, legal holds, access controls, audit trails, privacy safeguards, and controlled disposition complete the lifecycle architecture.

The central managerial lesson is that record management is not a clerical afterthought. It is an integrated governance capability that affects legal defensibility, employee trust, operational efficiency, information security, and the quality of HR decision-making.

Key Terms

Authoritative source: The designated system or repository that controls a specified record or data field when conflicts arise.

Business owner: The person or function accountable for the accuracy, access, retention, and use of a record series.

Controlled vocabulary: An approved set of terms used consistently for classification, status, or metadata.

Disposition: The authorized final action applied to a record, such as destruction, deletion, or archival preservation.

Documentation architecture: The designed structure governing the creation, classification, storage, use, retention, and disposition of organizational information.

File plan: A structured map of record classes, owners, locations, access rules, retention requirements, and disposition actions.

Functional classification: Classification according to the business activity or process that created or uses a record.

Integrity: The condition in which a record remains complete and protected from unauthorized alteration.

Legal hold: A formal suspension of ordinary retention and disposition for records potentially relevant to a legal, regulatory, audit, or investigation matter.

Metadata: Structured information describing a record’s identity, context, status, ownership, security, and lifecycle.

Personnel record: A record documenting an individual’s employment relationship and administrative history.

Record: Information maintained as evidence of an activity, transaction, decision, right, obligation, or relationship.

Record lifecycle: The stages of creation, active use, storage, preservation, and disposition through which a record passes.

Retention trigger: The event from which a retention period is calculated.

System of record: Another term for an authoritative source, emphasizing the system designated to maintain official information.

Taxonomy: A controlled classification scheme that groups records according to shared characteristics.

Traceability: The capacity to reconstruct a record’s origin, changes, access, transfer, and disposition.

Version control: A process for identifying, approving, preserving, and retrieving successive changes to a document or record.

Review Questions

Short Answer Questions

1. What is the difference between a document and a record?
2. Identify four quality characteristics of reliable HR records.
3. Why should medical records generally be separated from general personnel records?
4. What information should a file plan contain?
5. What is an authoritative source?

Long Answer Questions

1. Explain how a functional taxonomy can improve HR record governance across multiple technology platforms.
2. Discuss the relationship among metadata, naming conventions, and retrieval quality.
3. Analyze why version control is important for HR policies, employment contracts, and performance records.
4. Explain the role of retention schedules and legal holds in the HR record lifecycle.
5. Evaluate the ethical and privacy risks associated with broad managerial access to employee records.

Analytical / Application Questions

1. An organization stores salary information in its HRIS, payroll platform, and departmental spreadsheets. Design an authoritative-source rule and describe how conflicts should be resolved.
2. Create a file-plan entry for employee-relations investigation records, including classification, owner, repository, access, metadata, retention trigger, and disposition requirements.
3. A learning system marks an employee’s certification as complete, but the external licensing body shows that the license has expired. Analyze which source should control and propose a governance response.

Multiple Choice Questions with Answers

Question 1

Which characteristic means that an HR record is what it claims to be and was created by the responsible source?

A. Authenticity

B. Availability

C. Usability

D. Confidentiality

Correct Answer: A. Authenticity

Question 2

Which classification approach organizes records according to the HR activity that created or uses them?

A. Departmental classification

B. Functional classification

C. Alphabetical classification

D. Storage-media classification

Correct Answer: B. Functional classification

Question 3

Which system would normally be the authoritative source for net-pay transactions?

A. Applicant-tracking system

B. Learning-management system

C. Payroll system

D. Recruiter email archive

Correct Answer: C. Payroll system

Question 4

What is the primary purpose of metadata in HR records management?

A. To replace the record’s substantive content

B. To provide structured information about the record and its context

C. To make every record publicly accessible

D. To eliminate the need for retention rules

Correct Answer: B. To provide structured information about the record and its context

Question 5

Which status indicates that a document has been replaced by a later approved version but retained for historical evidence?

A. Draft

B. Under review

C. Superseded

D. Cancelled before review

Correct Answer: C. Superseded

Question 6

What does a legal hold do?

A. Automatically deletes records at the end of a schedule

B. Suspends ordinary disposition for potentially relevant records

C. Makes all HR records available to managers

D. Converts drafts into authoritative records

Correct Answer: B. Suspends ordinary disposition for potentially relevant records

Question 7

Which file name best follows the chapter’s recommended naming principles?

A. final_review_new.docx

B. John medical issue latest.pdf

C. PER_004582_EmploymentAgreement_2025-07-01_Approved_v03.pdf

D. HR document version final final.pdf

Correct Answer: C. PER_004582_EmploymentAgreement_2025-07-01_Approved_v03.pdf

Question 8

Why should a manager generally not receive an employee’s diagnosis when managing an accommodation?

A. The manager cannot use any attendance information

B. The principle of minimum necessary access limits exposure to clinical details

C. Medical records are never allowed to exist

D. Managers are always the authoritative source for medical data

Correct Answer: B. The principle of minimum necessary access limits exposure to clinical details

Question 9

Which statement best distinguishes a copy from a version?

A. A copy always contains different content from the original

B. A version is a controlled content change, while a copy is the same version stored elsewhere

C. A copy is always authoritative and a version is never authoritative

D. There is no meaningful distinction

Correct Answer: B. A version is a controlled content change, while a copy is the same version stored elsewhere

Question 10

What is a major risk of using AI-generated summaries as replacements for authoritative HR records?

A. They may omit uncertainty or distort the underlying evidence

B. They always increase record authenticity

C. They prevent all unauthorized access

D. They automatically determine legally correct retention periods

Correct Answer: A. They may omit uncertainty or distort the underlying evidence