How to compare draft and executed versions for Shareholders Agreements

Compare the last investor-approved negotiated draft with the complete executed shareholders agreement, including schedules and counterparts. Verify apparent differences against the originals, then trace changes through definitions, ownership thresholds, joinders, and related investment documents. The deliverable is a source-linked comparison checklist identifying changed investor rights, incomplete execution evidence, approval status, and assigned actions. Separate confirmed deviations from extraction errors and unresolved questions. This review reconciles the signed package with the approved bargain; it does not silently rewrite that bargain or establish enforceability.

When to use this workflow

Use this workflow when investor counsel or an in-house legal team receives the closing set, discovers competing signed copies, or needs to determine whether execution preserved approved concessions. It also supports targeted portfolio or acquisition diligence where retained investor rights depend on which version was signed.

The scope is version reconciliation, not fresh negotiation or comprehensive enforceability review. Investigate deviations affecting governance, economics, transfers, information access, and obligations. Keep proposed corrective wording separate from the executed record.

The statutory discussion concerns Delaware corporations only. Confirm incorporation jurisdiction, governing law, charter provisions, and applicable statutory effective dates before applying it. These are transactional checks, not litigation evidence or discovery procedures.

What you need

Collect the following before treating the comparison as complete:

• Approved baseline: final negotiated Word file or PDF, approval correspondence, and separately approved closing changes.
• Execution package: signed body, counterparts, schedules, exhibits, signature pages, joinders, and available signing correspondence.
• Related documents: charter, bylaws, investment agreement, side letters, amendments, and incorporated documents.
• Ownership evidence: closing capitalization table, share classes, issuance dates, and affiliate holdings relevant to thresholds.
• Investor instructions: dated internal negotiation checklist, approved concessions, escalation positions, and authorized decision-makers.

Assign stable document IDs, such as D01 for the baseline and E01 for the signed body. Preserve originals and compare working copies. Record claimed status separately from supporting evidence: a filename containing “final executed” does not establish that its attachments match the signed package.

Use the template

The companion template is Shareholders Agreements — Version comparison checklist. Copy this table into your working document or spreadsheet. Use one row per consequential deviation, missing component, or unresolved version question. Keep verified cosmetic differences in the underlying comparison log.

In each source field, record the document ID, section, and PDF page. If numbering moved, retain both references. “Not present in supplied E01 package” is more precise than “deleted” when an unproduced schedule might contain the provision.

Describe the change before evaluating it. Investor impact should identify the affected right, triggering scenario, and priority. Evidence / uncertainty separates verified wording from assumptions about ownership, execution, or approvals. Approval status records evidenced acceptance, pending confirmation, or no approval found—not an inference from materiality. Action / owner identifies the responsible person, next action, and eventual resolution evidence.

Step by step

1. Establish the approved baseline and executed package

Identify the version the investor actually approved. If an email approved specified changes, reconcile those instructions with its attachment rather than assuming the attachment incorporated them. Preserve the original draft and describe any reconstructed baseline explicitly. If two candidates remain, compare both and obtain a baseline decision from the deal lead.

Inventory every executed component. Match counterpart signature pages to the relevant body using available circulation or signing evidence. Identify incomplete party names, omitted schedules, competing dates, and later amendments. Do not combine components from different circulation sets without documenting why they belong together.

Record: a package-level row identifying baseline and execution-set IDs, approval evidence, missing components, and disputed version status.

2. Generate the comparison and verify apparent changes

Create a text comparison using suitable document-comparison tools. When reviewing scans, verify consequential differences against page images rather than relying exclusively on extracted text.

Inspect negations, percentages, decimal points, tables, definitions, annexes, footnotes, handwritten additions, and version information. Review signatures and attachments visually where text comparison cannot resolve them. Classify results as substantive, clerical, extraction-related, or unresolved.

Do not discard a moved paragraph until its wording and cross-references have been checked at the new location. Conversely, do not escalate formatting alone because the comparison displays extensive markup.

Record: verified differences with paired pinpoints, classification, and uncertainties requiring source inspection or a second reviewer.

