This version of Automata is still in its infancy. Not only are we building a new product from scratch but the business as well. This level of challenge and complexity demands a lot from the team. Therefore we’ve put a process together to address overtime that is stage appropriate and aims to support you in periods of ‘crunch’.

The examples below have a ‘Customer Success’ slant to them as this team is impacted most frequently by this type of work, however, this policy applies to everyone.

Principles

| | Reactive (Not pre-planned, has to be given for specific days; e.g. a team works long hours to deploy a system Mon-Thu, they are then given Fri off by their manager) | Proactive (Pre-planned, work spike identified in advance, quantified and pre-approved by manager and HR; e.g. a deployment needs to happen over a weekend so the team will work for these 2 days) | | --- | --- | --- | | Time Off In Lieu | ✔ Examples:

Getting called onto a customer site to troubleshoot a workflow on a Friday and having to work until 11pm. Your manager then might tell you to take a half day the following Monday

Working on preparing a system for FAT from Mon-Thu, until late every night. Your manager then might tell you to not come in on Friday | ✔ Examples:

A diagnostics lab needs us to deploy a system over the weekend to minimise downtime while deploying

To meet tight customer deadlines we have to deploy a 12-bench system in one calendar week and therefore have to work the weekend | | Overtime | ✖ | ✔ Examples:

A diagnostics lab needs us to deploy a system over the weekend to minimise downtime while deploying AND you can’t take TOIL

To meet tight customer deadlines we have to deploy a 12 bench system in one calendar week and therefore have to work the weekend AND you can’t take TOIL |

Additional Considerations