Skip to content
← Back to blogOperations

Read a Staff Member’s Workload and SLA History

Separate a staff member’s current open work from recorded ticket history, then inspect the SLA outcomes behind the totals.

See how it worksUnified Triage →

Priya Nair has two open tickets today. That backlog is not the same as the work recorded over a chosen period.

Priya Nair’s staff profile showing an all-age current backlog of two open tickets, an overdue count of zero, and a 90-day history filter

Priya’s profile separates open work now from the selected 90-day history. The screen uses fictional sample data.

Keep current work and history separate

The current-work cards include all open tickets, regardless of when they were created. The history window changes the handled and resolved totals instead. Filter by relationship (handled in period, currently assigned, previously assigned), then narrow by customer, site, issue, status, or priority. Select a bar or a date to open the matching ticket set, so every summary stays tied to the records behind it.

Recorded activity is an audit trail of actions, not attendance, availability, or productivity.

Read SLA outcomes with the ticket

The SLA view splits completed outcomes into met and breached groups, and each rate sits beside the number of eligible tickets. The target-versus-actual plot shows one completed ticket per point against its working-calendar allowance.

SLA target versus actual chart for Priya Nair showing met and breached completed tickets, with work mix and recorded activity calendar

Each dot represents a completed-ticket outcome; the diagonal is a timing reference for investigation.

Elapsed ticket time is not Priya's personal work effort. Open a matching SLA ticket and check its timestamps, policy, status, and history first. For the clock itself, use the SLA deadline calculator.

Continue exploring
Next product pathUnified TriageSee how Latch handles email, tickets, and queue routing in one operational workflow.Related pathOperations TeamsMap these patterns into an operator workflow with queue ownership and visible downstream actions.Related pathProduct OverviewSee how unified triage, approvals, audit trails, and plugins connect.
Related reads
Inspection Audit Trails Should Show the Work, Not Just the ResultSee how inspection audit trail software connects forms, photos, maker-checker approval, upstream work orders, and exportable evidence in one case record.Field Work Is Not Complete Until the Evidence Is CompleteHow field service teams define required ticket evidence, enforce complete records at closure, review AI troubleshooting, and report on outcomes.Why SLA Reports Need the Policy That Applied at the TimeSnapshot the SLA policy on each ticket so later reports explain performance against the commitment that actually applied.
Ready to move beyond reading?

See the same workflow running end to end.

Follow one ticket from intake through review and plugin execution. See the request, the decision, and the result in its audit trail.

See how it worksTalk to us