Data capture and trust

The customer problem

The moment a tool measures people, two fears appear. Employees and their representatives fear surveillance - that the tool watches keystrokes, judges unfairly, and punishes normal variation. IT and data-protection fear uncontrolled capture - data collected without a boundary, stored without a policy, visible to the wrong people. Both fears are legitimate, and both can stop a deal cold or quietly kill adoption after signature. The business impact: works-council or employee-representative objections in sensitive geographies, InfoSec blocking rollout, and - most corrosively - managers and agents not trusting the numbers because they do not understand or believe in how they were captured. A number nobody trusts is worse than no number, because it generates argument instead of action. Getting capture and trust right is not compliance theatre; it is the precondition for every downstream value claim.

How Time Champ captures - and what the demo shows

Capture spans the first two steps of the staircase.

• Activity evidence - Time and Activity derives attendance, available hours and utilisation from activity signals and configured productivity rules, with explicit 'privacy and data sources' areas in the product.
• Monitored work - Employee Monitoring captures application activity, with navigation that exposes capture policy and agent modes (including an RCM capture policy), productivity classifications, hybrid-work handling and administration. Capture is policy-driven, not all-or-nothing.
• Completed work - Work Output and Work Understanding capture work items, steps and process, again with explicit privacy areas and standards/taxonomy that govern what counts.

The important design truth the demo surfaces: capture is configurable by policy and mode, classifications are reviewable, and privacy and data-source settings are visible rather than hidden. That is your evidence that capture boundaries are first-class. What the demo does not, by itself, establish is the exact production retention, encryption, residency and access-control specifics for a given customer - those are product and security facts to confirm, not to improvise.

Trust boundaries - what to protect

Four boundaries matter in every conversation.

1. What is captured - activity and work evidence, governed by capture policy and agent mode. Not everything, everywhere, always; it is scoped by configuration.
2. Who can see it - access is scoped by role and organisation (see F05). The right answer to 'who sees my screen data?' is a role-and-scope answer, not 'the company'.
3. What it proves - a non-productive application label is not proof that an employee did no useful work (Employee Monitoring's own interpretation rule). Capture produces evidence to investigate, not verdicts to punish.
4. Employee communication - the product treats employee communication as part of monitoring setup; honest rollout tells employees what is captured and why. CSMs validate this during onboarding.

Hold these boundaries even when a customer pushes for more. A customer who wants to secretly surveil employees is asking for something that will damage their own adoption and may be unlawful in their geography - route that to a specialist, do not enable it on a demo call.

What to say / do

Sales talk track for the surveillance objection: 'I want to be direct about this, because it is the right concern. Capture here is policy-driven - you decide what is collected and for which roles - and access is scoped, so it is not a free-for-all. Just as important, a flag here is a prompt to investigate, not a verdict; a tool that pretends an app label proves someone was slacking would produce numbers your managers could not defend. The value is in understanding work, not catching people.' Then lead the demo at Work Output rather than at monitoring.

CSM onboarding routine (from the Employee Monitoring CSM task): validate agent coverage, classifications, capture policy, access and employee communication before anyone reads a number for a decision. If employee communication has not happened, that is a trust risk to raise, not to paper over.

For any specific question on retention, residency, encryption or legal basis: say 'I want to get you the precise answer' and bring in a specialist (F09, F10). Never guess on security.

Objections and honest limits

'Does it record keystrokes / screenshots / everything?' - Capture is governed by policy and agent mode; the honest answer names configurability and then routes exact capabilities and defaults to product confirmation. Do not assert a capability (or its absence) you have not verified.

'Where does our data live and who at the vendor can see it?' - Residency and vendor access are security facts - confirm with product, do not improvise.

'Can we monitor people without telling them?' - Treat as a red flag. Employee communication is part of honest setup and often a legal requirement; decline to position covert monitoring and escalate.

Honest limit: the demo demonstrates that capture is policy-driven and that privacy/data-source and access controls exist as product areas. It does not, on its own, prove the exact production privacy, retention, residency, encryption and legal-basis posture for a customer. Separate 'the product is built with capture boundaries' (demo-supported) from specific compliance commitments (specialist-owned).