StraViso TimeIQ™
Time Intelligence for the Workforce

When Every Minute Carries a Dollar, Provable Time Is the Advantage.

TimeIQ™ captures every minute of a worker's day from the devices and systems already in use, classifies it in real time as transit, activity, standby or white space, attributes it to the right job, shift or assignment, and produces an auditable Event Data Record that feeds billing, payroll, finance and operations with every minute explained.

One person, one shift, every minute attributedWorker 2847 · Mon 2 Nov · 8:00 shift
07:0009:0011:0013:0015:00
Check-in / wrap-upTransitActivity · job, shift or assignmentStandby / waitWhite space recovered
CHECK-IN07:00–07:10Shift start confirmed from device and schedule0:10
TRANSIT07:10–07:40To Assignment 1042 · auto-tagged from location and dispatch0:30
ACTIVITY07:40–09:50Assignment 1042 · status, location and attachments on the record2:10
WHITE SPACE09:50–10:15Untagged minutes matched to Assignment 1042 wrap-up0:25 · recovered
STANDBY11:00–11:40Waiting on access or next assignment · tagged, reason logged0:40
WRAP-UP14:30–15:00Assignment 1057 · manual override "handover" · reason required0:30 · reviewed
0 minutes unattributed0:25 white space recovered1 override, reason captured8 blocks, each an EDR
100% of minutes
attributed, minute by minute
Check-in, transit, activity, standby and white space, each on exactly one job, shift or assignment. Nothing lost, nothing counted twice.
1 reason
behind every manual change
Automatic tagging does the work; the worker confirms or overrides with a mandatory "why", and every change is logged.
0 systems replaced
over the top of what you run today
Reads the mobile, scheduling, dispatch, location and ticketing systems already in place; feeds billing, payroll, finance and BI through files, streams and APIs.
The Challenge

Time Is Recorded Everywhere and Proven Nowhere

A worker's day drives the invoice, the pay line, the utilization report and the margin. Yet the day is reconstructed from end-of-shift timesheets, a handful of status codes and estimates, long after the minutes themselves are gone.

Minutes that fall between
systems

Start and end times exist. The minutes in between are allocated by estimate, averaged, or left blank. Those white-space minutes leak straight out of the result, and nobody can say afterwards where they went.

LeakageWhite spaceAllocation

Time recorded from memory, not from the event

Status codes multiply into the thousands, yet the day is still keyed at the end of the shift from memory. Transit, standby and productive time blur together, and the numbers that reach finance describe the schedule, not what happened.

TimesheetsStatus codesSchedule vs actual

Questions after the cycle, not exceptions before it

Errors surface as customer disputes, pay corrections and failed audits. Evidence is rebuilt by hand, one case at a time, from systems that never agreed with each other. The first review of the number is often the one the other party does.

DisputesAuditRework
StraVisoTimeIQ™

Every Minute Captured. Every Minute Attributed. Every Minute Explained.

TimeIQ™ runs over the top of the mobile, scheduling, dispatch, location and ticketing systems your workforce already uses. Its embedded AI tags every second of the shift as it happens, matches it to the right job or assignment, and turns the day into a forensic Event Data Record that finance, operations and audit can all read. Nothing is replaced and no new tracking of people is introduced.

Capture

Automatic action detection

Check-in, transit, on-site or on-duty, standby, pause and complete are detected from location, status and activity signals and tagged in real time. The day is built from events as they happen, not keyed from memory at the end of the shift.

Attribute

White-space recovery

Continuous gap analysis finds the minutes between tagged blocks and matches them to the right job or assignment without extra taps or guesswork. Every minute lands in exactly one category on exactly one record.

Validate

One-tap confirmation, logged overrides

The worker confirms the shift or overrides a block with a comment. Any manual adjustment is flagged and requires a mandatory reason, so accountability runs from the point of work to finance.

Record

The Event Data Record (EDR)

One forensic, schema-versioned record per event: identity, context, domain detail and control metadata across 300+ fields. Start from a minimal profile and extend to your own domain without breaking what already runs.

See

Live utilization and margin insight

Minute-level attribution rolls up to real-time views of productive versus non-productive time, transit and standby ratios, and utilization by team, location, shift or assignment type, for leaders and supervisors alike.

Deliver

Audit-grade feeds, over the top

