... | ... | @@ -23,22 +23,21 @@ To assure this is possible at least part of the time, we would like to see you o |
|
|
If the team gives a "_go ahead_", it is usually enough.
|
|
|
|
|
|
### Reporting
|
|
|
- We use the [Availability tool](https://internal.sinergise.com/General/Availability) for reporting and tracking absences from work or from the office.
|
|
|
- We use the "Availability tool" for reporting and tracking absences from work or from the office.
|
|
|
The primary purpose of the tool is informing your colleagues of your (un)availability.
|
|
|
|
|
|
- Any unregular absences from office should be reported in the Availability tool as soon as possible.
|
|
|
|
|
|
- Absence due to compensation of overtime, exchanging for weekend/holiday work or otherwise compensating should be reported as **'Not Working'**.
|
|
|
|
|
|
- To receive email notifications on absences, subscribe to [availability@lists.sinergise.com](https://lists.sinergise.com/sympa).
|
|
|
|
|
|
- There are currently two people configured to confirm planned absences (Grega Milcinski and Ales Okorn).
|
|
|
- There are currently two people configured to confirm planned absences.
|
|
|
It may happen that both are away, which is why there is automatic confirmation after 24 hours for less than a week long absence.
|
|
|
It happens extremely rarely that someone's plans would be rejected and if it does, it is communicated first in other form (verbal, mail, IM).
|
|
|
In case it happens that no response (neither confirmation or rejection) comes on time follow a general rule "if team is OK with it, go ahead".
|
|
|
(we will consider adapting the IT part of the system to reflect team organisation, but this is low priority).
|
|
|
|
|
|
- When arriving to work late, leaving early, or going out of the office (or home when working remotely) for a few hours on regular days, report that to your team channels.
|
|
|
|
|
|
- **Students**: leave should be reported as **'Not working'** instead of **'Leave'**
|
|
|
|
|
|
### Remote work
|
... | ... | |