How to review post-employment obligations for Employment Agreements

Review post-employment obligations by assembling the operative employment agreement package, identifying each surviving duty, and testing its trigger, duration, scope, exceptions, and implementation. For the employer, the deliverable is a source-linked checklist separating verified contractual wording from missing evidence and unresolved legal questions. It should identify targeted amendments, departure instructions, and decisions requiring employment counsel—not simply list restrictive covenants. Review confidentiality, competition, solicitation, invention-assignment assistance, property return, and cooperation alongside release, severance, or equity provisions that affect those duties.

When to use this workflow

Use this workflow when employer-side counsel reviews proposed employment terms, updates an employee’s agreement, prepares for a departure, or evaluates an acquired workforce. The question is which surviving obligations the employer can responsibly describe, negotiate, or implement from the available documents.

This guide uses a US practice orientation and an October 13, 2026 research cutoff. It is not a fifty-state enforceability survey. Identify actual work locations, anticipated moves, governing-law wording, and the employee’s role before assessing jurisdiction-sensitive restrictions. Keep contractual text, factual assumptions, and legal conclusions separate.

Focus on surviving duties and their dependencies. Compensation belongs here when it conditions severance on compliance, changes a post-termination payment, or incorporates a relevant document—not merely because it appears in the agreement. Enforcement litigation and comprehensive wage, benefits, tax, and intellectual-property analysis are outside this review.

What you need

Collect the signed employment agreement, amendments, restrictive-covenant exhibits, confidentiality and invention-assignment agreements, side letters, and any proposed separation agreement. Obtain incorporated policies, equity awards, plans, and release forms where they affect surviving duties or payments.

Also request:

• The employing entity, employee’s role, work locations, and relevant access to customers, personnel, technology, and confidential information.
• Departure facts, if known: termination category, notice date, proposed last day, and any disputed trigger.
• An inventory of employer property, systems access, personal-device use, and business records requiring return or preservation.
• The employer’s dated negotiation checklist, acceptable fallbacks, approval owners, and operational constraints.

Assign each source a document ID and version. A missing exhibit is missing evidence, not proof that no obligation exists. Record whether an incorporated policy was merely referenced or also shown to have been provided.

Use the template

Use the Employment Agreements — Post-employment checklist below. You can copy this table into your working document or spreadsheet. Create one row per distinct duty, exception, or material dependency; link related rows by ID.

In Source / excerpt, include the document ID, version, section, page, and a short exact extract. Parties / scope identifies the obligor, beneficiary, covered activity, and relevant customer, personnel, information, or geographic boundary.

Trigger / duration records the contractual event and period, not merely an end date. Put incorporated documents, protected-disclosure language, payment conditions, and qualifications in Exceptions / dependencies. Evidence status distinguishes verified text, factual assumptions, wording not found in reviewed documents, and documents not supplied.

Risk / decision explains drafting ambiguity, operational difficulty, financial exposure, or a legal question. Action / owner records the correction, responsible person, due date where appropriate, and approval status. Extraction alone does not resolve enforceability.

Step by step

1. Establish the operative document chain

Read amendments against the provisions they replace and identify unchanged terms. Check signatures, execution and effective dates, attachments, and incorporation references. Preserve the signed package separately from the review draft.

The Cyngn employment amendment replaces specified provisions while preserving other terms of an earlier agreement. It illustrates why an amendment alone may not supply the operative contract; it is not evidence of standard drafting or enforceability. (sec.gov)

Record document precedence where the text addresses it; otherwise flag conflicts. Enter a dependency row for each missing source with a retrieval owner. Do not combine provisions from inconsistent versions into a supposedly complete obligation.

2. Extract duties and identify who benefits

Read definitions, termination provisions, remedies, and survival language, not just the restrictive-covenant section. Extract confidentiality, customer and employee solicitation, competition, invention-assignment assistance, property return, deletion, certification, and cooperation separately.

Identify each obligor and beneficiary. The employing entity, parent, affiliates, and successors may receive different protections. Capture that wording rather than normalizing every beneficiary to “company.”

Separate a present assignment from a later duty to execute documents. Likewise, returning equipment, deleting copies, and certifying completion require different verification. For cooperation, distinguish assistance with intellectual-property documentation from assistance in investigations or disputes. Record each duty’s source, scope, and material defined terms in its own row.

3. Resolve triggers, periods, and survival

Identify whether each duty begins at notice, termination, payment, request, or another defined event. Check whether termination categories change the consequences. Read survival language alongside the individual clause rather than assuming a uniform duration.

For a live departure, calculate dates only after confirming triggering facts and counting language. Record the formula and assumptions beside the proposed date. An unresolved last day, receipt event, or calendar-versus-business-day question must remain visible.

For request-based cooperation, capture notice, availability, expense reimbursement, and duration limits. For property return, identify items, recipient, and delivery method. Record conflicting triggers as assigned clarification issues, not settled calendar entries. Do not infer perpetual duties merely because a clause lacks an express end date.

4. Review confidentiality exceptions and notice

Examine the information definition, exclusions, permitted uses, protected-disclosure language, and policy references. Check whether proposed instructions contradict exceptions—for example, by requiring employer approval before every disclosure.

18 U.S.C. § 1833(b) protects qualifying confidential disclosures to government officials or attorneys solely to report or investigate suspected illegality, and qualifying sealed filings. Its conditions matter; it does not authorize otherwise unlawful access. (govinfo.gov)

For employee agreements governing trade secrets or other confidential information entered into or updated after May 11, 2016, § 1833(b)(3) requires immunity notice. A cross-reference to a qualifying reporting-policy document provided to the employee can satisfy that requirement. Noncompliance bars specified DTSA exemplary damages and attorney fees against the employee who lacked notice; it does not itself invalidate the agreement. The statutory employee definition includes individual contractors and consultants. (govinfo.gov)

