Records Theories, Models and Standards

Introduction

Human resource records are not merely administrative by-products. They are evidence of employment relationships, organizational decisions, legal compliance, professional conduct, and employee rights. Recruitment applications, contracts, payroll records, performance evaluations, absence records, disciplinary correspondence, learning records, equality-monitoring data, and termination documentation all support organizational memory and accountability.

For HR professionals, records management is therefore a governance discipline. It determines how information is created, captured, classified, protected, used, retained, and disposed of. Poor records management can produce legal exposure, inconsistent employee treatment, payroll errors, privacy breaches, and an inability to demonstrate that decisions were fair. Effective records management enables trustworthy decisions and defensible organizational action.

This chapter examines four complementary perspectives: the records lifecycle, the records continuum, information governance, and evidence-based management. It also introduces the principles and terminology associated with ISO 15489, the principal international standard for records management.

Learning Objectives

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

1. Explain the purpose and limitations of the records lifecycle model.
2. Compare the lifecycle and continuum perspectives.
3. Apply information-governance principles to HR records.
4. Use evidence-based management to improve HR records decisions.
5. Interpret the principal requirements and concepts of ISO 15489.
6. Design a defensible approach to classification, retention, access, and disposition.
7. Evaluate ethical, legal, technological, and managerial risks in HR documentation.

1. Records as Evidence

A record is information created, received, and maintained as evidence and as an asset by an organization or person in pursuit of legal obligations or business transactions. The important distinction is between information and records. Information may be transitory, analytical, or informal. A record has evidential value: it helps demonstrate what happened, who acted, when an action occurred, and under what authority.

For example, a draft discussion about a possible promotion may be information. An approved promotion decision, together with the evidence supporting it, is a record. An instant message may initially be informal communication, but it becomes a record if it documents an employment decision or instruction that must be retained.

Records have several interrelated values:

• Operational value: supporting current work, such as payroll processing.
• Evidential value: demonstrating actions, decisions, approvals, and responsibilities.
• Legal and regulatory value: showing compliance with employment, tax, health and safety, equality, or privacy requirements.
• Accountability value: enabling review by employees, auditors, regulators, courts, or governing bodies.
• Historical or research value: preserving institutional memory and organizational history.

A record should be understood in context. Its evidential meaning depends on its creator, business activity, relationship to other records, date, authority, and controls. A performance score without the applicable performance criteria, reviewer identity, and approval history may be much less useful than a complete performance-review record.

Important characteristics of trustworthy records

A trustworthy record is generally:

• Authentic: it is what it claims to be and was created or sent by the person or system represented.
• Reliable: its content can be trusted as a full and accurate representation of the transaction or activity.
• Integral: it has not been improperly altered, deleted, or corrupted.
• Usable: it can be located, retrieved, rendered, understood, and connected with related records for as long as required.

These qualities are not achieved simply by storing a file. They depend on procedures, metadata, access controls, audit trails, system design, and organizational culture.

2. The Records Lifecycle Model

The lifecycle model presents records as moving through stages from creation or receipt to final disposition. Although terminology varies, a common sequence is:

1. Creation or capture
2. Classification and registration
3. Active use and maintenance
4. Semi-active storage or restricted use
5. Disposition through destruction or archival preservation

The model is especially useful for operational planning because it directs attention to the changing business value and management requirements of a record.

2.1 Creation and capture

Records arise from business activities. In HR, examples include issuing an employment contract, approving a salary change, recording a workplace investigation, or completing a statutory report. Capture means deciding that the information must be managed as a record and placing it in an authorized records system or controlled repository.

Capture should occur as close as practical to the business activity. Delayed capture increases the risk of loss, alteration, duplication, and uncertainty about the authoritative version.

2.2 Classification and registration

Classification organizes records according to business functions, activities, subjects, or transactions. A functional classification may include:

A classification scheme should reflect how the organization works rather than merely how folders happened to evolve. Registration assigns identifying information such as a unique identifier, title, creator, date, security classification, retention rule, and relationship to a case or employee file.

2.3 Active use and maintenance

Active records support frequent work. They require reliable retrieval, controlled editing, version management where appropriate, backup, and access based on role and business need. A record should not be casually overwritten when the original content is needed as evidence. Corrections should normally preserve an audit trail or a superseded version according to organizational policy.

2.4 Semi-active storage

Records may no longer be used daily but may still be needed for audits, disputes, statutory periods, employee requests, or organizational reference. They can be transferred to lower-cost storage, but reduced frequency of use does not justify reduced protection. Security, readability, metadata, and retrieval capability must be maintained.

