How to compare provisions across a contract portfolio for Executive Employment Agreements

Compare executive employment agreements through a source-linked matrix that separates operative wording, normalized economics, eligibility conditions, and unresolved questions. Assemble each executive’s complete agreement package, define comparable termination and incentive scenarios, and extract provisions without erasing their differences. Verify material outliers against executed documents and the company’s approved position. The resulting deliverable is a comparison matrix and decision summary showing which differences affect company cost, discretion, administration, or legal review, with supporting evidence and an accountable owner for each material issue.

When to use this workflow

Company counsel, employment lawyers, and transaction teams can use this workflow before an acquisition, compensation committee review, executive hiring cycle, or agreement harmonization exercise. The trigger is a portfolio question: which executives have different protections or obligations, what explains those differences, and which warrant action?

Keep the assignment focused on comparing existing provisions. The matrix can support diligence and negotiations, but it is not a final severance calculation, release approval, or enforceability opinion.

This guide uses a US orientation and selected federal tax and age-discrimination waiver provisions. Assign state-specific wage, restrictive-covenant, choice-of-law, and enforcement questions for separate research based on work location, employer, governing language, and facts. Do not label provisions legally equivalent merely because their wording matches.

What you need

Collect an indexed package for each executive:

• Executed agreement, amendments, side letters, schedules, and relevant approval records.
• Bonus and retention arrangements, equity plans and awards, and separate severance or change-in-control plans.
• Restrictive-covenant documents, incorporated policies, and release forms.
• Employer entity, work location, role, agreement dates, and scenario-specific factual inputs.
• An identified company template version and the company’s own checklist of preferred terms, permitted exceptions, and approval authority.

Assign document IDs and preserve version relationships. Record missing documents immediately: an unavailable award agreement must not become a finding that equity protection is absent. Limit access to compensation and personal information under the team’s handling requirements.

Use the template

Use the Executive Employment Agreements — Contract comparison matrix below. You can copy this table into your working document or spreadsheet. Create one row per executive, provision, and scenario, using stable row IDs for follow-up requests and summaries.

Source / version identifies the document ID, execution or amendment date, and section/page citation. Clause evidence preserves operative wording or a precise excerpt, including relevant qualifications.

Normalized term states comparable units: salary months, bonus measure, benefits duration, or payment schedule. Conditions / links retains release requirements, defined terms, cure periods, offsets, and incorporated documents.

Distinguish verified, not located, missing source, ambiguous, and inapplicable in status / uncertainty; explain the basis. Action / owner records the consequence, proposed response, responsible role, and approval status. Cite dependent row IDs or spreadsheet cells when a formula relies on another entry. Keep legal uncertainty separate from arithmetic uncertainty.

Step by step

1. Define the comparison question and document boundary

Choose the decisions the matrix must support. Acquisition review may prioritize transaction benefits, retention repayment, and overlapping plans. Compensation review may prioritize incentive discretion, renewal terms, and severance differences by role.

Define scenarios before extraction: ordinary without-Cause termination, Good Reason resignation, transaction-related termination, death, and disability. Add incentive vesting or recovery scenarios where relevant. Not every executive needs every scenario; explain exclusions.

Distinguish executed documents from drafts and identify which amendments modify which provisions. Check priority language rather than assuming the newest document overrides everything.

Record: package completeness, scenario labels, operative-version basis, and unresolved priority questions in the relevant rows.

2. Set comparison rules before identifying differences

Identify the company template version or approved position serving as the baseline. If none exists, compare neutrally rather than calling the most frequent wording “standard.”

Establish a data dictionary. Bonus measures must distinguish target, actual, prior-year, and average awards. Severance multiples must identify their compensation base. Separate transaction-only benefits from benefits requiring a qualifying termination within a transaction window.

Define how reviewers will handle absent and ambiguous language. “Not located in reviewed documents” is different from an express exclusion and from a missing incorporated source.

