| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 2631 |
| Technical Name |
wt_hrms_lifecycle |
| License | OPL-1 |
| Website | https://way4tech.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 2631 |
| Technical Name |
wt_hrms_lifecycle |
| License | OPL-1 |
| Website | https://way4tech.com |
WT HRMS Lifecycle — Onboarding, Offboarding & Resignation Workflows
Reusable onboarding/offboarding checklist templates, one-click generation onto each employee, and a resignation workflow with multi-level approval chain, computed notice period, and full audit trail.
onboarding checklist · offboarding workflow · resignation management · employee lifecycle · clearance · notice period · hr templates · new joiner · Odoo 19 · Odoo 18 · community edition · enterprise alternative · open hrms · HR software · HR automation · way4tech
Live Preview
A real screenshot from a working WT HRMS install on Odoo 19.
The Problem This Solves
Every joiner needs the same 25 things done. Every leaver needs the same 18 things recovered. Without a template engine, every employee gets a different (incomplete) experience.
Onboarding chaos
IT didn't get the laptop request. Admin didn't book the desk. HR forgot the offer letter. Days lost on every joiner.
Offboarding losses
Leaver walks out with the laptop, the SIM, the door card, system access still active — classic security and asset losses.
Resignations off-system
Resignation emails get forwarded around with no formal record, no notice-period calculation, no clear approval trail.
The Solution — Templates, One-Click Generation, Approval Workflow
Define checklist templates once. One button on every employee form copies the right list onto the record. Resignations follow the WT HRMS approval engine with notice-period auto-pulled from the contract version.
- ✓ Checklist templates — one for onboarding, one for offboarding, per company
- ✓ Sequenced template lines — drag-handle reordering, optional notes per task
- ✓ 5 responsible types per task: HR / IT / Direct Manager / Employee / Administration
- ✓ One-click Generate from Template button on each employee — copies all template lines
- ✓ Onboarding tab + Offboarding tab on every employee form
- ✓ Per-task tick-off —
action_mark_donestamps user + date for audit - ✓ Resignation workflow — full approval chain via
wt.hrms.approval.mixin - ✓ 7 resignation reasons — Personal, Career, Relocation, Compensation, Management, Health, Other + free-text details
- ✓ Auto-computed notice period — pulls notice_period_days from the employee's hr.version (defaults to 30)
- ✓ Resignation date + last working date tracked separately, with mail thread + activities
- ✓ Color-coded resignation list — rejected red, approved green
- ✓ Multi-company aware — templates and resignations carry company_id
+
Offboarding
Step-by-Step User Guide
Install
Apps → install WT HRMS Lifecycle. Pulls in WT HRMS Core.
Build templates
WT HRMS → Configuration → Checklist Templates. Create one Onboarding template and one Offboarding template per company. Add tasks, responsible types.
Generate on a new joiner
Open the employee form → Onboarding tab → click Generate from Template. Every line from the matching template is copied onto this employee.
Tick tasks as done
Each task has an Is Done checkbox. Ticking it stamps done_by and done_date. Same model holds onboarding and offboarding rows, separated by the checklist_type field.
Process resignation
WT HRMS → Resignations → New. Pick employee, reason, resignation date. Click Submit → approval chain runs → HR Manager Approve or Reject.
Run offboarding
From the same employee form → Offboarding tab → click Generate from Template. IT, HR, manager, admin all see their tasks.
Every Feature That Matters
Checklist Templates
Per-company, per-type (onboarding / offboarding) checklist with sequenced task lines. Drag-handle reordering.
5 Responsible Types
Each task assigned to HR / IT / Direct Manager / Employee / Administration — everyone knows what's theirs.
One-Click Generation
Buttons on every employee form copy the right template lines onto that employee. No manual re-typing.
Per-Task Audit
Tick a task → stamps the user and date. Read-only fields surface "who finished what when" for compliance.
Onboarding Tab
Dedicated tab on hr.employee form scoped via domain to onboarding tasks only.
Offboarding Tab
Sister tab for leavers — same UX, separate domain. The lifecycle Recovery checklist HR has been writing on whiteboards.
Resignation Workflow
Full draft → submitted → under_review → approved/rejected lifecycle via the WT HRMS approval mixin.
7 Reason Codes
Personal, Career Growth, Relocation, Compensation, Management Issues, Health, Other — analyse attrition reasons over time.
Computed Notice Period
Reads notice_period_days from the employee's current hr.version. Falls back to 30 if not set. No re-entry.
Mail Thread + Activities
Resignations have full chatter — followers get notified on every state change, internal notes audited.
Color-Coded List
List view paints rejected resignations red and approved ones green. Department + reason filterable.
Multi-Company
Each template + resignation carries company_id, and template lookup respects company on generation.
Compatibility & Requirements
| Odoo Edition | Community & Enterprise |
| Odoo Version | 19.0 |
| Dependencies | wt_hrms_core (which depends on hr, mail, hr_contract) |
| Python Packages | None |
| External Services | None — runs entirely inside your Odoo instance |
About Waqas Riasat & Way4Tech
We build Odoo modules that fix real business pain — not nice-to-have features. Every WT HRMS module is hand-tested on a fresh Odoo 19 install before being published.
way4tech.com · info@way4tech.com
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module