Sabbatical and Faculty Leave Software
Kissflow routes a sabbatical proposal through eligibility verification, department chair and dean or provost approval, and a funding percentage decision, then tracks the mandatory report-back due when the leave ends, so a sabbatical is governed as the competitive, accountable award it actually is, not just another leave request in the queue.
Trusted by energy operators worldwide
A sabbatical proposal is not a leave request. It's closer to a grant application, with a report due when the leave ends.
A sabbatical carries obligations a standard leave request doesn't. Eligibility depends on years of service since the last one, not just available balance. The application itself is a proposal, a purpose statement, a project plan, sometimes a case for why the work benefits the institution, that a department chair, a dean, and often a provost's office all have to evaluate and approve. Funding is frequently partial, a percentage of salary, decided as part of the approval rather than assumed. And unlike most leave, a sabbatical typically comes with a condition attached to the approval itself: a report due after the faculty member returns, documenting what the leave produced.
Handled as a generic leave request, none of that gets tracked properly. Eligibility gets checked from memory. The proposal circulates as an email attachment through a chain of approvers who may not know what stage it's at. The funding percentage decision lives in an approval email, not a record anyone can audit later. And the report-back requirement, the one piece that closes the loop on why the institution granted a semester or a year of reduced teaching load, is the piece most likely to get forgotten once the faculty member is back in the classroom.
Kissflow runs the sabbatical specifically: eligibility tracking against years of service, proposal submission and review, sequential department, dean, and provost approval with a funding percentage decision recorded at each stage, and report-back tracking that stays open until the faculty member's post-sabbatical report is submitted and reviewed. Your HR leave system stays the record of leave balance and payroll; Kissflow is where the sabbatical's own governance, proposal to report, actually runs.
What breaks when a sabbatical is tracked like any other leave request
Eligibility isn't checked against actual years of service
Whether a faculty member is actually due for a sabbatical depends on someone manually checking against the last one taken.
The proposal circulates without a visible stage
A department chair, dean, and provost's office all need to review the same proposal, often without knowing where it currently sits.
The funding percentage decision isn't recorded anywhere auditable
Partial-salary funding gets decided in an email thread instead of on a record tied to the approval.
The report-back requirement gets forgotten
Once a faculty member returns to teaching, the post-sabbatical report condition attached to the original approval often goes untracked.
Six modules. Built so a sabbatical's report-back condition never gets forgotten.
Every module ships with default forms, routing, and dashboards. Configure each one to your sabbatical policy in the visual builder.
Eligibility tracking
Tracks years of service since a faculty member's last sabbatical against institutional eligibility policy.
Proposal submission
Captures the sabbatical proposal, purpose statement, and project plan as a single record for review.
Sequential approval
Routes the proposal through department chair, dean, and provost approval in order, with status visible at every stage.
Funding percentage decision
Records the approved funding percentage or salary arrangement directly against the sabbatical's approval record.
Report-back tracking
Keeps the sabbatical record open with a tracked deadline until the post-return report is submitted and reviewed.
Sabbatical program dashboard
Shows every active and upcoming sabbatical, funding commitment, and outstanding report across the institution.
From request to system of record in four steps
Submit
Eligibility is confirmed and the faculty member submits a sabbatical proposal for review.
Review
The proposal moves through department chair, dean, and provost review, with a funding percentage decided along the way.
Approve
The approved sabbatical is recorded and taken, with a mandatory report-back deadline set from the return date.
Record
The faculty member submits the required report, closing the sabbatical record once it is reviewed.
What changes when sabbatical governance runs on Kissflow
| Process | Before Kissflow | On Kissflow |
|---|---|---|
| Eligibility | Checked from memory against the last sabbatical taken | Tracked automatically against years of service |
| Proposal review | Circulated as an email attachment | Routed with visible stage and status at every approver |
| Funding decision | Settled in an email thread | Recorded on the approval record itself |
| Approval chain | Chair, dean, and provost each work from their own copy | One record moves through the full chain in order |
| Report-back | Easy to forget once teaching resumes | Tracked open until the report is submitted and reviewed |
| Program visibility | No institution-wide view of active or upcoming sabbaticals | One dashboard across every sabbatical and its funding commitment |
Connects to your HR leave and payroll system; leave balance and pay stay where they belong
Kissflow does not replace your HR system's leave balance tracking or payroll processing. It is where the sabbatical proposal, approval, funding decision, and report-back requirement are governed.
.svg){kind=logo}
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
Built for the report-back, not just the leave
Eligibility checked automatically
Years of service against the last sabbatical are tracked, not estimated from memory.
Funding decisions on the record
A funding percentage is recorded against the approval itself, not buried in an email thread.
Report-back that doesn't get forgotten
The sabbatical record stays open with a visible deadline until the post-return report is submitted.
Live in weeks
Academic affairs configures the eligibility rule, proposal form, and approval chain in the visual builder, without a systems project.
One proposal through every approver
Department chair, dean, and provost all work from the same record, with status visible at each stage.
Every sabbatical visible at once
Active, upcoming, and reporting-pending sabbaticals are visible across the institution, not tracked department by department.
Related apps
Leave Management & Teaching Schedule Coordination
Handles day-to-day leave requests and the teaching-coverage handoff across every leave type; this app runs the sabbatical-specific proposal, funding, and report-back governance cycle that generic leave tracking doesn't cover.
Faculty Lifecycle Events Management System
Tracks sabbatical as one event within the full faculty career lifecycle; this app is the deep workflow for that one event.
Faculty Governance Committee Coordination
Where a sabbatical policy or a contested proposal might go for committee-level review.
We help academic affairs govern a sabbatical as the accountable award it is, proposal through report-back
.gif)
“If a company cannot enable everybody to use AI, they will never get the true benefit of AI. Platforms like Kissflow allow us to put that capability in the hands of our users in a safe way.”
Vagesh Dave
GVP & CIO at McDermott International, Ltd
See The Full Story
“Advanced automation of all processes is easy to set up. I cannot imagine how to manage workflows without this software.”
Tanay Tiwary
Global Head - Digitalization & Business Improvement
See the Full Story
“Kissflow supports rapid application development by building a working application prototype in the shortest amount of time.”
Maria Theresa Cabigon
CIO, SN Aboitiz Power Group
See The Full Story
See what Kissflow can do for you
Talk to usGot questions? We're here to help.
Get SupportNo. Your HR system's leave balance tracking and payroll processing stay the system of record. Kissflow governs the sabbatical proposal, approval, funding decision, and report-back requirement.
That app handles day-to-day leave requests, FMLA, sick, vacation, standard sabbatical time-off, and the teaching-coverage handoff, across every leave type. This app runs the sabbatical-specific governance cycle underneath the leave itself: eligibility, the proposal, the funding percentage decision, and the mandatory report-back, which a generic leave request doesn't track.
Against your institution's policy on years of service since a faculty member's last sabbatical, tracked automatically rather than checked manually.
The record stays open and visible on the program dashboard as outstanding, rather than closing silently.
Yes, in the visual builder, with the AI Builder able to generate a starting workflow from a description of your sabbatical policy.
Access is role-based, restricted to the faculty member and the approvers at each stage of the chain.
Yes, the funding decision is recorded per proposal at the approval stage, not fixed institution-wide.
Yes. Kissflow is certified to SOC 1, SOC 2, SOC 3, and ISO/IEC 27001, and supports HECVAT review.