Record: baseline reference, units, scenario definitions, and any justified departure from the comparison rules. Put shared assumptions in a clearly identified matrix note rather than repeating inconsistent versions across rows.

3. Extract operative provisions and their dependencies

Capture economic terms alongside Cause, Good Reason, disability, and change-in-control definitions. Include notice, cure, resignation, release, payment, and offset provisions affecting eligibility. Identical cash formulas may operate differently when these conditions differ.

For incentives, separate opportunity from entitlement. One SEC-filed employment agreement distinguishes a target annual bonus from performance-based Board discretion and continued-employment conditions. It illustrates a drafting distinction, not market practice (Virgin Galactic agreement, § 2(b)(ii)).

Follow cross-references to plans and awards. For renewal and nonrenewal provisions, preserve notice triggers and receipt rules. Do not resolve conflicts by selecting whichever provision appears more generous.

Record: clause evidence, defined-term dependencies, linked document IDs, and verification status. Flag missing sources rather than supplying inferred terms.

4. Normalize economics without erasing eligibility

Compare salary-only multiples separately from salary-plus-bonus multiples. Express benefits continuation in months while retaining cost-sharing, cessation, and eligibility conditions. Distinguish equity vesting acceleration from settlement timing and identify covered award types.

Label common factual assumptions. A modeled amount must remain beside—not replace—the contractual formula. Do not assume a Good Reason event solely because an executive objects to a business change.

Keep guaranteed compensation, discretionary opportunities, contingent retention payments, and repayment obligations in separate rows when their triggers differ. Link potentially overlapping employment-agreement and plan benefits for review.

Record: normalized formulas, assumptions, exclusions, and potential duplication. For each material deviation, state the company consequence: additional cost, reduced discretion, contingent recovery, or administrative complexity.

5. Flag payment timing and tax dependencies

Extract payment events and schedules independently from amounts. For covered deferred compensation, Treasury regulations identify permissible payment events and generally require objectively determinable, nondiscretionary timing. Determine coverage or exemption first; contractual labels alone do not resolve regulatory definitions (26 CFR § 1.409A-3(a)–(b)).

The specified-employee separation-payment rule generally delays covered payments until six months after separation or earlier death. It is not a blanket rule for every executive or severance payment; status and exceptions require analysis (§ 1.409A-3(i)(2)).

For transaction scenarios, identify compensation outside the employment agreement. The Section 280G threshold generally concerns aggregate present value of change-contingent compensation to a disqualified individual reaching at least three times the base amount. Corporate and individual status, valuation, and exceptions matter (26 CFR § 1.280G-1, Q/A-2 and Q/A-30).

That threshold is not the excess-payment calculation: excess generally subtracts the allocated base amount, not three times that amount (Q/A-3).

Record: timing differences, contractual tax treatment, missing inputs, and specialist owner—not unsupported compliance conclusions.

6. Compare release and administration mechanics

Read release conditions beside payment schedules. Identify who delivers the release, what starts each period, whether effectiveness is required, and how the wording addresses periods spanning calendar years. Preserve deadline formulas before calculating dates.

For waivers governed by ADEA § 626(f)(1), selected requirements include additional consideration, written advice to consult counsel, specific reference to ADEA claims, and no waiver of future claims. Consideration periods are at least 21 days individually or 45 days for specified group programs, with at least seven days to revoke; covered group programs also require disclosures. Check age and statutory coverage. These are not universal contract deadlines, and § 626(f)(2) separately addresses settlements of filed charges or actions (29 USC § 626(f)).

Record: contractual periods, release dependencies, unresolved factual questions, and the owner of timing reconciliation. Compare administrative burdens without turning this exercise into a full calendaring project.

7. Verify outliers and prepare the decision summary

Reopen the source for each material difference. Determine whether it reflects an intentional concession, amendment, extraction error, or unresolved inconsistency. Check approval records where available.

Separate financial significance, legal uncertainty, and administrative difficulty. A smaller benefit with unclear payment mechanics may warrant attention before a larger, clearly approved benefit.

