How to extract obligations with source references for Separation Agreements

Extract obligations from a separation agreement by recording each required action separately and linking it to the controlling wording, incorporated documents, triggering facts, and completion evidence. For employers, distinguish an obligation’s existence from its readiness for performance: severance may depend on release delivery and effectiveness, while earned compensation requires separate treatment. The resulting obligations register should tell legal, HR, payroll, benefits, and IT who must do what, when, under which conditions, and what remains unverified. It should support approved instructions without turning unresolved assumptions into payment dates.

When to use this workflow

Use this workflow when an approved or signed separation agreement moves into administration, an amendment changes payment conditions, or an employer inherits separation obligations through a transaction. Employment counsel resolves interpretation; HR, payroll, benefits, and IT provide operational facts and evidence.

The scope is extraction and verification, not comprehensive enforceability review. This guide uses a US employer perspective and selected federal waiver and reporting protections. Refer applicable state wage-payment, confidentiality, restrictive-covenant, and notice questions—and relevant NLRA, benefit-plan, and tax questions—for separate analysis. The steps below are recommended controls, not universal legal requirements.

What you need

Assemble these inputs before issuing operational instructions:

• The signed agreement, release exhibits, amendments, incorporated agreements, and last approved draft.
• Offer and revision history, delivery records, signature timestamps, and records from designated revocation channels.
• Employing entity, employee work locations, age, role, separation date, individual or group-program status, and pending claims.
• Payroll and benefits records separating earned compensation, existing entitlements, and additional release consideration.
• Equity and retirement documents, property inventories, expense submissions, and required notice addresses.
• Named legal, HR, payroll, benefits, and IT owners, including payment-approval authority.

Assign stable document IDs and version designations. Keep sensitive employee information in access-controlled records; include only necessary administrative facts in the register.

Use the template

The companion template is Separation Agreements — Obligations register. Copy this table into your working document or spreadsheet. Use one row for each independently performable action, installment, or continuing restriction. Cross-reference shared conditions rather than duplicating them inconsistently.

Source / text identifies the document, version, section, page, and short operative excerpt. Include controlling definitions and cross-references. For unnumbered provisions, use a page and paragraph identifier within the retained copy.

Distinguish the contractual obligor from the internal owner: the employee may owe property return while IT verifies receipt. Preserve the contractual deadline formula and delivery method before adding calculated dates. Proof / status links evidence; Gaps / decision identifies uncertainty, confidence, decision owner, and any instruction hold. Keep stable row IDs when sorting a spreadsheet.

Step by step

1. Establish the controlling document set

Compare the executed agreement and exhibits with the last approved draft. Investigate changed amounts, dates, definitions, attachments, and signatures. Mark superseded versions without deleting the history needed to establish which offer or release was delivered.

Follow incorporation language. If an earlier confidentiality agreement supplies continuing duties, obtain it before summarizing those duties. A reference to an unavailable agreement establishes a dependency, not its contents.

Record: controlling document IDs and execution status, with missing attachments or discrepancies assigned to legal. Preserve the exact source copy used for extraction.

2. Separate actions, restrictions, and conditions

Read for operative verbs: pay, deliver, return, reimburse, cooperate, notify, maintain, and refrain. Extract employer promises alongside employee duties. Distinguish historical representations from future obligations, but flag representations that affect payment conditions.

Do not convert every release provision into a task. Link release scope, cutoff dates, and preserved rights to the rows they affect. Separate existing compensation and benefits from additional severance: ADEA waiver consideration must exceed existing entitlements. The regulation separately addresses understandable wording, naming the ADEA, written counsel advice, and exclusion of post-execution claims. These are review dependencies, not ordinary payroll tasks. See 29 C.F.R. § 1625.22(b)–(d). (eeoc.gov)

Record: action, obligor, recipient, and internal owner; identify conditions expressly rather than recasting them as independent promises.

3. Attach complete source references

Capture enough wording to substantiate the action, timing, and exceptions. Cite a controlling defined term where it appears, not merely its use in the payment paragraph. For incorporated duties, reference both the separation agreement and the underlying document.

An SEC-filed Arrow Electronics agreement illustrates the distinction: paragraph 14 conditions benefits on execution and delivery of a release and its becoming effective and irrevocable, subject to paragraph 11. Extracting paragraph 14 alone would omit that timing dependency. This is negotiated wording, not evidence of a universal rule. (sec.gov)

Separate extraction confidence from legal readiness. Legible wording may still require interpretation; an incomplete scan may prevent reliable extraction regardless of apparent simplicity.

Record: operative excerpt, necessary cross-references, and any missing or unreadable source material.

4. Build trigger and payment dependencies

Trace execution, delivery, release effectiveness, compliance conditions, and timing qualifications for each payment. Distinguish entitlement conditions from provisions fixing payment dates. Capture withholding, offsets, forfeiture, cure, and tax-timing references without treating their presence as proof of validity.

For ordinary ADEA waivers, the regulation provides at least 21 days for individual consideration, 45 days for covered group programs, and at least seven days after execution to revoke. Effectiveness awaits expiration of revocation; settlements of filed charges or court actions have separate provisions. Covered group programs also require specified disclosures. Counsel should confirm the applicable framework before dates become operational. See § 1625.22(e)–(g). (eeoc.gov)

Record: exact contractual formula, source of each trigger fact, linked condition rows, and any calculated date marked provisional until approved. Do not hold unrelated earned-pay instructions merely because severance readiness remains unresolved.

5. Preserve qualifications and protected-activity exceptions

Read confidentiality, cooperation, non-disparagement, notice, and repayment wording with their exceptions. Avoid an instruction such as “notify the employer before any agency contact” unless counsel has assessed the actual text and applicable protections.

