Sometimes you need to make a one-time change to a resource's availability. For example they have a vacation planned or are absent for other reasons. 



Rather than change the resource's normal working times (which apply to every week) or non-working day calendars (which apply to a range of resources), you enter a working time exception. Resource working time exceptions are set individually against each resource or resource team.


Working time exceptions override any availability % defined in the resources working pattern.


  • Select the resources menu option.


  • Select the edit icon next to the resource you want to update.





  • Select the exceptions section.


  • Click add exception.








Enter the exception


Exceptions for named resource are entered in hours. Exceptions for resource teams are entered in FTE.


Enter the exception details.


Start date - The date the exception period starts.


Finish date - The date the exception period ends.



If entering the exception for a named resource enter the exception hours per day






If entering the exception for a resource team enter the exception FTE per day


The exception FTE valued entered cannot be larger than the team size.






Resource working time exceptions and non-working day calendars restrictions


#1 You can't overlap resource working time exceptions with non-working day calendar entries


A resource working time exception cannot be added that overlaps with a non-working day calendar entry.


Example:

  • We have a resource who is on vacation from 20 December to 28 December.

  • The resource is using a non-working day calendar Public Holidays and this has 25 December as a non-working day. 


  • Two resource working time exceptions need to be added for 20 December to 24 December and 26 December to 28 December to enter the vacation.


  • The resource will now have the period 20 December - 28 December as non-working days.



#2 Non-working day calendar exceptions that are edited at the resource level become resource level exceptions


A resource is using a non-working day calendar and you update the resource directly to make one of the non-working days a working day. The working day now becomes a resource working time exception and any further changes for the date need to be made at the resource working time exception level.



Example: 

  • You have a resource using a non-working day calendar Public Holidays and this has 25 December as a non-working day.


  • You want to set the 25 December as a working day for the resource. 


There are two ways to do this:


  • Edit the resource working time exception for the 25 December (that has been inherited from the non-working day calendar and will currently be set as a non-working day) and set the 25 December to be a working day. 


  • Delete the resource working time exception for the 25 December (meaning the normal working time for the resource will be used instead).