Claude Project: A Vendor and Compliance Assistant That Already Knows Your Contracts

What This Builds

A broker contract question comes in on a Tuesday, and you spend twenty minutes digging through email and a shared drive folder to find the renewal terms before you can even start answering it. This Claude Project fixes that by holding your current broker and carrier contracts, your compliance filing calendar and your M&A integration playbook in one place, so every question starts from what is actually on file instead of your memory of a document you read six months ago.

Prerequisites

• A seat in your organization's Claude Team or Enterprise workspace, the tiers that give admins data controls. A personal Pro account ($20/month) also has Projects, but unsigned vendor contracts belong in the company's workspace, not yours. Check current Team pricing on Anthropic's pricing page
• Your current broker service agreement, carrier contracts and any recent renewal notes, saved as PDFs or Word files
• Your compliance filing calendar (ERISA, Form 5500, ACA, nondiscrimination testing and pay transparency deadlines)
• Your M&A integration playbook or checklist, if one exists. If not, skip that upload and add it once you build one
• 30 minutes to gather and rename documents, 30 to 60 minutes to build and test the project

Total ongoing cost is your Claude seat. Nothing else in this build carries a separate fee.

The Concept

Think of a Claude Project as a filing cabinet that talks back. You load it once with the documents that matter (the contracts, the calendar, the playbook), and from then on every conversation in that project already has access to them. You are not retyping context every time you have a question. You ask, and Claude checks the actual documents before answering.

This is different from a plain Claude chat. A regular chat only knows what you paste into that one conversation. A project keeps what you uploaded and references it in every new conversation, until you swap in a newer version of a document.

Build It Step by Step

Part 1: Gather and rename your documents

Collect these files before you start:

• Broker service agreement (current, signed version)
• Carrier contracts for each major plan (medical, dental, vision, life, disability)
• Renewal notes or emails from the last one or two cycles
• Compliance filing calendar, exported as a PDF or spreadsheet
• M&A integration playbook or checklist, if you have one

Rename each file so Claude can reference it clearly in an answer instead of calling everything "document 3":

• broker-agreement-2026.pdf
• medical-carrier-contract-2026.pdf
• dental-carrier-contract-2026.pdf
• compliance-calendar-2026.pdf
• ma-integration-playbook.pdf

Part 2: Create the project and set its boundaries

1. Go to claude.ai and click Projects in the left sidebar, then New Project
2. Name it something searchable, like Vendor and Compliance, [Company Name]
3. Add a short description: Broker and carrier contracts, compliance filing calendar and M&A playbook for [Company Name]. Used for RFP notes, contract review and compliance questions.
4. In the project knowledge panel, use the + button to upload your renamed files one at a time, so each one finishes processing before the next starts

What you should see: each document listed in the project knowledge panel once it has finished uploading.

Part 3: Write the project instructions

Open the project's instructions (in the same panel as the project knowledge) and paste something close to this, adjusted for your organization:

You are a vendor and compliance research assistant for [Company Name]'s total
rewards team. You have access to our current broker and carrier contracts,
our compliance filing calendar and our M&A integration playbook.

WHEN ANSWERING QUESTIONS:
- Base answers on the specific documents uploaded to this project and name
  which document a fact comes from
- If a contract clause is ambiguous or you are not confident in your reading,
  say so directly instead of guessing
- For anything touching a filing deadline, restate the exact date from the
  compliance calendar rather than estimating one
- Do not draft language meant to go directly into a signed contract. Draft
  questions and talking points for the manager to bring to legal or the
  vendor instead

WHAT YOU DON'T KNOW:
- Any contract amendment or renewal that has not been uploaded yet
- Individual employee pay, claims history or enrollment status
- Verbal agreements or side conversations with a broker that never made it
  into a document

TONE:
- Direct and specific, written for a total rewards manager who already knows
  the subject
- Flag anything that needs a second read from legal or the CHRO

Part 4: Test it against real questions

Run five or six questions you would actually ask before you trust the project day to day:

1. "What is the notice period for terminating our current broker agreement?"
2. "Given the medical carrier contract, what happens to pricing if enrollment drops more than 10 percent?"
3. "Draft three questions to ask at the upcoming broker renewal call based on last year's renewal notes."
4. "What compliance filings are due in the next 60 days?"
5. "Summarize the change in control clause in the dental carrier contract in plain language."

For each answer, open the source document yourself and check the quote or date Claude cites. A project is only as reliable as the documents behind it, and the fastest way to lose trust in this build is to skip that first round of checking.

Real Example: A Renewal Call Two Days Out

Setup: The project holds the broker agreement, three carrier contracts and the last two years of renewal notes.

Input: "The broker renewal call is Thursday. Based on last year's notes and the current contract, what should I push back on this cycle?"

Output: Claude pulls the renewal increase from last year's notes, flags a service level commitment in the broker agreement that was missed twice according to the notes, and drafts four questions: one on the proposed increase, one on the missed service commitment, one on whether a multi-year rate lock is available, and one asking for a breakdown of claims experience driving the renewal number.

Time saved: What used to mean re-reading two contracts and scrolling through old emails the night before a call now takes about ten minutes, most of it spent verifying the citations rather than finding them.

Data sensitivity: This project holds unsigned vendor contracts and internal filing details, so keep it in your organization's Team or Enterprise workspace, not a personal account. Leave individual employee pay, claims data and enrollment records out of every upload. If a document contains identifiable employee information, redact it before it goes in.

What to Do When It Breaks

• Claude cites a document that no longer matches reality → You renewed the broker contract three months ago and forgot to swap the file. Set a recurring reminder tied to each contract's renewal date to refresh the upload, and remove the outdated version so it cannot answer from stale terms.
• Answers get vague or generic → The project instructions may be too broad, or a document failed to index properly. Reopen the project, check that every file is still listed in the project knowledge panel, and tighten the instructions to name the exact documents Claude should lean on for each type of question.
• Claude answers confidently about something not in any uploaded document → This happens when a question strays outside what you gave it. Add a line to the project instructions telling it to say "not covered in the uploaded documents" rather than filling the gap from general knowledge.
• You stop trusting the citations → Go back to the testing routine from Part 4. Run a handful of known-answer questions and check them against the source. If it is still off, the document itself may be an older draft rather than the signed version.

Variations

• Simpler version: Start with just the broker agreement and the compliance calendar. Add carrier contracts and the M&A playbook once the first two documents prove useful.
• Extended version: Add a running log of renewal notes as a single document you update after every broker or carrier call, so the project's memory grows instead of resetting each cycle.

What to Do Next

• This week: Upload the broker agreement and compliance calendar, then run the five test questions from Part 4.
• This month: Add the remaining carrier contracts and start using the project as your first stop before any vendor call.
• Advanced: Pair this project with the compliance filing calendar automation, so new deadlines land in a place this project can already reference.

Advanced guide for compensation and benefits manager professionals. These techniques use more sophisticated AI features that may require paid subscriptions.