Summarize decisions by executive and issue, linking to row IDs. Recommend retaining the difference, obtaining evidence, seeking specialist advice, or considering an amendment. Identifying an outlier does not itself change the agreement.

Record: verified deviation, practical consequence, recommendation, approval requirement, and accountable owner. Keep unresolved rows visible in the final summary.

Worked example

Fictional scenario: Northbridge Instruments, Inc. compares three executive packages before proposing a common severance approach. All parties, documents, amounts, and clauses below are invented. Counsel assumes $300,000 annual salary for each executive solely to isolate formula differences. No qualifying termination or transaction has been established.

The company prefers 12 months of salary for ordinary without-Cause termination, subject to an approved release mechanism. This is an internal preference, not a market benchmark.

Chen’s amount matches the working preference, but the missing release form prevents a complete administration comparison. Reed’s $900,000 is transaction-dependent; presenting it beside Chen’s ordinary severance as an equivalent entitlement would misstate the difference. Soto’s provision concerns potential company recovery, not additional executive compensation.

Counsel therefore separates the three categories in the decision summary. Equity remains unquantified. Potential repayment is not treated as an established receivable without evidence of payment and satisfaction of the recovery conditions. Neither missing source is replaced with an assumption.

Common mistakes

• Comparing multiples without bases. Replace “2×” with the full formula and identify the bonus measure.
• Treating targets as guaranteed compensation. Retain discretion, performance certification, and continued-service conditions.
• Reporting missing awards as no acceleration. Identify unavailable incorporated documents and leave affected results unquantified.
• Comparing unlike triggers. Separate ordinary termination, transaction-only benefits, and transaction-related termination protections.
• Calling every difference a defect. Check approval history and distinguish intentional concessions from drafting inconsistencies.
• Combining release and payment periods. Preserve each trigger and dependency; assign unresolved interactions before calculating dates.

Final quality check

• Material rows identify operative documents, versions, and section/page locations.
• Amendments and incorporated documents are reconciled or expressly marked missing.
• Formulas retain compensation bases, eligibility conditions, and factual assumptions.
• Transaction and ordinary termination scenarios remain distinct.
• Source verification includes definitions, exceptions, and cross-references—not isolated excerpts.
• Tax and release flags identify questions rather than unsupported legal conclusions.
• Material outliers have been checked against available approval records.
• Open issues are resolved or assigned, with the required decision and approval status stated.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review and tabular review capabilities support comparison across multiple documents. Bulk document classification can help organize diligence and prioritize human review. Keep the matrix as the team’s work product, with lawyers verifying language, dependencies, and conclusions. To discuss an executive-agreement comparison workflow, book a demo.

Frequently asked questions

Should the matrix use one row per executive?

Use one row per executive, provision, and scenario for the evidence layer. An executive-level summary can consolidate results, but should link to those rows and preserve conditional terms.

How should we compare agreements without a company template?

Use neutral comparison rules and consistent units. Identify meaningful differences, then ask the authorized company decision-maker to approve preferred positions. Frequency alone is not evidence of suitability or market practice.

Can missing provisions be entered as zero?

Distinguish express exclusions, silence in reviewed documents, and unavailable sources. Use zero only when its meaning is defined and supported; otherwise, leave the economic result unquantified and explain why.

Does a Section 409A clause resolve payment-timing review?

No. Examine the benefit, payment event, schedule, and conditions, then assign coverage, exemption, and specified-employee questions. General tax wording does not replace review of operative payment provisions (26 CFR § 1.409A-3).

Sources

• 26 CFR § 1.409A-3: Permissible payments.
• 26 CFR § 1.280G-1: Golden parachute payments.
• EEOC: ADEA statutory text, including § 626(f).
• SEC: Virgin Galactic–Colglazier employment agreement, Exhibit 10.1.

Scope: General professional workflow guidance based on research through October 13, 2026, not advice for a particular matter. The regulatory pages displayed updates through October 9, 2026; intervening changes were not independently established.

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.