Employment Agreements

How to compare draft and executed versions for Employment Agreements

Compare draft and executed employment agreements with an employer-side checklist for compensation changes, missing exhibits, approvals, and corrective action.

October 19, 2026  ·  9 min read
Book a Demo →

Compare the executed employment agreement with the last employer-approved draft, not merely the newest file. Preserve both versions, reconcile the signing package, and produce a redline covering schedules, definitions, and incorporated-document references. Assess differences in compensation, termination, employer protections, and implementation against actual approvals. The deliverable is a source-linked comparison checklist separating approved deviations, unexplained changes, missing evidence, and formatting differences, with an owner and disposition for each material issue. Never silently edit the executed agreement to restore approved wording.

When to use this workflow

Use this workflow when employer-side counsel receives a signed employment agreement, discovers competing “final” versions, or verifies an executive’s package against internal approvals. It also applies to signed amendments changing salary, incentives, severance, or restrictive covenants.

The scope is execution verification, not renegotiation or a comprehensive enforceability opinion. Establish the employing entity, employee’s work locations, and governing-law provision before routing legal questions. This US-oriented guide includes limited federal references, not a state-law survey. Contract rights depend on the language, applicable law, facts, and deal context.

What you need

Collect the approved draft, approval communication identifying it, executed agreement, and available signing-package records. A later timestamp does not establish approval.

Also obtain:

  • Earlier agreements and amendments that the signed document preserves or replaces.
  • Offer letters, compensation schedules, bonus terms, equity awards, incorporated plans, restrictive-covenant exhibits, and side letters.
  • Employer instructions covering compensation, work location, termination terms, and negotiation fallbacks.
  • Employing-entity details, employee name, role, signing dates, and intended effective dates.

Assign stable document IDs. Distinguish materials supplied to the employee from internal records. Request the applicable version of each incorporated plan; do not infer its contents from the agreement’s summary.

Use the template

Use the Employment Agreements — Version comparison checklist below. You can copy this table into your working document or spreadsheet. Create one row per meaningful difference or unresolved completeness question.

ID / topic Approved source Executed source Difference / evidence Impact / uncertainty Approval evidence Action / owner Status

Source fields should identify document ID, clause, and page. Add PDF-page references where printed numbering differs. Describe deletions and insertions together, using short excerpts where useful.

Separate observation from consequence: “employment-at-payment condition deleted” is verified wording; whether payment remains conditional requires reviewing other provisions. Approval evidence should identify a communication or decision. Use statuses such as verified match, approved deviation, open, and resolved with documentation. Record closure evidence and next actions in the action field; keep formatting-only differences separately identifiable.

Step by step

1. Establish the approved baseline and agreement chain

Identify the exact draft authorized for signature, preserve its original format, and link its ID to the approval record. If business and legal approvals covered different provisions, record that distinction. Do not assume a general instruction to proceed approved every change.

Determine whether the signed document is a replacement, an amendment, or one component of a package. For amendments, identify retained provisions needed to interpret changed text. The Cyngn employment amendment expressly preserves unmodified terms of an earlier agreement; it is not the complete agreement chain.

Record: baseline ID, approval reference, related document IDs, and unresolved baseline questions.

2. Verify the executed package before comparing text

Check page sequence, names, signature blocks, dates, exhibits, and attachments against the approved package. Inspect the rendered document as well as extracted text: a scan may obscure handwriting or omit material that a text-only comparison cannot evaluate.

Use available signing records to investigate package identity without treating them as a substitute for counsel’s assessment of execution. Flag absent signatures and inconsistent dates. Distinguish an attachment not supplied from one supplied and verified unchanged.

Preserve the received file. Create a separate searchable working copy if needed, checking suspect passages against the image.

Record: completeness discrepancies, locations, supporting evidence, and the owner obtaining missing material.

3. Produce the redline and validate its coverage

