> For the complete documentation index, see [llms.txt](https://kb.theloops.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.theloops.io/digitalworkers/ifs-loops-digital-workers/digital-worker-guides/time-entry-manager/core-concepts/real-world-scenarios.md).

# Real-world scenarios

## Overview&#x20;

This article walks through a manager’s team being processed on a predetermined schedule, showing how the Time Entry Manager moves from historical reporting patterns to entries an employee has verified themselves.&#x20;

### Scenario: A Manager’s Team, Processed on Schedule&#x20;

Here we see an employee’s time registration page. The Time Entry Manager runs on a predetermined schedule, so no manual trigger is required for these entries to be reviewed.&#x20;

**Step 1: Scope Resolved**&#x20;

When time entries are submitted, the Digital Worker first resolves who is in scope: the manager and the people who report to them.&#x20;

**Step 2: Reporting History Read and Ranked**&#x20;

Next, for each person, it reads their actual reporting history and ranks the activity and report code combinations they use most, weighted toward what they’ve done most recently.&#x20;

**Step 3: Codes Checked for Validity**&#x20;

Then it checks that each code is still valid for the date, since codes expire and assignments change.&#x20;

**Step 4: Every Employee Handled Independently**&#x20;

Every employee is handled independently, so employees requiring additional human review don’t delay records already approved by the Digital Worker.&#x20;

**Step 5: Confirmation Email Sent**&#x20;

Following Digital Worker verification, a confirmation email is sent to the employee. An embedded button makes it easy for the employee to return to their time entry page and make any necessary edits.&#x20;

**Step 6: Employee Verifies Before Manager Approval**&#x20;

Requiring employee verification prior to manager approval ensures all entries are appropriately cross-checked. This is a critical distinction: entries are submitted, not confirmed. Any line the Digital Worker gets wrong is corrected by the employee, right here, and only then sent on for manager approval.&#x20;

Result: No more end-of-week guesswork about where the hours went. Employees and their teams reclaim the hours once spent reconstructing timesheets, avoid repeated correction cycles, and gain full visibility into every submission’s outcome.&#x20;

## What This Scenario Illustrates&#x20;

A schedule, not a person, starts the process. The Time Entry Manager runs on a predetermined schedule, so timesheets are reviewed and prepared without anyone having to remember to trigger it.&#x20;

Ranking favors what’s recent, not just what’s frequent. Activity and report code combinations are weighted toward what an employee has done most recently, not simply the most common entry across their whole history.&#x20;

Validity is checked fresh, every time. A code that was valid in an employee’s reporting history isn’t assumed valid today; codes expire and assignments change, so each suggestion is checked against the current date.&#x20;

One employee’s exception doesn’t hold up the team. Every employee is handled independently, so a record that needs additional human review never delays entries that have already been approved for someone else.&#x20;

Submitted is not the same as confirmed. The Digital Worker’s output goes to the employee for verification before it ever reaches a manager. Getting a line wrong isn’t a failure state; it’s exactly what the employee’s review step exists to catch.&#x20;

Verification is the cross-check, not a formality. Requiring the employee to verify before manager approval means two people, not one, have looked at every entry before it’s finalized.&#x20;