Delivery Execution and Facilitation Support

Introduction

Training delivery is often treated as the visible endpoint of a long design process. In practice, however, a well-designed programme can fail during execution because rooms are not ready, technology is unreliable, facilitators receive incomplete information, learners are incorrectly enrolled, or problems are escalated too slowly. Delivery execution is therefore an operational and managerial discipline that converts a training plan into a controlled learning experience.

For HR professionals, coordination is not merely administrative support. It involves managing dependencies among learning objectives, people, technology, facilities, vendors, compliance requirements, learner experience, and evidence of completion. The coordinator must create conditions in which the facilitator can teach effectively and participants can engage without unnecessary friction. This requires structured readiness reviews, facilitator briefings, rehearsals, live monitoring, issue resolution, help-desk support, attendance verification, closure, and systematic learning from experience.

This chapter presents an integrated framework for those activities. It emphasizes operational control without reducing learning to a mechanical process. The central principle is that coordination should protect the conditions for learning while preserving the professional autonomy of the facilitator.

Learning Objectives

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

1. Conduct a systematic readiness review before a training session.
2. Brief facilitators on objectives, participants, logistics, risks, and escalation procedures.
3. Design and evaluate a rehearsal appropriate to the delivery format.
4. Monitor sessions using evidence-based operational and learning indicators.
5. Resolve incidents through prioritization, escalation, and documented corrective action.
6. Operate an effective learner help desk and verify attendance ethically and accurately.
7. Close sessions with appropriate records, communications, feedback, and follow-up.
8. Conduct a lessons-learned review that produces actionable improvement rather than blame.

1. Delivery Execution as a Socio-Technical System

A training session is a socio-technical system: outcomes emerge from the interaction of people, processes, technology, physical space, content, and organizational context. A useful conceptual model is:

Inputs → Readiness controls → Live delivery → Closure and evidence → Improvement

Inputs include the approved learning design, participant list, facilitator, venue or platform, materials, schedule, budget, and policies. Readiness controls test whether these inputs are sufficiently available and aligned. Live delivery transforms them into a learner experience. Closure creates evidence of participation and identifies follow-up actions. Improvement feeds lessons into the next delivery cycle.

This model has two important implications. First, readiness is not a single final inspection. It is a series of risk-reduction activities beginning when the session is scheduled. Second, operational quality and learning quality are related but not identical. A session can start on time and still fail pedagogically; it can also be educationally strong while suffering minor technical problems. Coordination must therefore monitor both execution and learning conditions.

1.1 Roles and accountability

A delivery plan should distinguish accountability from participation. Typical roles include:

A responsibility matrix, often called a RACI matrix, can clarify who is Responsible, Accountable, Consulted, and Informed. Its value lies not in the acronym but in preventing gaps and duplicated authority. For example, the coordinator may be responsible for attendance records, while the programme owner remains accountable for the integrity of completion reporting.

2. The Readiness Review

A readiness review is a structured assessment of whether a session can proceed as intended. It should occur at multiple points: during planning, several days before delivery, shortly before start time, and immediately after setup. The depth of review should be proportional to risk. A two-hour internal webinar with a familiar facilitator requires less control than a regulated assessment delivered simultaneously to several hundred employees.

2.1 Readiness domains

A comprehensive review addresses at least eight domains.

Purpose and scope. Confirm the approved objectives, audience, duration, delivery method, language, sequence, and success criteria. Check that late changes have been authorized and communicated.

People. Verify facilitator availability, participant eligibility, accessibility requirements, substitute arrangements, producer coverage, and escalation contacts. Participant data should be limited to what is necessary.

Content and materials. Confirm the correct version of slides, activities, facilitator guide, handouts, assessment instruments, links, case materials, and job aids. Version control is especially important where legal, safety, or compliance content is involved.

Environment. For physical delivery, inspect room capacity, seating, lighting, acoustics, temperature, signage, accessibility, power, catering, emergency arrangements, and privacy. For virtual delivery, inspect platform settings, registration, authentication, breakout rooms, recording policy, captions, chat, polls, screen-sharing permissions, and bandwidth assumptions.

Technology and data. Test devices, displays, audio, cameras, software, integrations, access permissions, backup files, and recording storage. Confirm how personal data will be collected, accessed, retained, and deleted.

Communications. Check invitations, joining instructions, calendar information, pre-work, time-zone statements, cancellation procedures, contact details, and reminders. Communications should state what participants need to do rather than merely describe the event.

