Time and Activity: Investigate
Objective. Open the investigate view, move a single flagged signal from 'something looks off' to an evidenced finding with a named next step - without treating the flag itself as the conclusion.
This screen answers 'I can see an exception or an odd number - now what actually happened, and is it real?' It is the drill-down workspace where a manager turns a signal into evidence before acting.
See it in the demo
What this screen answers
A Sales or CSM person opens Investigate when a number or an exception has already caught their eye and the question is now 'what is behind this, and does it hold up?' It answers the step between seeing a flag and doing something about it: pull the context around one person, team or day so a manager can decide whether there is a real issue, a data gap, or a benign explanation. In a demo it is the screen that shows Time Champ routing attention, not just displaying dashboards.
The task
Start from one signal you can name out loud - an idle spike, a missing attendance, overtime outside policy. Scope the view to the team and the period that signal sits in, then open the underlying detail for the specific person or day. Narrate the chain: present time, then available hours, then the specific exception, then the surrounding context (was the agent reporting at all, was this a one-off or a pattern). The job is a short evidence trail, not a verdict in one click.
How to read it
The classic misread is to treat the flag as the finding. A signal here is a prompt to look, not a proven conclusion. Before you act, check two things: coverage (was there a signal at all for this person, or is a gap being read as a behaviour) and denominator (is the number against available hours or scheduled hours). A low figure driven by a missing data source is a data problem, not a performance problem. Confirm which sources feed this view with product and with the customer's own baseline before drawing a conclusion.
Honest limits
Investigate shows availability and activity evidence; it does not prove whether useful work was produced - that is a Work Output question. It also cannot tell you intent. A documented reason (approved leave, a system outage, a client-side delay) can fully explain a flag, so the honest output of this screen is 'here is what the evidence shows and what still needs confirming', escalated to the manager who owns the person or process.
Interpretation check
A flagged signal is a reason to look, not a proven conclusion. Check coverage and denominator before you act, because a data gap can masquerade as a behaviour problem.
In the field
KnackGlobal (~6,000 RCM seats): with labour the dominant cost line, a lead investigating a daily idle flag must first rule out a coverage gap before raising it, so the capacity-visibility story stays credible rather than accusatory.
Practical task
Pick one visible exception in the demo, scope to its team and day, and write a two-line finding: what the evidence shows, and the one thing you would confirm (coverage, denominator or a documented reason) before acting.
Self-check
A manager sees a red idle flag and wants to raise it with the employee. What do you check first?
Whether there was any signal for that person at all, and what the denominator is. A missing or partial data source can read as idle time. Confirm the evidence and coverage before any conversation.
Why is Investigate a step rather than an answer?
It assembles context around a signal so a human can judge it. It does not establish intent or cause, and it does not prove output. The output is an evidenced finding plus what still needs confirming, handed to an owner.
A low availability figure turns out to coincide with a VPN outage. How should it be read?
As a data or capture problem, not a performance one. The figure is unreliable for that window. Note the confound and do not treat the number as a behaviour finding.
What should this screen never be used to claim?
That an employee produced no useful work. Availability and activity evidence cannot prove or disprove output; that belongs to Work Output.
Verified vs demo. Screen is live in the demo at /#/investigate; exact controls and figures are SME-validation-pending.