How to compare provisions across a contract portfolio for Employment Agreements

Compare employment agreements by assembling each employee’s operative document package, grouping employees into meaningful cohorts, and extracting selected provisions into a source-linked matrix. Normalize topics without stripping out payment conditions, exceptions, incorporated documents, or jurisdiction questions. Then distinguish verified differences from missing evidence and route material deviations for employer-side decisions. The deliverable is a contract comparison matrix showing what each package provides, how it differs from an identified internal position, what remains uncertain, and who must resolve it.

When to use this workflow

Use this workflow before an acquisition, executive compensation review, template revision, or targeted remediation exercise. It helps legal and HR teams compare packages with different severance definitions, bonus conditions, restrictive covenants, and amendment histories.

Define the decision first. A severance comparison needs compensation definitions and incorporated plans; a confidentiality comparison needs notice language and referenced policies. Neither requires extracting every provision equally.

This is a US employer-side workflow, not a fifty-state enforceability survey or comprehensive wage, benefits, or tax analysis. Identify relevant work locations and applicable-law questions separately. Contractual rights depend on actual language, governing law, facts, and deal context. The comparison methods below are process recommendations, not legal requirements.

What you need

Collect these inputs before substantive comparison:

• Employee records: employing entity, employee identifier, role, executive status, employment status, and current and relevant prior work locations.
• Agreement packages: executed agreements, offer letters, amendments, side letters, restrictive-covenant exhibits, equity awards, and incorporated compensation or benefit plans.
• Supporting evidence: referenced confidentiality policies, applicable policy versions, and available evidence that policies were provided.
• Comparison instructions: selected topics, reporting cutoff, cohort definitions, materiality criteria, and the employer’s dated, jurisdiction-specific checklist.
• Decision owners: legal, HR, compensation, and business contacts authorized to retrieve records or approve deviations.

The checklist is the employer’s work product, not evidence of prevailing market terms. Keep drafts separate from executed documents. A template identifies differences but does not establish an employee’s operative terms.

Use the template

Use Employment Agreements — Contract comparison matrix for one employee-and-topic comparison per row. You can copy this table into your working document or spreadsheet.

Assign stable row IDs rather than relying on spreadsheet positions. Use employee identifiers instead of names where practical.

“Operative source” identifies the document ID, execution date, different effective date, and section/page citation. “Evidence” contains a short excerpt or precise paraphrase. “Normalized terms” preserves the relevant obligor, beneficiary, amount or scope, trigger, timing, exceptions, and survival period.

Identify a dated internal position or defined cohort in “Comparator”; avoid unexplained labels such as “standard.” Keep evidence confidence separate from decision priority. Use linked rows where several documents control one benefit, and record verification status in the final column.

Step by step

1. Define the comparison population and question

Choose a question that reviewers can answer consistently: which executive packages include special bonuses in severance, which confidentiality agreements contain immunity notices, or which restrictions require location-specific review?

Create cohorts using work jurisdiction, executive status, agreement vintage, compensation structure, and transaction context. Do not treat a commission-based sales arrangement and a chief executive’s equity package as comparable merely because both documents are employment agreements.

Record: employee identifier, cohort, selected topic, and comparator. Document excluded populations in the working instructions so the summary does not imply portfolio-wide coverage.

2. Establish the operative document chain

Assign document IDs and connect each amendment to the agreement it changes. Identify replaced provisions, preserved terms, and differences between execution and effective dates. The newest file should not automatically displace the entire earlier agreement.

Cyngn’s March 6, 2025 amendment preserves unmodified terms of an earlier agreement while replacing salary language effective January 1, 2025. The exhibit therefore illustrates both amendment precedence and a distinct compensation-effective date; it does not supply the complete agreement. (sec.gov)

Record: controlling sources and unresolved dependencies. If a referenced severance plan is missing, mark that topic incomplete rather than reporting “no severance.”

3. Extract provisions with their dependencies

Read term provisions with termination rights. Separate salary, conditional bonuses, equity, benefits, reimbursements, and severance. For termination payments, capture the qualifying event, payment base, release condition, exclusions, and referenced definitions.

Verizon’s executive agreement, paragraph 1, states a term through December 31, 2027 while preserving at-will termination. Paragraphs 4–7 separately address salary, incentives, equity, and benefits. These are company-specific drafting examples, not market benchmarks. (sec.gov)

For restrictive covenants, capture duration, prohibited conduct, geographic or customer scope, exceptions, and survival language. Preserve relevant definitions and exhibit references.

Record: source evidence and normalized terms, including dependencies that could change the comparison.

4. Normalize wording without creating false equivalence

Use consistent topic names while preserving operative differences. An annual bonus may be a target opportunity, a discretionary award, or a payment conditioned on continued employment. Do not reduce these to a single “bonus amount.”

Use explicit evidence states: “present,” “not present in reviewed documents,” “referenced document missing,” and “conflicting text.” Reserve “not applicable” for a reasoned determination.

Cyngn’s amendment separately conditions special-bonus installments on employment at payment and excludes those bonuses from defined severance calculations. That wording supports distinct payment-condition and severance-inclusion fields—not a general rule about bonus entitlements. See §§ 3.2(b)(ii)–(iii). (sec.gov)

Record: the normalized result, evidence state, and any missing definition or document blocking comparison.

