WTR Reporting - Backfeed from Timesheets to Main Client

The system allows actual worked hours recorded in GRS Web Time Sheets to be reflected within the Working Time Regulation (WTR) reports.

Users, such as supervisors, can report against rostered, planned, or actual hours. This can help you to gain a more accurate view of working patterns, overtime, and potential breaches.

Where actual clocking data is unavailable, the system falls back to planned or rostered shifts to maintain continuity of reporting. The two fallback views are available in the WTR Summary Report and WT Breach Report.

  • Actual (fallback to Planned, then Rostered)

  • Planned (fallback to Rostered)

You can access these views via:

  • Analysis > Individual Duties > WTR Summary Report, and selecting Roster View

  • Individual Duties > WTR Individual Report and Analysis > WT Breach Report

Individual WTR Reports - include Worked Hours

The full set of views and behaviour for the two WTR Reports is as follows:

  • Rostered*: displays shift data based on the person's rostered post shift pattern. It ignores any planned overrides.

  • Planned*: displays the shift data based on the person's plan on the posting sheets (a combination of shifts from the underlying rostered pattern and any planned changes, including absences). It extends the period to accommodate non-worked absences in the average.

  • Planned (fallback to Rostered): displays the shift data based on the person's plan on the posting sheets and, where the person has no shift, it falls back to the pattern shift to fill the gap. For example, a person not having a shift because they are in the person's available area on the Posting Sheet because they are not on a shift. It extends the period to accommodate non-worked absences in the average. It usually displays the same values as those for Planned.

  • Actual*: displays the shift data based on the person's complete clockings and, for 'today' (the current given day) and where there are no clockings or incomplete clockings, it displays the Planned situation. It extends the period to accommodate non-worked absences.

  • Actual (fallback to Planned, then Rostered): displays the shift data based on the person's complete clockings and, for 'today' (the current given day) and where there are no clockings or incomplete clockings, the Planned (fallback to Rostered) situation. It extends the period to accommodate non-worked absences. It usually displays the same values as those for Actual.

*This is based on original WTR functionality.

WT Breach Report - include Worked Hours

The full set of views and behaviour for the WT Breach Report is:

  • Rostered: displays the breaches data based on the person's rostered post shift pattern. It ignores any planned overrides.

    The shift list used for checks is based on original WTR functionality.

  • Planned: default on load, displays the breaches based on the person's plan on the posting sheets (a combination of shifts from the underlying rostered pattern and any planned changes, including absences).

    This is the previous behaviour of this report.

  • Planned (fallback to Rostered): displays the breaches based on the person's plan on the posting sheets and, where the person has no shift, it falls back to the pattern shift to fill the gap. For example, a person not having a shift because they are in the person's available area on the Posting Sheet because they are not on a shift. It usually displays the same values as those for Planned.

  • Actual: displays the breaches based on the person's complete clockings and, where there are no clockings or incomplete clockings for 'today' (the current given day) and the future, it displays the Planned situation.

    This is based on original the WTR functionality.

  • Actual (fallback to Planned, then Rostered): displays the breaches based on the person's complete clockings and, where there are no clockings or incomplete clockings for 'today' (the current given) day and the future, it displays the Planned (fallback to Rostered) situation. It usually displays the same values as those for Actual.