Every leave request gets an answer, and the department always knows who is out.
Leave lives in email right up until the morning two lecturers from the same department are away and nobody saw it coming. This recipe gives faculty one form, sends the department head a request they can decide in a tap, emails the decision straight back, and leaves you with a full term of leave history on a single sheet instead of scattered across four inboxes.
Free · no credit card · you connect your own apps
Installing provisions each one, wired together and ready to run.
Where faculty submit a request: name, email, leave type, dates, reason. Publishing it auto-creates the Leave Requests response sheet, the single system of record.
Sent to the faculty member once the department head approves or rejects.
On submission, pauses for department head approval, then stamps the request's status on the response sheet and emails the requester the decision.
You connect your own accounts. Swap any app that offers an alternative at install.
Posts the review request (with the secure approval link) to your approvals channel. Swap for Telegram or Discord.
Emails the submitter the approval decision. Swap for Brevo.
Faculty fill the published Leave Request Form: name, email, leave type, start and end dates, and the reason. Your leave policy note can be shown right on the acknowledgement step, so the rules are visible at the moment they're relevant. Submitting fires the workflow automatically.
Publishing the form auto-creates its Leave Requests response sheet, the single record of every submission, and the workflow stamps each row's status once the decision comes in. One sheet, one row per request, no parallel tracker for someone to maintain.
The owning department-head channel gets a summary with a secure review link, and the workflow genuinely pauses at a human-in-the-loop step until someone clicks Approve or Reject. Nothing times out into an approval. Swap Slack for Telegram, Discord, or Google Chat at install.
On approval the row is marked approved and the faculty member is emailed the green light. On rejection it's marked rejected and they're asked to adjust and resubmit. Either way they hear back, which is the part that email threads reliably fail at. Nobody has to ask whether their leave was approved, and nobody has to go looking for the thread to find out.
Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.
