The Routine Appraisal Cycle and Evidence Management

Introduction

Routine performance appraisal is often described as an annual event, but effective appraisal is better understood as a recurring evidence-and-dialogue system. It begins with preparation and expectation setting, continues through observation and documentation, and culminates in evaluation, calibration, sign-off, and follow-up. The quality of the final rating depends less on the elegance of the appraisal form than on the quality, relevance, and governance of the evidence accumulated throughout the cycle.

For HR professionals, the central challenge is to create a process that is sufficiently structured to support consistency, yet sufficiently flexible to reflect different roles, projects, work arrangements, and business conditions. A routine appraisal must also be fair to employees, useful to managers, defensible to the organization, and compliant with applicable employment, privacy, and equality requirements.

This chapter examines the appraisal cycle as an integrated management process. It distinguishes observation from judgment, performance evidence from personal impressions, developmental feedback from formal evaluation, and calibration from forced ranking. It also considers employee self-assessment, appeals, technology, artificial intelligence, and the construction of an auditable evidence trail.

Learning Objectives

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

1. Explain the stages and governance requirements of a routine appraisal cycle.
2. Design reliable methods for collecting, documenting, and organizing performance evidence.
3. Distinguish facts, interpretations, judgments, and contextual information.
4. Conduct effective interim reviews and employee self-assessments.
5. Apply fair procedures for formal evaluation, calibration, sign-off, and appeal.
6. Identify ethical, legal, privacy, and bias risks in appraisal documentation.
7. Design follow-up arrangements that connect appraisal results with development and performance improvement.

1. The Appraisal Cycle as a Management Control and Development System

A routine appraisal cycle performs several functions simultaneously. It communicates organizational expectations, provides feedback, supports decisions about development and rewards, identifies performance barriers, and creates an institutional record. These functions can conflict. A conversation intended to encourage learning may become defensive if the employee believes it determines pay. A rating intended to support consistency may oversimplify complex work. A detailed record may improve accountability but create unnecessary privacy risks.

A well-designed system therefore separates, while connecting, four purposes:

The cycle should not be treated as a purely administrative sequence. It is a social process shaped by power, trust, managerial capability, role ambiguity, and organizational culture. Employees are more likely to accept difficult feedback when expectations were clear, evidence was collected consistently, and they had meaningful opportunities to respond.

A useful operating principle is no surprise appraisal. This does not mean that every observation must be immediately escalated, nor that managers cannot identify emerging issues. It means that formal conclusions should normally be grounded in issues that have been communicated and discussed during the cycle, subject to serious misconduct or other exceptional circumstances.

2. Designing the Cycle Before It Begins

2.1 Establishing the appraisal architecture

Before the cycle starts, HR should define its architecture. This includes the appraisal period, participants, roles, rating scale, evidence standards, review dates, approval requirements, record-retention rules, and links to compensation or promotion. The architecture should be proportionate to the work. A complex research project may require milestone-based review, whereas a stable operational role may be assessed through service, quality, safety, and teamwork indicators.

The organization should specify who does what. The employee provides information, reflects on performance, and participates in planning. The line manager observes, coaches, evaluates, and documents. A second-level manager may review consistency and fairness. HR designs and governs the process, advises on difficult cases, monitors patterns, and protects procedural integrity. No participant should be expected to perform a role for which they lack sufficient information or authority.

2.2 Translating strategy into assessable expectations

Performance expectations should be stated in terms that are observable and relevant to the role. They may include:

• results, outputs, or deliverables;
• quality, accuracy, or reliability;
• customer, stakeholder, or team contribution;
• compliance, safety, and ethical conduct;
• use of resources and judgment; and
• capability development and collaboration.

Objectives should identify the expected result, relevant timeframe, quality standard, and constraints. A weak objective says, “Improve stakeholder relationships.” A stronger objective says, “By the end of the second quarter, establish a monthly service review with the three principal internal clients and document agreed actions within five working days.” The stronger formulation does not eliminate judgment, but it gives the parties a shared reference point.

Not every important contribution can be reduced to a numerical target. Qualitative evidence is legitimate when the organization defines what good performance looks like and requires examples. An assessment of leadership, judgment, inclusion, or collaboration should not be based on vague impressions alone.

2.3 Preparing participants

