> 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/fundamentals.md).

# Fundamentals

## Overview&#x20;

The Job Rate Manager is an AI-powered Digital Worker that turns complex job rate rules into consistent, automated decisions for payroll, project, and operations teams. Triggered by a work order or project transaction, it enriches the time entry with the right master data and rule sets, classifies the resource and the time, applies the applicable labor, union, travel, equipment, and cost rules, and recommends the correct time and cost types before updating transactions in IFS Cloud, with human-in-the-loop review where needed.&#x20;

The Job Rate Manager never classifies on its own judgment. Classification comes from the rule engine first, and the update to IFS Cloud follows only once that classification is set. That order is what makes the output safe to hand to payroll.&#x20;

## Key Benefits&#x20;

**Faster rate creation:** Rates are determined in minutes rather than manual cycles, replacing spreadsheet-based calculation with an automated decision.&#x20;

**Higher accuracy:** Complex rule sets, labor, union, travel, equipment, and cost rules, are applied consistently every time, regardless of who entered the underlying data.&#x20;

**Reduced dependency:** Less reliance on tribal knowledge and the handful of subject matter experts who previously carried the exceptions in their heads.&#x20;

**Compliance ready:** Supports collective bargaining agreements, apprenticeship tiers, and FUTA/SUTA thresholds, with every rate decision traceable and auditable.&#x20;

**Payroll ready:** Produces clean job cost details ready for export to ADP and other payroll systems.&#x20;

## The Challenge It Solves&#x20;

Job rate determination in construction and field-heavy operations draws on many rule sources at once: customer-specific agreements, labor and union rules, equipment and travel costs, and cost rules that change frequently. That knowledge often sits with only a few individuals who know the exceptions by heart.&#x20;

Determining rates by hand against all of these sources is slow and inconsistent, which leads to revenue leakage, audit challenges, and heavy dependence on tribal knowledge. When the person who understands a particular union agreement’s quirks is unavailable, the whole team stalls.&#x20;

## Before and After&#x20;

#### Before&#x20;

Before the Job Rate Manager, determining the correct rate for a reported time entry requires manual effort at every stage:&#x20;

{% stepper %}
{% step %}
Identify which customer agreement, union rule, or labor classification governs the employee and the job
{% endstep %}

{% step %}
Look up the applicable geography-specific rules, calendars, and rate agreements by hand
{% endstep %}

{% step %}
Classify the reported time against overtime and double-time thresholds, often relying on one person’s memory of how a particular agreement works
{% endstep %}

{% step %}
Manually split or correct time entries across the right pay categories
{% endstep %}

{% step %}
Re-key or correct payroll and billing lines when a rate was misapplied or based on an outdated rule
{% endstep %}
{% endstepper %}

#### After&#x20;

With the Job Rate Manager, the same process runs automatically:&#x20;

{% stepper %}
{% step %}
A work order or project transaction triggers the Job Rate Manager the moment it comes in
{% endstep %}

{% step %}
The time entry is enriched with employee, labor classification, rate agreement, union, and job cost data
{% endstep %}

{% step %}
Geography-specific rules, calendars, and the applicable rate agreements are loaded
{% endstep %}

{% step %}
The resource and the time are classified against the correct thresholds for regular, overtime, and double-time hours
{% endstep %}

{% step %}
Labor, union, travel, equipment, fringe, and burden cost rules are applied, and hours are split across the correct pay categories
{% endstep %}

{% step %}
The correct time and cost types are recommended, and the corresponding transactions are updated or created in IFS Cloud, with human-in-the-loop approval where needed
{% endstep %}
{% endstepper %}

## How It Works&#x20;

The Job Rate Manager follows a consistent eight-step sequence for every transaction.&#x20;

**Capture time entries:** The worker triggers automatically on work order and project transactions.&#x20;

**Enrich context:** It pulls employee, labor classification, rate agreement, union, and job cost data relevant to the entry.&#x20;

**Prepare rule sets:** Geography-specific rules, calendars, and the applicable rate agreements are loaded.&#x20;

**Classify resource and time:** The worker determines the resource group, labor classification, and how the reported hours split across regular, overtime, and double-time thresholds.&#x20;

**Apply rate rules:** Labor, union, travel, equipment, fringe, and burden cost rules are run against the classified time.&#x20;

**Structure time:** Hours are split into regular, overtime, and double-time categories by threshold.&#x20;

**Recommend types:** The worker suggests the correct time and cost types, logged for reuse on similar entries.&#x20;

**Update and log:** Transactions are split, created, or updated in IFS Cloud, with human-in-the-loop approval where the worker’s confidence requires it.&#x20;

## What Triggers the Job Rate Manager&#x20;

**A work order or project transaction:** The worker activates the moment a new transaction of either type comes in.&#x20;

**A time entry requiring classification:** Any reported time that needs to be evaluated against labor, union, travel, equipment, or cost rules to determine the correct pay category.&#x20;

**Thresholds and premiums:** Hours that cross a regular, overtime, or double-time threshold, or that fall on a day governed by a premium rule, such as a registered public holiday.&#x20;

**Missing or conflicting information:** Where required information is missing or rules conflict, the transaction is flagged and routed to a person rather than finalized on an assumption.&#x20;