Review vendor renewal and notice evidence

Practice relevance

Cross-practice idea · Useful supporting administrative method; no claim of practice-specific legal instructions.

Scope: Approved contracts, amendments and notice evidence reviewed in Adobe Acrobat PDF Spaces. No automatic notice, renewal or legal interpretation.

The problem

Track approved dates, decisions and proof of any formal notice.

Why it matters: An informal sales conversation may not satisfy an approved notice process. Keeping the required recipient, channel and evidence beside the reviewed dates helps the owner identify unresolved renewal or cancellation questions.

Sources & evidence

Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified.

What’s been verified

Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result.

What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed.

Pain evidence: Westlaw vs Lexis: read this before you choose ↗Westlaw vs Lexis: read this before you choose, 2026-01-08, older: a lawyer reports discussing a switch with a vendor but later being told the contract required a different formal cancellation notice, resulting in a disputed renewal. This supports the need for an evidence register, not a finding about the contract or vendor.
Method: Microsoft Lists calendar views ↗Microsoft Lists calendar views document calendar presentation of date columns. The system can display approved dates; it does not interpret notice provisions.

Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. We wrote these prompts. The adapted workflow hasn’t been tested.

Suggested approach

Start when: New vendor agreement is approved or periodic renewal review

organize owner-approved renewal/notice values and proof of any authorized notice
Keep source references and report unknowns instead of filling gaps.
The responsible reviewer checks the report before any separately approved action.

Limits and review

The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included.

Who reviews it: Authorized contract owner verifies source terms and actual notice evidence. Test a discussion with a sales representative that has no formal notice acknowledgment. Distinct from S18 seat counts and billing-plan reconciliation.

What you need

Your firm-approved AI assistant · prepared files

Actual current agreement/amendments and a contract owner or lawyer who supplies approved term, renewal and notice dates, recipient/channel and decision status.
Existing firm-approved Acrobat Studio, AI Assistant add-on, or another plan including Acrobat AI; online services/cloud storage, language and region must be permitted. No purchase, login or connection is part of this verification. The manual route works without AI.
Preserve original evidence unchanged in restricted storage. Use synthetic material first. Prepare a separate, explicitly approved minimized AI input; aliases alone do not anonymize narrative or attachments. Do not upload raw originals or an alias key merely because another tab/file is sanitized.
Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details.

How to use

Documentation-verified component path; proposed adaptation, not tested

Before you start

Clause extraction cannot interpret contract obligations or calculate notice deadlines. A sales discussion is not proof of notice or its legal effectiveness.

Check access and setup

Actual account access, source versions/completeness, privacy approval and reviewer sign-off were not observed.

Acquire the clause and notice evidence
Acrobat and Outlook · Open signed contract/amendment PDFs; Outlook message > Save as / File > Save As
Preserve agreements and any sent/received notice evidence. Staff copies exact relevant clause passages with file/version/PDF page/printed label. Owner separately supplies approved dates and recipient/channel plus approval reference. Record actual notice evidence references without claiming effectiveness.
Expected output
Contract excerpts, owner-approved metadata and notice-evidence list.
Next step
Only minimized clause excerpts and approved metadata go into the AI source set; full agreements stay restricted unless separately cleared.
Check before continuing
If approved dates are missing, stop date comparison. Do not ask AI to derive them from “30 days before” or renewal language.
Step documentation 1 ↗Step documentation 2 ↗Step documentation 3 ↗
Load only the approved AI input
Acrobat PDF Spaces · Acrobat homepage > PDF Spaces > Create a PDF Space > upload files or Paste copied text > Add to PDF Space
Add approved contract metadata, minimized clause excerpts and notice-evidence descriptions. Use clear source/version labels and verify the Files panel. Do not add originals that have not separately been cleared for Adobe processing.
Expected output
Visible approved source set in the PDF Space; no account integration is implied.
Next step
Use the AI Assistant message field in this same space for the next prompt.
Check before continuing
Confirm every named source is actually loaded and readable. PDF Spaces supports up to 100 files, 100 MB and 600 pages per file; unsupported/password-protected/handwritten material blocks affected extraction.
Step documentation 1 ↗Step documentation 2 ↗Step documentation 3 ↗
Run the bounded prompt and inspect citations
Acrobat AI Assistant · The PDF Space AI Assistant message field
Paste the prompt below. Open each source-number citation, check it, and use Copy to transfer the answer into a new local Word document or text file. Correct errors using the originals before reliance.
Acrobat AI Assistant promptBuild a vendor-renewal review register using only already-approved contract metadata. Show contract_alias,owner,approved renewal date,approved notice date,approved recipient/channel,approval_ref,clause locator,decision status and sent/received evidence refs. Flag absent approvals, inconsistent supplied dates and pending decisions; never resolve them by interpreting a clause. Preserve exact clause quotes where supplied. Do not calculate notice periods, determine legal effectiveness, renew, cancel, accept terms or send a notice.
Expected output
Review register with approval and evidence gaps.
Next step
Save the checked draft as vendor-renewal-review.docx; carry source IDs, versions and reviewer corrections into the next review step.
Check before continuing
Verify approved dates against the owner’s signed-off source; do not equate sales correspondence with formal notice.
Step documentation 1 ↗
Human review and final handoff
Final human review
Responsible staff reviewer and lawyer/process owner · Local reviewed report beside the frozen source set
Contract owner checks each row and decides action. Copy approved dates as values into the firm’s existing review register or calendar-entry request; maintain clause/version and notice-evidence links.
Expected output
Approved administrative review register with unresolved rows visible.
Next step
Any reminder creation, contract decision or notice transmission is a separate action.
Check before continuing
All unresolved or unreadable evidence stays open. No inferred approval or external action follows from AI output.
Step documentation 1 ↗

