How to prepare a clause-level risk assessment for Separation Agreements

Prepare an employer-side clause-level risk assessment by connecting each operative provision to the employee’s circumstances, applicable law, related documents, and performance conditions. Record legal and operational risk separately, identify supporting evidence, and propose a revision or a specific question for counsel. The resulting clause risk register should distinguish confirmed defects from missing information and commercial choices, assign responsibility, and state approval conditions. It should explain whether the separation agreement achieves the employer’s objectives—not merely whether its wording resembles an approved form.

When to use this workflow

Use this workflow when employment counsel or an in-house team receives a separation draft, evaluates employee revisions, or reviews a form for a departure program. Focus on provisions affecting release scope, consideration, protected reporting, payment conditions, and surviving obligations.

This is a US employer-side workflow addressing selected federal waiver and reporting issues. Separately assign jurisdiction-specific research on wages, releases, confidentiality, restrictive covenants, and notices, plus NLRA coverage, benefit plans, and tax treatment where relevant. Contract rights depend on wording, governing law, facts, and deal context; the register is not an enforceability opinion.

What you need

Assemble the following before rating clauses:

• Departure facts: employing entity, work locations, age, role, termination circumstances, individual or potential group-program status, and pending claims.
• Agreement package: controlling draft, earlier offers, exhibits, release forms, incorporated employment agreements, restrictive covenants, equity awards, and benefit plans.
• Economic evidence: payroll records, existing benefit entitlements, proposed incremental consideration, expenses, and payment instructions.
• Review instructions: employer objectives, approved negotiating positions, approval authority, and jurisdiction questions.
• Timing evidence: delivery records, revisions, proposed execution dates, and any signature or revocation records.

The employer’s negotiation playbook means its own checklist and instructions. Confirm that its positions fit this departure rather than copying another employee’s negotiated exceptions.

Use the template

Use the Separation Agreements — Clause risk register below. Copy this table into your working document or spreadsheet. Create one row per distinct issue, including multiple rows for one clause when the required decisions differ.

In Source / text, include document ID, version, section, page, and enough operative wording to verify the finding. Use “not present” for absent language in reviewed documents and “not supplied” for an unavailable document. Do not treat those findings as interchangeable.

In Context / authority, capture jurisdiction, assumptions, cross-references, and supporting authority. Link lengthy analysis through a stable issue ID rather than overloading the cell.

Define ratings locally: high means a central employer objective or material performance is threatened; medium means a consequential ambiguity or dependency; low means a limited drafting or implementation issue. Rate legal and operational risk independently. Confidence describes evidentiary support, not severity: missing program facts can justify a serious provisional finding without establishing a legal defect.

Step by step

1. Establish the review package and legal path

Assign document IDs and identify the controlling draft. Index the agreement, exhibits, incorporated documents, and prior obligations. Confirm the departure’s relationship to other exits; headcount alone does not establish the applicable waiver framework.

Determine whether an Age Discrimination in Employment Act (ADEA) waiver is relevant. Distinguish an ordinary separation release from settlement of an already-filed age-discrimination charge or court action, which has separate provisions under 29 C.F.R. § 1625.22(g). (eeoc.gov)

Record: missing documents, unresolved classification questions, owners, and affected clauses. Identify approval-blocking gaps before substantive redlining.

2. Separate existing entitlements from new consideration

Reconcile each economic promise with payroll and plan records. Distinguish earned compensation and preserved benefits from proposed severance or insurance support. A heading such as “separation benefits” does not establish that every component is new consideration.

An ADEA waiver requires consideration beyond existing entitlements. It also requires understandable written language, identification of the ADEA, written advice to consult counsel, and exclusion of claims arising after execution. These are minimum safeguards, not a complete voluntariness determination. See § 1625.22(b)–(d). (eeoc.gov)

Record: each disputed classification, supporting record, proposed correction, and payroll or benefits owner. Keep any existing-entitlement payment question separate from release-conditioned severance.

3. Map the release and preserved rights

Identify releasing persons, released parties, claim categories, cutoff dates, unknown-claim wording, and exceptions. Cross-check agreement-enforcement rights, preserved benefits, and intended indemnification protections against integration and survival provisions.

The EEOC explains that an agreement cannot prevent filing a charge or testifying, assisting, or participating in an EEOC proceeding. Preserving agency access does not automatically preserve every individual monetary remedy. Its guidance also describes differing judicial approaches to whether Title VII, ADA, and Equal Pay Act waivers are knowing and voluntary. See the EEOC’s severance-waiver guidance. (eeoc.gov)

Record: each scope conflict, affected exception, proposed revision, and any controlling-law research needed. Do not infer voluntariness from wording alone.

4. Test timing and group-program dependencies

For ordinary ADEA waivers, check at least 21 days for individual consideration or 45 days for a covered group program, plus at least seven days after execution to revoke. Effectiveness awaits revocation expiry. Material final-offer changes restart consideration unless the parties agree otherwise. Covered programs require specified eligibility, timing, age, and job-title disclosures. See § 1625.22(e)–(f). (eeoc.gov)

Review delivery and revision history. Ask counsel to confirm program status, decisional unit, disclosure completeness, and revision effects before publishing dates.

Record: timing assumptions, evidence, missing disclosures, and mismatches among signature, effectiveness, and payment. Distinguish a minimum consideration opportunity from a mandatory waiting period before signing.

