How to prepare a clause-level risk assessment for Employment Agreements

Prepare an employer-side clause-level risk assessment by assembling the operative agreement package, extracting material obligations with their sources, and evaluating legal uncertainty, financial exposure, operational feasibility, and drafting ambiguity separately. Read compensation, termination, and post-employment provisions together before assigning priority. Record missing evidence rather than filling gaps with assumptions. The deliverable is a source-linked clause risk register identifying the employer’s exposure, proposed revision or acceptance decision, responsible reviewer, and unresolved dependencies—not merely a list of unfavorable clauses.

When to use this workflow

Use this workflow when employment counsel or an in-house team must approve a new agreement, assess an executive’s negotiated draft, review an amendment, or evaluate an existing employment package before a transaction. Define the immediate decision: approve, revise, obtain specialist advice, or accept a documented business risk.

This is a general US employer-side review guide, not advice for a particular employment relationship. Identify actual and anticipated work locations and obtain applicable-law analysis rather than relying exclusively on the governing-law clause. The federal sources below address limited trade-secret and noncompete questions; they are not a comprehensive wage, benefits, tax, intellectual-property, arbitration, or state-law review.

What you need

Collect the document chain and interpretive facts:

• The signed agreement or current draft, amendments, offer letter, side letters, restrictive-covenant exhibits, and any agreement purportedly replaced.
• Incorporated incentive plans, equity plans and awards, severance arrangements, confidentiality policies, and relevant benefit documents.
• Employer entity, employee role, reporting line, work locations, expected mobility, start date, and proposed compensation.
• The employer’s dated, jurisdiction-specific negotiation checklist, approved fallbacks, approval authority, and commercial priorities.
• Relevant policy-delivery evidence and a list of requested documents not supplied.

Assign document IDs and versions. Separate execution dates from effective dates, and identify whether each document is signed, proposed, superseded, or of uncertain status. Treat the negotiation checklist as the employer’s instructions, not evidence of law or market practice.

Use the template

Use the Employment Agreements — Clause risk register below. You can copy this table into your working document or spreadsheet. Create one row per distinct decision; split a clause when different issues require different owners.

In Source / version, record document ID, version date, section, and page. In Text / evidence, use a short excerpt or precise paraphrase identifying the obligor, obligation, trigger, and exceptions.

Use Dependency / gap for incorporated documents, factual assumptions, and related row IDs. Distinguish “not present in reviewed text” from “document not supplied.” In Risk / priority, identify the risk dimension and consequence; priority is not an enforceability conclusion.

Record the accountable reviewer and disposition—revise, accept, escalate, or await evidence—in Owner / decision. Use Verification for the supporting check, closure evidence, and any remaining approval condition. Keep detailed calculations and legal analysis in referenced working notes.

Step by step

1. Establish the operative package and review boundary

List documents received and their relationships. Identify supersession language, amendments, incorporated schedules, and exclusions from other arrangements. If versions conflict, identify the controlling review version or record that question as unresolved.

Define scope precisely: approval of a proposed executive agreement, for example, rather than verification of historical payroll performance. An amendment-only review still requires the provisions needed to understand the amendment’s effect.

Output: a package-level register row identifying the review version, material missing instruments, and retrieval owner. Link affected substantive rows to that dependency.

2. Extract obligations and connect related clauses

Identify who owes what, to whom, upon which trigger, subject to which exceptions, and for how long. Capture defined terms and cross-references. Read identity, duties, location, term, termination, and severance together.

Do not equate a stated term with guaranteed employment. As a company-specific drafting example, Verizon’s Schulman agreement states a term while preserving at-will termination; separate provisions condition specified succession payments on a defined event and release. The example demonstrates why connected clauses matter, not a universal interpretation rule. Verizon agreement, paragraphs 1 and 9. (sec.gov)

Output: source-linked obligation rows, with related provisions and interpretive ambiguities identified.

3. Map compensation and termination exposure

Separate salary, conditional bonuses, equity, benefits, reimbursements, and severance. Identify eligibility, calculation base, payment trigger, termination treatment, and controlling plan or award. Check whether “base salary,” “base compensation,” and “target bonus” are defined consistently.

Test relevant contractual scenarios: resignation, termination without cause, asserted cause, and any good-reason or change-in-control trigger. Identify possible overlapping payments without assuming they accumulate. Separate verified wording from exposure assumptions.

Verizon’s agreement separately addresses salary, performance incentives, equity subject to plan and award terms, and benefit eligibility, including exclusions from specified severance arrangements. Those provisions illustrate dependencies, not guaranteed payouts or market standards. Verizon agreement, paragraphs 4–7. (sec.gov)

Output: financial-risk rows recording assumptions, scenario calculations, and missing documents needed to validate exposure.

4. Review confidentiality and post-employment restrictions

Map confidentiality, competition, solicitation, invention assignment, return-of-property, and cooperation provisions by activity, duration, scope, and exceptions. Identify the employer’s protection objective and relevant work locations. Assign jurisdiction-sensitive questions for legal analysis rather than inferring enforceability from template conformity.

For agreements governing trade secrets or other confidential information entered into or updated after May 11, 2016, check the immunity-notice requirement in 18 U.S.C. § 1833(b)(3). The statute permits a cross-reference to a policy document provided to the employee that states the employer’s suspected-law-violation reporting policy. Noncompliance bars specified DTSA exemplary damages and attorney fees against the employee who lacked notice; it does not itself invalidate the entire confidentiality agreement. 18 U.S.C. § 1833(b). (uscode.house.gov)