Every block carries its source, timestamps, approver and reason. EDRs flow as files, streams and APIs into billing, payroll, ERP, BI and customer portals, so the same record answers a dispute, a pay query and an auditor.

Add StraViso Operations Cloud

From what happened to what it is worth

TimeIQ™ records the day. Pair it with StraViso Operations Cloud and the same record is priced under your own rules, checked before and after the cycle, and written back approved, so the number that leaves is the number you can defend.

Your rules, versioned

Contracts, rate cards, policies and agreements as effective-dated rules your owners approve. Competing readings are held as versions. AI drafts rules and explanations; rules decide the outcome, never a model.

Checked twice

Before the cycle: complete, consistent, computed under the rule in force, approved. After it: what was billed or paid is read back and tied to what was approved. Exceptions arrive with evidence, before the cut-off.

Retroactive replay

A new rule version, rate step or settlement re-runs every period it touches and shows the population impact before anything posts. Whole periods are replayed from the record, not re-keyed.

How It Works

From the Shift Event to the Finance Feed, in One Traceable Flow

TimeIQ™ turns the signals a workforce already generates into attributed, validated, exportable time, and keeps the evidence on every block.

Capture · read-only

Signals

Check-ins, location, status changes, schedule and ticket events from the mobile, scheduling, dispatch and location systems already in use. No new tracking of people.

Detect

Blocks

Check-in, transit, activity, standby, pause and complete detected and tagged in real time, each with start, end and source.

Attribute

Every minute to an assignment

Blocks matched to the right job, shift or assignment; white space recovered; transit and standby classed by your policy.

Validate

Confirm or override

One-tap confirmation by the worker, supervisor review where needed; every override carries a reason and is logged.

Deliver · EDR

To billing, payroll, finance, BI

One Event Data Record per block, exported as files, streams or APIs. Add StraViso Operations Cloud to price, check and write back approved lines.

Wherever time becomes money. The same attributed day feeds every number that depends on it, and proves each one the same way.
InvoicesPay linesSettlementsCommissionsClaimsContractor payablesUtilization & margin
Granular by design

One Record That Grows With You

The Event Data Record is the unit TimeIQ™ works in. Every event, from a single status change to a completed job, becomes one record with the same layered shape, so any system can read it and any downstream process can rely on it. New domains add fields; they never change the core.

  • Granular. Minute-level time, geo, status, attachments and notes on the record itself, with the scheduled and actual values side by side.
  • Extensible. Schema-versioned. A minimal profile needs a dozen fields; a full domain profile uses hundreds. Both validate against the same structure.
  • Auditable. Source, timestamps, approver and override reason travel with every time block, and a basis identifier ties the block to the line it produced downstream.
  • Portable. Streamed as events, exported as files, or queried through APIs into finance, analytics and customer-facing portals.
BaseEvent identity. Event id, type, source, correlation id, timestamp. The seven fields every record shares.
ContextWho, where, under which agreement. Identity, role, supervisor, partner, geo and location.
DomainWhat the work was. Tickets, scheduling, risk and compliance, orders, fulfillment, pricing, payment, claims and more, added per domain.
ControlGovernance. Schema version, processing status, validity window, encryption and error handling.
Measured Impact

What Operations Achieve with TimeIQ™

Figures come from StraViso programs running on the same platform and are directional. Scope and baseline are agreed in discovery, and results are measured in your own numbers.

71%

Leakage reduction

On a field program once every minute was attributed before it reached the invoice.

20%

Of lines flagged before the cycle

Anomalies surfaced to finance in a 60-day production-scale test with Operations Cloud, ahead of the bill run.

10M+

Events a day

Carried by the platform today, with 100M+ API calls across the systems it orchestrates.

2,000+

Systems orchestrated

Over the top, through their own interfaces. None replaced.

5 mo

Payback

On a comparable program, measured in the customer's own metrics.

SOC 2 Type 2 SOC 2 Type 2 controls · dedicated tenants · private connectivity · role-based access · 24x7 managed service

See TimeIQ™ on Your Own Records

Start with one team and one completed period. We rebuild their shifts from the signals you already hold, show where the white space went and what each override cost, and compare the result with what was billed or paid. A 30-minute working session sets the scope.

  1. Discovery — agree the period, the sources and how success is measured.
  2. Replay — one team's completed period re-attributed from your records, read-only.
  3. Run live — real-time tagging and EDR feeds for that team, then the next.
Request a Demo
AskLumen