Time and Activity - Practical Assessment
Objective. Certify mastery of Time and Activity: the learner must demo an exception and defend the utilisation denominator, run the validation-and-routine play as a CSM, and avoid the critical errors - presenting a projection as a result, misreading a denominator, or treating a flag as a verdict.
This is the certification-gate assessment for the Time and Activity app. The learner works realistic scenarios, is scored against a checklist of what a correct answer contains, and fails on any critical error regardless of score. Pass requires a practical score of 80 or more, no critical error, and manager review. The self-check items below are the actual assessment questions with model answers.
See it in the demo
Scenario 1 - Sales: demo and defend the denominator
A prospect operations director says: 'Our team leads swear everyone is busy, but I cannot see where the paid hours go, and a tool we trialled last year just felt like spyware.'
The learner must, against the demo lab: (1) open on the business question before any screen; (2) walk attendance and hours to show scheduled time becoming available hours; (3) show one real exception from the queue and drill it; (4) show utilisation and name its denominator (available hours, not scheduled) and its ceiling (activity, not output) out loud; (5) handle the surveillance objection honestly via the privacy posture and an employee-communication plan; and (6) close on a pilot that agrees the denominator and thresholds and captures baselines - without promising any uplift number.
Scenario 2 - CSM: validate, diagnose and install the routine
A live customer's manager escalates: 'Your tool says my team was only 62% utilised last week and flagged three of my best agents as idle. That is wrong and my team is furious.'
The learner must: (1) refuse to interpret the 62% until coverage and freshness are checked for that scope and period; (2) confirm the utilisation denominator (available vs scheduled hours) and whether it was agreed; (3) reframe the idle flags as prompts to investigate, checking whether a coverage gap or uncaptured work (a long call, offline work) produced false positives; (4) check the productivity rules against the customer's policy; (5) separate what is a data/configuration finding from any genuine behaviour question; and (6) install or correct the manager review routine and name what, if anything, escalates to the specialist. The output is an evidenced finding plus what still needs confirming, not a verdict.
Scored checklist - what a correct answer contains
Score out of 100; 80 or more to pass, subject to no critical error and manager review.
- Leads with the question / the coverage gate (15). Sales opens on the business question; CSM refuses to read a number before validating coverage and freshness.
- Names the denominator explicitly (20). States utilisation is productive activity over available hours, not scheduled hours, and confirms it was agreed.
- States the output ceiling (15). Says utilisation is activity/engagement, not completed output, and routes the output question to Work Output.
- Treats flags as prompts, not verdicts (15). Reframes exceptions/idle as cases to investigate against agreed rules; checks coverage for false positives.
- Keeps capacity separate from cash (10). Does not convert leaked or idle hours into guaranteed savings.
- Honest limits and escalation (15). Confirms capture/privacy specifics with product; escalates integration and rule redesign rather than improvising.
- Lands a routine or next step on a customer baseline (10). Closes on the review routine and customer-owned measures, no promised uplift.
Critical errors - automatic fail
Any one of these fails the assessment regardless of the checklist score, because each would mislead a real customer:
- Presenting a projection or opportunity as a realised result - e.g. multiplying leaked or idle hours by a rate and stating it as guaranteed cash savings. Capacity is not cash.
- Misreading or mis-stating the denominator - reading utilisation as over scheduled hours when it is over available hours, or comparing two figures on different denominators without flagging it.
- Presenting utilisation as productivity/output - letting a customer conclude a high utilisation means the team is producing value.
- Treating a flag as a verdict - raising an exception or idle flag against a person without checking coverage and context first.
- Asserting capture-policy, security or entitlement specifics from the demo instead of confirming with product.
- Interpreting a figure without stating coverage when coverage is unknown or weak.
How this ties to the certification gate
This assessment is the app-level gate for Time and Activity and follows the Academy standard: a practical score of 80 or more, no critical error, and manager review of the recorded work. A learner who scores well but commits a critical error does not pass - the critical errors exist precisely because they are the mistakes that cost customer trust in the field.
Manager review checks two things the score alone cannot: that the honest limits were stated out loud and unprompted (not just known), and that the next step was anchored to the customer's own baseline rather than a vendor promise. Re-attempts are expected; the bar is competence a customer can rely on, not a first-try pass. Record both scenarios so the reviewer can see the reasoning, not just the conclusion.
Interpretation check
Passing proves the learner can defend the utilisation denominator, treat flags as prompts not verdicts, keep capacity separate from cash, and state honest limits unprompted. Any critical error - projection as result, denominator misread, utilisation as output, flag as verdict - fails regardless of score.
In the field
KnackGlobal (~6,000 RCM seats): the critical errors here mirror the real stakes - in a ProHance-displacement fight, one overstated savings claim or one utilisation-as-productivity slip hands the incumbent a credibility attack, which is exactly why the gate fails those errors outright rather than averaging them away.
Practical task
Complete both scenarios for manager review. For Scenario 1, record the seven-minute demo. For Scenario 2, write the evidenced finding: the coverage/denominator/rule checks you ran, your diagnosis (data gap, misread or genuine mismatch), the reframed flags, and the routine or escalation you would set. Self-score against the checklist and flag any critical error before submitting.
Self-check
ASSESSMENT Q1: A prospect says 'show me how productive my team is.' You open utilisation. What must you say about this screen, and what must you not claim?
MODEL ANSWER: Say utilisation is the share of available hours engaged in activity classified as productive - a capacity/engagement signal, measured against available hours, not scheduled hours. Must NOT claim it proves the team is productive in output terms; a team can be highly utilised and produce little of value, and that question belongs to Work Output. Also note the productive classification is configurable. Critical error if utilisation is presented as output.
ASSESSMENT Q2: A manager disputes a 62% utilisation figure as 'wrong.' Walk your first three moves.
MODEL ANSWER: (1) Do not interpret 62% yet - check coverage and freshness for that team and period on the data sources view, because a gap skews the denominator rather than reading as zero. (2) Confirm the denominator - available vs scheduled hours - and whether it was agreed with the customer. (3) Check the productivity rules match the customer's policy. Only then decide if it is a data/config finding or a genuine question. Critical error if you interpret the number before validating coverage.
ASSESSMENT Q3: A customer multiplies 1,200 idle hours by their blended rate and says 'that is our monthly saving.' Respond.
MODEL ANSWER: That converts a capacity opportunity into cash, which is a critical error. Recovered capacity, billed value and collected cash must stay separate; idle also includes uncaptured work and policy-compliant breaks, so the hour count itself overstates the recoverable slice. Freed hours become money only if redeployed to work that is billed and collected - an owner-driven Value Leakage exercise, not a figure this screen can promise.
ASSESSMENT Q4: Three strong agents are flagged idle and the manager wants to confront them. What do you do?
MODEL ANSWER: Reframe the flags as prompts to investigate, not verdicts. Check coverage first - a missing or partial signal reads as idle - and whether the time was uncaptured work such as a long call, meeting or offline reading. Confirm the idle threshold was agreed. Only after an evidenced drill, handed to the owning manager with what still needs confirming, is any conversation warranted. Critical error if a flag is treated as proof of wrongdoing.
ASSESSMENT Q5: A prospect asks exactly what the agent captures and how long data is retained. How do you answer, and what would fail you?
MODEL ANSWER: Describe the model honestly - availability and activity signals with an agreed privacy boundary and employee-communication plan - and confirm the specific capture policy, retention and entitlements with product for their deployment. Asserting capture, security or retention specifics from the demo as fact is a critical error.
Verified vs demo. The scenarios run against the live demo lab and the paid-hour model is demo-shown. Specific figures are illustrative/SME-validation-pending, and any capture, security, retention or entitlement claim in an answer must be 'confirm with product', not asserted - asserting such specifics is itself a critical error in this assessment.