Statement-of-Work Reviewer

1. Overview

This process examines a Statement of Work (SOW) PDF and, based on whether the reviewer is the contractor or the client, highlights red‑flag language, hidden pitfalls, typographical errors, unusual clauses, and practical negotiation suggestions. The result is a concise, professional review report that can be shared with the relevant decision‑makers.

2. Business Value

• Risk Reduction: Early detection of ambiguous or unfavorable terms prevents costly disputes later.

• Negotiation Leverage: Clear, actionable recommendations give the reviewer concrete points to discuss with the other party.

• Quality Assurance: Ensures the SOW is free of typographical errors and follows industry‑standard language, protecting brand reputation.

• Time Savings: Automates the first‑pass review, allowing legal or business teams to focus on higher‑level strategy.

3. Operational Context

• When to run:

  • When a new SOW is received for a project and before any signatures are placed.

  • When an existing SOW is being amended or extended.

• Who uses it: Founders, contractors, and business leaders who need a quick, reliable assessment of contract terms.

• How often: Typically once per SOW (or per amendment).

4. Inputs

No additional files, IDs, or external data are required.

5. Outputs

5.1 Executive Summary

2-3 Sentences

5.2 Red Flag List

List of flags

5.3 Typo / Grammar List

List of typographical and grammatical errors.

5.4 Unusual Clauses

List of unusual clauses

5.5 Negotiation Recommendation

List of points to negotiate and change. Should include:

• An overview of the negotiation point, like what it is, why it's important, and what the goal is.

• The original offending clause(s)

• An updated suggestion

Sometimes the same offending point may be replicated in multiple places within the document. Have on entry in the negotiation list per offense (that way we can give tailored rewrite suggestions for each offending area)

5.6 Summary and Closing Notes

Summarize the overall assessment of the SOW, while also providing thoughts and opinions on it.

6. Detailed Plan & Execution Steps

1. Receive Inputs – Confirm that the SOW PDF and the Reviewer Role are present. If either is missing, stop and flag an error.

2. Extract Text – Convert the PDF to searchable plain text, preserving the original ordering of sections.

3. Identify Sections – Locate standard SOW headings (e.g., Scope of Work, Deliverables, Timeline, Payment Terms, Intellectual Property, Confidentiality, Termination, Liability, Dispute Resolution).

4. Red‑Flag Scan – For each heading, compare the clause wording against the Red‑Flag Checklist (Appendix C). Flag any clause that:   a. Uses ambiguous language (e.g., “reasonable effort”).   b. Imposes unlimited liability.   c. Lacks clear termination notice.   d. Assigns IP ownership contrary to the reviewer’s role.   e. Contains jurisdiction or governing law that is unfavorable.

5. Typo / Grammar Scan – Run a spell‑check and grammar review on the extracted text. Record each error with its location (section & line).

6. Unusual Clause Scan – Detect clauses that are uncommon for the industry or that deviate from standard practice (e.g., exclusivity, non‑compete, forced arbitration). Use the Unusual Clause Catalog (Appendix C) as reference.

7. Perspective‑Based Adjustments – Tailor the Negotiation Recommendations to the Reviewer Role:   - If the reviewer is the Contractor, focus on payment terms, IP ownership, liability caps, and scope clarity.   - If the reviewer is the Client, emphasize deliverable definitions, acceptance criteria, change‑order processes, and warranty periods.

7. Validation & Quality Checks

• Input Validation: Ensure the PDF opens and contains extractable text; confirm the Reviewer Role is exactly “Contractor” or “Client”.

• Completeness Check: All five sections must be present. If a section has no items, it can be an empty list.

• Accuracy Check: Randomly spot‑check three flagged items against the source text to confirm correct location and wording.

• Consistency Check: Verify that the tone is neutral and professional throughout.

• Error Handling: If the PDF cannot be read or the role is invalid, output an error message stating the missing or incorrect input and halt further processing.

8. Special Rules / Edge Cases

• Conflicting Clauses: If two clauses contradict each other (e.g., payment terms vs. termination clause), flag both and note the conflict in the Red‑Flag List.

Appendix A – FAQ

Q1: What if the SOW is longer than 50 pages? A: The process will still extract and scan the entire document. Review time may increase, but all sections will be evaluated.

Q2: Can I use this SOP for contracts other than SOWs? A: The checklist is tailored to SOWs. For other contract types, adjust the Red‑Flag Checklist accordingly.