Preparation includes training managers in observation, feedback, documentation, bias awareness, and difficult conversations. Employees should understand the process, rating definitions, evidence expectations, rights to comment, and avenues of appeal. Calibration participants need guidance on comparing performance against standards rather than comparing personalities or personal preferences.

Preparation should also identify foreseeable changes. Objectives may become obsolete because of restructuring, supply disruption, technological change, or a shift in customer demand. A fair system permits documented revision rather than evaluating employees against expectations that were no longer reasonable.

3. Evidence Management: From Events to an Auditable Record

3.1 What counts as performance evidence?

Performance evidence is information that reasonably helps establish what an employee did, achieved, attempted, or contributed in relation to agreed expectations. Examples include completed work, project milestones, quality records, customer feedback, documented decisions, peer observations, compliance records, and the employee’s explanation of contextual factors.

Evidence is stronger when it is:

1. Relevant to the role and the stated criterion.
2. Specific, identifying what occurred rather than offering a general label.
3. Contemporaneous, recorded close enough to the event to reduce memory distortion.
4. Corroborated, where appropriate by records or multiple informed sources.
5. Balanced, including effective performance and areas requiring improvement.
6. Contextualized, recognizing resources, dependencies, constraints, and changes.
7. Accessible, so the employee can understand and respond to it.

Evidence is not synonymous with data. A dashboard metric may be informative but misleading if the employee lacks control over the result, if cases vary in difficulty, or if the metric encourages undesirable behavior. Conversely, a carefully documented decision may be persuasive evidence even without a numerical measure.

3.2 The evidence record

A practical evidence record can contain the following fields:

The distinction between observation and interpretation is essential. “The report was submitted two days after the agreed deadline” is an observation if supported by the project record. “The employee is careless” is an interpretation, and potentially an unfair character judgment. The manager may need to investigate why the delay occurred, whether deadlines were realistic, and whether similar delays occurred in comparable assignments.

3.3 Triangulation and source quality

Triangulation means examining a performance issue through more than one relevant source or method. For example, a customer complaint may be considered alongside the service record, the employee’s account, and comparable cases. Triangulation does not require a mechanical averaging of sources. Its purpose is to test reliability and identify missing context.

Sources should be evaluated for proximity, expertise, independence, and possible bias. A peer who worked directly on a project may provide useful evidence about collaboration, but a person with an unresolved conflict may require cautious interpretation. Anonymous comments can alert a manager to a concern but are generally weaker as sole evidence for a consequential judgment because the employee cannot meaningfully test the allegation.

3.4 Documentation discipline

Documentation should be factual, respectful, proportionate, and understandable to a third party who was not present. Managers should avoid sarcasm, speculation about motives, coded language, and references to protected characteristics. They should distinguish verified information from allegations and note when an issue remains under review.

A good record is not the longest record. Excessive notes can create noise, increase privacy exposure, and make significant evidence harder to identify. The objective is a sufficient record: enough information to explain the conclusion, support procedural fairness, and enable future follow-up.

4. Observation and Ongoing Feedback

Observation is the disciplined process of obtaining information about performance. It may be direct, such as watching a presentation or reviewing a work product, or indirect, such as examining service data or stakeholder reports. Observation should be continuous enough to avoid overreliance on recent events, memorable incidents, or a single project.

Managers should schedule periodic performance conversations rather than waiting for the formal review. An effective conversation usually has four parts:

1. Describe the relevant event, result, or behavior.
2. Explain its impact in relation to the expectation.
3. Invite the employee’s perspective and contextual information.
4. Agree on reinforcement, correction, support, or follow-up.

Feedback should be proportionate. A minor error may require quick coaching; a repeated or high-risk issue may require a formal improvement plan. Positive feedback also needs specificity. “Good job” offers little learning value, whereas “Your early risk escalation allowed the team to reallocate testing resources before the release date” identifies the behavior and its impact.

Managers should not confuse frequent contact with high-quality observation. In hybrid and remote work, visibility bias can cause managers to favor employees whose work is more observable. Systems should therefore emphasize outcomes, documented contributions, and structured check-ins rather than physical presence or responsiveness alone.

5. Interim Reviews and Mid-Cycle Adjustment

An interim review is a formal checkpoint within the appraisal period. It is not usually a miniature final appraisal. Its main purpose is to test whether expectations remain clear, assess progress, identify barriers, and make timely adjustments.

A sound interim review addresses:

