Secretary with a messy desk yelling on the phone

The coordinator role started with a real problem: fifteen to twenty hours every week burned on manual client log updates and spreadsheet formatting. Building a handful of macros and formula templates cut that down to about an hour, freeing up nearly two full workdays a week for higher-value work. Last Friday, that efficiency became the reason for a layoff. Management merged the role with a part-time position and let the position go, citing the reduced administrative workload as justification.

Now, severance is contingent on writing step-by-step documentation for every macro built along the way.

💸 Take Back Control of Your Finances in 2025 💸
Get Instant Access to our free mini course
5 DAYS TO A BETTER BUDGET

What the Original Job Description Actually Covers

Whether documentation is legally required depends heavily on what the actual job description and any signed employment agreement say about ownership of work product and post-employment obligations. If the original role was scoped around data entry and administrative coordination, and the automation work wasn’t part of any documented job duties, that’s relevant context, but it likely doesn’t change one key fact: work created during employment, using company time and company systems, generally belongs to the employer regardless of whether it was explicitly listed in a job description.

Most employment relationships, particularly in the US where employment is largely at-will, don’t require every task to be pre-specified in a job description for it to count as legitimate work product owned by the company. Building tools that improved the company’s own processes, on company time, with company data, typically falls under that umbrella even if “build automation macros” never appeared on the original hiring paperwork.

The Severance Condition Is Where the Real Leverage Sits

The more relevant question isn’t really whether there’s a legal obligation to document these macros in the abstract, it’s whether the severance offer is conditioned on completing that documentation, and whether that condition is being presented as a take-it-or-leave-it requirement. If the severance agreement explicitly states documentation must be completed to receive the payout, refusing to document likely means forfeiting that severance, a decision with real financial consequences, but one that’s fully within the right to make.

Reading the actual severance agreement closely matters here, specifically any language tying the payout to specific deliverables, deadlines, or conditions. If that documentation requirement isn’t written into the agreement itself and is only being requested verbally, that changes the leverage considerably, since verbal requests carry far less weight than something formally tied to a signed agreement.

Negotiating the Terms Before Agreeing to Anything

Given the severance is explicitly tied to a specific deliverable, this is a reasonable moment to negotiate rather than simply comply or refuse outright. That could look like asking for additional compensation specifically for the documentation work itself, treating it as a separate, paid deliverable rather than an unpaid condition of severance. It could also mean asking for a longer timeline, clarity on exactly what “documentation” needs to include, or a written confirmation that completing it satisfies the full severance condition with nothing else expected afterward.

Companies asking a departing employee to hand over specialized knowledge before they leave are, in a very real sense, asking for something valuable. There’s nothing wrong with treating that request as worth negotiating on its own terms, separate from whatever baseline severance was already being offered.

Weighing the Actual Trade-Off Here

The frustration here is completely understandable. Building something that made the role more efficient, only to have that efficiency used as the direct justification for eliminating the position, is a bitter outcome regardless of the technical details around documentation requirements. But the practical decision now is narrower: is the severance amount worth the time it would take to write clear documentation, or is walking away without it, and without that documentation ever existing, the better trade given how this was handled.

There’s no universal right answer here. Some people would rather take the severance and move on cleanly, treating the documentation as a final, distasteful task worth completing to get paid and leave. Others would rather withhold that specialized knowledge entirely, accepting the financial hit as the cost of not rewarding a company that used their own efficiency gains against them.

Getting Real Legal Clarity Before Deciding

Given the financial stakes involved, a brief consultation with an employment attorney, many offer free initial consultations, would clarify exactly what’s enforceable here, whether the documentation condition is standard and reasonable, and whether there’s room to negotiate additional compensation for it before signing anything. That consultation would also confirm whether anything in the original employment agreement addresses ownership of tools or processes built during employment, removing the uncertainty around what’s actually owed versus what’s simply being requested.

Where This Leaves the Decision

There’s no absolute requirement to document anything beyond what’s explicitly tied to the severance agreement’s actual terms, and even then, refusing remains an option, just one with a financial cost attached. Reading the severance agreement closely, negotiating for additional compensation or clearer terms around the documentation request, and getting a quick legal read on the specifics would provide much more solid footing before deciding whether to comply, push back, or walk away from the severance altogether.

Featured on Cents + Purpose: