Review Counterparty Employment Agreement For Acquisition Targets Key Executive

Skill: Review Counterparty Employment Agreement for Acquisition Target's Key Executive

1. Subject-matter triage

Review the base employment agreement and any amendment separately, then reconcile them as one integrated contract. Read the document set from the acquirer's perspective: what survives closing, what is altered by the transaction, what may be triggered by integration steps, and what produces payment or compliance risk.

If the record includes multiple possible executives, identify the single executive actually in scope before analyzing. If the agreement references other plan documents, offer letters, equity papers, policy manuals, or change-in-control materials, treat them as interaction points rather than side notes.

2. Failure modes the skill is correcting

• The analyst flags a consent or assignment issue without first testing whether the deal changes the employer entity or only the ownership of that entity.
• The analyst identifies a Good Reason clause without mapping it to the planned reporting line, duties, location, compensation, title, or other integration steps that may trigger it.
• The analyst states that Cause is narrow without testing which misconduct categories are missing and whether the cure right leaves the acquiror exposed during the notice period.
• The analyst reviews severance language without tying it to the actual pay components and benefits continuation mechanics in the agreement.
• The analyst discusses confidentiality without checking for trade-secret whistleblower notice language or similar preservation language.
• The analyst mentions an arbitration clause without testing it against the governing enforceability rules for the relevant jurisdiction.
• The analyst compares the base agreement to the amendment in isolation and misses the practical hierarchy between them.

3. Legal frameworks / domain conventions that apply

• Contract hierarchy and amendment control: an amendment supersedes only the provisions it actually changes; read the operative text against the base agreement and any incorporated policies or exhibits.
• Transaction-structure assignment analysis: under ordinary contract principles, an assignment restriction must be tested against whether the transaction effects an assignment, a deemed assignment, or no assignment at all.
• Good Reason doctrine as drafted: the operative definition controls; compare each trigger to expected post-closing changes in role, reporting, pay, duties, location, and authority.
• Cause drafting conventions: compare the stated Cause definition against common misconduct buckets, including dishonesty, theft, fraud, willful misconduct, policy violation, criminal conduct, breach of duty, and conduct harmful to the employer or its business.
• Cure-period risk: a contractual cure period can materially delay termination and should be assessed for operational acceptability.
• Severance and release mechanics: severance exposure depends on the formula, included compensation elements, and any conditions precedent such as release execution, timing windows, or continued compliance.
• Trade-secret and confidentiality compliance: restrictive covenant language should be checked for any statutory notice or carveout language required to preserve remedies under applicable trade-secret law.
• Deferred-compensation timing: if separation pay may be subject to delayed-payment rules for specified service providers, the agreement should be checked for that compliance language.
• Arbitration enforceability: if arbitration is included, compare it to the governing jurisdiction’s enforceability requirements, including any procedural requirements for employee disputes.
• Reporting-structure sensitivity: if reporting is part of the job architecture, changes to reporting lines can be independently material even when title and pay remain unchanged.

4. Analytical scaffolds

• Transaction-structure screen: identify whether the contemplated acquisition changes the employer, the contracting party, or only the ownership of the employer; then decide whether assignment or consent issues are real.
• Amendment reconciliation: list each provision changed by the amendment, identify the operative version, and note any internal tension between the amendment and residual base text.
• Good Reason map: enumerate every contractual trigger, compare each one to the planned integration path, and determine which post-closing steps could activate resignation rights.
• Severance exposure review: identify the severance formula, the compensation inputs, benefit continuation, and any acceleration or gross-up mechanics; assess the likely economic burden if a trigger occurs.
• Cause-gap review: compare the contractual Cause definition to a broader market set of misconduct categories and note any omission that narrows exit flexibility.
• Cure-right review: isolate the notice-and-cure mechanics, the length of any cure period, and whether the alleged breach is curable in practice.
• Compliance overlay: test confidentiality, whistleblower carveouts, deferred-compensation timing, and arbitration language against the relevant legal regime.
• Practical consequence analysis: for each issue, state how it affects closing, integration, retention, termination flexibility, payment exposure, enforceability, or dispute risk.

5. Vertical / structural / temporal relationships

• Base agreement vs. amendment: identify whether the amendment modifies compensation, title, duties, termination rights, restrictive covenants, or dispute resolution, and treat the amended language as controlling only to that extent.
• Pre-closing vs. post-closing: separate obligations and restrictions that apply immediately from those that arise only on termination, change in control, or a specific integration event.
• Event sequencing: trace the order of notice, cure, resignation, termination, severance accrual, release delivery, and payment timing so the memo captures when the risk is triggered.
• Cross-document interaction: flag where the employment documents interact with acquisition covenants, retention arrangements, equity plans, or closing deliverables.

6. Output structure conventions

• Write an issues memorandum organized by ordinal severity using a fixed scale defined once at the top, such as Critical / High / Medium / Low.
• Use one entry per discrete issue; do not merge separate issues merely because they arise in the same clause.
• For each issue, include: the provision at issue, the acquiror concern, the relevant authority or drafting rule supporting the concern, the downstream consequence, and the recommended protective position.
• When a provision turns on a threshold, amount, period, or trigger, state the governing threshold from the document set and explain why it matters.
• When an issue depends on another clause, amendment, exhibit, policy, or related document, cite that interaction explicitly in the entry.
• If the agreement allows enough arithmetic, include a short severance exposure section that shows the contractual inputs and the resulting payment concept without inventing missing data.
• End with a Recommended Actions block that assigns each action to the responsible role and ties it to a transactional or regulatory timing anchor.
• Use conventional memorandum headings rather than a rubric-style checklist.