2.5 Disposition

Disposition is the final action taken with a record. It may involve destruction, transfer to an archival institution, or continued preservation by the organization. Destruction must be authorized, documented, secure, and suspended where litigation, investigation, audit, or a legally recognized hold is active.

A retention schedule normally specifies the trigger for the retention period, the period itself, the final action, and the authority approving it. The trigger is crucial. “Seven years” is incomplete unless it states whether the period begins at creation, employee termination, contract expiry, completion of an investigation, or another event.

Strengths and limitations of the lifecycle model

The lifecycle model encourages planned management and makes responsibilities easier to allocate. It supports retention scheduling, storage planning, and disposition controls. However, it can imply that records pass through neat, linear stages. Modern digital records may be used simultaneously by several departments, copied across systems, revised through controlled versions, and linked to data generated before and after the apparent life of a document. Some records also acquire archival value while still operationally active.

The lifecycle is therefore best treated as a management heuristic, not a universal physical law. It describes changing management priorities rather than necessarily describing a single movement from one container to another.

3. The Records Continuum Model

The records continuum emerged partly as a response to the linear assumptions of the lifecycle model. It views recordkeeping as a continuous, multidimensional process rather than a sequence that begins only after a document is completed.

A commonly used continuum framework considers four dimensions:

1. Create: records and information are generated through activity.
2. Capture: records are incorporated into a recordkeeping system with evidence of context.
3. Organize: records are related to business functions, people, processes, and systems.
4. Pluralize: records become part of broader organizational, social, cultural, or collective memory.

The dimensions coexist. A record can be created, captured, organized, and made available for broader accountability at the same time. Recordkeeping decisions are made early, including when a process is designed, a form is created, or an HR information system is configured.

The continuum perspective is especially useful for digital HR environments. Consider an automated recruitment platform. Decisions about fields, audit logs, access rights, retention, explainability, and export capability are made during system design. If those decisions are postponed until the end of a record’s operational life, important evidence may never be captured.

Lifecycle and continuum compared

The two perspectives are not mutually exclusive. An HR department may use the lifecycle to schedule retention and the continuum to design systems that capture reliable evidence from the beginning.

4. Information Governance

Information governance is the coordinated framework of policies, decision rights, standards, roles, controls, and technologies used to manage information as an organizational asset and risk. Records management is a central component of information governance, but governance also includes privacy, cybersecurity, data quality, information security, legal discovery, knowledge management, and technology architecture.

A useful governance structure answers five questions:

1. What information exists? — inventory, classification, and metadata.
2. Who is accountable? — ownership, stewardship, and approval authority.
3. Who may access it? — role-based access, purpose limitation, and segregation of duties.
4. How long is it needed? — retention, review, legal holds, and disposition.
5. How is trust maintained? — integrity controls, audit trails, quality assurance, and monitoring.

Governance roles in HR

• Executive sponsor: establishes authority and resources.
• Records manager or information-governance lead: develops policy, schedules, controls, and assurance processes.
• HR process owner: defines the business and evidential requirements of HR records.
• Data protection or privacy officer: advises on lawful, fair, and proportionate processing.
• Information security specialist: protects confidentiality, integrity, and availability.
• System administrator: configures permissions, logging, backup, and technical controls.
• HR practitioner and manager: create, classify, use, and protect records in daily work.
• Employee or data subject: may have rights of access, correction, explanation, or challenge depending on applicable law.

Governance fails when accountability is diffuse. “Everyone owns information” often means that nobody is responsible for it. A practical policy should identify accountable owners and specify who may approve creation, access, alteration, retention exceptions, and destruction.

Information governance principles

A mature HR records program commonly applies the following principles:

• Accountability: a named authority is responsible for decisions.
• Transparency: employees and stakeholders receive understandable information about processing and retention.
• Purpose limitation: records are collected and used for defined legitimate purposes.
• Data minimization: only necessary information is collected and retained.
• Accuracy: records are kept accurate and corrected through controlled processes.
• Security: confidentiality, integrity, and availability are protected proportionately to risk.
• Retention limitation: records are not retained indefinitely without justification.
• Traceability: significant actions can be reconstructed through metadata and audit logs.
• Interoperability: records remain usable across systems where business needs require it.
• Disposal accountability: destruction is authorized and evidenced.

These principles must be applied together. For example, retaining every email “just in case” may preserve information but violate minimization, increase security exposure, and make retrieval less reliable.