Record notice wording, policy references, delivery evidence, and remediation questions. Assign other protected-reporting issues separately; DTSA compliance is not a comprehensive confidentiality-law assessment.

5. Assess competition and solicitation restrictions separately

Break each restriction into activity, covered relationships, geography if any, duration, and exceptions. Compare wording with the employee’s role and access. Customer coverage may turn on contact, knowledge, a lookback period, or broader definitions. Employee restrictions may distinguish solicitation from hiring; preserve that difference.

The FTC’s Noncompete Rule status page states that the rule is not in effect and is unenforceable. That does not establish enforceability of any particular covenant. Do not treat the page’s reproduced rule text as operative compliance duties. (ftc.gov)

Record locations and facts for jurisdiction-specific review, including whether additional execution or notice questions need investigation. Separate business justification from legal assessment. The checklist should identify retained wording, proposed narrowing, or an approval-required issue—not an unsupported “valid” label.

6. Connect duties to payments and implementation

Trace references linking surviving duties to severance, equity treatment, release execution, repayment, or other consequences. Keep the duty separate from the asserted consequence of breach. Confirm the relevant plan or award is available before summarizing it; record notice, cure, and decision-maker provisions where present.

Paragraph 9 of the Verizon executive agreement conditions specified succession payments on a defined event and execution of a release. This illustrates a document dependency, not a general payment rule or a breach-forfeiture conclusion. (sec.gov)

Test implementation with HR, IT, and the business. Can property be returned without destroying records? Can cooperation occur within the clause’s limits? Record instructions, unresolved payment consequences, and owners. Route withholding, repayment, or forfeiture decisions for separate legal review rather than presenting contractual wording as dispositive.

7. Record disposition and verify proposed changes

Compare findings with the employer’s dated, jurisdiction-specific negotiation checklist. Classify changes as preferred, permitted fallback, or approval-required, with a business reason. This checklist is the team’s work product, not a substitute for legal analysis.

Prepare targeted redlines and matching departure instructions. Confirm that changes to definitions, exceptions, duration, or beneficiaries carry through related provisions. For executed agreements, distinguish documented obligations from proposed amendments; do not describe a proposed correction as already operative.

Finish every row with an accepted disposition or an assigned open issue. Recheck citations and relevant package changes against the approved draft. The deliverable should explain the employer’s proposed action, supporting evidence, and unresolved dependencies.

Worked example

Fictional scenario: Northbank Sensor Systems employs Elena Ruiz as a sales engineering director. Counsel has signed agreement EA-01, version 1, and amendment AM-02, version 1. AM-02 changes compensation only and expressly preserves other terms. Ruiz proposes leaving November 20, 2026, but HR has not confirmed the contractual termination date. She worked in two US states; jurisdictional review remains open. Referenced reporting policy RP-4 and an equity award are absent.

The fictional clauses below supply the three representative entries. No future-employer or customer-outreach facts have been provided.

The review changes Northbank’s proposed departure communication. It should not expand “customers contacted” to every customer or announce an end date before confirming the trigger. Missing RP-4 prevents a supported notice assessment; it does not prove notice was never provided.

Counsel also separates return from deletion so IT can inventory records and obtain preservation instructions first. The missing equity award receives its own dependency row outside these representative entries. Neither forfeiture nor continued vesting can be inferred from its absence.

Common mistakes

• Reading only the covenant section. Check definitions, survival, termination, and incorporated documents before stating a duty.
• Equating missing documents with absent wording. Distinguish an unavailable policy from language not found in a reviewed source.
• Treating duration as the entire restriction. Capture covered activities, relationships, exclusions, and beneficiary entities.
• Equating FTC rule status with enforceability. Obtain a jurisdiction-specific assessment of the actual covenant.
• Turning disputed consequences into instructions. Review withholding, repayment, forfeiture, and deletion questions before issuing departure communications.

Final quality check

• Every duty has an operative document ID, version, section, and page.
• Defined terms and beneficiary entities match the source.
• Triggers, duration formulas, counting questions, and factual assumptions are visible.
• Confidentiality exceptions and notice dependencies are resolved or assigned.
• Jurisdiction-sensitive restrictions have a documented disposition or responsible counsel owner.
• Payment, release, and equity dependencies are verified or expressly missing.
• Redlines and operational instructions agree, with unresolved issues assigned rather than marked complete.

Complete the workflow with DecoverAI

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

Frequently asked questions

Should each surviving obligation have its own row?

Yes, where triggers, scope, evidence, or implementation differ. Link related rows—for example, confidentiality, deletion, and a severance-compliance condition—rather than combining them into an opaque summary.

Is the governing-law clause the only jurisdiction input?

No. Record work locations, relevant changes, and role facts. Counsel should determine what additional jurisdictional analysis is needed rather than treating the clause as the complete answer.

What if an incorporated policy cannot be located?

Mark it as not supplied, identify dependent conclusions, and assign retrieval. Do not verify its content or delivery by inference. Escalate material gaps before approving dependent instructions.

Does a confidentiality-notice defect void the agreement?

Section 1833(b)(3)(C) limits specified DTSA exemplary damages and attorney-fee remedies for notice noncompliance; it does not declare the entire agreement invalid. Record that narrower issue and seek a remediation decision. (govinfo.gov)

Sources

• 18 U.S.C. § 1833 — trade-secret disclosure immunity and notice
• FTC — Noncompete Rule status
• Verizon — Schulman employment agreement, Exhibit 10j
• Cyngn — Tal employment amendment, Exhibit 10.33

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.