• progress against each important objective;
• quality and sustainability of results;
• behavioral or capability expectations;
• changes in role, priorities, resources, or dependencies;
• support required from the manager or organization;
• risks that could affect year-end performance; and
• agreed actions, owners, and dates.

If an objective is changed, the record should state what changed, why, when, and how the revised expectation will be assessed. This protects both parties. It prevents managers from quietly replacing difficult objectives with easier ones, and it prevents employees from being judged against obsolete requirements.

The interim review is also an opportunity to detect systemic problems. Repeated underperformance may reflect inadequate training, conflicting instructions, workload imbalance, defective systems, or unrealistic targets rather than individual unwillingness. Managerial accountability requires examination of these conditions before assigning blame.

6. Employee Self-Assessment

Self-assessment gives employees an opportunity to assemble evidence, interpret their own performance, identify achievements, and explain constraints. It improves procedural voice: employees are not merely objects of evaluation but participants in the assessment process.

A useful self-assessment asks employees to:

• summarize results against each objective;
• provide evidence of quality, contribution, and impact;
• identify work that did not proceed as planned and explain why;
• describe learning, collaboration, and broader contributions;
• identify resources or decisions that affected performance; and
• propose development priorities for the next cycle.

Self-assessment should not be treated as a vote that determines the final rating. Nor should disagreement automatically be interpreted as defensiveness. Differences may reveal unclear standards, incomplete managerial observation, or legitimate contextual information. Managers should consider the submission seriously, verify relevant claims, and explain where their conclusion differs.

Employees should be cautioned against disclosing confidential client information, sensitive personal data, or material belonging to another individual. The organization should provide a secure system and clear guidance on appropriate evidence.

7. Formal Evaluation and Rating Judgment

7.1 From evidence to conclusion

Formal evaluation requires a reasoned judgment about the extent to which performance met expectations during the entire period. The manager should synthesize evidence rather than simply count positive and negative incidents. A single major safety breach may have greater significance than several routine successes; alternatively, an isolated error may be outweighed by sustained high-quality performance when the error was promptly corrected and had limited impact.

The evaluation narrative should answer three questions:

1. What was expected?
2. What evidence shows what occurred?
3. What conclusion follows, and why?

Rating scales must be behaviorally anchored. Labels such as “excellent,” “successful,” and “needs improvement” are interpreted inconsistently unless accompanied by clear descriptions. A five-point scale, for example, should distinguish exceptional performance from consistently effective performance and from performance that only partly meets requirements. More rating levels do not automatically create greater accuracy.

7.2 Common judgment errors

Important appraisal errors include:

• Recency error: giving excessive weight to recent events.
• Halo effect: allowing one favorable characteristic to influence all criteria.
• Horns effect: allowing one unfavorable event to dominate the assessment.
• Similarity bias: favoring employees who share the evaluator’s background or style.
• Leniency or severity: rating everyone unusually high or low.
• Central tendency: avoiding distinctions by rating everyone near the middle.
• Attribution error: attributing success to personal ability and failure to personal deficiency without examining circumstances.
• Availability bias: overweighting memorable events rather than representative evidence.
• Proximity or visibility bias: confusing presence, activity, or responsiveness with contribution.

Training can reduce these errors, but it cannot replace sound system design. Structured criteria, multiple evidence sources, review of distributions, and documented reasoning are more reliable than exhortations to “be objective.”

8. Calibration Without Forced Ranking

Calibration is a structured review of proposed evaluations to improve consistency across managers, teams, or functions. Participants examine whether similar levels of performance are being treated similarly and whether standards have been applied appropriately.

Calibration should focus on standards and evidence. It should ask:

• Are the criteria being interpreted consistently?
• Does the evidence support the proposed conclusion?
• Are differences caused by role context or by inconsistent judgment?
• Have managers considered the whole review period?
• Are there patterns suggesting bias or unequal opportunity?

Calibration is not a requirement that a predetermined percentage of employees receive each rating. Forced ranking can create artificial competition, undermine collaboration, and produce unfair outcomes when an entire team performs well or when conditions differ across units. A distribution may be reviewed as a diagnostic signal, but it should not substitute for individual evidence.

Confidentiality is important during calibration. Participants should receive only information necessary for the review, and discussion should avoid irrelevant personal details. HR should retain a record of material changes to a proposed evaluation and the rationale for those changes.

9. The Formal Meeting, Sign-Off, and Appeals

