How Teho baselines work without turning people into productivity data.
Teho runs bounded Teho Baselines. 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 page explains the Baseline boundary, privacy controls, evidence limits, prohibited outputs, and review materials available before rollout.
Every Baseline starts with an agreed question, not open-ended monitoring.
The Baseline starts with the operating question leaders need answered.
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.
Business question, teams, workflows, signal categories, exclusions, reviewer audience, and reporting level.
Thresholds, optional evidence modes, retention, redaction, and change-control path are named before rollout.
Coverage and confidence notes explain what the findings represent and where interpretation must stop.
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
The readout should be useful without pretending to be wall-to-wall.
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 because it is outside scope, excluded by policy, below threshold, low-confidence, unclassified, newly emerging, or outside the observation window.
Approved work-pattern signals, with richer evidence only where explicitly agreed.
Typical Baselines use approved work-pattern signals such as application context, active-window metadata, timestamps, duration, interaction labels, calendar metadata, ticket-system events, and communication timing.
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.
Review materials
Baseline-specific rollout and responsible-use materials. Vendor assurance documents live in the main Trust Centre.
Vendor assurance lives in the main Trust Centre.
Use the main Trust Centre for DPA posture, security and data residency, subprocessors, ISO readiness controls, AI provider disclosure, and security review packs.
Common questions
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 Baseline 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 are vendor security and processing details covered?
The main Teho Trust Centre owns subprocessors, regions, transfer mechanisms, DPA posture, and security review materials. This page only covers how a Teho Baseline should be bounded, explained, and used.
Need the client-specific Baseline trust pack?
Email info@teho.ai with the business question, team or function in scope, and the reviewer audience. Teho will route you to the right Baseline Charter, control pack, or employee-facing material.