The EEOC explains that an agreement cannot prevent filing a charge or participating in its proceedings. Preserving agency access is distinct from preserving every individual monetary remedy. (eeoc.gov) The SEC explains that Rule 21F-17(a) prohibits impeding direct communications about possible securities-law violations; conflicting notification requirements can create problems even where another clause permits reporting. (sec.gov)

Do not silently repair conflicting language in the register. Preserve the source and obtain legal direction before communicating a restriction.

Record: applicable exceptions alongside the action or condition, with conflicts assigned to counsel and affected instructions held pending resolution.

6. Assign verification and completion evidence

Identify who verifies each trigger and what evidence closes the row. HR may verify delivery; legal resolves effectiveness questions; payroll executes approved instructions. A notation that the release is “done” is insufficient if it conceals missing delivery or revocation checks.

Specify appropriate evidence: payment confirmation, property receipt, approved expense record, or documented notice delivery. Distinguish a payment instruction from completed payment. Keep continuing cooperation duties open for their contractual duration, with a process for checking each request’s scope and reimbursement terms.

Record: verification owner, evidence reference, status, and next decision. “Awaiting proof” should not mean “confirmed nonperformance.”

7. Reconcile and approve the register

Check in both directions. Read the agreement again to account for every operative promise, including provisions deliberately excluded as historical statements. Then test each row against its cited source: could an operator follow it without omitting a condition or imposing an extra one?

Approve instructions row by row. Escalate approaching deadlines even when evidence is incomplete; an administrative hold should not hide a potentially due obligation. Preserve earlier sources and completion records when an amendment changes performance.

Record: reviewer, review date, approved instruction, and each unresolved issue’s owner and required resolution. Retain the distinction between approved extraction and authorization to perform.

Worked example

Fictional scenario: Cedar Vale Instruments, Inc. and Morgan Hale, age 54, sign an individual separation agreement, CVI-SA-vFinal. Section 2 promises $48,000 in additional severance within ten business days after the defined Effective Date and requires delivery of Exhibit A’s executed release. Section 1 defines that date by reference to expiration of Exhibit A’s seven-day revocation period without revocation. The file lacks release-delivery evidence and a completed revocation-record check.

Morgan’s separation date is September 30, 2026. Section 5 requires delivery of a laptop and badge to IT within five calendar days afterward. IT acknowledges only the laptop. Section 8 promises reimbursement of reasonable, documented cooperation expenses under Schedule 2, which is missing. These invented terms illustrate extraction, not recommended drafting or a complete waiver analysis.

The register prevents signature of the main agreement from becoming an unsupported payment trigger. It also prevents IT from closing a two-item return obligation on one receipt. The missing schedule does not erase the reimbursement promise, but it prevents a complete process instruction. These are three representative entries, not the entire register; Morgan’s underlying cooperation duty would require its own row.

Common mistakes

• Using signature as every trigger. Separate execution, delivery, separation, effectiveness, and each installment’s timing rule.
• Combining earned pay with severance. Maintain distinct rows and instructions so unresolved release conditions do not automatically control existing entitlements.
• Citing only the amount paragraph. Add definitions, release exhibits, incorporated terms, and timing qualifications.
• Dropping exceptions from restrictions. Carry relevant carve-outs into instructions and escalate conflicting language instead of rewriting it silently.
• Treating missing proof as breach. Assign evidence retrieval and distinguish uncertainty from confirmed nonperformance before considering contractual consequences.

Final quality check

• Every active row identifies the controlling document, version, section, and page.
• Excerpts, definitions, and cross-references match the retained source.
• Each action has an obligor, recipient, and internal owner.
• Payment conditions remain separate from earned-pay and existing-benefit instructions.
• Calculated dates use verified trigger facts and approved interpretations.
• Restrictions preserve exceptions; conflicting instructions remain escalated.
• Completion statuses link evidence, and every open issue has an owner and resolution requirement.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review workflow supports party-specific instructions in Word and findings that quote clauses, locate text, rank severity, and identify missing language as not present. Tabular review supports review across documents; the obligations register remains your work product. Lawyers retain responsibility for interpreting conditions, verifying evidence, and authorizing instructions. To discuss this separation-agreement workflow, book a demo.

Frequently asked questions

Should employee duties appear in an employer’s register?

Yes. Property return and cooperation require employer coordination. Identify the employee as obligor and the employer’s verification owner separately. Do not assume every employee duty conditions severance; establish that link from the controlling wording and legal review.

Can we calculate effectiveness immediately after signature?

Enter only a provisional date until the applicable terms, release execution, delivery facts, and revocation records are verified. Preserve the formula and assumptions beside it. An unexplained calendar entry should not become payment authorization.

What if the agreement changes after delivery?

Retain both versions and delivery history. For ordinary ADEA waivers, material changes restart consideration unless the parties agree otherwise; nonmaterial changes do not restart it. Refer the classification and any agreement about restarting to counsel rather than reusing the original clock mechanically. See § 1625.22(e)(4). (eeoc.gov)

Does a complete register establish enforceability?

No. It documents extraction and verification. The EEOC describes differing approaches to whether certain discrimination waivers are knowing and voluntary, including circumstances outside the document. A populated table cannot establish those circumstances or replace controlling-law analysis. (eeoc.gov)

Sources

• EEOC: 29 C.F.R. § 1625.22, ADEA waiver requirements and timing. (eeoc.gov)
• EEOC: Understanding Waivers of Discrimination Claims in Employee Severance Agreements. (eeoc.gov)
• SEC: Whistleblower Protections, including Rule 21F-17(a). (sec.gov)
• Arrow Electronics: Separation and Release Agreement, Exhibit 10.1; negotiated wording only. (sec.gov)

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.