Contingencies. Define alternatives for facilitator absence, room loss, platform failure, inaccessible materials, low attendance, security incidents, and delayed materials. A contingency is useful only when its trigger, owner, and action are explicit.

Governance and compliance. Confirm approval requirements, procurement rules, intellectual-property permissions, health and safety obligations, assessment integrity, accessibility standards, and records-management requirements.

2.2 Risk-based readiness

A simple qualitative risk model can prioritize attention:

Likelihood and impact may be rated on an agreed ordinal scale, such as 1 to 5. The expression is a prioritization device, not a precise probability calculation. It assumes that the organization has defined consistent rating criteria and that multiplying the scores is appropriate for its risk method. A high-impact, low-likelihood event may deserve more preparation than a frequent but minor inconvenience.

For example, if a platform failure is rated likelihood 2 and impact 5, its priority score is 10. If a missing name badge is rated likelihood 4 and impact 1, its score is 4. The platform failure should receive more attention, even though it is less likely. The coordinator should also record mitigation, owner, trigger, and residual risk rather than relying on a score alone.

A readiness register can use the following structure:

Readiness status should be evidence-based. “Green” means the item is verified, not merely expected to be complete.

3. Facilitator Briefing and Rehearsal

3.1 The facilitator briefing

A briefing should be a purposeful conversation rather than a document dump. It aligns the facilitator with the operating context while allowing the facilitator to identify pedagogical risks. At minimum, it should cover:

• intended outcomes and evidence of learning;
• participant profile, prior knowledge, roles, language, and likely concerns;
• schedule, breaks, transitions, and time-critical activities;
• room or platform configuration;
• materials, assessments, accessibility arrangements, and content boundaries;
• roles of the coordinator, producer, observer, and help desk;
• expected learner communications and attendance rules;
• escalation thresholds and emergency contacts;
• feedback, evaluation, and post-session reporting.

The briefing should also address psychological and cultural conditions. Facilitators need to know whether participation is voluntary, whether managers are present, how confidentiality is handled, and whether discussion could involve sensitive employee information. In HR training, topics such as harassment, performance, health, identity, or organizational conflict require careful boundaries and referral routes.

3.2 Rehearsal design

A rehearsal is a controlled test of the delivery system. It should match the real session sufficiently to reveal important failures. A superficial review of slides is not a rehearsal.

A useful rehearsal sequence is:

1. Confirm the run-of-show and timing.
2. Test entry, authentication, room access, or platform permissions.
3. Walk through opening instructions and attendance capture.
4. Execute the most technically or pedagogically demanding activities.
5. Test transitions, media, polls, breakout rooms, assessments, and handoffs.
6. Simulate at least one likely failure, such as a lost connection or unavailable file.
7. Confirm the recovery action and decision authority.
8. Record defects, owners, deadlines, and retest requirements.

For high-risk programmes, a full dress rehearsal may be justified. For routine sessions, a targeted rehearsal of critical paths may be more efficient. The critical-path principle means testing activities whose failure would prevent learning, create compliance exposure, or materially damage learner experience.

3.3 Timing and operational capacity

Timing should be treated as a design constraint. If a programme contains eight activities requiring an average of 12 minutes each, activity time alone is 96 minutes. Adding two 10-minute breaks and 15 minutes for opening and closure gives 131 minutes. This is not a prediction of actual performance; it is a planning estimate that assumes the activities can be completed within their average times and that transitions are included as specified. If discussion is likely to expand, the coordinator and facilitator should identify activities that can be shortened or moved to pre-work.

The same reasoning applies to help-desk capacity. If 120 participants are expected and historical data indicate that 8% contact support during the first 20 minutes, the expected number of contacts is:

Thus, 120 × 0.08 = 9.6, or approximately 10 contacts. This is an estimate, not a guarantee. It assumes the historical rate is relevant to the current audience and that contacts are counted consistently. A coordinator may use it to decide whether one support person is sufficient, but should also consider simultaneous contacts, issue complexity, and peak timing.

4. Session Monitoring

Monitoring should support delivery rather than turn the coordinator into an intrusive evaluator. The coordinator observes the system, identifies emerging problems, protects the facilitator’s attention, and ensures that significant events are recorded.

4.1 What to monitor

Operational monitoring includes:

• start and end times;
• successful access and authentication;
• audio, visual, captioning, and presentation quality;
• participation in activities and polls;
• attendance changes and unexplained departures;
• pace against the run-of-show;
• help-desk volume and unresolved issues;
• safety, privacy, or security events;
• facilitator requests and decisions;
• completion of required assessments or acknowledgements.