For the October 13, 2026 assessment date, the FTC’s status page states that its Noncompete Rule is not in effect and is unenforceable. Do not treat the rule text reproduced below that notice as operative duties or infer that a particular restriction is enforceable. FTC Noncompete Rule status. (ftc.gov)

Output: distinct rows for drafting omissions, missing policy-delivery evidence, and unresolved jurisdictional analysis.

5. Test whether the employer can administer the language

Walk through notice, cure, release, payment, return-of-property, and cooperation provisions with the responsible business owner. Identify recipients, delivery methods, trigger dates, and calendar-versus-business-day ambiguities. Ask whether HR, payroll, and legal can obtain the necessary implementation facts.

For a release-conditioned payment, trace the contractual sequence rather than extracting only the amount. Identify the release form, execution conditions, and payment wording that require further review. Do not invent a deadline where the documents leave timing unresolved.

Output: operational-risk rows naming the process owner, uncertain trigger, and required clarification or supporting document.

6. Assign priorities and proportionate responses

Assess legal uncertainty, financial exposure, operational feasibility, and drafting ambiguity separately. Then assign an overall priority with a short reason. Use consistent categories—for example, approval blocker, approval-required concession, or drafting correction—without suggesting mathematical precision.

A material unresolved payment obligation may block approval. A understood commercial concession may require business authorization instead. A numbering error ordinarily calls for correction, not the same escalation as uncertain severance exposure.

Compare proposed revisions with the employer’s checklist. Identify preferred wording, permitted fallback, or approval-required departure, together with the business reason.

Output: a reasoned priority, proposed response, and approving person for every substantive finding.

7. Verify findings and close the decision record

Return to each source. Confirm that the text, version, citation, and cross-reference support the finding. Check proposed revisions against related definitions and compensation provisions so a local fix does not introduce a conflict.

Distinguish resolved findings from transferred responsibilities. A specialist referral remains open until the required decision is obtained or an authorized approver expressly permits proceeding subject to a recorded condition.

Output: a decision-ready register separating verified findings, assumptions, accepted risks, and outstanding approval blockers, with closure evidence or an assigned next action.

Worked example

The following parties, documents, amounts, and clauses are entirely fictional.

Harbor Lantern Systems, Inc. requests review of D1 version 3 for incoming sales executive Maya Reed. Section 4 provides a $240,000 annual salary and target bonus under an annual incentive plan. Section 8 promises six months of undefined “base compensation” after a qualifying termination, subject to a release. Neither the plan nor release form was supplied.

Section 10 contains confidentiality duties and a policy cross-reference, but no standalone immunity notice in the reviewed draft. The policy and delivery evidence are unavailable. Section 11 restricts work for competing businesses without defining restricted activities. Maya anticipates working in two states; HR has confirmed only one.

R1 changes the decision from accepting a six-month benefit to resolving its calculation and conditions. The $120,000 estimate is arithmetic under a stated assumption, not verified liability. R2 prevents treating unavailable policy language as either present or absent. R3 identifies the facts needed before counsel recommends scope. None closes merely because its priority is recorded.

Common mistakes

• Reviewing the main agreement alone. Obtain amendments and incorporated plans; identify conclusions that remain provisional.
• Treating at-will language as eliminating payment exposure. Separate termination rights from their contractual payment consequences.
• Combining compensation into one figure. Separate salary, conditional incentives, equity, and severance, including their conditions.
• Equating checklist deviation with unenforceability. Record commercial departure and legal uncertainty separately.
• Calling unavailable language absent. Identify documents searched and documents not supplied.
• Revising restrictions before confirming locations. Establish work-location facts and assign applicable-law analysis first.

Final quality check

• Every finding identifies document, version, section, and page.
• Excerpts, paraphrases, and legal-source propositions have been checked.
• Amendments, definitions, exclusions, and incorporated documents are reconciled or flagged.
• Compensation estimates state assumptions and avoid unsupported payout conclusions.
• Termination rights and payment consequences have been assessed together.
• Legal uncertainty is distinguished from commercial preference and administrative difficulty.
• Every open issue has an owner, next action, and stated approval effect.
• Proposed revisions and accepted risks match the decision record.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. In its contract review workflow, choose the employer as the represented party in Word and provide deal-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. Lawyers edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name and can dismiss findings with reasons. Tabular review supports work across documents; counsel retains responsibility for verification and approval. Book a demo to discuss employment agreement review.

Frequently asked questions

Should every clause receive a risk-register row?

No. Maintain review coverage separately, but reserve issue rows for material obligations, decisions, dependencies, and uncertainties. Split a clause when distinct issues require different owners or dispositions.

What if the bonus plan is missing?

Extract the agreement’s wording, request the plan, and identify dependent conclusions. Do not convert a target into a guarantee or assume termination treatment. State whether the gap blocks approval.

Can a confidentiality policy satisfy the notice requirement?

Section 1833 permits the specified policy cross-reference. Verify the policy’s contents and that it was provided to the employee; a title alone does not establish those conditions. 18 U.S.C. § 1833(b)(3). (uscode.house.gov)

Can we approve with open findings?

Use the employer’s approval authority. Record the unresolved issue, potential consequence, required evidence, owner, and approval condition. Business acceptance does not turn an unresolved legal question into a verified conclusion.

Sources

• 18 U.S.C. § 1833 — trade-secret immunity and notice.
• Federal Trade Commission — Noncompete Rule status.
• Verizon Communications Inc. — Schulman employment agreement, Exhibit 10j, used only as a company-specific drafting example.

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.