See where the working day goes, without watching people.
Endpoint and web activity is sampled by the same agent that reports hardware, then rolled up into focus hours, application categories, project time and idle patterns. Reporting defaults to team level, individual views are permission-gated, and every collection rule is written into a policy the employee can read.
- DEFAULT REPORTING
- Team-first
- AGENT COLLECTION
- Consent-based
- TIME ATTRIBUTION
- Per project
- CATEGORY RULES
- Configurable
Capabilities
Focus hours and activity
Active, idle and meeting time are sampled and summarised into focus blocks per day and per week, with no screenshots and no keystroke logging.
Application categorisation
Applications and sites are grouped into productive, neutral and personal categories using rules you configure per team and per role.
Project and ticket attribution
Measured time is attributed to the ticket in Desk or the project it belongs to, turning timesheets into evidence instead of recollection.
Workload and capacity
Team dashboards show load distribution, overtime patterns and available capacity before the next commitment is made.
Consent and policy controls
Collection scope, retention window and who may see individual data are set in policy, shown to the employee and recorded in the audit log.
Overload signals
Sustained after-hours activity, no-break days and rising rework are surfaced to the manager as a wellbeing signal, not a scorecard.
Monitoring employees can see.
Monitoring only earns trust when people can see what is collected and why, so the limits are built into the product, not left to each manager.
Visible, never covert
A collection indicator is always shown on the device, and the agent checks for an active consent record before it sends anything.
Some things are never collected
Keystrokes, file contents, messages, webcam, microphone and location are never collected, whatever the policy says.
Teams first
Reporting is team-level by default, groups too small to stay anonymous are suppressed, and there are no individual rankings or leaderboards.
Effort lands against the ticket and the team.
Pulse attributes measured time to the tickets in Desk and reports capacity against the team structure held in People. Cost of delivery per customer becomes a number you can defend in a renewal conversation.
- MaeOne Desk
Measured effort is attributed to the ticket and project it belongs to, so timesheets are evidence.
- MaeOne People
Reports capacity against the team structure held in People.
- DEPLOYMENT
- Cloud tenant or private VPC
- AGENT SUPPORT
- Windows, macOS, Linux
- COLLECTION
- Consent-based, policy-scoped
- ACCESS
- Team-level by default, individual gated
- DATA RESIDENCY
- US, EU or UK region, fixed per tenant
Questions about MaeOne Pulse.
Not covered here? A named engineer replies within one business day.
No. Pulse samples endpoint and web activity into focus hours, application categories, project time and idle patterns, under a collection policy the employee can read.
Reporting defaults to team level. Individual views are permission-gated, so only the roles you authorise can open them.
Measured time is attributed to the tickets in Desk and the projects they belong to, and capacity is reported against the team structure in People.
