The Study starts with the operating question leaders need answered.
Trust Centre
How Teho studies work without turning people into productivity data.
Teho runs bounded Work Redesign Studies. We help leaders see where time and cost concentrate in the work we can safely evidence, then decide what to stop, simplify, automate, AI-assist, redesign, or keep human-led.
This Trust Centre explains the Study boundary, privacy controls, evidence limits, prohibited outputs, and review materials available before rollout.
01 - Study boundary
Every Study starts with an agreed question, not open-ended monitoring.
Teams, workflows, evidence modes, exclusions, time window, and reporting audience are agreed before rollout.
Findings are team-level work-pattern evidence and opportunity recommendations.
Coverage notes explain what the readout can represent and where interpretation should stop.
Before rollout, Teho can provide a client-specific Study Charter. It shows the proposed scope, cohorts, approved signal categories, optional evidence settings, exclusions, privacy thresholds, prohibited outputs, and expected report limits.
Review Study Privacy Posture02 - Outputs
Teho studies the work system, not the worker.
Outputs should help a sponsor understand where work is becoming slower, more manual, more fragmented, or more expensive than it needs to be. They should not be used to rank people, score effort, compare individuals, or automate employment decisions.
Teho produces
- Team-level Work Profile Maps
- Work-mix and opportunity patterns
- Ranked opportunities for work redesign
- Coverage and confidence notes
- Client-specific review materials before rollout
Teho does not provide
- Individual productivity scores
- Employee rankings or leaderboards
- Pace metrics or events-per-hour performance measures
- Supervisor-facing activity feeds
- Personal work histories or timelines
- Automated disciplinary, payroll, scheduling, or employment-decision recommendations
- Below-threshold small-group findings
03 - Coverage and confidence
The readout should be useful without pretending to be wall-to-wall.
Teho does not force every signal into a finding. A pattern needs enough contributor breadth, enough confidence, and enough relevance to the agreed business question before it can become leadership evidence.
Some real activity may be absent from the readout because it is outside the Study boundary, excluded by policy, below threshold, low-confidence, unclassified, newly emerging, or outside the observation window.
Coverage limits tell readers what the findings can safely represent. They also protect activity that is too small, too sensitive, too uncertain, or outside the agreed boundary to become a named leadership finding.See Coverage & Confidence in the sample readout
04 - Capture and optional evidence
Approved work-pattern signals, with richer evidence only where explicitly agreed.
Typical Studies use approved work-pattern signals such as application context, active-window metadata, timestamps, duration, interaction labels, calendar metadata, ticket-system events, and communication timing.
Optional evidence
Screenshot, semantic, or LLM-enabled evidence paths are deployment-specific. They should be used only where needed to answer the business question and only with explicit approval.
Exclusions and controls
Clients can agree exclusions, Privacy Guard rules, evidence settings, reporting levels, and retention posture before a Study begins.
Technical caveat
Excluded activity is kept out of the evidence base, and deployment-specific controls define what is technically blocked before capture.
05 - Security and processing
Security detail is routed to the right review surface.
The Activity Analysis baseline is UK-hosted. Deployment-specific subprocessors, data categories, regions, transfer mechanisms, optional evidence paths, and retention settings are named before contract signature.
06 - Review materials
Trust should be inspectable before rollout.
Before a Study rolls out, Teho can provide or co-create the materials a client needs to review the Study boundary, controls, outputs, and limits.
PublicStudy Privacy Posture
Overall Study posture, capture principles, prohibited outputs, and retention approach.
Public legal-supportingDPA summaryController/Processor roles, data categories, subprocessors, retention, and rights-support posture.
Public legal-supportingSecurity & Data ResidencyHosting baseline, security controls, optional evidence caveats, and review process.
Public legal-supportingEngagement TermsStudy commercial model, fixed-scope terms, and governing documents.
Client-specific or sample by requestStudy Charter
Proposed boundary, cohorts, signal categories, exclusions, thresholds, optional evidence, and expected report limits.
Request-based / client-specificDeployment control pack
Actual deployment settings, capture policy, Privacy Guard configuration, subprocessors, data-flow, retention, and change-control path.
Request-based / client-specificAcceptable-use / prohibited-output statement
What Study outputs should and should not be used for.
Generic source available; deployment copy client-specificEmployee-facing summary or FAQ
What employees should understand before rollout.
Final readout artifactCoverage & Confidence Statement
What the final findings represent and where interpretation limits sit.
07 - Common questions
The questions reviewers usually ask first.
Is this employee monitoring?
Teho studies repeated work patterns across a defined team or workflow. It is designed for work redesign, not individual productivity monitoring. Outputs are team-level and should not include personal productivity scores, rankings, leaderboards, pace metrics, or supervisor-facing activity feeds.
Do you score individuals?
No. Teho should not provide per-person productivity scores, employee rankings, or individual performance dashboards. The readout is designed to identify work patterns and operating opportunities at team or workflow level.
What happens to activity that is below threshold?
Below-threshold activity is protected from named reporting. It may be real work, niche work, sensitive work, early activity, or work attached to too few contributors to discuss safely. It should not be treated as absent or irrelevant.
Can we exclude apps, topics, teams, or workflows?
Yes. Exclusions are agreed as part of the Study boundary. Excluded activity is kept out of the evidence base, and the deployment control pack states which controls technically block, filter, or suppress each category.
Are screenshots required?
No. Screenshot or richer evidence paths are optional and deployment-specific. They should be used only where needed to answer the agreed business question and only with explicit approval.
Where is data processed?
The Activity Analysis baseline is UK-hosted. Deployment-specific subprocessors, regions, transfer mechanisms, and optional evidence paths are named before contract signature.
What can legal, security, or People teams review before rollout?
They can review the Study Privacy Posture, DPA summary, Security & Data Residency page, Study Charter, deployment control pack, data-flow and retention summary, employee-facing rollout materials, and prohibited-output / acceptable-use statement where applicable.
Review before rollout
Request trust materials Want the client-specific trust pack?
Email info@teho.ai with the business question, team or function in scope, and the reviewer audience. We will route you to the right Study Charter, control pack, or employee-facing material.