Nanny Agency Jobs How-to / checklist

A useful time-off request gives the person making the decision a clear view of the dates, affected shifts and response you need. Start with the process already agreed for your job, then keep the request, decision and calendar entry connected. Sending a message is one step; it does not tell you whether the dates have been approved or entered correctly.

This guide concerns planned time away under an existing process. It does not establish leave entitlement, payment, accrual or a standard notice period. The worksheet and messages below are original tools you can adapt to the arrangement you actually have.

Find the existing request route

Check your work agreement or the instructions you have been given for requesting dates. Identify the recipient, communication channel and any stated timing. If an agency helped place you, do not assume the recruiter approves leave during the employment relationship. Establish who handles that decision now.

If the route is unclear, ask a focused process question before sending requests to several people: “Where should I submit planned time-off dates, and who confirms the decision?” Keep that answer with your work records so the next request follows the same route.

Henriette Dyer's communication article advises clear wording and attentive listening. That is the author's advice, not an INA leave policy. Here, clarity means describing the request precisely enough that the response can address the same dates and shifts.

Translate travel dates into affected work

A trip's dates and the work you are requesting off may differ. Leaving on a Saturday does not itself explain whether Friday afternoon is affected. Returning on Sunday does not tell your employer whether you intend to work your ordinary Monday start.

Write full dates, including the year, and use times for partial shifts. Separate nonworking days from scheduled work you are asking to miss. If your working pattern varies, check the current schedule rather than copying a usual week from memory.

Use this request worksheet before composing the message:

  • Request prepared: Date you are preparing this version.
  • Recipient and route: Named decision maker and agreed submission method.
  • Requested absence: Full dates, with start and end times where relevant.
  • Affected shifts: Each scheduled working block included in the request.
  • Next intended shift: The date and time you expect to return, subject to confirmation.
  • Flexibility: Any genuine alternative dates, kept separate from your first choice.
  • Response request: When you would like an answer, clearly distinguished from any agreed process deadline.
  • Current status: Prepared, submitted, awaiting clarification or decided.

Keep private travel details out unless they serve a practical purpose you want to explain. The request usually becomes easier to assess when the work dates occupy more space than the itinerary.

Send one clear request

Lead with the action you are asking the recipient to take. “I would like to request” is clearer than announcing that you will be away when a decision is still pending. A proposed response date can help organize the conversation, but it does not create approval if that date passes.

Fictional example: an original request to adapt.

“Hi Morgan, I would like to request time off on 12 and 13 November 2026, covering my scheduled 8 a.m.–5 p.m. shifts on both days. My next intended shift would be 16 November at 8 a.m. I am submitting this through our agreed email process. Could you let me know whether these dates are approved? If possible, I would appreciate a response by 2 November so I can plan. Thank you, Alex.”

The example includes no assumption about pay or leave balance. If your existing process calls for additional fields, provide those through that process. Keep an alternate option distinct: “If those dates do not work, I could instead request…” should describe a real option, not a promise to accept any proposed dates.

Separate approval from calendar recording

Keep three questions visible: Was the request received? What decision was made? Does the shared schedule reflect that decision? A reply acknowledging the message may answer only the first question.

If the response is uncertain, clarify the remaining point. “Thanks for checking. Should I keep 12 and 13 November marked as requested, pending your confirmation?” records the uncertainty without treating silence or a conversational “probably” as a final answer.

Once the decision is clear, retain its date and exact scope. Check that the calendar shows the approved absence and the intended return shift. Follow the existing arrangement for who updates that calendar. An entry marked “time off” without dates or status can be misleading when someone revisits it later.

Handle changed dates as a new decision

If your plans change, reference the earlier request and spell out the replacement. Do not quietly edit a shared calendar and assume the changed dates inherit the earlier approval.

Fictional example: an original changed-date message.

“Hi Morgan, my plans have changed. Could you review a request for 13 November only, instead of the approved 12–13 November absence? I am asking to work my usual 12 November shift and return on 16 November as previously discussed. Please confirm the revised arrangement before we update the calendar.”

Before leaving, share any agreed handover information through the usual private channel: where current routine notes are stored, which ordinary work items remain open and what needs an update before your return. Keep that information distinct from decisions about who provides care during the absence. Finally, check the latest approved dates against the latest calendar version so the original request does not remain the apparent plan.

Sources