Time and Activity - Application Overview

The customer problem

Operations leaders pay for labour by the hour but manage it by anecdote. They know the headcount and the roster, but they cannot say with evidence how many of those paid hours were actually available to do work versus lost to absence, late starts, long breaks or idle time - and they certainly cannot see it by team or by day without someone hand-building a spreadsheet.

The cost shows up in three ways. First, reconciliation effort: team leads spend hours each week stitching attendance logs, leave records and timesheets together just to answer 'who worked and for how long'. Second, silent capacity loss: available hours leak away through exceptions nobody reviews. Third, arguments without evidence: when a manager challenges an attendance or overtime pattern, it becomes one person's recollection against another's. In an RCM BPO like KnackGlobal, where margin per claim is thin and labour is the largest cost line, even a few percent of unseen unavailable time across thousands of seats is a material number.

How Time Champ addresses it

Time and Activity turns raw attendance and activity signals into a structured view of the paid hour. The observed areas in the demo cover attendance and hours, overtime, utilisation, capacity and leakage, a day timeline, idle and breaks, and exceptions, plus comparisons, productivity rules and a privacy and data sources area that makes the denominator and the capture basis explicit.

The key move is that it separates two different questions that customers routinely confuse. Attendance answers 'was the person present for their scheduled time?' Utilisation answers 'of the available hours, how much went to productive activity?' - a different numerator and a different denominator. The exceptions view is where value concentrates: instead of reading every timeline, a manager is routed to the days and people that fall outside agreed rules (for example excessive idle, missing attendance, or overtime beyond policy), so review effort lands where it matters.

Confirm with product which attendance and activity sources are in scope for a given customer; the demo shows the model, not a specific customer's entitlement.

The value and how to measure it

The value is recovered manager attention and defensible labour decisions, not surveillance. When available hours and exceptions are visible, reconciliation stops being a weekly manual chore, review time is spent on the few cases that matter, and attendance or overtime conversations are grounded in the same evidence both sides can see.

Measure it with the grounding's candidate measures, framed as a baseline the customer owns: attendance reconciliation effort (hours per week team leads spend assembling the picture - target: falls toward zero once the view is trusted); exception review rate (what share of flagged exceptions a manager actually reviews each week); and manager follow-through (do reviewed exceptions result in a logged action or decision). Avoid promising a utilisation uplift number - the honest value story is 'you will see available time and act on exceptions you currently cannot see', and the customer sets the target from their own baseline.

Sales task made concrete

Your task is to demonstrate an account exception and explain the denominator behind utilisation. Concretely:

1. Open the application at the daily operations view (https://time-activity.demo.timechamp.io/#/daily) and pick a team with a visible exception - an idle spike, a missing attendance, or overtime outside policy.
2. Say the business question out loud first: 'Of the hours we paid this team for yesterday, how many were available, and where should a lead look today?'
3. Open the attendance and hours view, then the exception, and narrate the drill: present time vs available time vs the specific exception.
4. Then make the honest point: show the utilisation figure and name its denominator explicitly - 'this percentage is productive activity over available hours, not over scheduled hours; that is why it answers a different question from attendance.'

Qualification questions to pair with the demo: 'How do your team leads reconcile attendance today, and how long does it take?' 'When a manager questions an overtime pattern, what evidence do they have?' 'Which exceptions would you want a lead to review every morning?'

CSM task made concrete

Your task is to review a team exception, distinguish absent time from available hours and overtime, and agree a manager review routine. A first-30-days adoption run:

1. With the customer admin, confirm the data sources and the utilisation denominator on the privacy and data sources view, so everyone agrees what 'available hours' means before anyone reads a number.
2. Take one real team and walk a single day's timeline: separate absent time (not present), available hours (present and able to work) and overtime (beyond scheduled). Make the customer say which is which - that is the comprehension check.
3. Agree productivity rules / exception thresholds with the customer rather than accepting defaults, so flagged exceptions match their policy.
4. Install a manager review routine: who looks at the exceptions view, how often, and where the resulting action is logged. Adoption is the routine, not the login.

Validate: is agent/data coverage complete for the team, or are there people with no signal that would distort the denominator?

Objections and honest limits

'This is surveillance / my staff will revolt.' Time and Activity is about the availability and use of paid hours, and the exceptions worth a manager's time - not keystroke voyeurism. Point to the privacy and data sources area and agree an employee communication plan during onboarding. Capture-policy specifics must be confirmed with product for the customer's deployment.

'We already have attendance / HRIS.' Attendance tells you presence; it does not tell you available hours, utilisation against that denominator, or route a manager to exceptions. Position Time and Activity as the layer that makes those existing records actionable, not a replacement for payroll.

Honest limit: utilisation here is activity-based availability, not completed output. A team can be highly utilised and still produce little of value - that question belongs to Work Output. Do not let a customer read utilisation as productivity in the business sense.