Employee Probation Management

This is a build-to-order module, not an instant download. After purchase, an ECOSIRE Odoo engineer contacts you to confirm your probation policy, Odoo version (17, 18 or 19) and edition (Community or Enterprise). We then build, install and test the module on your instance and hand over docs and training. Typical delivery is 2 to 4 weeks depending on how customised your evaluation checklist and workflow need to be.

Every build ships with a post-delivery support and bug-fix window covering the deployed module — if something breaks or behaves incorrectly, we fix it. We also provide guidance on configuration changes during that window. Because you receive the full source code, you can maintain it yourself afterward, or engage ECOSIRE for ongoing support, feature additions, or a paid upgrade when you move to a newer Odoo major version.

Yes. The module is built on standard Odoo framework primitives — hr.employee, mail messaging, ir.cron scheduled actions, QWeb reports and security CSV/record rules — so it runs on both Community and Enterprise across Odoo 17, 18 and 19. We build against your exact version so nothing is left to a compatibility guess.

Yes. Default probation durations are set in Odoo Settings (and can differ per company or department), and the evaluation checklist items are configured to your policy during setup, so changing them later doesn't require touching code. Anything structural — like an extra approval stage in the sign-off workflow — we scope and build in during the engagement.

A daily scheduled action (ir.cron) checks each active probationer's computed probation-end date. As completion approaches, it notifies the assigned manager and HR through Odoo's messaging layer. When the manager confirms sign-off, an automated action changes the employee's status to permanent and records the confirmation date; if they extend, the end date rolls forward and stakeholders are re-notified. No manual date-watching required.

It is delivered as a proper Odoo addon — clean models, manifest and views rather than direct database edits — which upgrades far more cleanly than ad-hoc customisation. Moving between major versions (for example 18 to 19) can still require a migration pass, which ECOSIRE can handle as a scoped update so the module keeps working on your new version.