5. Separate textual differences from legal questions

Assess legal uncertainty, financial exposure, operational feasibility, and drafting ambiguity separately. An internal-checklist deviation is not itself an enforceability conclusion.

Under 18 U.S.C. § 1833(b)(3), employee agreements governing trade secrets or other confidential information must provide immunity notice if entered into or updated after May 11, 2016. A cross-reference to a provided policy stating the employer’s suspected-law-violation reporting policy can satisfy the requirement. Noncompliance bars the specified DTSA exemplary damages and attorney fees against the employee who lacked notice; it does not declare the entire agreement invalid. (uscode.house.gov)

For noncompetes, the FTC’s status page states that its Noncompete Rule is not in effect and is unenforceable. Do not treat the reproduced rule text as operative duties or infer that a particular covenant is enforceable. (ftc.gov)

Record: the textual finding, distinct legal-review question, priority rationale, and responsible counsel.

6. Compare within cohorts and assign decisions

Review each cohort by topic against the identified comparator. Count employee packages, not matrix rows, when reporting prevalence. State the denominator and separately identify incomplete packages.

Separate accepted business differences from unexplained departures. A negotiated executive benefit may be intentional; a missing amendment may merely make it appear exceptional. Any exposure estimate should identify compensation inputs, triggering assumptions, exclusions, and unresolved facts.

Choose a disposition: accept with rationale, obtain evidence, seek legal analysis, or propose an amendment. Recommending an amendment does not change existing rights.

Record: disposition, business reason, approval owner, and status. Do not force unresolved rows into definitive conclusions.

7. Validate the matrix and prepare the comparison summary

Reopen sources for material findings and verify citations, amounts, triggers, exclusions, and amendment precedence. Check extracted text against the document, especially where scans or tables obscure wording.

Summarize the reviewed population, incomplete packages, material differences by cohort, and decisions requested. Distinguish confirmed contractual text, factual assumptions, internal preferences, and legal conclusions. Retain the reporting cutoff and checklist version so later readers understand the comparison’s basis.

Record: verification status and corrected interpretations. Another lawyer should be able to trace each material finding without repeating the review.

Worked example

Fictional scenario: Harbor Lantern Systems, Inc. compares three executive packages before revising its severance guidance. All parties, documents, amounts, and clause descriptions below are fictional. Its dated internal checklist prefers base-salary-only severance and separately requires confidentiality-notice review.

HR reports that all three executives work in Colorado; counsel has not resolved applicable-law questions. The supplied agreements were signed in 2024. H01-A, a signed 2025 amendment, changes E01’s salary. E02’s package lacks referenced Plan P; E03’s package lacks reporting policy RP-4. Evidence cells below are paraphrases, not quotations.

E01 produces a conditional salary estimate, not a presently payable obligation. E02 cannot be treated as equivalent merely because both agreements provide six months of salary: the incentive addition remains unresolved. E03 requires evidence before counsel determines notice sufficiency.

The decision is to retain E01’s conditional estimate and request evidence for E02 and E03—not to issue three completed risk conclusions. Do not reconstruct missing terms from another employee’s package.

Common mistakes

• Treating headings as operative terms. Read stated duration together with termination rights before classifying guaranteed employment.
• Flattening compensation into one value. Separate opportunity, eligibility, payment conditions, and severance inclusion.
• Counting missing documents as absent rights. Use a missing-evidence status and assign retrieval responsibility.
• Comparing unlike employees. Segment by location, role, vintage, and compensation structure before identifying outliers.
• Reporting misleading percentages. Count distinct packages and disclose incomplete evidence rather than counting provision rows as employees.

Final quality check

• Every reviewed employee has an identified package and cohort.
• Amendments link to affected provisions, with distinct effective dates captured.
• Material findings have verified document IDs and clause/page citations.
• Compensation comparisons retain eligibility, payment, release, and exclusion conditions.
• Missing documents, absent wording, and conflicts have different statuses.
• Summary counts reconcile to employee packages and disclose incomplete evidence.
• Legal conclusions remain separate from extracted text and internal preferences.
• Every material open issue is resolved or assigned with a specific requested decision.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its transactional tabular review supports work across multiple documents; due diligence classification can organize packages and prioritize human review. For follow-on contract review in Word, lawyers can select 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 retain source verification and legal judgment. To discuss this portfolio workflow, book a demo.

Frequently asked questions

Should each employee occupy one row?

Use one row per employee and topic. Add linked rows where separate documents control different components; one employee-wide row makes dependencies difficult to audit.

Can we compare only signed employment agreements?

Only where the selected question can be answered from them. Otherwise, identify referenced plans, amendments, and side letters as missing and explain which conclusions remain blocked.

How should we handle different work locations?

Create location-based cohorts and ask counsel to identify applicable-law questions. Record governing-law clauses separately from HR’s location facts rather than treating either as a completed legal analysis.

What belongs in the executive summary?

Include the population reviewed, material differences by cohort, incomplete packages, conditional exposure estimates, and decisions needed. Link findings to row IDs; avoid a single portfolio score that conceals uncertainty.

Sources

• 18 U.S.C. § 1833 — Trade-secret immunity and notice provisions.
• FTC — Noncompete Rule status.
• Verizon — Schulman employment agreement, Exhibit 10j.
• Cyngn — 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.