5. ISO 15489 and Records-Management Principles

ISO 15489-1:2016, Information and documentation — Records management — Part 1: Concepts and principles, provides an internationally recognized framework for managing records. It is not a retention schedule for every country or industry, nor does it prescribe one software product. Instead, it establishes concepts and principles that organizations adapt to their legal, operational, and technological contexts.

The standard emphasizes that records-management programs should include policies, assigned responsibilities, monitoring, training, and processes for creating and controlling records. Records should be managed as evidence of business activity and should remain authoritative for as long as required.

5.1 Records, metadata, and context

ISO 15489 treats metadata as essential to recordkeeping. Metadata is structured information describing a record and its management context. Examples include:

• title and unique identifier;
• creator, sender, recipient, or responsible unit;
• date and time;
• business function and activity;
• classification and security level;
• relationship to a case, employee, or transaction;
• retention and disposition authority;
• version or status;
• access and audit history.

Metadata should not be viewed as an optional technical label. Without context, a file may be readable but evidentially weak. For example, “review_final.pdf” does not identify which employee, review period, approver, or policy it relates to.

5.2 Records systems and controls

A records system should support the capture, maintenance, use, and disposition of records. Relevant controls may include:

• controlled classification schemes;
• access permissions and authentication;
• audit trails;
• version or status controls;
• backup and recovery;
• format and migration management;
• retention and disposition workflows;
• search and retrieval;
• documentation of procedures and responsibilities.

The appropriate control level depends on risk. A public organizational announcement and a medical accommodation record should not receive identical access treatment. Overly weak controls threaten confidentiality and integrity; overly restrictive controls can obstruct legitimate work and employee rights.

5.3 Authenticity, reliability, integrity, and usability

These four qualities provide a practical test for HR systems. A digitally signed contract may have strong authenticity, but if the system cannot retrieve its associated approval metadata, usability and reliability may be weakened. A spreadsheet can be accurate at creation but lose integrity if users can silently overwrite values without an audit trail.

Controls should address the whole recordkeeping environment, not only the file format. A PDF is not automatically trustworthy, and a paper document is not automatically reliable.

6. Evidence-Based Management and HR Records

Evidence-based management (EBM) involves making managerial decisions through the conscientious, explicit, and judicious use of the best available evidence, combined with professional expertise, stakeholder values and concerns, and organizational context.

The approach is particularly relevant to records management because organizations often adopt policies based on custom, anecdote, vendor claims, or fear rather than evidence. For instance, an HR department may retain all employee correspondence permanently because a manager once needed an old email. EBM asks whether the decision is supported by legal requirements, risk analysis, actual retrieval patterns, employee interests, and reliable research.

Four sources of evidence

1. Best available research evidence: peer-reviewed studies, systematic reviews, and validated methods.
2. Organizational evidence: audit findings, incident data, retrieval statistics, process measures, and cost information.
3. Professional expertise: informed judgment from records, HR, legal, privacy, security, and technology specialists.
4. Stakeholder values and concerns: employee expectations, fairness, accessibility, confidentiality, and public accountability.

Evidence should be appraised rather than merely collected. A vendor white paper may provide useful technical information but should not automatically outweigh independent testing or legal advice.

Applying EBM to a records decision

A disciplined sequence is:

1. Define the decision, such as whether to extend retention for investigation records.
2. Frame the relevant question, including population, risk, time period, and intended outcome.
3. Gather internal data, legal requirements, professional guidance, and research evidence.
4. Assess quality, relevance, bias, completeness, and uncertainty.
5. Integrate evidence with expertise and stakeholder interests.
6. Implement a proportionate policy or control.
7. Monitor outcomes and revise the decision when evidence changes.

EBM does not mean waiting for perfect evidence. Records decisions frequently involve uncertainty. The obligation is to make assumptions visible, use the strongest available evidence, and review decisions systematically.

Example of evidence-informed retention

Suppose an organization is considering a longer retention period for unsuccessful recruitment applications. Relevant evidence includes applicable equality and privacy law, the likelihood of discrimination claims, actual complaint and litigation patterns, the sensitivity of applicant data, security capacity, and candidate expectations. A defensible policy would document why the selected period is necessary and proportionate, rather than relying on a universal number copied from another organization.

7. Designing an HR Records Framework

A practical framework can be built through the following stages.

Stage 1: Analyze functions and processes

Map HR activities such as recruitment, onboarding, payroll, absence management, performance management, employee relations, learning, workforce planning, and separation. Identify where records are created, who uses them, and which decisions they evidence.

