Time Card Reviewer Determination

Modified on Tue, Jan 20 at 6:35 AM

TABLE OF CONTENTS


Where Time Card Approvers are set up

Time Card Reviewer determination is a technical adjustment, and it is set up in the "Approval Processes Configuration” reference. This setup can vary by client. The system follows default logic to assign a Reviewer, as outlined below.






Who reviews Time Cards


Step 1: Start with the Employee's Time Card

The process begins with the specific Time Card under review.


Step 2: Check Scheduled Work Orders

  • Review Dispatches scheduled for the Time Card's date.
  • If at least one Dispatch includes a Crew Container with an assigned Owner, the system selects that Owner as the Reviewer.
  • If no such Owner exists, proceed to Step 3.


Step 3: Check Employee's Time Keeping Configuration

  • Examine the Employee's TK Configuration card for a default Work Order.
  • If a default Work Order is set, the system assigns the Employee's Supervisor as the Reviewer.
  • If no default Work Order exists, proceed to Step 4.


Step 4: Determine the Build Plan

A Build Plan is required to identify a Reviewer from its card. The system evaluates Time Card-related objects in this order:

  • A. Payroll Allocation: Select the Work Order (WO) with the majority allocation. If ties occur, it picks the first available WO (random selection).
  • B. Actual Allocation (if payroll allocation is empty): Check time entries with actual hours > 0 and non-empty allocated/GPS WOs. Sum hours by allocated WO (or GPS WO if needed) and select the majority WO. Ties default to the first available.
  • C. No Allocated Time Entries: Use the WO from the first available scheduled Dispatch (random if multiple).
  • D. Calculation Specification: Verify if the selected WO matches the specified combination of Region, Market, Project, Scenario, and WO in the Time Card Reviewer Calculation Specification.
  • E. Finalize Build Plan: Use the determined WO to identify the associated Build Plan.


Calculation Specification for TC Reviewer.

The Calculation Specification reference is accessible only to employees assigned to the Project Library Manager role. 



Step 5: Assign the Reviewer

Once a Build Plan is determined, the system assigns a Reviewer based on this priority from the Build Plan card:

  1. Project Role (highest priority).
  2. Build Plan Owner.


If no Build Plan is found, or if the Reviewer cannot be calculated from the Project Role or Build Plan Owner:

  • Fall back to the Employee's Supervisor (or next available in the hierarchy).


Exception Handling: If the calculated Reviewer is closed or matches the Time Card Employee, the system selects the next available option in the priority scheme (e.g., Build Plan Owner, then Supervisor).






When Time Card Reviewer is determined

The Reviewer is assigned either automatically (based on the Reviewer Approval Configuration) or manually. Automatic recalculation occurs in these scenarios:


Automatic Determination

Every time one of these events happens, the system recalculates the Reviewer for affected Time Cards:

  1. Daily during Time Keeping Processing (every morning, when Time Cards become ready for review).
  2. When an Employee allocates time via the mobile app.
  3. Each time a new TK Request is created for the Time Card's date.


Affected Time Cards:

  • Incomplete Time Cards.
  • Time Cards with active requests (TAR, Time-off, Misc).


These Time Cards must be:

  • From yesterday, or
  • From past days where the Reviewer field is empty.


Note: The Show Approvers action on a desktop Time Card triggers recalculation, displays the result, and allows manual override afterward.



Manual Determination

A TK Manager (Administrator) can set or change the Reviewer directly:

  • Via the Reassign action.
  • By editing the Reviewer field in the desktop Time Card.




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article