How to extract obligations with source references for Employment Agreements

Extract employment-agreement obligations by tracing each operative promise through the executed agreement, amendments, incorporated documents, and definitions. Record who must act, what triggers performance, when it is due, which conditions apply, and precisely where the supporting language appears. The deliverable is an employer-side obligations register that distinguishes verified contractual text, event evidence, and unresolved questions. Payroll, HR, equity administration, and legal should be able to verify each row without mistaking conditional compensation for an unconditional payment obligation or a contractual restriction for an enforceability conclusion.

When to use this workflow

Use this workflow when an employment agreement is signed or amended, an executive joins or leaves, compensation administration changes hands, or diligence requires a source-backed account of employment commitments. It serves employer counsel and in-house teams translating contractual language into assigned actions, not renegotiating the agreement or resolving every employment-law issue.

This is a US-oriented workflow, not a fifty-state survey. Identify relevant work locations and applicable law separately. Contract wording, governing law, employee circumstances, and related documents affect the analysis. A contractual payment schedule does not resolve wage-law requirements; an extracted covenant does not establish enforceability. The steps below are process recommendations except where a legal requirement is expressly identified.

What you need

Collect the executed employment agreement, amendments, side letters, offer letter, restrictive-covenant exhibits, equity awards, and incorporated compensation or benefit plans. Include referenced policies and relevant delivery evidence. Preserve superseded documents to reconstruct the agreement chain.

Obtain the employing entity, employee role, work locations, start date, and relevant compensation or termination facts. Identify payroll, HR, benefits, equity, and legal contacts. Do not substitute a parent company for the contractual employer.

Assign stable document IDs and versions. Where pagination differs, record printed and PDF pages. Maintain an intake list of requested documents not supplied: an incomplete package does not establish that a provision is absent.

Use the template

Use the Employment Agreements — Obligations register as the working record. Copy this table into your working document or spreadsheet. Add separate rows for duties with different triggers, owners, or completion evidence.

Source / excerpt should contain document ID, version, section, page, and a short operative excerpt, with cross-references to modifying amendments and definitions. Duty / parties identifies the obligor and beneficiary; the internal owner may be neither.

Keep the contractual trigger separate from evidence that it occurred. Preserve the timing formula before adding a calculated date. Conditions include exclusions, incorporated terms, survival limits, and missing evidence. Verification records who checked the row, when, and any remaining uncertainty. Useful statuses include “conditional,” “active,” “awaiting evidence,” “completed—verified,” and “superseded.”

Step by step

1. Establish the operative agreement chain

Order documents by execution date, recording effective dates separately. Identify what each amendment replaces, preserves, or supplements. Do not assume its signature date controls every amended obligation.

The Cyngn employment amendment illustrates the distinction: the March 6, 2025 amendment changes salary effective January 1, 2025 while preserving unmodified terms of an earlier agreement. It does not itself supply the complete agreement package.

Register output: cite the controlling provision and predecessor where needed. Mark displaced rows “superseded” and assign collection of missing base agreements or attachments. Retain links between old and replacement rows.

2. Identify actionable duties without overstating rights

Read for payment promises, notices, approvals, delivery requirements, employee covenants, and event-dependent duties. Distinguish obligations from discretion, eligibility, definitions, and statements of intent. Record discretion as a qualification, not a mandatory payout.

Read term, at-will, termination, and severance provisions together. The Verizon Schulman agreement, paragraphs 1 and 9, combines a stated term with at-will termination and separately conditions specified succession payments on a defined event and release. The term date alone therefore does not describe the employment commitment.

Register output: create one row per independently actionable duty, identify both parties, and label eligibility or discretion explicitly. Cross-link related notice, termination, and payment rows rather than merging their conditions.

3. Attach enough source language to reconstruct the duty

Capture operative wording and pinpoint references to definitions, exceptions, and incorporated documents. A citation to an entire agreement is insufficient when payroll needs to verify a particular installment. Record multiple supporting citations when no single clause contains the complete obligation.

Where OCR supplied text, compare amounts, dates, negatives, and defined terms against the document image. Preserve the executed source rather than relying on an editable transcription. If provisions conflict, cite both and assign interpretation to counsel.

Register output: enter the primary citation, supporting references, and concise excerpt. Use “not found in documents reviewed” only after checking the identified review set. Use “referenced document not supplied” when that is the actual gap; these findings require different follow-up.

4. Separate compensation components and dependencies

Extract salary, annual incentives, special bonuses, equity, benefits, reimbursements, clawbacks, and severance separately. Distinguish earning, vesting, eligibility, and payment conditions. An award amount, vesting date, and settlement date may depend on different documents.

The Cyngn amendment’s special-bonus provisions specify quarterly installments, a payment window, continued employment at payment, and an exclusion from defined severance calculations. These illustrate drafting dependencies, not general payment rules.

Register output: record each amount or formula with its conditions and exclusions. Link installment rows to a parent obligation ID. Leave calculations unresolved when a required plan, award, or factual input is unavailable; do not substitute a target amount for an established entitlement.

5. Translate triggers into dates without inventing facts

Capture the trigger precisely: commencement, quarter-end, receipt of notice, termination, release effectiveness, or another defined event. Identify evidence needed to establish it. For notices, extract recipient, delivery method, address, and deemed-receipt wording where provided.

