Call now for EXPERT ADVICE 0115 931 4007 or ask a question here ...

captcha

Get Ready for British Summer Time

BST-MarchWith British Summer Time fast approaching, now is the time to make sure that the settings in your clocking terminals are correct.  On Sunday 29th March 2015 clocks advance forward one hour at 1am in the morning to become 2am.  On Sunday 25th October 2015 clocks turn back one hour at 2am in the morning to become 1am – a return to Greenwich Mean Time.

Recording the correct time of an employee’s clocking is crucial for accurately calculating their pay, bonuses and assessing attendance performance.  To help you ensure that your clocking terminals change their time automatically on the correct day we’ve put together a series of instruction sheets to help you update your terminals and ensure that the settings are correct.  Please select the appropriate instruction sheet for your clocking terminal(s):

HandPunch BST and GMT Settings via Focus Clock Utilities

HRX Proximity Terminal BST and GMT Settings via Focus Clock Utilities

Torus Timelink GMT to BST (March) Settings

Torus Timelink BST to GMT (October) Settings

Following the clock change it is wise to check:

Are the times now displayed on your clocking terminals correct?

If not, please contact us as soon as possible so that we can assist you making any necessary corrections to the terminals and timesheets.

Did anybody work over the 1am to 2am period within your organisation?

If yes, and you use the timesheet information to calculate those employees’ pay, then you’ll need to:

  • Deduct one hour from each affected employee’s total hours worked for the change to British Summer Time on 29th March.
  • Add one hour to each affected employee’s total hours worked for the change back to Greenwich Mean Time on 25th October.
  • Consider any impact on overtime or bonus entitlement and adjust accordingly.

Good luck and if you need further advise or assistance then please don’t hesitate to contact us.

Call now for EXPERT ADVICE 0115 931 4007 or ask a question here ...

captcha