Learning-sensitive monitoring includes signs of confusion, silence after instructions, unequal participation, excessive cognitive load, irrelevant discussion, or activities that are taking longer than intended. These observations should be interpreted cautiously. Low chat activity does not necessarily mean low learning, and high verbal participation does not necessarily demonstrate competence.

4.2 A monitoring log

A monitoring log should separate observation from interpretation and action.

This structure reduces hindsight bias and creates an auditable record. It also prevents vague statements such as “the session went badly,” which are difficult to improve.

4.3 Performance measures

Measures should be selected for decisions, not collected because they are easy. Useful indicators include:

• On-time start rate = sessions starting on time ÷ total sessions × 100.
• Attendance completion rate = participants meeting the defined attendance rule ÷ registered participants × 100.
• Issue resolution rate = issues closed within the service target ÷ total logged issues × 100.
• No-show rate = registered participants absent ÷ registered participants × 100.

These indicators require clear definitions. For instance, “on time” might mean beginning within five minutes of the scheduled start, while “attendance completion” might require presence for 80% of the session and completion of an assessment. Rates can be misleading when denominators are small, when participants are forced to register, or when records are incomplete. Operational measures should therefore be combined with qualitative feedback and evidence of learning or application.

5. Issue Resolution and Escalation

Incidents are inevitable; unmanaged incidents are not. An effective response distinguishes urgency, impact, ownership, and communication.

5.1 Incident classification

A practical classification is:

• Critical: threatens safety, privacy, legal compliance, assessment integrity, or the ability to deliver the core session. Stop, isolate, or escalate immediately.
• Major: substantially affects access or learning for a group but may have a workaround. Assign an owner and communicate a recovery plan.
• Minor: affects individuals or convenience without preventing the main learning experience. Resolve through normal support channels and record for improvement.

The classification should be based on impact, not on who reports the issue or how loudly it is expressed. A single accessibility failure may be critical for the affected learner even if the rest of the group is unaffected.

5.2 The response cycle

A disciplined response cycle is:

1. Detect the issue through observation, learner report, or system alert.
2. Validate the facts without delaying urgent protective action.
3. Classify severity, affected population, and reversibility.
4. Contain the impact, such as pausing a recording or removing an incorrect file.
5. Communicate what is known, what is being done, and when the next update will occur.
6. Resolve or workaround using the authorized option.
7. Verify that the solution works for affected learners.
8. Document and review the root cause and preventive action.

The coordinator should avoid unauthorized improvisation where the issue concerns assessment answers, employee data, safety, or regulated content. Escalation is not failure; it is a control mechanism.

5.3 Root-cause thinking

A problem may have several causes. The “five whys” technique can help move beyond symptoms, but it should not be applied mechanically. For example:

• Learners could not access the assessment.
• Why? The link required a permission not granted to external users.
• Why? The test used internal accounts only.
• Why? The rehearsal did not include a representative user.

The corrective action is not simply “send the link again.” It is to include representative access testing in the readiness standard. More complex incidents may require a causal map, process review, or privacy/security investigation.

6. Help-Desk Support and Learner Experience

A help desk is part of the learning architecture. It reduces avoidable friction and gives facilitators room to focus on teaching. Support may be delivered through a dedicated email, phone line, chat channel, service portal, or named producer.

A support model should specify:

• channels and hours of availability;
• identity and access verification;
• common solutions and approved scripts;
• service targets for response and resolution;
• escalation criteria;
• documentation standards;
• accessibility and language support;
• privacy restrictions on information requested from learners.

The help desk should not require learners to disclose unnecessary personal information. Screenshots may contain names, employee numbers, or private messages, so collection and storage must be controlled. Support staff should also know when not to troubleshoot publicly, particularly where a learner’s performance, health, or employment status may be exposed.

A knowledge base should contain concise, tested instructions for joining, audio troubleshooting, password recovery, file access, captions, mobile use, and assessment submission. Articles should be version-controlled and reviewed after platform changes. AI-enabled chat support may answer routine questions, but it should be supervised, transparent, limited to approved information, and designed to hand off ambiguous or sensitive cases to a human. It should not make unsupported claims about attendance, eligibility, assessment results, or employment consequences.

7. Attendance Verification and Completion Evidence