Compare approved text against executed text in that direction so insertions and deletions remain intelligible. Include tables, footnotes, schedules, definitions, and signature-page additions. Where formats prevent reliable comparison, reconcile affected passages manually and identify the limitation.

Check numbering and cross-references independently. For example, renumbering a “Cause” definition can leave a severance provision pointing elsewhere. Search both versions for compensation amounts, dates, defined terms, and conditions such as “subject to” and “provided that.” Check handwritten additions and changes to work location or reporting lines.

Record: meaningful differences with paired citations; label unreadable or untested material open, not unchanged.

4. Reconcile compensation and termination dependencies

Review salary, bonuses, equity, benefits, and severance separately. For each change, inspect eligibility, vesting, payment timing, release conditions, exclusions, and plan or award references. Matching amounts do not establish matching economics if a condition disappeared.

Distinguish signing dates from compensation-effective dates. The Cyngn amendment, dated March 6, 2025, changes salary effective January 1, 2025. Its special-bonus provisions separately address continued-employment conditions and exclusion from defined severance calculations. These illustrate drafting dependencies, not general payment rules.

Read term, at-will wording, termination grounds, and severance together before characterizing employment duration or payment exposure.

Record: changed economic conditions, dependent clauses checked, unresolved inputs, and implementation approvals needed.

5. Review employer protections and legally sensitive changes

Compare confidentiality, invention assignment, return of property, cooperation, solicitation, and competition provisions for scope, duration, exceptions, and survival. Investigate any deletion of protected-disclosure wording or replacement with a policy reference.

For agreements entered into or updated after May 11, 2016, 18 U.S.C. § 1833(b)(3) requires immunity notice in employee contracts governing trade secrets or other confidential information. A cross-reference can satisfy the requirement if the employee was provided a policy stating the employer’s reporting policy for suspected legal violations. Noncompliance prevents recovery of the specified DTSA exemplary damages and attorney fees against the employee lacking notice; it does not invalidate the entire agreement under that provision.

The FTC’s rule-status page states that its Noncompete Rule is not in effect and is unenforceable. Do not apply the reproduced rule text as operative duties or infer that a particular restriction is enforceable. Route changed restrictions for applicable-law review.

Record: changed protections, work-location and law questions, missing policy evidence, and reviewing counsel.

6. Match differences to actual approvals

Compare substantive changes with the employer’s dated negotiation checklist and deal instructions: preferred position, permitted fallback, or approval-required. That checklist is the team’s work product, not proof of approval or a product feature.

Keep deviation severity separate from enforceability. A reporting-line change may require operational approval; a severance-definition change may require financial analysis. Neither category supplies a legal conclusion.

Ask the relevant decision-maker to address the paired text and dependencies where approval is unclear. Retain the response. Silence in the supplied approval record is a gap to investigate, not proof that nobody approved the change.

Record: approval source, decision-maker, rationale, conditions, and outstanding legal or business decisions.

7. Close discrepancies without rewriting history

Prepare an exception summary distinguishing approved deviations, unresolved changes, missing evidence, and possible corrective documentation. Counsel should determine whether clarification, amendment, or another response is appropriate. An internal redline does not amend the signed agreement.

Keep the received package separate from proposed corrections. Link any subsequently executed corrective document to the original and repeat the comparison for its changed provisions. Tell payroll, HR, equity, or legal contacts precisely which implementation instructions are confirmed and which remain unresolved; do not distribute competing instructions from different versions.

Record: disposition, decision or corrective-document reference, implementation owner, and expressly assigned next actions.

Worked example

Fictional scenario: Alder Cove Analytics, Inc. receives employment agreement EA-S01 for incoming chief operating officer Maya Rowan. Approved draft EA-D12 provides a $310,000 annual salary, a $75,000 retention payment conditioned on employment at payment, and severance equal to six months of Annual Base Salary, subject to stated conditions. The draft defines Annual Base Salary as salary alone.