3. Trace governance changes through the investor’s position

For board seats and reserved matters, compare decision-maker, ownership threshold, denominator, quorum, waiver, vacancy treatment, affiliate aggregation, and sunset. Test executed wording against closing ownership and a plausible dilution or transfer scenario.

Keep shareholder voting commitments distinct from corporate consent covenants and nominee-director approval. Delaware § 218(c) permits two or more stockholders to specify voting arrangements through a written agreement signed by its parties; it does not describe every governance mechanism. DGCL § 218(c). (delcode.delaware.gov)

Section 122(18) authorizes specified contracts with current or prospective stockholders or beneficial owners for board-determined minimum consideration. Its limits include conflicts with the charter and specified Delaware-law constraints. Flag changed corporate undertakings for contextual review rather than declaring every veto valid. DGCL § 122(18). (delcode.delaware.gov)

Record: changed mechanism, ownership assumptions, affected scenario, and charter or authority questions requiring review.

4. Compare transfer and exit provisions as a sequence

Read lock-up, permitted transfers, joinder, first-offer or first-refusal rights, tag rights, and drag rights together. An unchanged tag clause may operate differently if execution expands permitted transfers. Check indirect transfers, pledges, consideration form, valuation conditions, liability allocation, and survival of rights after affiliate transfers.

For permitted Delaware transfer restrictions, § 202(a) addresses conspicuous certificate notation or notice for uncertificated shares; without the specified disclosure, a restriction is ineffective except against a person with actual knowledge. Section 202(b) also addresses holder participation for securities issued before the restriction. DGCL § 202(a)–(b). (delcode.delaware.gov)

If execution added a restriction or changed holder coverage, identify the issuance, participation, and disclosure evidence needed. Contract text alone cannot establish those facts.

Record: affected transfer pathway, linked provisions, investor exposure, and missing supporting evidence.

5. Check economics, information rights, and operative mechanics

Compare funding commitments, distributions, dilution protection, reporting access, confidentiality exceptions, and termination. Follow defined terms into schedules and related investment documents. A changed ownership definition can narrow information rights even when the reporting clause is untouched.

For altered notice or response provisions, identify trigger, business-day definition, dispatch versus receipt, permitted method, recipient, and waiver mechanism. Do not supply a missing deadline from convention.

Check related-document consistency without assuming a universal hierarchy. One SEC-filed shareholders agreement calls for consistent interpretation with a related governance framework and concurrently executed definitive agreements; it also requires amendments in writing signed by all parties. That agreement selects Wyoming law and supplies drafting examples, not Delaware-law conclusions or market standards. DentonX agreement, §§ 12.1–12.3. (sec.gov)

Record: changed rights or obligations, cross-document dependencies, operational consequences, and unresolved inconsistencies.

6. Reconcile deviations with approval evidence

Match each substantive difference to approval correspondence, documented closing instructions, or another identified authorization source. Separate “commercially acceptable” from “approved”: the former is an assessment; the latter needs evidence. Likewise, “no approval found” describes the reviewed record, not a final conclusion about authority or contractual effect.

Prioritize by scenario rather than unexplained scores. A lost nomination right may require immediate escalation; a corrected address may need confirmation. Treat an added funding obligation separately from ambiguity about reporting recipients.

Where a change was approved but absent from the baseline, preserve that history instead of labeling it an unauthorized execution change.

Record: approval source, reasoning, priority, and the person authorized to decide any unresolved concession.

7. Issue the reconciliation and assign remediation

Deliver the checklist, comparison files, and a short summary of material deviations, incomplete package evidence, and unresolved approvals. Distinguish confirmed findings from questions awaiting documents.

Actions may include confirming an attachment, obtaining a counterpart, documenting an approved concession, or asking counsel to prepare an appropriate corrective instrument. Review the agreement’s amendment requirements and affected-party approvals before selecting that route. Do not overwrite the executed file or present revised working text as an effective amendment.