The formal appraisal meeting should be a two-way discussion, not the first disclosure of a final judgment. The manager should explain the overall assessment, connect it to evidence, acknowledge achievements, discuss concerns, and identify future priorities. The employee should be given time to ask questions, provide information, and correct factual errors.

Sign-off normally confirms that the appraisal was discussed and received; it should not be represented as proof that the employee agrees with every conclusion. Digital systems should provide separate options such as “acknowledged,” “comment added,” and “declined to acknowledge.” If an employee refuses to sign, the manager should record that the document was presented and explain the applicable procedure. A refusal should not automatically be treated as misconduct.

An appeal or review process should be accessible, time-limited, and independent enough to be credible. Grounds may include factual error, procedural irregularity, inconsistent application of standards, discrimination, retaliation, or significant evidence that was not considered. Mere disagreement with a reasonable managerial judgment may not justify a full rehearing, although the organization should define this clearly.

A fair process includes notice of the decision, reasons, the reviewer’s authority, deadlines, confidentiality limits, and possible outcomes. Outcomes may include confirming the assessment, correcting factual material, requiring reconsideration, removing unsupported content, or initiating a separate investigation where the issue concerns misconduct or discrimination.

10. Follow-Up and Closing the Loop

An appraisal has little value if its conclusions are not converted into action. Follow-up should specify what will happen, who is responsible, what support will be provided, and when progress will be reviewed.

Typical actions include:

• targeted training or coaching;
• revised objectives;
• mentoring or job rotation;
• workload or process redesign;
• access to equipment, information, or authority;
• recognition or broader assignment; and
• a formal performance improvement plan where appropriate.

A performance improvement plan should identify the performance gap, expected standard, support, review dates, evidence that will be considered, and consequences of insufficient improvement. It should be developmental and procedurally fair, not a vague warning disguised as a plan.

The next cycle should begin with learning from the previous one. HR can examine whether appraisal results correlate with turnover, promotion, absence, engagement, grievances, or development access. Such analysis must use appropriately aggregated and protected data. Patterns can reveal managerial inconsistency or structural inequality, but correlation alone does not establish causation.

11. Governance, Ethics, and Regulation

Appraisal records contain employment information and may include sensitive personal data. Organizations should apply data minimization, purpose limitation, access control, retention schedules, secure transmission, and correction procedures consistent with applicable law. Employees should know what information is collected, who can access it, how it will be used, and how long it will be retained.

Ethical appraisal requires respect for dignity and equal opportunity. Managers should not penalize employees for approved leave, disability-related limitations, pregnancy, caregiving responsibilities, religious observance, or other protected circumstances. Reasonable adjustments may be necessary to ensure that the process measures performance rather than the effect of an inaccessible work design.

Documentation should not become a mechanism for retaliation. Employees who raise concerns, report wrongdoing, or exercise workplace rights require protection from adverse treatment. Where allegations involve harassment, discrimination, safety, or serious misconduct, the appraisal process should not replace a properly governed investigation.

12. Digital Systems and Artificial Intelligence

Performance-management platforms can improve reminders, version control, workflow visibility, access permissions, and audit trails. They can also encourage superficial documentation, turn every interaction into surveillance, and amplify biased or incomplete data.

Artificial intelligence may assist with administrative tasks such as summarizing manager notes, identifying missing fields, suggesting neutral language, or detecting inconsistent application of rating definitions. It should not independently determine an employee’s rating or infer character, loyalty, future potential, or emotional state from emails, keystrokes, facial expressions, or other weak proxies.

AI-assisted appraisal requires human accountability, transparency, data-quality testing, bias assessment, security controls, and a meaningful opportunity for employees to challenge an output. Managers must verify generated summaries against original evidence. A system that produces fluent text can still omit context, reproduce stereotypes, or state an unsupported inference with unwarranted confidence.

The governing principle is that technology may support evidence management, but responsibility for judgment, explanation, and fairness remains with accountable human decision-makers.

13. Illustrative Case: The Meridian Service Team

Background

Meridian Health Devices, a fictional organization, introduced a quarterly appraisal cycle for its customer-support analysts. Ratings considered service quality, resolution effectiveness, collaboration, compliance, and learning. Analysts worked partly from home, and managers initially relied heavily on ticket counts and visible online activity.

Problem