Attendance is not identical to learning, yet organizations often need reliable evidence that a person participated. Attendance rules should be defined before delivery and communicated clearly. Possible evidence includes authenticated entry, participation in required activities, presence during specified intervals, completion of an assessment, or facilitator confirmation.

No single method is universally reliable. Platform presence may record an unattended open window. Manual sign-in may contain errors. Poll participation may be completed by another person. A defensible approach combines proportionate evidence, such as authenticated registration, interval checks, required activity completion, and a clear exception process.

Attendance data should satisfy four governance principles:

1. Purpose limitation: collect only what is needed to establish participation or compliance.
2. Accuracy: provide correction mechanisms and reconcile conflicting records.
3. Transparency: tell learners what is recorded, why, who can access it, and how long it is retained.
4. Security and retention: protect records and delete or archive them according to policy and law.

For virtual training, automated analytics should not be treated as unquestionable truth. A learner may lose connectivity while continuing to engage by telephone; another may remain logged in without participating. Exception handling should be humane, documented, and consistent.

8. Post-Session Closure

Closure begins before the session ends. The facilitator should reserve time for questions, assessment instructions, commitments, resources, and next steps. After delivery, the coordinator completes a structured closeout.

Immediate actions may include:

• confirming the session ended and the platform or room was secured;
• saving attendance, assessment, and issue records in approved locations;
• sending resources, completion confirmations, or follow-up instructions;
• notifying sponsors of material deviations;
• reconciling vendor, room, or catering obligations;
• checking unresolved learner cases;
• preserving evidence needed for audit while removing unnecessary personal data.

A closeout report should distinguish facts from judgments. It might state that the session began 11 minutes late because the room was unavailable, that 14 learners were affected, that an alternative room was used, and that the venue contract owner was assigned a preventive action. This is more useful than saying “logistics were poor.”

9. Lessons-Learned Reviews

A lessons-learned review is a structured inquiry into what should be repeated, changed, stopped, or tested next time. It should occur while evidence is still available, often within one week, with a later check on whether actions were completed.

A productive review asks:

• What was expected to happen?
• What actually happened?
• Which differences mattered to learners, facilitators, compliance, cost, or time?
• What conditions produced those differences?
• What should be retained, revised, or discontinued?
• What action has an owner, deadline, and success measure?

The review should include the facilitator, coordinator, producer, help-desk representative, and—where appropriate—learner or sponsor perspectives. Psychological safety matters. If reviews become blame exercises, participants conceal problems and the organization loses learning. At the same time, a learning orientation does not excuse negligence or deliberate policy violations; accountability and learning must coexist.

A useful action format is:

The success measure should test whether the change worked, not merely whether the action was completed.

Applied Case: Meridian Health Services Compliance Workshop

This is an illustrative case.

Background

Meridian Health Services planned a mandatory two-hour virtual workshop on respectful workplace conduct for 180 employees across four time zones. The programme included a scenario discussion, anonymous poll, knowledge check, and acknowledgement of the organization’s reporting procedure. Completion records were required for internal assurance.

Problem

During the first delivery, the facilitator’s slides displayed correctly, but several participants could not open the scenario file. The platform recorded attendance based on login duration, although some learners reported unstable internet connections. The help desk received 22 contacts in the first 15 minutes, exceeding its capacity. The facilitator continued teaching but shortened the scenario discussion and rushed the knowledge check. Post-session feedback showed that learners valued the topic but were uncertain about the reporting procedure.

Analysis

The readiness review had confirmed the facilitator’s internal test account but had not tested access with an external or mobile profile. The attendance rule was not clearly communicated, and the support estimate used a generic historical rate from low-risk webinars. No explicit trigger required the coordinator to pause or adapt the session when support demand exceeded capacity. The programme therefore had separate checks, but not an integrated readiness model.

Approach and solution

For the next delivery, the coordinator introduced four changes. First, a representative-user rehearsal tested desktop, mobile, accessibility, and external authentication. Second, the scenario was embedded in the platform and supplied as an accessible backup. Third, attendance was verified through authenticated entry, a mid-session activity, and completion of the knowledge check, with an exception process for documented connectivity problems. Fourth, a second support person was assigned during the first 30 minutes, and a severity trigger required the coordinator to notify the facilitator when more than five simultaneous access problems occurred.

The facilitator briefing also clarified that the reporting procedure was a critical outcome and could not be removed to recover time. A shorter optional discussion was identified in advance as the element that could be deferred.

Outcome