Record: decision, supporting evidence, owner, and completion proof. Distinguish resolved rows from open issues transferred to a named owner; assignment alone is not substantive resolution.

Worked example

Fictional scenario: Alder Quay Ventures invests in Meridian Sensorworks, a fictional Delaware corporation. Counsel approved D01, recorded in approval email A01. The closing team supplies signed body E01, counterparts E02, and capitalization table C01. All parties, documents, figures, and clause descriptions below are fictional.

C01 reports Alder’s ownership as 13% fully diluted. D01 grants a nomination right at 10%; E01 raises the threshold to 15%. The contractual denominator still needs reconciliation with C01. E01 also adds founder family vehicles to permitted transfers. In both versions, the tag clause expressly excludes permitted transfers. Finally, E01 references Schedule B for reporting deliverables, but no executed Schedule B was supplied. A01 approves D01 without discussing these changes.

These findings require different responses. V01 warrants prompt escalation, but counsel must verify the denominator before concluding the right is unavailable. V02 demonstrates why unchanged language needs contextual review: expanding the transfer exception changes tag coverage. V03 remains an evidence gap, not a confirmed deletion. None justifies assuming missing approval or signing evidence exists.

Common mistakes

• Comparing the latest filename. Establish the baseline from correspondence and content, especially after closing concessions.
• Reviewing only changed paragraphs. Trace changed definitions and schedules into unchanged governance, transfer, and reporting provisions.
• Equating execution with concession approval. Track signing evidence separately from internal approval evidence; escalate their legal significance rather than assuming it.
• Calling an unavailable attachment deleted. Describe the supplied-set gap and obtain package evidence before deciding what changed.
• Editing the signed record as remediation. Preserve it and prepare corrective wording separately through the appropriate approval process.

Final quality check

• Baseline status and separately approved changes have identified supporting evidence.
• Bodies, counterparts, schedules, and joinders are inventoried without unexplained mixing.
• Material differences have paired pinpoints and original-page verification.
• Threshold denominators, definitions, and linked provisions have been tested together.
• Legal propositions match the cited source’s jurisdiction and scope.
• Approval evidence is distinguished from execution and reviewer acceptance.
• Every unresolved issue has an owner and next action; none is marked resolved merely because it was assigned.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. In its contract review workflow, lawyers can choose the represented party in Word and provide deal-specific instructions. Findings quote clauses, locate text, rank severity, and identify missing language as not present. Lawyers can edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name, or dismiss findings with reasons. Use these capabilities to investigate verified differences and prepare separate corrective drafts—not as proof of the executed package or approval history. Book a demo to discuss this workflow. (decover.ai)

Frequently asked questions

Which draft should be compared with the executed agreement?

Use the last investor-approved negotiated version, accounting for separately evidenced approved changes. Preserve the original and identify any reconstructed baseline. If approval remains ambiguous, obtain a decision rather than silently selecting a file.

Is a clean text comparison enough?

No. Supplement it with package, signature, attachment, and ownership checks. Verify consequential wording against originals, including scans and tables, and document what was unavailable.

What if the executed agreement contains an apparently unapproved concession?

Preserve the evidence, explain investor impact, and escalate. Whether to accept, investigate, or seek correction depends on actual wording, authority, governing law, execution facts, and deal context. An internal approval gap does not itself answer enforceability.

Must every difference appear in the investor report?

Maintain the comparison record, but prioritize consequential deviations and unresolved gaps in the report. Identify excluded formatting noise. A one-word change can matter more than extensive rearrangement, particularly in exceptions, thresholds, and termination provisions.

Sources

• Delaware Code, Title 8, § 122(18) — corporate contracting powers and limitations.
• Delaware Code, Title 8, § 202 — transfer restrictions, disclosure, and holder participation.
• Delaware Code, Title 8, § 218(c) — stockholder voting agreements.
• SEC-filed DentonX shareholders agreement — transaction-specific drafting example selecting Wyoming law.

Scope: October 13, 2026 research cutoff. Online statutory text is not a certified historical snapshot. This is a general professional workflow guide, not a matter-specific legal opinion.

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.