Every time a rule shifts, a GSE updates its guide, or a vendor ships a release, every lender figures it out alone. bankingops.org is the open, vendor-neutral layer that turns that scramble into collective intelligence — starting with a process catalog you can actually watch run.
Origination, underwriting, closing, servicing — all reasonably solved. What has no shared tooling is everything that happens when those systems have to change. Five gaps, every lender absorbing them alone.
Change managers can't see enough of the technical architecture to evaluate a spec with confidence.
Business-process language and developer language don't map to each other. Meaning gets lost on the handoff.
No shared space exists for mortgage change managers to compare notes across companies.
Regulatory, GSE, and technology changes arrive faster than any one org can operationalize them.
No objective standard tells you whether a change actually landed the way it was intended.
Because no single company owns the catalog, everyone can trust it — and every other tool gets sharper as it cross-references against it. The minimum viable build is the catalog with governance solid enough to earn participation. Everything else is additive.
Process maps built outward from regulatory, GSE, and agency requirements — not from how any one lender happens to operate. Explicitly maps API connections, human decision points, and AI-agent touchpoints. Open contribution with structured peer review.
Regulatory monitors tell you a rule changed. This tells you which downstream processes it touches, which vendor APIs need updating, and a realistic implementation timeline — by cross-referencing the catalog automatically.
Upload your IT team's proposed technical spec. It cross-references the catalog and surfaces gaps — missing process steps, unconsidered API dependencies, compliance exposures — in plain language.
Change managers anonymously share post-implementation outcomes — what worked, what broke, what surprised them — tagged by change type, system, and process area. A structured data layer, not a forum.
Define a change before committing. The system maps it against the catalog, flags affected roles and systems, identifies regulatory intersections, and outputs a risk-weighted roadmap.
A community-maintained map of integrations between LOS, POS, pricing engines, document vendors, title, and servicers — known dependencies, common failure points, implementation gotchas vendors never publish.
Below is a real BPMN default-management / foreclosure process from the catalog, animated step-by-step. This is how every map will be explorable — a shared language change managers and developers can both read.
Token movement, flow tracing, and step highlighting are driven by an open animation engine — the same one that will make every catalog process walkable.
The value isn't any single tool — it's a shared, neutral data layer that turns individual outcomes into collective intelligence. That only works if no one can capture it.
The catalog is built from regulatory and agency requirements outward, governed by open contribution and structured peer review — so no vendor or lender can bend it to their own setup.
Free during beta, no lock-in. Built on open standards (BPMN, JSON) and proven analogies: Bloomberg for intelligence, the FAA for shared failure data, Grammarly for spec review.
We're not boiling the ocean. The MVP is the catalog with governance solid enough to trust. Early members shape that structure before anything is set.
Beta members shape the catalog's structure, get early access to the Change Feed and Spec Translation before public release, and are credited as founding contributors. Tell us a little about your work.