What you’ll get

renewal-review.csv: contract_id, owner_alias, approved_dates, decision_status, required_recipient_channel, notice_evidence, approval_ref, mismatch, next_review_question. No contract interpretation, notice or cancellation.

Inputs and a sample test Synthetic example · not a measured result

Input files

contracts.csv: contract_id, vendor_alias, owner_alias, approved_term_start, approved_term_end, approved_renewal_date, approved_notice_date, approved_notice_recipient, approved_notice_channel, clause_locator, reviewer_ref, reviewed_at, decision_status
notice-evidence.csv: contract_id, notice_id, sent_at, recipient_alias, channel, sent_evidence_ref, received_evidence_ref; scope.txt: as-of date and approval coverage

Synthetic example

Synthetic inputs are included in the starter kit.
contracts.example.csv
notice-evidence.example.csv
scope.example.txt

Expected output

CON1 approved notice date 2026-10-01 has passed. N1 is email to Sales-representative rather than supplied Formal-notice-desk/registered-letter, and lacks received evidence.
Do not treat the sales conversation as proven formal or legally effective cancellation notice. Flag channel/recipient/evidence mismatch for Owner-A.
CON2 has pending decision and missing reviewer/date approval. Keep date obligations unverified despite populated fields.
No renewal, cancellation, terms acceptance or notice is sent.

Test a failure

Authorized contract owner verifies source terms and actual notice evidence. Test a discussion with a sales representative that has no formal notice acknowledgment.

Try with the sample files

Follow the tool steps above and use the inputs named in each step. Where provided, native-* files are blank scaffolds and NATIVE-INPUT-MAPPING explains their fields. Original examples and the optional full review prompt use a separate prepared-input schema. Keep them separate unless the mapping explicitly connects them. Downloading a kit does not connect accounts or prove the workflow works.

Download inputs and checklist 10 files

Instructions, blank templates and separate synthetic examples; these files do not install an automation. Blank templates still need verified source data.

Download starter kit All inputs, synthetic examples and review notes in one ZIP. No automation is installed.
Start here: get the sources and prepare the review Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits
contracts.csv Blank input template with exact recipe headers.
contracts.example.csv Separate synthetic fixture input. Do not mix these rows into real exports.
notice-evidence.csv Blank input template with exact recipe headers.
notice-evidence.example.csv Separate synthetic fixture input. Do not mix these rows into real exports.
scope.txt Blank text input worksheet. Fill its fields with approved evidence; no default assumptions are supplied.
scope.example.txt Separate synthetic text input fixture; use with the example CSV files only.
Expected fixture findings Read-only expected output and failure conditions for the included synthetic input files.
Setup and review checklist Recipe-specific prerequisites, file mapping, prompt, setup steps, checklist and limits.

Optional full review prompt for prepared inputs

Prepared-input review prompt with Your firm-approved AI assistant · prepared files

Build a vendor-renewal review register using these already-approved contract metadata rows. Show owner, renewal date, notice date, approved channel, clause locator and evidence of any completed notice. Flag missing approval, inconsistent dates and decisions still pending. Do not calculate or interpret contractual notice periods, conclude that a notice is legally effective, renew, cancel, accept terms or send anything.

INPUTS
contracts.csv: contract_id, vendor_alias, owner_alias, approved_term_start, approved_term_end, approved_renewal_date, approved_notice_date, approved_notice_recipient, approved_notice_channel, clause_locator, reviewer_ref, reviewed_at, decision_status
notice-evidence.csv: contract_id, notice_id, sent_at, recipient_alias, channel, sent_evidence_ref, received_evidence_ref; scope.txt: as-of date and approval coverage

OUTPUT
renewal-review.csv: contract_id, owner_alias, approved_dates, decision_status, required_recipient_channel, notice_evidence, approval_ref, mismatch, next_review_question. No contract interpretation, notice or cancellation.

Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing.

Proposed / not tested · editorial prompt. This prompt uses the original prepared-input schema shown in the sample test. Step prompts may use different tables. Follow NATIVE-INPUT-MAPPING where supplied; do not mix the original examples with native-step inputs without mapping and checking every field.

Read original method Read pain evidence