Every HR team has dealt with the fallout from a quick-and-dirty employee archive. Someone leaves the company, a manager hits the archive button, and three weeks later the finance team discovers that a company car is still assigned to a person who no longer works there. Or the IT department finds that a laptop never made it back because nobody flagged it during the departure. Or a performance review gets scheduled for someone who left two months ago.
Odoo has quietly replaced the old archive-and-forget approach with something substantially more deliberate: an End of Collaboration workflow that turns employee departure into a structured, scheduled process instead of a single destructive click.
The Old Way Was a Liability
Previously, archiving an employee in Odoo was a blunt instrument. You opened their record, chose archive from the actions menu, and the system did its best to clean up — ending the contract and cancelling upcoming appraisals and time off. But it left fleet vehicles and equipment still assigned. For a small company with a handful of employees, that might be manageable. For an organization running dozens of departures a year across multiple departments, it was a reliable source of dangling references and forgotten assets.
The core problem wasn’t that archiving was broken. It’s that departures aren’t instantaneous events — they’re processes that unfold over days or weeks, and the system needed to reflect that.
End of Collaboration: What It Actually Does
The new workflow lives under the Actions menu on any employee record. Instead of immediately archiving the record, selecting “End of Collaboration” opens a structured form that captures the full context of a departure before anything happens.
The first decision is the departure reason. Odoo ships three built-in options — Fired, Resigned, and Resigned: Retired — but companies can create custom reasons through the Employees app configuration. This matters for reporting. When you’re analyzing turnover at the end of the quarter, knowing that twelve people resigned versus three who were terminated versus two who retired tells a fundamentally different story than just seeing seventeen archived records.
Next come two dates that most ERP systems conflate but Odoo now separates: the Dismissal Date and the Departure Date. The dismissal date is when notice is given. The departure date is the employee’s actual last working day. In many jurisdictions, these can be weeks or months apart, and having both on record matters for legal compliance, final payroll calculations, and benefit cutoff timing.
Planned Actions: The Real Power
The feature that makes this more than a cosmetic rename is the Planned Actions tab. Instead of executing everything immediately or leaving it all to manual follow-up, Odoo lets you configure exactly what happens and when.
Each planned action can be toggled independently: archive the employee record, end the active contract, unassign the company car, return equipment, cancel future appraisals, and cancel approved time off. For each action, you choose the trigger date — either the departure date itself or a custom date you specify.
This granularity matters in practice. You might want to end the contract on the departure date but keep the employee record active for another week while payroll processes the final payment. Or you might want to unassign the company car a few days before the departure date to give the fleet manager time to schedule a pickup. The system accommodates these real-world timing differences instead of forcing everything into a single moment.
A Free-Text Field That Earns Its Place
The Detailed Reason tab provides a free-text field for departure notes. It sounds trivial, but it fills a genuine gap. When an employee leaves after a dispute, or a resignation comes with specific conditions about non-compete enforcement, or there’s a mutual agreement about reference letters, that context needs to live somewhere that’s attached to the employee record — not buried in an email thread that the next HR manager will never find.
What Happens When You Click Apply
Clicking Apply doesn’t immediately execute anything. It schedules the configured actions for their respective dates. On the departure date (or whatever custom dates you’ve set), the system automatically runs each action: the record gets archived with a visible “Archived” banner, the contract ends, fleet assignments clear, and future appraisals and time off disappear from the schedule.
If something goes wrong — say, the system can’t end a contract because of an unresolved payslip — Odoo surfaces a validation error in a pop-up that explains exactly what needs to be resolved before the action can proceed. No silent failures, no half-completed departures where some actions ran and others didn’t.
The Direct Archive Still Exists, But Think Twice
The old archive option hasn’t been removed entirely. You can still archive an employee directly from the Actions menu if you need to. But it comes with a catch: direct archiving ends the contract and cancels appraisals and time off, but it does not unassign fleet vehicles or equipment. It’s the quick-and-dirty path, preserved for edge cases but no longer recommended as the default approach.
The distinction is worth understanding for anyone managing HR processes. The End of Collaboration workflow exists because employee departures have consequences that ripple across departments — fleet management, IT asset tracking, payroll, scheduling, performance management — and a one-click archive was never equipped to handle all of them reliably. The new workflow doesn’t add complexity for its own sake. It adds the structure that prevents the three-weeks-later discovery that nobody returned the company car.