Stage 2: Identify record classes

Group records by function and business activity. Avoid classifications based only on file format or individual preference. “PDF files” is a weak class; “approved employee-relations investigation outcomes” is more meaningful because it reflects purpose and risk.

Stage 3: Define metadata and authority

Specify the minimum metadata needed for retrieval, context, security, retention, and accountability. Identify the authoritative copy or system of record. Duplicate copies should not create conflicting evidence.

Stage 4: Conduct risk and impact analysis

Assess confidentiality, integrity, availability, legal exposure, employee harm, operational dependence, and archival value. Sensitive categories, such as health information, biometric data, identity documents, and disciplinary records, normally require enhanced controls.

Stage 5: Establish retention and disposition rules

For each record class, document the trigger, retention period, review conditions, disposition authority, and legal-hold process. Retention should reflect law, business need, risk, and historical value. It should not be based solely on storage capacity.

Stage 6: Configure technology and procedures

Systems should support role-based access, audit trails, reliable search, controlled export, retention workflows, and preservation of metadata. Procedures should cover email, collaboration platforms, mobile devices, paper records, scanned documents, and AI-generated content where such content informs an HR decision.

Stage 7: Train, monitor, and improve

Training should explain not only what to do but why records matter. Monitoring can examine misfiling, unauthorized access, overdue disposition, retrieval time, missing metadata, and user compliance. Findings should feed policy revision and system improvement.

8. Technology, Cloud Services, and Artificial Intelligence

Digital transformation has expanded the locations in which HR records exist. Cloud HR platforms, collaboration tools, messaging applications, employee self-service portals, workflow systems, and automated recruitment tools may all create or store records. Governance must therefore follow the record across systems rather than assuming that the HR database is the only authoritative source.

Cloud outsourcing requires attention to service-provider responsibilities, data location, subcontractors, export capability, continuity, security, deletion at contract termination, and audit rights. A contract should clarify who controls records, how incidents are reported, and how records can be retrieved in usable form.

AI introduces additional questions. A generated summary, recommendation, or classification may become a record if it materially informs an employment decision. Organizations should preserve sufficient information to understand the input, purpose, human review, model or system version where relevant, decision authority, and outcome. AI output should not be treated as inherently accurate or unbiased. Human oversight, quality testing, explainability appropriate to the decision, and a method for correcting errors are essential.

AI also creates a distinction between source records and derived outputs. A summary should not replace the underlying evidence where the source is necessary to understand or challenge a decision. Retaining every intermediate prompt or model output is not automatically justified; retention should be based on evidential value, risk, law, and organizational policy.

9. Ethical, Legal, and Professional Challenges

Privacy and employee dignity

HR records frequently contain information that can cause personal, economic, or reputational harm if misused. Access must be limited to legitimate purposes, and employees should receive clear information about how their records are used. Monitoring should be proportionate and should not create a culture of unjustified surveillance.

Bias and fairness

Incomplete or inaccurate records can produce unequal treatment. For example, undocumented informal opportunities may make promotion decisions appear objective while concealing unequal access. Recordkeeping should support fair process, but documentation alone cannot guarantee fairness. Organizations must examine how records are created, whose voices are absent, and whether categories embed discriminatory assumptions.

Deletion and accountability

Deletion supports privacy and risk reduction, but premature deletion can obstruct legal rights, audits, or organizational accountability. Conversely, indefinite retention can harm employees and increase breach exposure. The correct approach is controlled, documented, and proportionate disposition.

Discovery and legal holds

When litigation, investigation, or regulatory review is reasonably anticipated, ordinary disposition may need to be suspended for relevant records. A legal hold should identify scope, custodians, systems, preservation duties, and release authority. HR managers should not independently delete or alter potentially relevant records once a hold applies.

10. Illustrative Case: Rebuilding Records Governance at Northbridge Services

Background. Northbridge Services, a fictional multinational employer, stored HR information in a core HR system, shared drives, email inboxes, messaging applications, and paper files. Different departments used different employee-number conventions. The organization retained terminated-employee files for inconsistent periods and had no documented legal-hold process.

Problem. During an employee-relations dispute, HR could not determine which version of a performance warning was authoritative. A manager had edited a shared document, a later email attached a different version, and the HR system contained only a summary. The organization also discovered that a former contractor retained access to a shared folder containing sensitive medical-accommodation information.

