Reuse last week’s requests or availability
Copying uses the immediately preceding week for a client or employee. It does not clone an entire confirmed schedule.
Before you start
Display the destination week and check permissions. Your workflow may require recurrence instead of copying; availability copying also depends on the planning mode.
Steps
- In the request week, find the client and use its last-week copy action when offered. This copies that client’s requests.
- For availability, open the employee week and that person’s action in availability-based mode. This copies availability, not assignments.
- Wait for reload and read the destination week’s items. These two actions have no universal arbitrary source-week selector.
- Correct relevant dates and constraints, then prepare assignments and communications through their separate workflows.
Example and expected result
Situation : Last week resembles next week, but Camille will be away Tuesday and the client changed one window.
Actions : Compare weeks before copying. After the available action, inspect target dates, people and requests; correct differences before sending.
Expected result : The target week retains only what you have checked. Tuesday and the changed window need a current decision.
Limits : Successful copying certifies neither eligibility nor old responses. Do not send the entire schedule assuming nothing changed.
If something goes wrong
For a missing action, check mode, permissions, prior items and recurrence workflow. After an uncertain response, read the result before repeating. Copying requests or availability means neither assignment nor acceptance.