Contract Analysis & Compliance Checker

1. Overview

The Contract Analysis & Compliance Checker reviews two or more versions of a contract, extracts the key obligations and important dates, and compares each clause across the versions to flag any inconsistencies. The result is a concise report that the Contract Manager can use to verify compliance and manage contractual risks.

2. Business Value

• Risk reduction – By automatically spotting missing or altered obligations, the organization reduces exposure to unfavorable contract changes.
• Efficiency – Manual line‑by‑line comparison can take hours; this process delivers the same insight in minutes.
• Compliance – Highlights dates (e.g., renewal, termination) that must be tracked, supporting timely actions.

3. Operational Context

• When to run:

  • When a new version of a contract is received and needs to be compared with a prior version.
  • When a contract manager wants to verify that obligations and dates have been captured correctly.

• Who uses it: Contract Managers, Legal Operations staff, and any stakeholder responsible for contract compliance.

• How often: Every time a contract version is revised (typically 2–3 times per contract lifecycle).

4. Inputs

Note: Only the files listed above are needed for a single run of this process.

5. Outputs

1. Number of obligations extracted,
2. Number of dates extracted,
3. Number of clause differences, and
4. Recommendations for follow‑up (e.g., “Review Clause 4.2 – new termination notice requirement”). | Formal, professional tone; headings for each section; plain‑text (no markup). |

6. Detailed Plan & Execution Steps

1. Load the Documents

   • Open the PDF for Version A.
   • Open the PDF for Version B.

2. Extract Text

   • For each PDF, extract the full text preserving page numbers.

3. Identify Obligations

   • Scan each paragraph for duty‑bearing verbs (e.g., “shall”, “must”, “will be required to”).
   • For each identified sentence, record: the exact sentence, its clause heading, version label, and location (page/paragraph).

4. Extract Dates

   • Scan the entire text for date patterns (e.g., “January 5, 2024”, “2024‑01‑05”, “15/03/2024”).
   • For each date, note the surrounding text that explains its meaning (e.g., “Effective Date”, “Payment Due”).

5. Compile Clause Texts

   • Locate every clause heading (e.g., “Termination”, “Confidentiality”).
   • Capture the entire text under each heading for both versions.

6. Compare Clauses

   • For each clause heading, compare the version‑A text with the version‑B text.
   • Identify differences: added/removed sentences, altered obligations, changed dates, or new language.
   • Record any difference with a brief description of the change.

7. Create the Obligations List

   • Assemble all identified obligations into the Obligations List table (Section 5).

8. Create the Dates List

   • Assemble all extracted dates into the Important Dates List table (Section 5).

9. Create the Clause Consistency Report

   • List each clause where a difference was found, with the text from both versions and a short explanation of the difference.

10. Generate the Summary Report

    • Write a short narrative that (a) counts the obligations, dates, and inconsistent clauses, (b) highlights any critical changes (e.g., new penalties), and (c) suggests next steps (e.g., “review new termination notice period”).

11. Review and Finalise

    • Verify that all tables are complete and that the summary accurately reflects the findings.

12. Deliver Outputs

    • Provide the three tables (Obligations List, Important Dates List, Clause Consistency Report) and the Summary Report to the Contract Manager.

7. Validation & Quality Checks

• Document Presence – Ensure both PDF files are accessible and readable.
• Extraction Confirmation – Verify that each obligation and date includes a location reference (page and paragraph).
• Date Format Check – All dates must follow the YYYY‑MM‑DD pattern; flag any unrecognizable date for manual review.
• Clause Matching – Confirm that every clause heading appears in both versions; flag any missing heading as a “Missing Clause” error.
• Report Consistency – The total number of obligations listed must equal the count of rows in the Obligations List.
• Final Review – The Contract Manager reviews the Summary Report for accuracy; if any errors are found, they are flagged for re‑run.

8. Special Rules / Edge Cases

• Missing Document – If either PDF cannot be opened, abort the process and flag for manual review; no output is generated.
• Unreadable Pages – If any page cannot be read, note the page number in the Summary Report and continue with the rest of the document.
• No Obligations Found – If no obligations are detected in a version, add a note “No obligations detected in Version X” and continue with dates and clause comparison.
• Multiple Versions – The process can handle more than two versions. The same steps repeat for each pair of versions; the Clause Consistency Report will include a comparison column for each version.

9. Example

Input

• Version A Document – PDF file named Contract_2022_Original.pdf (original version, dated 2022‑04‑01).
• Version B Document – PDF file named Contract_2023_Revision.pdf (revised version, dated 2023‑03‑15).
• Version Labels – “Original (2022‑04‑01)”, “Revised (2023‑03‑15)”.
• Clause List – Not provided (process will examine all clauses).

Output

Obligations List

