For Florida law firms

The firm's own conflict registers: declined parties, prior affiliations, joint representation

firm lane · Deterministic — no model call

Current availability

ShippedConfigured and enabled: the firm's governance roles.

Where it lives: Firm settings → Conflicts (/firms/manage/conflicts) · /api/firm/conflicts
What unlocks it: the firm's governance roles (firm admin, firm attorney, firm paralegal); a platform administrator does not write a firm's register

Status is evaluated against this deployment's configuration by the capability-status service at build time; the catalogue's facts were last reviewed on the date shown.

Capabilities

ShippedThe declined register: people and organizations the firm declined to represent (a declined consult request lands here too); a match is a declined finding that holds the engagement.
ShippedMembers' prior affiliations: a member's prior clients and prior firms (a lateral hire's history), screened on every intake.
ShippedAn entry is withdrawn on the record with who, when and why — never edited, never deleted.
ShippedThe joint-representation policy: when on, an attorney's determination of a joint representation needs the date the clients consented in writing.

Limits

No Bar number and no licence field is asked for or kept.
A prior affiliation is shown for review; it holds nothing by itself.

What EstateDraftFL refuses

Reason code	HTTP	What it means
invalid-name	400	Give the person's or organization's full name (up to 200 characters).
not-a-member	400	An affiliation names a member of this firm.
not-open	409	That entry is not on this firm's register, or was already withdrawn.
joint-consent-required	400	The firm records the clients' written-consent date for joint representation.

Evidence

src/app/api/firm/conflicts/route.ts
src/app/firms/manage/conflicts/page.tsx
src/components/conflicts/FirmConflictControls.tsx
src/app/api/admin/conflict-check/route.ts
docs/security/MASTER-PLAN-PHASE9-2026-09-26.md

Last reviewed 2026-09-26

← All surfaces