In the subsequent delivery, support contacts fell to seven, all core materials were accessible, and the session finished within the planned window. Three learners used the connectivity exception process. Knowledge-check completion increased, and feedback showed improved confidence regarding reporting routes. The organization retained the revised readiness register and added representative-user testing to its standard for mandatory virtual programmes.

Learning points

The case illustrates that delivery failure rarely has a single cause. Technical testing, staffing, attendance design, facilitation choices, and escalation rules interacted. The strongest intervention was not a more detailed checklist alone; it was the creation of evidence-based tests, explicit decision triggers, and protected learning priorities. It also shows why attendance analytics should be interpreted rather than blindly accepted.

Challenges, Limitations, and Ethical Considerations

Coordination systems can create unintended burdens. Excessive checklists may encourage compliance theatre, in which boxes are marked without meaningful evidence. Excessive monitoring can undermine trust and produce surveillance anxiety. Automated attendance systems can disadvantage learners with disabilities, unstable connectivity, or caring responsibilities. Recording discussions may expose sensitive information. Standardization can also suppress facilitator judgment when unusual learner needs require adaptation.

Ethical coordination therefore requires proportionality, transparency, accessibility, confidentiality, and human review. The organization should explain monitoring practices, offer reasonable adjustments, restrict access to records, and distinguish support data from performance-management data. Where training concerns sensitive HR matters, facilitators and coordinators need clear referral procedures and should never promise absolute confidentiality beyond organizational policy and law.

Contemporary delivery increasingly combines learning platforms, analytics, automated reminders, virtual classrooms, and generative AI. These tools can improve consistency and responsiveness, but their outputs require validation. AI-generated communications may contain inaccurate dates or inappropriate tone; automated classifications may misidentify attendance exceptions; analytics may privilege visible interaction over reflective learning. Human oversight, auditability, data minimization, and an appeal route are essential.

Best-Practice Principles

1. Begin readiness work early and revisit it at defined control points.
2. Test the real learner journey, not only the administrator’s view.
3. Use evidence, owners, deadlines, and contingencies for readiness items.
4. Brief facilitators on context and decisions, not just logistics.
5. Rehearse critical paths and simulate realistic failures.
6. Monitor learning conditions without confusing activity with learning.
7. Classify incidents by impact and escalate sensitive matters promptly.
8. Design help-desk support for peak demand and privacy protection.
9. Define attendance rules before delivery and provide fair exceptions.
10. Close every session with records, communications, unresolved-case management, and improvement actions.
11. Treat lessons learned as organizational learning, not a blame ritual.
12. Evaluate operational metrics alongside learner experience and evidence of application.

Chapter Summary

Delivery execution and facilitation support transform an approved training design into a reliable learning experience. The work is socio-technical: people, content, facilities, technology, data, governance, and learner needs must operate together. Readiness reviews should be risk-based and evidence-driven, covering purpose, people, materials, environment, technology, communications, contingencies, and compliance.

Facilitator briefings align objectives, participants, timing, roles, boundaries, and escalation procedures. Rehearsals test critical paths and realistic failure scenarios. During delivery, monitoring should protect learning conditions, identify emerging risks, and document observations, actions, and ownership. Issue resolution depends on detection, classification, containment, communication, verification, and root-cause analysis.

Help desks are part of the learning architecture and must be designed for capacity, accessibility, privacy, and escalation. Attendance verification requires transparent, proportionate evidence and humane exception handling. Post-session closure creates reliable records and follow-up, while lessons-learned reviews convert experience into tested improvements. Effective coordination balances control with professional judgment, operational efficiency with learner dignity, and standardization with accessibility and context.

Key Terms

Attendance verification: The process of establishing reliable evidence that a participant met defined participation requirements.

Contingency: A planned alternative action used when an expected condition fails.

Coordinator: The professional who integrates people, logistics, communications, records, and escalation for delivery.

Critical path: The sequence of activities whose failure would materially prevent successful delivery.

Escalation: The transfer of an issue to a person or authority with greater expertise or decision rights.

Facilitator briefing: A structured alignment conversation about learning, logistics, participants, risks, and responsibilities.

Help desk: A designated support service that assists learners with access, technical, administrative, or procedural problems.

Incident classification: Categorization of a problem according to its impact and urgency.

Lessons-learned review: A structured examination of experience to identify evidence-based improvements.

Monitoring log: A time-sequenced record of observations, risks, actions, owners, and status.

Readiness review: A formal assessment of whether the conditions for delivery are sufficiently prepared.

Representative-user testing: Testing conducted with users whose access, devices, roles, or needs resemble those of the actual audience.