Analysis. A review team applied lifecycle and continuum perspectives. The lifecycle analysis identified failures in capture, classification, retention, and disposition. The continuum analysis showed that the problem began earlier: the performance-management process had never defined the authoritative record, required metadata, approval workflow, or access model. An evidence-based review examined incident data, retrieval needs, applicable law, professional guidance, and employee concerns.

Approach. Northbridge adopted the following measures:

• a functional classification scheme for HR activities;
• a unique employee and case identifier;
• a designated system of record for approved employment decisions;
• mandatory metadata for creator, date, status, approver, and retention class;
• role-based access for sensitive employee-relations and health records;
• audit logging and controlled supersession rather than silent overwriting;
• a documented retention schedule with event-based triggers;
• a legal-hold procedure and disposition approval workflow;
• quarterly access reviews and annual schedule reviews;
• training using realistic HR scenarios rather than only policy recitation.

Outcome. After implementation, retrieval became more reliable, unauthorized access was reduced, and managers could distinguish drafts from approved records. The organization also identified that some records previously retained indefinitely had no continuing business or legal purpose and could be securely disposed of after review.

Learning points. The case demonstrates that records failures are usually process and governance failures, not merely filing failures. The lifecycle model helped structure controls over time; the continuum model exposed design failures at the point of process creation; ISO principles clarified the need for authenticity, reliability, integrity, usability, and metadata; and evidence-based management prevented the organization from selecting retention rules based only on habit.

Best-Practice Checklist

An HR records program should be able to answer “yes” to the following questions:

• Is every major HR process mapped to its records requirements?
• Are authoritative records distinguished from drafts and duplicates?
• Are classification, metadata, access, retention, and disposition documented?
• Are sensitive records protected by least-privilege access?
• Can significant actions and changes be traced?
• Are retention triggers and legal holds clearly defined?
• Can records be retrieved and understood throughout their required life?
• Are cloud, messaging, and AI-enabled systems included in governance?
• Are employees treated fairly and informed appropriately?
• Are policies tested, measured, and revised using evidence?

Chapter Summary

Records are evidence of organizational activity, not simply containers of information. In HR, trustworthy records support operational continuity, legal compliance, employee rights, accountability, and informed management. The records lifecycle provides a practical framework for creation, capture, use, storage, and disposition, but its linear structure may not fully represent networked digital environments. The records continuum complements it by emphasizing that recordkeeping decisions begin during process and system design and continue across multiple dimensions.

Information governance integrates records management with privacy, security, data quality, legal discovery, technology, and accountability. ISO 15489-1:2016 provides internationally recognized concepts and principles, including the importance of metadata, records systems, assigned responsibilities, and the qualities of authenticity, reliability, integrity, and usability. Evidence-based management strengthens records decisions by combining research, organizational data, professional expertise, stakeholder values, and context.

Effective HR records governance requires functional classification, proportionate access, event-based retention, controlled disposition, auditability, training, and continual review. Technology, cloud services, and AI make early design decisions increasingly important. Ethical practice requires balancing accountability with privacy, fairness, dignity, and the prevention of unnecessary surveillance or indefinite retention.

Key Terms

Authenticity: The quality of being what a record claims to be and originating from the stated source.

Authoritative record: The record designated as the official evidence of a transaction or decision.

Classification scheme: A structured arrangement of records based on functions, activities, subjects, or transactions.

Continuum model: A perspective that treats recordkeeping as continuous, multidimensional, and beginning during process design.

Disposition: The final action taken on a record, such as destruction or archival preservation.

Evidence-based management: Decision-making that integrates the best available evidence with expertise, stakeholder values, and organizational context.

Functional classification: Organizing records according to what the organization does rather than merely by format or location.

Information governance: Policies, roles, controls, standards, and technologies governing information throughout its life and use.

Integrity: The quality of being complete and protected against unauthorized alteration or deletion.

Legal hold: A suspension of normal disposition for records relevant to anticipated or ongoing legal or regulatory proceedings.

Lifecycle model: A model describing stages through which records are created, used, maintained, and disposed of or preserved.

Metadata: Structured information describing a record, its context, management requirements, and relationships.

Pluralization: In the continuum model, the incorporation of records into broader organizational, social, or collective memory.

Records system: An organized system for capturing, maintaining, using, and disposing of records.

Reliability: The quality of accurately representing the transaction or activity to which a record relates.

Retention schedule: An authorized instrument specifying how long records are kept and what happens afterward.

Usability: The quality of being locatable, retrievable, renderable, understandable, and usable for as long as required.

ISO 15489: An international standard providing concepts and principles for records management.

