> 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/job-rate-manager/core-concepts/real-world-scenarios.md).

# Real-world scenarios

## Overview&#x20;

This article walks through one employee’s reported time across four days of the same week, showing how the Job Rate Manager applies the same agreement differently depending on the day, the hours already worked that week, and the type of day involved.&#x20;

### Scenario: One Employee, One Week Under the Same Agreement&#x20;

#### Step 1: Agreement Established&#x20;

The Job Rate Manager first establishes which agreement governs this employee. Every decision that follows traces back to that agreement.&#x20;

#### Step 2: Thursday, Fourteen Hours Split Three Ways&#x20;

Thursday, fourteen hours land on a single line, entered as one entry, because that’s how a long day typically gets recorded. The Job Rate Manager classifies the time: eight hours regular, a daily cap, four hours overtime, and two hours double time, three pay categories from one entry.&#x20;

It updates one line and creates two. The original entry is corrected to eight hours regular, and two new lines are written beside it for overtime and double time. Classification comes from the rule engine first, and the update follows; that order is what makes the output safe to hand to payroll.&#x20;

#### Step 3: Friday, Nine Hours, a Different Result&#x20;

Friday, nine hours are reported: six hours regular, three hours overtime. Thursday’s cap was eight regular hours. Friday, under the same agreement, the same employee gets six, because this employee has nearly used up their regular hours for the week. Only six remain before the weekly cap, so six of Friday’s hours are classified as regular and the rest roll into overtime, regardless of how the hours were originally entered.&#x20;

The Job Rate Manager isn’t applying one flat rule to every day. It’s evaluating this employee’s actual position in the agreement on that date, which is the difference between a calculator and a rule engine.&#x20;

#### Step 4: Saturday, No Split Needed&#x20;

Saturday, six hours are reported, all of it overtime. No split is needed here, so the Job Rate Manager doesn’t create one. It corrects the type on the existing line and stops.&#x20;

#### Step 5: Sunday, a Full Day of Double Time&#x20;

Sunday, another six hours come back as double time for the entire day, not just the hours past a threshold. Registered public holidays follow the same pattern: Saturday overtime, Sunday double time.&#x20;

**Result:** Across four days under the same agreement, the same employee’s hours are classified four different ways, each correct for that specific day and that specific point in the week. Every union agreement carries quirks like these, and the Job Rate Manager applies them the same way regardless of who entered the data.&#x20;

## What This Scenario Illustrates&#x20;

The agreement governs every decision that follows. Establishing which agreement applies happens first, and every classification made afterward traces back to it.&#x20;

Classification comes before the update, always. The Job Rate Manager never classifies on its own judgment; the rule engine sets the classification, and only then does the update to IFS Cloud follow. That order is what makes the output safe to hand to payroll.&#x20;

The same rule set produces different results depending on position in the week. Thursday’s eight-hour regular cap and Friday’s six-hour regular cap come from the same agreement applied to the same employee. The difference is how many regular hours were already used, which is the difference between a calculator and a rule engine.&#x20;

No unnecessary lines are created. When a day’s hours don’t need splitting, like Saturday’s straight overtime, the worker corrects the existing line and stops rather than generating extra entries.&#x20;

Premium days apply to the whole day, not just the hours past a threshold. A double-time Sunday, or a registered public holiday, is treated as double time from the first hour, not only the hours that would otherwise exceed a cap.&#x20;

Consistency holds regardless of who entered the data. Every union agreement carries its own quirks, and the Job Rate Manager applies them the same way every time, whether the underlying entry was clean or came in as one long line for a fourteen-hour day.&#x20;