The pair room: a better model for bilateral OTC exceptions

OTC post-trade operations is bilateral by nature. A trade is a relationship between two counterparties, and a break is a conversation between their two ops desks. But the tools that support that work are overwhelmingly unilateral — each side has its own queue, its own status, its own view of "the trade", and the two views are reconciled through chat, email, and spreadsheet attachments.

We've been describing an alternative as a pair room.

What a pair room is

A pair room is a shared operating surface scoped to a specific pair of counterparties. Both sides see the same queue of matches, the same status, the same aging, the same notes, and the same canonical attestations.

The core move is that the pair room is not either side's system. It is a shared view over state that both sides have attested. Identity is derived deterministically from canonical terms, so the pair room doesn't need to pick sides or act as a system of record. It is a lens, not a database of truth.

What goes in it

• Attestations. Each side's canonical trade terms, submitted via their own systems and identity-derived.
• Matches. Confirmed items where both Sigrids agree.
• Breaks. Items where Sigrids disagree, with the field-level diff attached.
• Awaiting items. Items where only one side has attested and the aging clock is running.
• Notes. Ops-to-ops notes on individual items, visible to both sides.
• Lineage. The timeline of amendments and novations that connect related Sigrids.

What it replaces, and what it doesn't

The pair room replaces ad hoc email and chat for break triage. It also replaces the side-of-the-trade ambiguity that reconciliation tools inherit from running on top of unilateral views.

It does not replace the OMS, the trade booking systems, the allocation workflow, or the regulatory reporting pipeline. Trades are still booked where they are booked today. The pair room is downstream of booking and upstream of regulatory reporting — it is specifically the shared workbench for bilateral exception resolution.

Why this is harder than it sounds

Shared operational surfaces are easy to describe and hard to build. They require:

• A canonical form both sides can agree on.
• Signed attestations so neither side can silently mutate the other's view.
• Role-aware access so confidentiality between desks is preserved inside each firm.
• A trust model that doesn't rely on either counterparty trusting the other's infrastructure.

Get those right, and the pair room quietly removes most of the friction of bilateral OTC exceptions — not by speeding up any individual step, but by eliminating the coordination tax between steps.