How to track key dates and notice requirements for Executive Employment Agreements

Track executive employment obligations by turning each operative clause into a source-linked record of who must act, what triggers the obligation, how the deadline is calculated, and what proves completion. Start with the executed agreement and incorporated documents, then separate renewal, termination, cure, release, payment, and recovery events. The resulting tracker distinguishes confirmed dates from contingent or disputed dates, identifies notice recipients and permitted delivery methods, and assigns a company owner. Counsel verifies interpretations; HR, payroll, finance, and corporate administration implement approved actions.

When to use this workflow

Use this company-side workflow when onboarding an executive, signing an amendment, approaching a renewal boundary, receiving a resignation or potential Good Reason notice, planning a termination, or preparing for a transaction. It also helps when responsibility moves between legal and HR.

The task is obligation management, not renegotiating the agreement or preparing a comprehensive severance opinion. Include executive obligations where the company must receive, assess, or enforce performance.

This is a general US workflow guide. Selected federal tax and release provisions are addressed below; state wage-payment, restrictive-covenant, and contract-enforcement questions require separate analysis. Actual language, governing law, executive location, and event facts control the matter-specific assessment. The tracking recommendations are process controls, not independent legal requirements.

What you need

Collect the executed employment agreement, amendments, side letters, incorporated bonus plans, equity awards, restrictive-covenant documents, release form, and relevant approvals. Assign stable document IDs and distinguish operative documents from superseded versions.

Also obtain:

• Executive start date, employing entity, current role, and known term boundaries.
• Notice addresses, designated recipients, required copies, permitted channels, and documented address changes.
• Event evidence: incoming notices, termination communications, milestone certifications, releases, and payment records.
• Legal, HR, payroll, finance, and corporate administration owners and backups.
• Existing calendars and trackers for reconciliation.

Mark missing documents explicitly. An unavailable equity plan is a dependency, not evidence that the employment agreement supplies every applicable deadline.

Use the template

Use the Executive Employment Agreements — Key dates and notices tracker below. Copy this table into your working document or spreadsheet. Keep one row per required action, even when several actions arise from one termination.

In ID / source, enter the row ID, document/version ID, section, and page. Preserve operative wording in a source note referenced by that ID. Timing / due date should retain both the formula and calculated date; a date alone hides the interpretation.

Use Conditions / links for definitions, exceptions, related row IDs, and unresolved dependencies. Recipient / method records contractual requirements, including effectiveness rules, rather than preferred business communications. Status / evidence distinguishes provisional, verified, awaiting trigger, disputed, completed, and closed without action. Keep absent, ambiguous, and inapplicable provisions distinct. Supporting notes can hold approval history and evidence locations without expanding the table.

Step by step

1. Establish the operative contract set

Compare the signed package with the last approved draft. Check signatures, effective dates, schedules, and amendments affecting term, notices, termination, compensation, or releases. A reporting-line amendment may affect the factual assessment under a Good Reason definition.

Do not assume the newest document displaces every earlier obligation. Resolve priority from the documents; flag conflicts rather than choosing a convenient deadline.

Tracker output: Identify each row’s controlling source and add document-gap rows for missing instruments that could change timing.

2. Extract actions rather than headings

Read for actor, action, trigger, timing, conditions, and completion evidence. Look beyond notices and termination sections for reimbursement submissions, incentive certifications, cooperation requests, retention repayments, and address-change requirements.

Separate linked actions. Good Reason language may establish an executive notice window, company cure period, and resignation window. Severance may require release delivery, execution, irrevocability, and payment on different schedules. Track nonrenewal separately from termination and assess their relationship under the actual wording.

Tracker output: Create one row per action, linking related rows and recording the definitions that determine eligibility or trigger an obligation.

3. Translate timing language without losing qualifications

Classify obligations as fixed, recurring, event-relative, or milestone-dependent. Preserve calendar-day versus business-day wording and distinctions among dispatch, receipt, execution, and effectiveness. Identify any counting convention, time cutoff, holiday provision, or deemed-receipt rule.

Calculate only after confirming the trigger. Where counting is unresolved, retain alternative dates for counsel’s decision. Do not import court-filing deadline conventions into a contract calculation. Keep earlier internal planning targets separate from contractual deadlines, especially where timely receipt—not dispatch—is required.

Tracker output: Record source wording, normalized formula, trigger evidence, proposed date, and reviewer approval in the row or its referenced note.

4. Build the notice delivery record

Identify sender, recipient, address, copies, permitted methods, and effectiveness rule. Check whether a special termination provision modifies the general notices clause. Verify address changes against the agreement’s mechanism.

Prepare an approved notice and delivery instructions, including responsibility for retaining proof. An informal acknowledgment should prompt counsel’s assessment, not an unexplained conclusion that contractual delivery requirements were satisfied.

Preserve incoming communications and delivery metadata. Route potential Good Reason notices to legal even without that label; retain competing dates if receipt or validity is disputed.

Tracker output: Enter delivery requirements, dispatch and receipt evidence, unresolved validity questions, and an owner for retrieving missing proof.

5. Connect release and payment dependencies

Map release delivery, consideration, execution, revocation, effectiveness, and payment separately. For waivers governed by ADEA § 626(f)(1), the statutory minimum consideration periods are 21 days for individual agreements and 45 days for specified group programs, with at least seven days after execution to revoke. Section 626(f)(2) separately addresses settlements of filed charges or court actions. These are not universal employment deadlines. ADEA § 626(f). (eeoc.gov)

Counsel must assess applicability, the other waiver requirements, and any required group disclosures. A completed calendar does not establish release validity.