5. Reconcile confidentiality, reporting, and cooperation

Read confidentiality, non-disparagement, cooperation, notice, property-return, repayment, and remedy provisions together. A favorable reporting exception may be undermined elsewhere.

The SEC explains that Rule 21F-17(a) prohibits impeding direct communications about possible securities-law violations. Its guidance identifies reporting permission paired with a notification requirement as a potential violation. This is not a general prohibition on confidentiality terms. See SEC Whistleblower Protections. (sec.gov)

Check advance approval, notification, award restrictions, and sanctions against the protected-activity language. Assign separate state-law and NLRA questions rather than assuming an SEC-focused exception resolves them.

Record: both conflicting provisions, the consequence, and the revision needed to reconcile them.

6. Trace payment conditions and surviving obligations

Follow each payment through execution, delivery, revocation expiry, effectiveness, and additional contractual conditions. Examine offsets, forfeiture, cure, withholding, and tax dependencies. Early payment is not automatically an ADEA violation; assess whether the employer would pay before obtaining the effective release it intended to require.

Reconcile incorporation, integration, and survival clauses. As a wording example, the Arrow Electronics filed agreement, paragraphs 3, 7, 11, and 14 separately addresses surviving agreements, accrued rights, tax timing, and release-conditioned benefits. It establishes neither enforceability nor a market standard. (sec.gov)

Record: inconsistent triggers, unavailable incorporated documents, unclear duties, and resolution owners. Keep the register focused on assessment rather than expanding it into payment administration.

7. Prioritize and verify resolutions

Classify actions as legal concerns, commercial preferences, factual corrections, or unresolved research questions. Explain why the employer should accept, revise, or escalate each provision. A high rating without a consequence and response is not decision-ready.

Test proposed edits against definitions, exceptions, cross-references, and exhibits. Preserve reasons for dismissing findings. Verify replacement wording in the controlling version rather than closing an issue on conceptual approval.

Record: disposition, approving authority, verified version, and remaining dependencies. Distinguish “wording resolved” from “facts outstanding,” and state whether either prevents approval.

Worked example

Fictional scenario: Cedar Vale Instruments, Inc. proposes an agreement for Mira Solen, a 56-year-old director working in Colorado. CV-SEP-v3 offers $48,000, including $9,000 described as earned salary and expenses. It allows 21 days for consideration, provides seven days to revoke, and requires the entire payment five days after signature without an effectiveness condition. HR mentions two related departures but supplies no program analysis.

Agency reporting is permitted, but cooperation language requires advance notice of every agency inquiry. A referenced equity plan is not supplied. All parties, documents, amounts, and provisions are fictional; Colorado law remains separately assigned for review.

The decision changes from routine approval to targeted resolution. CV-02 identifies premature employer performance, not an automatic prohibition on early payment. The timing and disclosure question remains conditional on program facts.

Neither the arithmetic remainder of $39,000 nor the draft’s labels establish incremental consideration. Payroll and benefit records must support that conclusion. The missing equity plan requires another open row; its absence supports an information-gap finding, not a vesting or forfeiture conclusion.

Common mistakes

• Reviewing headings rather than effects. Cite both provisions when a notice duty contradicts a reporting exception.
• Treating absent evidence as low risk. Assign the missing plan or program facts and identify the approval consequence.
• Combining earned pay with severance. Reconcile categories before attaching release conditions to payment.
• Applying one timing checklist universally. Confirm waiver type, program status, pending proceedings, and revision history.
• Closing issues on an approval email. Verify the agreed wording and exhibits in the controlling draft.

Final quality check

• Every finding identifies document, version, section, and page.
• Extracted wording matches the source, including exceptions.
• Authorities support the precise proposition and applicable context.
• Existing entitlements and incremental consideration are supported or flagged.
• Release, reporting, confidentiality, and cooperation provisions reconcile.
• Timing and payment findings distinguish legal requirements from employer preferences.
• Legal risk, operational risk, confidence, and consequence remain separate.
• Open issues have owners, dispositions, and stated approval effects.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. In its contract-review workflow, choose the employer as represented party in Word and provide deal-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. Lawyers can edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name and dismiss findings with reasons. Tabular review supports work across documents; counsel retains legal judgment and approval. To discuss this separation-review workflow, book a demo.

Frequently asked questions

Should every clause receive a risk row?

Check every operative clause, but reserve risk rows for decisions, corrections, and dependencies. Maintain a separate coverage list for reviewed provisions with no identified issue so silence does not suggest omission.

Can an overall score determine approval?

Not by itself. An average can obscure a reporting restriction or missing release prerequisite. State material approval conditions individually, even if a summary rating is useful for reporting.

How should employee revisions be assessed?

Compare them with the last reviewed version and test related clauses. Record whether each change creates a legal concern, commercial choice, or factual correction. Reassess applicable consideration timing when revisions may be material.

What if an incorporated plan is unavailable?

Identify affected clauses and request the controlling plan and award documents. Do not infer their terms. Counsel should determine whether approval must wait or the agreement can remove the unresolved dependency.

Sources

• EEOC: 29 C.F.R. § 1625.22—ADEA waivers
• EEOC: Understanding Waivers of Discrimination Claims
• SEC: Whistleblower Protections
• Arrow Electronics: Separation and Release Agreement, Exhibit 10.1

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.