One analyst, Priya, received a below-expectations draft rating because her ticket volume was lower than that of colleagues. Her self-assessment showed that she handled a disproportionate number of technically complex cases, trained two new colleagues, and prevented escalation of several high-risk customer issues. The manager had recorded no contemporaneous notes about this work.

Analysis

HR reviewed the role criteria, ticket-complexity data, quality audits, customer escalations, and the manager’s notes. The review found that ticket volume was an incomplete indicator and that the manager’s informal reliance on online visibility created a risk of proximity bias. Priya’s work products supported her claims, while quality audits showed that her resolution accuracy exceeded the team average.

Approach and solution

The manager revised the draft evaluation using the defined criteria rather than ticket volume alone. The evidence record was updated to distinguish volume, complexity, quality, and developmental contribution. The manager and Priya agreed on a future objective for documenting complex-case outcomes and on a monthly review of workload mix. HR provided calibration training and amended the guidance to prohibit use of online presence as a standalone performance indicator.

Outcome

Priya received a rating consistent with effective performance and was given a development opportunity in technical coaching. The organization did not treat the case as evidence of managerial bad faith; instead, it used the appeal and calibration process to identify a flawed measurement practice. Subsequent reviews incorporated case complexity and quality evidence.

Learning points

The case demonstrates that evidence must be connected to the nature of work. It also shows the value of self-assessment, review of contextual information, calibration, and correction before sign-off. Most importantly, a defensible appraisal process can improve both an individual decision and the underlying system.

Best-Practice Checklist

Before closing an appraisal cycle, HR and managers should confirm that:

• expectations were documented and revised when circumstances changed;
• evidence covers the full period and relevant criteria;
• observations are distinguished from interpretations;
• the employee had an opportunity to provide context and respond;
• the evaluation explains how evidence supports the conclusion;
• bias and consistency risks were considered;
• calibration did not become forced ranking;
• sign-off records receipt rather than manufactured agreement;
• appeal rights and deadlines were communicated;
• follow-up actions have owners and review dates; and
• records are secure, proportionate, and retained appropriately.

Chapter Summary

The routine appraisal cycle is an integrated process of expectation setting, observation, evidence management, interim dialogue, self-assessment, formal evaluation, calibration, sign-off, appeal, and follow-up. Its credibility depends on the quality of the evidence trail and on the fairness of the procedures used to interpret that evidence.

Effective evidence is relevant, specific, timely, contextualized, balanced, and open to employee response. Managers should distinguish observable events from interpretations and should triangulate important conclusions where appropriate. Interim reviews prevent surprises and enable objectives, resources, and support to be adjusted when conditions change.

Formal evaluation requires reasoned judgment rather than mechanical counting. Calibration can improve consistency, but it should not become forced ranking. Sign-off should record receipt and discussion, while appeals should provide a credible route for correcting factual or procedural failures. Follow-up converts appraisal into development and performance improvement. Throughout the cycle, privacy, equality, accessibility, data security, and protection from retaliation are essential governance requirements. Digital tools and AI can support administration and analysis, but they cannot replace accountable human judgment.

Key Terms

Auditable evidence trail: A traceable record showing how performance information was collected, interpreted, discussed, and used.

Calibration: A structured review intended to improve consistency in the application of performance standards.

Contextualization: Consideration of constraints, dependencies, resources, and changing conditions affecting performance.

Employee self-assessment: The employee’s structured account of achievements, difficulties, evidence, and development needs.

Evidence triangulation: Examination of relevant information from multiple sources or methods.

Formal evaluation: The documented judgment of performance against established expectations.

Forced ranking: A system requiring employees to be placed into predetermined rating categories or proportions.

Halo effect: The tendency for one favorable characteristic to influence judgments about unrelated criteria.

Horns effect: The tendency for one unfavorable characteristic or event to distort the overall evaluation.

Interim review: A scheduled checkpoint used to assess progress, clarify expectations, and identify support.

No-surprise appraisal: A principle that formal conclusions should normally reflect issues previously communicated and discussed.

Observation: The disciplined collection of information about results, behavior, or work processes.

Performance improvement plan: A documented plan specifying a performance gap, expected standard, support, review dates, and possible consequences.

Proximity bias: Favoring employees who are more physically visible or frequently observed.

Rating anchor: A description of behavior or results that clarifies the meaning of a rating level.

Sign-off: A recorded acknowledgment that an appraisal was presented or discussed, not necessarily that it was accepted.