Residual risk: The risk remaining after controls or mitigations have been applied.

Rehearsal: A planned simulation or walkthrough used to test delivery processes and critical activities.

RACI matrix: A responsibility tool identifying who is Responsible, Accountable, Consulted, and Informed.

Run-of-show: The detailed sequence of timing, activities, transitions, roles, and technical actions.

Service target: An agreed expectation for response or resolution time.

Session closure: The post-delivery process of securing records, communicating outcomes, resolving cases, and initiating follow-up.

Review Questions

Short Answer Questions

1. What are the principal domains of a training readiness review?
2. Why should a rehearsal test the learner journey rather than only the facilitator’s slides?
3. Distinguish attendance verification from evidence of learning.
4. What information should a monitoring log contain?
5. Why is root-cause analysis important after an operational incident?

Long Answer Questions

1. Explain how a training coordinator can balance operational control with facilitator autonomy.
2. Discuss the design of an effective learner help desk, including capacity, privacy, accessibility, and escalation.
3. Evaluate the strengths and limitations of automated attendance analytics.
4. Describe a complete incident-response cycle for a major virtual-training failure.
5. Explain how lessons-learned reviews can produce organizational learning rather than blame.

Analytical / Application Questions

1. A mandatory virtual session for 250 employees experiences 15 simultaneous access problems during its opening. Develop an incident classification, immediate response, communication plan, and post-session corrective action.
2. Design a readiness register for a blended HR programme involving a physical classroom, a virtual group, an assessment, and external vendor support. Identify at least six high-priority controls and their evidence.
3. Attendance data show that 92% of learners logged in for the required duration, but only 68% completed the case activity. Analyze at least three possible interpretations and recommend additional evidence before judging programme success.

Multiple Choice Questions with Answers

Question 1

Which statement best describes a readiness review?

A. A final survey of learner satisfaction

B. A structured assessment of whether delivery conditions are sufficiently prepared

C. A performance appraisal of the facilitator

D. A financial reconciliation completed after training

Correct Answer: B. A structured assessment of whether delivery conditions are sufficiently prepared

Question 2

What is the primary purpose of a rehearsal?

A. To replace the facilitator’s professional judgment

B. To test critical delivery paths and reveal likely failures

C. To guarantee that every learner will achieve the objectives

D. To eliminate the need for contingency planning

Correct Answer: B. To test critical delivery paths and reveal likely failures

Question 3

A platform failure is rated likelihood 2 and impact 5. Using Risk priority = Likelihood × Impact, what is its priority score?

A. 2

B. 5

C. 7

D. 10

Correct Answer: D. 10

Question 4

Which issue should normally be classified as critical?

A. A missing name badge

B. A minor delay in distributing refreshments

C. A privacy breach involving learner records

D. A facilitator using a different opening example

Correct Answer: C. A privacy breach involving learner records

Question 5

Which action belongs first in a disciplined incident-response cycle?

A. Detect the issue

B. Write the lessons-learned report

C. Delete the monitoring log

D. Assign blame to the nearest role

Correct Answer: A. Detect the issue

Question 6

Why should attendance analytics not be treated as unquestionable truth?

A. Platforms never record login information

B. Presence data may not demonstrate engagement and may miss connectivity exceptions

C. Manual attendance is always more accurate

D. Attendance is unrelated to governance

Correct Answer: B. Presence data may not demonstrate engagement and may miss connectivity exceptions

Question 7

Which principle requires collecting only information needed for a defined attendance or compliance purpose?

A. Purpose limitation

B. Unlimited retention

C. Open access

D. Informal escalation

Correct Answer: A. Purpose limitation

Question 8

What makes a lessons-learned action measurable?

A. It uses strongly worded language

B. It has an owner, deadline, and success measure

C. It is assigned only to the facilitator

D. It avoids recording evidence

Correct Answer: B. It has an owner, deadline, and success measure

Question 9

A programme has 120 participants and an estimated support-contact rate of 8%. What is the expected number of contacts?

A. 6.4

B. 8.0

C. 9.6, approximately 10

D. 15.0

Correct Answer: C. 9.6, approximately 10

Question 10

Which practice best protects facilitator attention during delivery?

A. Having the facilitator resolve every technical issue personally

B. Using a producer or help desk to handle operational support and escalation

C. Ignoring learner access problems until the session ends

D. Allowing participants to change assessment rules during the session

Correct Answer: B. Using a producer or help desk to handle operational support and escalation