Determine separately whether each payment is covered by or exempt from Section 409A. The regulation identifies permissible payment events and generally requires objectively determinable, nondiscretionary payment timing. A contractual termination label does not resolve the regulatory event definition. 26 CFR § 1.409A-3(a)–(b). (ecfr.gov)

Tracker output: Link payment rows to release and tax dependencies. Record counsel’s approved payment instruction before payroll acts; escalate incompatible deadlines rather than silently moving payment.

6. Test incentive and transaction conditions

Separate bonus eligibility, performance measurement, certification, payment, vesting, settlement, and repayment. Preserve continued-service and milestone conditions when entering dates.

An SEC-filed executive agreement illustrates the distinction: its second retention installment depends on a flight milestone and continued employment. Specified departures trigger repayment within 90 days, while a defined change in control ends the repayment obligation. This is negotiated wording, not a market standard or evidence that an event occurred. Virgin Galactic agreement, § 2(b)(iii). (sec.gov)

For a transaction, identify affected arrangements and assign relevant tax review without turning this tracker into a compensation valuation exercise.

Tracker output: Record each condition, certifying decision-maker, missing evidence, and event that changes or ends the obligation.

7. Assign execution and close with evidence

Give each row an accountable owner and backup. Operational owners need concrete instructions, not unexplained clause extracts. Set internal advance checks appropriate to delivery risk, approval requirements, and payroll processing.

After performance, retain delivery confirmation, an executed release, certification, payment record, or repayment receipt. Completing one step should prompt review of the next linked row, not close the entire chain.

Reconcile amendments and new evidence against existing entries. Preserve the former date and reason for change.

Tracker output: Record owner acceptance, internal check dates, completion evidence, and the disposition or assigned resolution of open issues.

Worked example

Fictional scenario: Alder Cove Instruments, Inc. employs Maya Rowan under fictional agreement AC-EEA-01. Section 3 requires nonrenewal notice to be received at least 60 calendar days before the December 31, 2026 term end. Section 8 allows 30 calendar days after receipt of a qualifying Good Reason notice to cure. Section 12 permits personal delivery or overnight courier and makes actual receipt controlling. The fictional agreement contains no weekend adjustment.

On October 5, Rowan emails concerns about reduced responsibilities. HR reports that a signed notice also arrived by courier, but its contents and receipt date remain unverified. Fictional addendum AC-RET-01 requires repayment of an already-paid $80,000 retention amount within 90 calendar days after a company termination for Cause or resignation without Good Reason occurring before December 31, 2026. A defined change in control ends repayment obligations. Neither departure nor transaction is confirmed.

R1 requires a delivery plan, not last-day dispatch. November 1, 2026 falls on a Sunday; the company should plan earlier receipt rather than assume an extension. R2 requires urgent evidence collection and substantive assessment. The email date cannot silently become the cure-period start, but uncertainty should not justify inaction. R3 remains contingent: neither a possible departure nor the calendar alone establishes a current repayment obligation.

Common mistakes

• Combining notice and termination dates. Separate dispatch, receipt, cure expiration, resignation, and employment end dates.
• Calendaring incentives as unconditional cash. Preserve service, performance, certification, and termination exceptions beside payment timing.
• Applying a six-month delay to every executive payment. The Section 409A delay concerns covered separation-triggered payments to specified employees, generally until six months after separation or earlier death. Assign tax review rather than imposing a blanket delay. 26 CFR § 1.409A-3(i)(2). (ecfr.gov)
• Treating email dispatch as completed notice. Verify permitted methods and effectiveness rules; preserve evidence.
• Closing a row on verbal assurance. Obtain a completion record or assign the evidence gap explicitly.

Final quality check

• Every active row identifies the operative document, section, and page.
• Source wording, formulas, and calculated dates have been independently checked.
• Day-counting, receipt, effectiveness, and weekend questions are resolved or assigned.
• Recipients, addresses, methods, and copies match the operative requirements.
• Release, tax, incentive, and transaction dependencies have named reviewers.
• Owners and backups have accepted the next actions and internal check dates.
• Completion has evidence; open issues have owners and resolution targets.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. In contract review, Word users can choose the represented party and provide deal-specific instructions; findings quote clauses, locate text, rank severity, and identify missing language as not present. Lawyers can insert or edit suggestions as ordinary tracked changes in the signed-in user’s name. Keep this tracker as a company work product, with counsel verifying dates and operational owners maintaining calendars and evidence. Book a demo to discuss reviewing executive agreement obligations. (decover.ai)

Frequently asked questions

Should every executive have a separate tracker?

Use consistent fields across the portfolio, with executive and document identifiers. Separate views can support access controls, but preserve agreement-specific definitions, conditions, and source notes.

What if the agreement has no clear notice deadline?

Distinguish absent from ambiguous language. Check incorporated documents and linked provisions, then assign counsel the question. Label any internal response target as operational, not contractual.

When can payroll rely on a severance payment date?

Use an approved instruction after counsel verifies the trigger, conditions, release dependencies, and relevant tax treatment. Keep unresolved conditions visible and assign their resolution before payment authorization.

How should disputed Good Reason notices be tracked?

Preserve the asserted trigger, delivery evidence, company position, and alternative calculations. Assign an immediate legal owner and distinguish protective steps from an admission that notice is valid or Good Reason exists.

Sources

• 26 CFR § 1.409A-3: covered deferred-compensation events, timing, and specified-employee delay.
• ADEA, 29 USC § 626(f), EEOC statutory text: waiver requirements and consideration/revocation periods.
• Virgin Galactic executive employment agreement, Exhibit 10.1: illustrative retention conditions and repayment timing.

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.