Keep the formula beside the calculated date. If counting conventions, business-day treatment, or the event date is unclear, record that uncertainty rather than displaying an apparently settled deadline. Good-reason notice, cure, release, and payment periods may form a sequence of dependent dates.

Register output: record trigger source, event evidence, timing formula, and verified date—or an unresolved calculation with an owner. Arrange calendaring through the team’s chosen process; the register does not itself establish reminders or monitoring.

6. Extract post-employment duties and legal dependencies

Map confidentiality, invention assignment, property return, cooperation, solicitation, and competition provisions by subject, duration, and scope. Preserve exceptions beside the restriction.

For agreements entered into or updated after May 11, 2016 that govern trade secrets or other confidential information, 18 U.S.C. § 1833(b)(3) requires employee notice of statutory immunity. A cross-reference to a policy provided to the employee that states the employer’s suspected-law-violation reporting policy can satisfy the requirement. Noncompliance limits specified DTSA exemplary-damages and attorney-fee remedies against the employee lacking notice; it does not statutorily invalidate the entire agreement.

The FTC’s Noncompete Rule status page states that the rule is not in effect and is unenforceable. Do not extract the reproduced rule text as operative employer duties or infer that a particular restriction is enforceable.

Register output: preserve contractual duties and exceptions. Assign missing-policy, delivery-evidence, and jurisdiction questions to counsel separately from performance tasks.

7. Assign performance and verify completion

Give each active or conditional row an internal owner who can obtain trigger evidence or arrange performance. Separate interpretation from administration: payroll should not resolve an ambiguous severance definition, and legal should not mark payment complete merely because instructions were sent.

Specify appropriate completion evidence: payment confirmation, notice-delivery record, signed release, property-return acknowledgment, or another identified record. Link that evidence without replacing the contractual citation. Keep evidence access appropriate to sensitive employment information.

Register output: record owner, next action, status, and completion evidence. Have a second reviewer check material compensation, termination, and restrictive-covenant rows against the sources before operational handoff.

Worked example

Entirely fictional scenario: Harbor Lantern Robotics, Inc. employs Morgan Vale under executed agreement EA-01. Executed amendment AM-01, signed September 18, 2026, changes annual salary to $246,000 effective September 1. It promises a $24,000 retention payment within 20 calendar days after December 31, 2026, provided Morgan remains employed on the payment date. For this example, the amendment expressly excludes the trigger day when counting that period.

EA-01 requires property return within five calendar days after employment ends. Its confidentiality section references a reporting policy, but neither that policy nor delivery evidence was supplied. HR requests payment instructions and a contingent exit checklist. No termination date is established. All parties, documents, wording, and amounts below are fictional.

Salary reconciliation starts on September 1, not the signature date. January 20 is the retention-payment outer date under the fictional counting provision, not proof of entitlement. Property-return preparation can begin without inventing a termination date.

Record the unavailable reporting policy as a separate open review item linked to the confidentiality provision. Its absence prevents verification of the policy-based notice route; it does not establish that no compliant notice exists elsewhere in the reviewed package. Counsel should check that package and assign any remediation.

Common mistakes

• Extracting only employer payments. Include employee notices, property return, and cooperation duties; distinguish obligor from internal owner.
• Treating benefit eligibility as fixed entitlement. Preserve plan conditions and exclusions; collect incorporated documents before finalizing the row.
• Replacing timing formulas with dates. Retain counting language and event evidence so another reviewer can reproduce the calculation.
• Using signature dates for every change. Read effective-date language provision by provision and preserve superseded sources.
• Closing rows when instructions are sent. Require evidence of actual performance, not merely an internal request to perform.

Final quality check

• Every actionable row identifies obligor, beneficiary, and internal owner.
• References identify the correct executed version, section, and page.
• Amounts, negatives, dates, and defined terms match source images.
• Amendments, incorporated terms, exclusions, and conflicts are linked.
• Calculated dates retain formulas and supporting event evidence.
• Missing documents and legal questions are resolved or assigned to an identified reviewer.
• Completed rows contain performance evidence; conditional duties remain distinguishable from presently due obligations.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review capabilities support clause-based review, and tabular review supports work across multiple documents. Bulk classification can organize employment documents and prioritize human review during due diligence. The register remains the legal team’s work product: lawyers verify sources, interpret conditions, and assign actions. To assess the workflow against your agreement set, book a demo.

Frequently asked questions

Should discretionary bonuses appear in the register?

Yes, where relevant to administration. Label the discretion precisely and distinguish an obligation to administer or consider an incentive from an obligation to pay. A target opportunity is not automatically a guaranteed amount.

How should missing equity awards be handled?

Record the employment agreement’s commitment and award or plan reference. Mark vesting, settlement, and termination treatment unresolved where unavailable documents control. Assign collection rather than assuming their contents.

Can one citation support several obligations?

Yes. Use separate rows when triggers, owners, or completion evidence differ. Repeat the pinpoint citation and link related IDs so completing a payment does not prematurely close a notice duty.

Does extraction establish enforceability?

No. The register records wording and dependencies. Preserve jurisdiction-sensitive restrictions, identify work locations and factual gaps, and obtain counsel’s analysis before treating an entry as authority for enforcement.

Sources

• 18 U.S.C. § 1833(b) — immunity and employee notice.
• FTC — Noncompete Rule status.
• Verizon — Schulman employment agreement, paragraphs 1 and 9.
• Cyngn — employment amendment, compensation provisions.

The SEC exhibits illustrate particular drafting choices, 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.