Review Questions

Short Answer Questions

1. How does a record differ from general information?
2. Identify the four qualities of a trustworthy record discussed in this chapter.
3. What is the purpose of a retention trigger?
4. Why is metadata important in HR records management?
5. Name four sources of evidence used in evidence-based management.

Long Answer Questions

1. Explain the records lifecycle model and evaluate its strengths and limitations in a digital HR environment.
2. Compare the lifecycle and continuum models, using an automated recruitment system as an example.
3. Explain how information governance connects records management with privacy, security, and legal discovery.
4. Discuss the significance of authenticity, reliability, integrity, and usability under ISO 15489.
5. Develop a records-governance framework for an organization that uses cloud-based HR systems.

Analytical / Application Questions

1. An HR manager proposes retaining every employee email indefinitely to protect the organization against future disputes. Using evidence-based management and information-governance principles, analyze the proposal and recommend a defensible alternative.
2. A performance review exists as a manager’s draft, an email attachment, and an approved HR-system record. Apply the lifecycle and continuum perspectives to determine how the organization should establish the authoritative record and preserve relevant context.
3. An AI tool recommends candidates and produces summaries used in hiring decisions. Design the records, metadata, access, review, retention, and accountability controls needed to make the process defensible.

Multiple Choice Questions with Answers

Question 1

Which characteristic means that a record is what it claims to be and comes from the represented source?

A. Authenticity

B. Usability

C. Disposition

D. Pluralization

Correct Answer: A. Authenticity

Question 2

Which activity most directly represents the capture stage of the records lifecycle?

A. Deleting a record after its retention period

B. Placing an employment decision in an authorized records system

C. Reviewing an archival collection

D. Changing an employee’s job title

Correct Answer: B. Placing an employment decision in an authorized records system

Question 3

What is a central difference between the lifecycle and continuum perspectives?

A. The lifecycle addresses paper only, whereas the continuum addresses paper and digital records

B. The lifecycle emphasizes sequential stages, whereas the continuum emphasizes continuous and multidimensional recordkeeping

C. The lifecycle concerns privacy, whereas the continuum concerns cybersecurity only

D. The lifecycle rejects metadata, whereas the continuum requires paper classification

Correct Answer: B. The lifecycle emphasizes sequential stages, whereas the continuum emphasizes continuous and multidimensional recordkeeping

Question 4

Which item is an example of records metadata?

A. A server’s physical color

B. The creator, date, classification, and retention rule

C. An employee’s personal opinion about filing

D. The number of desks in the HR office

Correct Answer: B. The creator, date, classification, and retention rule

Question 5

Which statement best describes ISO 15489-1:2016?

A. It is a universal retention schedule with fixed periods for every record type

B. It is a software certification standard for HR databases

C. It provides concepts and principles for records management that organizations adapt to context

D. It applies only to archival institutions

Correct Answer: C. It provides concepts and principles for records management that organizations adapt to context

Question 6

Which action is most consistent with information-governance principles?

A. Giving all managers unrestricted access to all HR records

B. Retaining records permanently because storage is inexpensive

C. Assigning accountability, limiting access by legitimate need, and documenting disposition

D. Allowing employees to overwrite approved records without an audit trail

Correct Answer: C. Assigning accountability, limiting access by legitimate need, and documenting disposition

Question 7

Which source is part of evidence-based management?

A. Vendor claims considered without evaluation

B. Organizational evidence such as audit findings and retrieval data

C. Personal preference alone

D. An undocumented tradition

Correct Answer: B. Organizational evidence such as audit findings and retrieval data

Question 8

What should normally happen when a legal hold applies to relevant HR records?

A. Normal disposition should be suspended for those records

B. All organizational records should be destroyed immediately

C. Access controls should be removed

D. The records should be converted to informal notes

Correct Answer: A. Normal disposition should be suspended for those records

Question 9

Which classification is most likely to support effective HR records governance?

A. All files larger than 10 megabytes

B. Files created on Tuesdays

C. Approved employee-relations investigation outcomes

D. Documents stored on an employee’s desktop

Correct Answer: C. Approved employee-relations investigation outcomes

Question 10

Why should an AI-generated hiring summary not automatically replace the underlying source records?

A. AI outputs can never be stored electronically

B. The source evidence may be needed to understand, verify, or challenge the decision

C. Summaries are always more reliable than source records

D. Underlying records have no evidential value after a summary is created

Correct Answer: B. The source evidence may be needed to understand, verify, or challenge the decision