Advanced Claude: from a governed Claude Project to a cross-vendor compliance fabric
Most compliance teams meet Claude as a chat window. That is the first rung, not the destination. This is the path a mortgage compliance function can climb, one deliberate step at a time, where each rung keeps the rigor a compliance officer is accountable for and adds leverage on top of it. The goal is never to route around the compliance pro. It is to give the people doing the hardest thinking in the building a system that scales with them.
Where you start: Microsoft Copilot, then Claude
Most shops don’t start on Claude — they start in Microsoft Copilot, because it’s already inside their approved tenant: no new vendor to security-review, and the data stays put. That’s the right on-ramp. Drop the regulation files and a P&P section into Copilot and go.
You graduate to Claude at the point Copilot can’t keep up — and that point is concrete, not a sales pitch. The first time you feed Copilot a full servicing P&P (100–300 pages), it runs out of context window and starts dropping sections. Claude’s larger context (about 500 pages on Pro and Team, more on Enterprise) reviews the whole thing in one pass, and the quote-only discipline in the prompts is what keeps it from inventing regulatory language on a job that size. So moving from Copilot to Claude isn’t “switch vendors” — it’s “use the tool that fits the size of the job,” and the full-P&P review is the first job that demands it.
*Microsoft caps Copilot’s rewrite at ~3,000 words (~6 pages) and notes quality drops on larger inputs — so even though Copilot can summarize a document up to ~300 pages, it can’t redline one that big. Claude holds the whole P&P plus the regulations in context (200K tokens on Pro/Team, 500K on Enterprise) and redlines in one pass. Page figures are approximate; the token windows are the hard numbers.
The ladder below is the Claude progression you climb from there.
Run the compliance function on Claude
Stand up a real compliance function, and do its document work in Claude instead of in scattered Word files and inboxes.
The mechanism is the Claude Project: a workspace preloaded with the regulations that govern the work and the templates that produce the deliverables. A policy is not drafted from a blank page and a half-remembered citation. It is drafted inside a Project that already holds the verbatim regulatory text, the source snapshots, and the firm’s approved P&P templates. The compliance officer stays the author and the approver. The Project removes the blank page, the stale citation, and the re-keying.
The step that makes this real instead of a demo is enforcement: the whole team works in the same governed Project, not in ad-hoc personal chats. One source of regulatory truth, one set of templates, one place the work happens, so the output is consistent and reviewable.
On this site: the regulation library is the corpus you load into the Project, and the Claude tutorials show how to set the Project up.
Put operations on the same governed tools
The people who run the loans use the same Projects and templates the compliance team built, so policy and practice stop drifting apart.
When operations needs to update a procedure or refresh a P&P, they work from the same governed Project, against the same regulatory text and the same approved templates. Compliance and operations share one substrate instead of trading documents and hoping the versions match. The compliance team sets the guardrails once; operations works inside them by default. Updates to a procedure inherit the citations and the structure the compliance team already vetted.
On this site: the regulatory-update kits are the change-driven work operations actually runs, built on the same library the compliance team governs.
Add the plumbing, and the tracking
Connect Claude to the systems where work happens through MCP or local plumbing, and make sure the compliance side is properly tracked.
At this rung operations does not just draft in a Project, it works through Claude against real tools and data, and every step that matters for compliance leaves a record. The tracking is the point: who did what, against which standard, with what result. Anthropic’s Compliance API is part of this story for claude.ai organizations, and it is worth understanding precisely what it captures and where its blind spots are, because those blind spots are exactly what a mortgage compliance program needs to fill.
This is the rung where “we use AI” becomes “we can show an examiner how we use AI, and prove the controls held.”
On this site: the Compliance API page lays out what first-party tracking covers and what it leaves uncovered.
A cross-vendor compliance fabric
Your vendors interact with your standards through MCP to do their work, and you can see compliance across all of them from one place.
A mortgage company does not originate or service alone. The work runs across an AVM provider, a pricing engine, a verification vendor, a servicing platform. Within each vendor, compliance is the vendor’s job. Across vendors, it is structurally nobody’s, and that is the gap. The top rung uses a compliance layer over MCP so each vendor’s agents work against your regulatory standards, and you get audit evidence you can hand to an examiner.
This is the layer we are building. It is the destination the first three rungs are walking toward: the same governed regulatory truth, now enforced not just inside your team but across every vendor that touches a loan.
Want to follow or shape this: the Engage page is where early partners and advisors come in.
Why climb it
Each rung delivers on its own, so you are never forced to boil the ocean. But there is a compounding reason to keep climbing: the guardrails a compliance team builds to use AI safely are the same guardrails that let the rest of the firm adopt AI with confidence. Done well, the compliance function is not the brake on AI adoption. It is the part of the company that makes broad, safe adoption possible, and it gets to lead it.
Start at rung one with the library and a governed Project. When you are ready to talk about rungs three and four, come say hello.