In EA-S01, the retention amount remains unchanged, but the employment condition is deleted. The Annual Base Salary definition now adds the retention payment. Confidentiality Schedule A also substitutes a policy reference for the draft’s immunity notice. Neither the policy nor delivery evidence was supplied. Every party, document, amount, and provision in this example is fictional.

ID / topic Approved source Executed source Difference / evidence Impact / uncertainty Approval evidence Action / owner Status
V01 / Retention EA-D12 §4(b), p.3 EA-S01 §4(b), p.3 Employment-at-payment condition deleted; $75,000 unchanged Eligibility may change; inspect remaining conditions A07 approves amount only Counsel and HR: reconcile intended conditions Open
V02 / Severance EA-D12 §§1, 7(d), pp.1, 6 EA-S01 §§1, 7(d), pp.1, 6 Annual Base Salary now adds retention payment Severance basis changes; application requires review None supplied Compensation lead and counsel: assess wording and response Open
V03 / Confidentiality EA-D12 Sch. A §2, p.9 EA-S01 Sch. A §2, p.9 Notice replaced with policy reference Policy content and delivery unverified Package lacks policy HR: obtain policy and delivery evidence; counsel: assess Open

These findings change the next step from filing to targeted reconciliation. V01 and V02 need joint review because one payment affects eligibility and a separate severance definition. The table does not assume how the added payment operates within the formula. V03 establishes missing evidence, not necessarily defective notice: counsel needs the referenced policy and evidence it was provided before assessing that route. None permits restoring draft wording silently.

Common mistakes

  • Using the newest draft. Anchor the baseline to approval evidence, not chronology.
  • Checking numbers without conditions. Reconcile eligibility, triggers, definitions, and incorporated terms beside each amount.
  • Stopping at matching signatures. Compare exhibits, schedules, handwriting, and package completeness.
  • Equating missing documents with missing language. Distinguish absent wording in supplied text from unavailable referenced material.
  • Calling unexplained changes unauthorized or unenforceable. Investigate approval history and assign legal analysis separately.
  • Fixing the signed file directly. Preserve it and document the selected corrective process independently.

Final quality check

  • The baseline links to a specific employer approval record.
  • Original approved and executed files remain preserved and identifiable.
  • Exhibits, schedules, signature pages, and incorporated references are accounted for.
  • Material differences have paired citations checked against source text or images.
  • Economic changes include dependent definitions, triggers, exclusions, and conditions.
  • Legal propositions have supporting primary sources and remain separate from assumptions.
  • Resolved issues link to decisions; open issues have owners and next actions.
  • Implementation recipients can distinguish confirmed instructions from unresolved questions.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review capabilities support this review: in Word, choose the represented party 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 under the signed-in Word user’s name, or dismiss findings with reasons. Use working copies for proposals; retain executed originals and lawyer control over approval and remediation. To discuss this workflow, book a demo.

Frequently asked questions

Which draft should be compared with the executed agreement?

Use the draft approved for signature. If approval cannot be tied to one file, identify competing candidates and resolve the baseline before describing differences as deviations from approval.

Must every formatting difference reach the exception summary?

No. Preserve comparison coverage, but summarize meaningful exceptions. Escalate formatting that obscures text, changes a compensation table’s meaning, or breaks numbering and cross-references.

What if an incorporated bonus plan is unavailable?

Record its reference and request the applicable version. Compare available wording, but leave affected rights and package verification open until the relevant incorporated terms are checked.

Can HR implement compensation while discrepancies remain open?

Separate confirmed instructions from disputed ones and route timing to counsel and the responsible business owner. A comparison issue is not itself permission to delay or alter payment.

Sources

The SEC exhibit illustrates contractual wording, not market standards or enforceability.

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.

Run this workflow in DecoverAI

Clause-quoted findings, missing-language flags, and tracked changes in your name — with your team deciding every call. Plans from $299 per seat per month, SOC 2 Type II certified.

Book a demo
to learn more.
Book a Demo