Important Dates List

Clause Consistency Report

• Termination Clause

  • Original: “Either party may terminate the agreement with 30 days written notice.”
  • Revised: “Either party may terminate the agreement with 60 days written notice.”
  • Difference: Notice period increased from 30 to 60 days.

• Confidentiality Clause

  • Original: “Confidential information shall be kept confidential for 3 years after termination.”
  • Revised: “Confidential information shall be kept confidential for 5 years after termination.”
  • Difference: Confidentiality period extended from 3 to 5 years.

• Payment Clause

  • Original: “Payment is due 30 days after receipt of invoice.”
  • Revised: No change.

• Force‑Majeure Clause

  • Original: Not present.
  • Revised: “The parties shall be released from obligations in case of events beyond their control.”
  • Difference: New clause added.

Summary Report

Formal, professional tone

Summary of Findings – Contract Comparison (Original vs. Revised)

1. Obligations – 12 obligations identified across both versions. The most significant new obligation is the extended confidentiality period (5 years) introduced in the revised version.
2. Dates – 5 date entries identified (two effective dates, two expiration dates, and a new renewal‑notice deadline). All dates conform to YYYY‑MM‑DD format.
3. Clause Differences – 3 major changes identified: (a) termination notice period increased from 30 to 60 days; (b) confidentiality period extended from 3 to 5 years; (c) new force‑majeure clause added.
4. Recommendations – Review the extended notice period and the new force‑majeure clause with the legal team to confirm compliance with corporate policy. Update the contract register with the new expiration dates and set calendar reminders for the renewal‑notice deadline (2023‑02‑01).

Appendix A – FAQ

Q1. What if a PDF contains scanned images instead of selectable text? A: The process requires readable text. If a document is scanned, request a searchable (OCR‑processed) PDF and resubmit.

Q2. Can I compare more than two versions at once? A: Yes. Add each additional version as a separate PDF and label it accordingly. The SOP will compare each version to the first (original) version and report all differences.

Q3. How are “obligations” defined? A: Any sentence that imposes a duty, requirement, or restriction on a party (e.g., “shall”, “must”, “required to”, “will be responsible for”).

Q4. What should I do if a date is ambiguous (e.g., “the first day of the next month”)? A: Flag the date as “Unclear” in the Important Dates List and note the original text. Manual review will be required.

Q5. The Clause Consistency Report shows “No change” for some clauses—should I keep those? A: Yes. “No change” confirms that the clause text is identical across the versions, confirming consistency.

Q6. What happens if the same clause appears under different headings in the two versions? A: The process will treat them as separate headings and will still compare the text. If the content matches, the report will note “No change.”

Q7. How are duplicate obligations handled? A: If the same obligation appears in multiple clauses, each instance is listed separately with its location reference.

Q8. I need a report in a specific format (e.g., Excel). A: This SOP only produces plain‑text tables. Convert the tables to the desired format (e.g., copy into Excel) after receiving the output.

Q9. Who reviews the final output? A: The Contract Manager should verify the Summary Report and, if needed, flag any items for further legal review.

Q10. What if a clause is missing entirely in the revised version? A: The report will mark the clause as “Missing in Revised version.” This is a critical inconsistency that should be investigated.

Appendix B – Glossary

• Obligation – A sentence in a contract that creates a duty for a party (e.g., “shall deliver”, “must maintain”).
• Clause – A numbered or titled section of a contract that covers a specific topic (e.g., “Termination”, “Confidentiality”).
• Version – A specific iteration of a contract, usually identified by a date or version number.
• Reference Location – The page number and paragraph number where a piece of text appears in the PDF.
• Consistency – The condition where a clause or obligation is identical (or intentionally changed) across versions.
• Force‑Majeure – A clause that releases parties from obligations when extraordinary events prevent performance.

Appendix C – Reference Materials

C.1 – Typical Clause Headings (Common in Legal Contracts)

C.2 – Common Obligation Verbs

• shall
• must
• shall be required to
• is obligated to
• shall be responsible for
• shall ensure

C.3 – Date Formats Recognized

• YYYY-MM-DD (e.g., 2024-01-15)
• DD/MM/YYYY (e.g., 15/01/2024)
• Month DD, YYYY (e.g., January 15, 2024)

Tip: Use consistent date formatting across all documents to simplify comparison.

C.4 – Sample Clause Comparison Table (for Manual Reference)

Note: The above list can be expanded as needed.

Additional Notes

• Consistency of Naming – Use the same wording for the same clause across versions to make comparison easier.
• Version Labels – Keep the version label short but unique (e.g., “Original‑2022”, “Revised‑2023”). This helps in reporting.
• Manual Review – The Contract Manager should review the “Missing Clause” and “New Clause” entries before final acceptance.

--- ()