Awaiting is a status. Aging is the risk.

Most reconciliation dashboards treat "awaiting" as a benign status. The trade has been booked on one side, the other side hasn't attested yet, nothing is explicitly broken. Visually, these items sit in a neutral column, often lower priority than confirmed breaks.

That mental model is the problem. Awaiting is not benign. Awaiting is an SLA clock that nobody has their eye on.

The shape of an awaiting problem

In a healthy bilateral pair, most awaiting items resolve within minutes. One side books, the other side books a little later, both attest, and the item confirms. The awaiting state is a brief intermediate.

In an unhealthy pair, awaiting items accumulate quietly. A trade booked at 8:47 that hasn't been matched by 10:00 is no longer early; it is late. By noon, it is a risk. By end of day, it is a regulatory and accounting problem, especially if the counterparty has booked it differently or not at all.

The cost is not in the individual items. It is in the fact that nobody noticed the shape of the queue soon enough.

Aging buckets, not just timestamps

The right UI primitive for this is aging buckets, not timestamps. A timestamp tells an analyst when an item arrived. A bucket tells them how much of the SLA budget has been spent. Simple bucketing (fresh / warm / hot / SLA) does most of the work.

Once items are bucketed, the shape of the awaiting column becomes visible at a glance. A healthy pair shows a thin tail. An unhealthy pair shows a thickening middle that is on its way to becoming a hot tail.

Shared ownership across the pair

The second failure mode is that awaiting items have no owner. On each side, they sit in a "not yet my problem" state until someone crosses an SLA boundary. Nobody picks them up because nobody is responsible for them yet.

A pair room changes this. Both sides see the same awaiting queue, with the same aging buckets and the same item-level notes. Either side can open an item, leave a note ("we don't have this trade, can you resend your booking?"), and the item moves from ambient risk to actively worked.

The quiet KPI

Most teams track break resolution time because it's visible and breaks are loud. They under-track awaiting resolution time because awaiting items are quiet.

They shouldn't be. Median and 95th-percentile awaiting age, bucketed by counterparty, is one of the strongest leading indicators of operational health in a bilateral OTC book. When it drifts, breaks drift behind it.

Awaiting is a status. Aging is the risk.