Sufficient record: Documentation containing enough relevant information to support fairness, explanation, and follow-up without unnecessary detail.

Visibility bias: Mistaking observable activity or presence for actual contribution.

Review Questions

Short Answer Questions

1. What are the four principal purposes served by a routine appraisal system?
2. Identify four characteristics of high-quality performance evidence.
3. Why should an interim review not be treated as merely a shortened final appraisal?
4. What is the difference between calibration and forced ranking?
5. What should an employee’s signature on an appraisal normally signify?

Long Answer Questions

1. Explain how an organization can design an appraisal cycle that balances consistency with flexibility.
2. Discuss the distinction between observation, interpretation, and judgment in appraisal documentation, using examples.
3. Evaluate the role of employee self-assessment in improving procedural fairness and decision quality.
4. Describe the governance requirements for a fair appraisal appeal process.
5. Analyze the ethical and managerial risks of using digital monitoring and artificial intelligence in performance appraisal.

Analytical / Application Questions

1. A manager rates an employee poorly because the employee completed fewer cases than colleagues. The employee demonstrates that the cases were substantially more complex and that quality scores were higher. Design an evidence review and explain how the rating should be reconsidered.
2. During calibration, senior managers insist that exactly 10 percent of employees must receive the lowest rating, although most employees met their objectives. Assess the practice and recommend an alternative approach.
3. An employee refuses to sign a final appraisal because the employee disputes two factual statements but accepts that the meeting occurred. What should the manager and HR do, and what records should be maintained?

Multiple Choice Questions with Answers

Question 1

Which practice most directly supports an auditable evidence trail?

A. Recording only the final rating

B. Linking observations to criteria, sources, context, and follow-up

C. Allowing managers to rely on memory at year end

D. Replacing narrative evidence with a numerical score

Correct Answer: B. Linking observations to criteria, sources, context, and follow-up

Question 2

What is the primary purpose of an interim review?

A. To impose a final rating early

B. To eliminate the need for a formal appraisal

C. To assess progress, clarify expectations, and identify support

D. To compare employees across departments

Correct Answer: C. To assess progress, clarify expectations, and identify support

Question 3

Which statement is an observation rather than an interpretation?

A. The employee is careless

B. The employee lacks commitment

C. The report was submitted two days after the agreed deadline

D. The employee has a poor attitude

Correct Answer: C. The report was submitted two days after the agreed deadline

Question 4

What is the main objective of calibration?

A. To ensure a predetermined rating distribution

B. To improve consistency in applying standards

C. To allow managers to share confidential personal information

D. To replace the line manager’s evaluation

Correct Answer: B. To improve consistency in applying standards

Question 5

Which is an example of recency error?

A. Considering evidence from the entire appraisal period

B. Giving excessive weight to an event occurring shortly before the final review

C. Checking evidence against the role criteria

D. Inviting the employee’s explanation

Correct Answer: B. Giving excessive weight to an event occurring shortly before the final review

Question 6

What should employee sign-off normally establish?

A. That the employee agrees with every conclusion

B. That the appraisal was presented or discussed

C. That an appeal is impossible

D. That the rating was determined by HR

Correct Answer: B. That the appraisal was presented or discussed

Question 7

Which evidence is generally strongest for evaluating a complex project contribution?

A. Online presence alone

B. A single unverified rumor

C. A combination of deliverables, quality records, stakeholder input, and context

D. The employee’s job title alone

Correct Answer: C. A combination of deliverables, quality records, stakeholder input, and context

Question 8

Why is forced ranking problematic?

A. It prevents any documentation

B. It requires every employee to receive the same rating

C. It can create artificial competition and unfair outcomes

D. It eliminates managerial judgment entirely

Correct Answer: C. It can create artificial competition and unfair outcomes

Question 9

Which principle is most appropriate when using AI in appraisal?

A. Allow the system to determine ratings independently

B. Use generated summaries without checking source evidence

C. Maintain human accountability, transparency, and challenge rights

D. Infer motivation from keystroke patterns

Correct Answer: C. Maintain human accountability, transparency, and challenge rights

Question 10

A performance improvement plan should normally specify which combination?

A. Only the employee’s weaknesses

B. The performance gap, expected standard, support, review dates, and possible consequences

C. A secret target and an immediate penalty

D. A general instruction to work harder

Correct Answer: B. The performance gap, expected standard, support, review dates, and possible consequences