Q3: How are “unusual clauses” defined? A: Any clause that deviates from the standard industry practices listed in Appendix C, such as exclusivity, non‑compete, or forced arbitration in jurisdictions not typical for the industry.

Q4: What if I’m unsure whether I’m a contractor or client? A: Select the role that reflects your primary position in the agreement. If you wear both hats, run the review twice—once for each perspective.

Q5: Will the review catch legal compliance issues (e.g., data‑privacy laws)? A: Only if they appear as obvious clause language. Detailed regulatory compliance requires a specialist legal review beyond this SOP.

Appendix B – Glossary

Appendix C – Reference Materials

C.1 Red‑Flag Checklist (Legal Best Practices for SOWs)

1. Ambiguous Scope Language

   • Phrases like “reasonable effort,” “as needed,” or “to the best of ability.”

   • Recommendation: Define measurable deliverables and success metrics.

2. Unlimited Liability

   • Statements that impose “all damages, direct or indirect.”

   • Recommendation: Insert a liability cap (e.g., 1‑2× the contract value).

3. Termination Without Cause

   • Allows one party to end the agreement at any time without notice.

   • Recommendation: Require a minimum notice period (e.g., 30 days) and specify any termination fees.

4. IP Assignment Without License

   • Full transfer of IP to the client with no usage rights for the contractor.

   • Recommendation: Include a license back to the contractor for portfolio or future reuse.

5. Payment Terms Lacking Milestones

   • “Pay upon completion” with no interim milestones.

   • Recommendation: Break payment into milestones tied to deliverable acceptance.

6. Force Majeure Overly Broad

   • Covers any event, even minor delays.

   • Recommendation: Limit to events beyond reasonable control (e.g., natural disasters, war).

7. Governing Law Unfavorable

   • Jurisdiction far from either party, increasing litigation costs.

   • Recommendation: Choose a neutral, mutually convenient jurisdiction.

8. Indemnification Imbalance

   • One side indemnifies the other for all claims, including its own negligence.

   • Recommendation: Restrict indemnity to third‑party claims arising from the indemnifying party’s breach.

9. Change‑Order Process Missing

   • No mechanism for scope changes or additional work.

   • Recommendation: Add a change‑order clause with approval workflow and pricing impact.

10. Warranty Period Too Short or Missing

    • No guarantee of performance post‑delivery.

    • Recommendation: Include a minimum 30‑day warranty for defect correction.

C.2 Common Unusual Clauses (When to Flag)

C.3 Negotiation Recommendation Templates

• Liability Cap: “We propose a liability cap of $[Amount] which is standard for projects of this size.”

• Termination Notice: “A 30‑day written notice period for termination by either party provides reasonable protection for both sides.”

• IP License: “In addition to the client’s ownership of the deliverables, we request a perpetual, royalty‑free license to use the work for portfolio purposes.”

• Payment Milestones: “We suggest splitting payment into three milestones: 30 % upon signing, 40 % upon delivery of the first prototype, and 30 % upon final acceptance.”

• Scope Clarity: “Please define ‘reasonable effort’ as ‘completion of tasks as outlined in Appendix X within the agreed timeline.’”

C.4 Style Guide for Review Reports

• Tone: Professional, neutral, and objective.

• Structure: Use clear headings, bullet points, and concise sentences.

• Length: Aim for 1‑2 pages per review; keep each bullet ≤ 30 words.

• Citation: Reference the exact section and line number for each issue (e.g., “Section 5, line 12”).

• Actionability: Every red‑flag bullet must include a suggested amendment or negotiation point.

C.5 Worked Example – Full Review (Condensed)

Red‑Flag: “The contractor shall indemnify the client for any claim arising from the services, even if caused by the client’s negligence.” – Section 6Recommendation: Limit indemnity to claims arising from the contractor’s gross negligence or willful misconduct only.

Typo: “The deliverables shall be submited by June 30.” – Section 3, line 8Correction: Change “submited” to “submitted”.

Unusual Clause: “Contractor agrees not to engage with any other client in the SaaS industry for 24 months after project completion.” – Section 9Recommendation: Remove or reduce the exclusivity period to 6 months and limit it to the specific technology used.

Negotiation Recommendation: “Add a 30‑day notice period for termination by either party and a $50,000 liability cap.