Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
A strong leave application is specific about the requested dates, gives enough truthful context to evaluate the request without oversharing, follows the institution’s actual process, and makes any necessary handoff, attachment, or return date clear.
School leave application To: [Principal/Class Teacher/Role] Subject: Leave request for [dates] Dear [Title/Name], I request leave from [start date] to [end date] because [brief truthful reason]. I expect to return on [date]. [Missed-work note if relevant]. Please let me know if [documentation/action] is required. Yours [appropriate close], [Name / class / identifying detail if required]
Work leave request Subject: Leave request — [dates] Hello [Manager/HR], I would like to request [leave type if known] from [start] through [end], returning on [date]. [Brief context if appropriate]. Before leave, I will [handoff/coverage]. [Urgent-contact boundary if relevant]. Please let me know if I need to complete any additional process. [Name]
Leave extension Reference: [earlier leave/approval] Current return date: [x] New requested return date: [x] Reason for change: [brief truthful context] Work/class impact: [x] Request: Please confirm whether the extension can be approved and whether any additional documentation is needed.
Emergency notification I am unable to attend [school/work] on [date] because [brief reason at appropriate detail]. I am notifying you as soon as possible. I will update [role/person] by [time/date] about [return / required paperwork / handoff] once that information is available.
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].