Product
Litigation
- Early Case Assessment
- Evidence Analysis
- Web Search
- Document Review
- Production Setup
- Connectors (Upcoming)
- Legal Research (Upcoming)
Transactional
- Contract Review
- Contract Intelligence
- Word Add-In
- Web Search (Upcoming)
- Connectors (Upcoming)
- Legal Research (Upcoming)
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Extract obligations by reading the executed employment package as a connected set, then recording each actor, required action, trigger, timing formula, condition, and completion evidence against a precise source reference. For company counsel, the deliverable is an obligations register that HR, payroll, finance, and legal can administer without treating contingent compensation as immediately payable. Preserve contractual wording beside normalized instructions, separate legal questions from operational tasks, and calculate dates only after verifying triggering facts and applicable notice provisions.
When to use this workflow
Use this workflow when onboarding an executive, integrating an acquired leadership team, administering retention arrangements, or preparing for renewal or departure. It translates negotiated terms into assigned responsibilities; it does not replace entitlement analysis or amend the agreement.
The scope is US executive employment arrangements. Selected federal tax and release requirements are addressed below. State wage, restrictive-covenant, choice-of-law, and enforcement questions require separate research tied to the executive’s location and circumstances. Contract rights depend on the operative language, governing law, and facts. The register should expose those dependencies rather than resolve them by assumption.
What you need
Collect the signed agreement, amendments, side letters, compensation plans, equity awards, restrictive-covenant documents, release form, and relevant approvals. Include incorporated documents maintained by other teams; identify unavailable materials explicitly.
Obtain evidence relevant to triggers: employment dates, notice correspondence, delivery receipts, compensation decisions, milestone certifications, and payment records. Identify the entities responsible for employment, payroll, benefits, and equity administration.
Assign document IDs and preserve stable source copies. Where pagination is unavailable, use the section, paragraph, and a distinctive text anchor. Identify contacts in HR, payroll, finance, equity administration, and legal so unresolved rows have accountable owners.
Use the template
Use the Executive Employment Agreements — Obligations register below. You can copy this table into your working document or spreadsheet. Keep one independently actionable obligation per row; split payment, notice, cooperation, and repayment duties even when they share a paragraph.
| ID / scenario | Source / exact text | Actor → recipient | Action / value | Trigger / conditions | Timing / delivery | Owner / evidence | Status / questions |
|---|---|---|---|---|---|---|---|
The source cell holds the document ID, version, section, page, and short exact excerpt. Add linked definitions and cross-references in that cell or an identified source note. An excerpt is an anchor, not a substitute for the complete provision.
The action cell contains the normalized instruction, units, and any discretion. Separate conditions from timing: a milestone may establish eligibility while continued service remains necessary for payment. Preserve deadlines as formulas until inputs are verified.
Use the final columns for the internal owner, expected evidence, confidence, and assigned questions. Distinguish “not present in reviewed documents,” “ambiguous,” and “not applicable.” Also distinguish extraction status from performance status: accurately extracted does not mean payable or completed.
Step by step
1. Establish the controlling document set
Inventory execution dates, amendments, incorporation language, and express priority provisions. Do not assume the latest employment agreement replaces every equity award or plan term. Compare the executed package with the approved draft to identify changed duties, omitted exhibits, or handwritten changes.
Where a release or award is missing, create a dependency row rather than reconstructing its terms from another executive’s documents.
Record: document/version identifiers, missing materials, collection owners, and the obligations whose interpretation remains provisional. Mark collection tasks as internal follow-up, not contractual duties owed by the executive.
2. Extract duties by actor and compensation component
Review company and executive duties: salary, bonus decisions, retention payments, reimbursements, benefits, notices, confidentiality, cooperation, property return, and repayment. Separate the obligation to make a decision from any resulting payment duty.
Do not convert a target bonus into guaranteed compensation. The SEC-filed Virgin Galactic agreement, for example, distinguishes a target opportunity from the performance-based amount determined by the Board and includes a continued-employment condition. It illustrates negotiated wording, not a market standard (§ 2(b)(ii)).
Record: actor, recipient, action, amount or formula, discretion, and supporting language. Describe the reviewed document set before concluding that a provision was not found.
3. Connect triggers, definitions, and exceptions
Trace capitalized terms to their definitions. Where Good Reason requires notice, an opportunity to cure, and timely resignation, extract those requirements separately. Keep ordinary termination, transaction-related termination, death, and disability scenarios distinct.
Map incentives through eligibility, certification, vesting, settlement, forfeiture, and recovery. Preserve events that end repayment duties. The same SEC-filed agreement illustrates milestone-dependent retention compensation and repayment language that ceases to apply upon a change in control; the filing does not establish whether those events occurred (§ 2(b)(iii)).
Record: linked definitions, exceptions, scenario labels, and dependencies. Assign conflicts to counsel rather than selecting the easiest reading.
4. Preserve timing formulas before calculating dates
Identify the precise timing basis: execution, receipt, termination, separation from service, certification, or release effectiveness. Check calendar versus business days, delivery methods, addresses, and receipt rules. Separate nonrenewal, cure, resignation, release, revocation, and payment events.
Calculate dates only after documenting the trigger evidence and counting assumptions. Assign a calendar owner and backup; these are human responsibilities.
For covered deferred compensation, § 1.409A-3 identifies permissible payment events and generally requires objectively determinable, nondiscretionary timing. Its specified-employee rule generally delays covered separation-triggered payments for six months, or until earlier death. It is not a blanket delay for all executive severance: coverage, status, and exceptions require analysis (26 CFR § 1.409A-3(a), (b), and (i)(2)).
Record: contractual formula, verified inputs, calculated date, assumptions, and any unresolved tax dependency. Do not silently equate contractual termination with a tax-defined separation from service.
5. Separate legal review requirements from contractual tasks
Keep the contractual task intact while identifying legal questions that may affect performance. Release-conditioned severance needs both contractual mechanics and applicable waiver review.
For waivers governed by § 626(f)(1), selected requirements include specific reference to ADEA claims, additional consideration, written advice to consult counsel, and exclusion of future claims. Consideration periods are at least 21 days for individual waivers or 45 days for specified group programs; revocation must remain available for at least seven days after execution. Covered group programs require disclosures. These are not universal contract deadlines or a complete release checklist; § 626(f)(2) separately addresses specified settlements (ADEA § 626(f)).
Transaction-related compensation may require package-wide § 280G review. The threshold generally compares aggregate present value of change-contingent compensation with three times the individual’s base amount, subject to applicable requirements and exceptions. Excess parachute payments involve a separate calculation—not merely subtraction of three times base compensation (26 CFR § 1.280G-1, Q/A-1–3 and Q/A-30).
Record: question, required facts, reviewing lawyer, and decision status beside the affected obligation.
6. Assign performance and completion evidence
Name the person who can perform each duty, not just the extracting lawyer. Payroll may execute payment while HR verifies service and finance confirms milestone approval. Preserve the contractual recipient, especially for notices directed to a particular officer or address.
Specify proportionate evidence: delivery receipt, effective release, approval record, payment confirmation, or property-return record. An acknowledgment does not establish continuing compliance with confidentiality or cooperation duties.
Record: primary owner, backup where needed, prerequisite evidence, and completion record. Keep evidence of performance separate from the clause citation establishing the duty.
7. Reconcile and approve the register
Have a reviewer trace material rows to operative sources and surrounding language. Then reverse the check: inspect compensation, termination, notice, covenant, and tax sections for omitted obligations.
Test representative departures. Are release execution and effectiveness distinct? Do repayment exceptions survive normalization? Are benefits duplicated across the agreement and another plan? Recheck affected rows after amendments or verified factual changes.
Record: reviewer, review date, confidence, unresolved issues, and handoff status. An extraction can be verified while performance remains blocked pending facts or legal analysis.
Worked example
Fictional scenario. North Quay Robotics, Inc. reviews executive Mira Vale’s package before a possible departure. All parties, documents, amounts, and provisions below are invented.
Executed agreement EEA-01, § 3(c), p. 4, provides a $90,000 retention installment within 30 calendar days after written prototype acceptance, subject to employment on payment day. Section 3(d) requires repayment of the net installment actually received within 60 calendar days after voluntary departure before the second anniversary of payment, except a departure meeting the agreement’s Good Reason definition. Section 7(b), p. 8, conditions six months’ base-salary severance on a qualifying termination and an effective Exhibit B release; § 7(d), p. 9, supplies payment timing.
The team lacks acceptance evidence and Exhibit B. HR has proposed a departure scenario, not confirmed a termination. The three representative rows are not the complete register.
| ID / scenario | Source / exact text | Actor → recipient | Action / value | Trigger / conditions | Timing / delivery | Owner / evidence | Status / questions |
|---|---|---|---|---|---|---|---|
| R1 / retention | EEA-01, executed, § 3(c), p. 4: “within 30 calendar days after written acceptance” | Company → Vale | Pay $90,000 | Written prototype acceptance; employed on payment day | Acceptance + 30 calendar days; method unstated | Finance/payroll; acceptance, service and payment records | Obtain acceptance evidence; no date calculated |
| R2 / repayment | EEA-01, executed, § 3(d), p. 4: “net installment actually received”; link Good Reason definition | Vale → company | Repay net amount received | Voluntary departure before payment’s second anniversary; Good Reason excluded | Departure + 60 calendar days; method unstated | HR/legal; departure evidence and payment ledger | Verify payment, departure classification and exception before demand |
| R3 / severance | EEA-01, executed, § 7(b), p. 8: “subject to an effective release in Exhibit B”; § 7(d), p. 9 | Company → Vale | Pay six months’ base salary | Qualifying termination; effective release | Timing governed by § 7(d); not yet normalized | Legal/payroll; release and payment evidence | Obtain Exhibit B and extract § 7(d); not payment-ready |
R1 prevents scheduling from an unverified milestone date. R2 prevents a demand based merely on proposed resignation: counsel must verify payment and classify the departure. R3 identifies two distinct problems—a missing exhibit and incomplete extraction of an available timing clause. Obtaining Exhibit B alone will not complete that row.
Common mistakes
- Flattening compensation into one row. Separate bonus determination, retention eligibility, equity settlement, and payment because their sources and triggers differ.
- Treating defined terms as ordinary language. Link Cause, Good Reason, and change in control to their actual definitions and exceptions.
- Recording an unsupported date. Preserve the formula, trigger evidence, notice rules, and counting assumptions.
- Citing a page without document identity. Include version and section; draft pagination may differ from the executed agreement.
- Closing a conditional row prematurely. Distinguish extraction verified, conditions satisfied, authorized for performance, and completed with evidence.
Final quality check
- Each material obligation traces to the operative document and clause.
- Incorporated plans, awards, amendments, and exhibits are included or expressly missing.
- Targets, discretionary decisions, and fixed commitments remain distinct.
- Definitions, exceptions, and termination scenarios survive normalization.
- Calculated dates are reproducible from verified facts.
- Legal questions have named reviewers and recorded outcomes or restrictions.
- Operational rows have owners and appropriate completion evidence.
- Open issues are resolved or explicitly assigned before handoff.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review supports deal-specific instructions, clause quotations, text locations, severity-ranked findings, and identification of missing language as not present. Tabular review supports work across documents; due diligence classification can organize the package for human review. Lawyers and business owners retain responsibility for the register, date verification, and performance decisions. To discuss this workflow, book a demo.
Frequently asked questions
Should the register include executive obligations?
Yes. Include notice, cooperation, confidentiality, property return, and repayment. Assign a company owner to verify performance without changing who owes the duty.
What if an incorporated equity award is unavailable?
Record the reference and missing award as a dependency. Do not infer vesting, acceleration, or settlement terms unless the available operative documents actually supply them.
Can severance appear as one amount?
A summary can show an amount, but retain supporting rows for salary, bonus measures, benefits, equity, offsets, release conditions, and timing. Otherwise, the summary conceals entitlement dependencies.
How should ongoing duties be tracked?
Record duration, triggering requests, exceptions, and evidence for discrete acts. A cooperation request can be completed while the broader duty remains active; confidentiality should not be closed merely because employment ends.
Sources
- 26 CFR § 1.409A-3: permissible payments.
- 26 CFR § 1.280G-1: golden parachute payments.
- EEOC: ADEA statutory text, § 626(f).
- SEC-filed Virgin Galactic–Colglazier employment 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.
