Report the drafts and who is late
Table of Contents
This page is a capture in the inbox bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
1. What
A draft now says why it is not live, and the reason names the desk that owns it. A report of drafts would list each one with its age — how long it has sat since it was captured — its reason, and the desk responsible, oldest first.
Nothing reports that today. A draft is a row in the blotter that has not moved, and the only way to find the ones that have sat too long is to read them.
2. Why
The reason and the responsible desk exist so that an aged draft is somebody's work. Without a report they are two columns nobody reads: the desk that should be chasing a confirmation cannot see that a draft has waited a week, and the operations manager cannot see which desk is carrying them.
The trading side already stores what the report needs. What is missing is the report itself, and the reporting side is where it belongs.
3. Shape of the work
Not designed here. The pieces that appear necessary:
- A report definition over the drafts of a party or a tenant: the reference, the kind, the trade date, the age, the draft reason and its responsible desk.
- An age that means something: days since the trade was captured, counting business days against a calendar the tenant already holds.
- A group by desk, since the question the report answers is "who is late", not "what is open".
- Whether a draft that has sat past a threshold raises a notice, which the approval side already knows how to do.
4. What done looks like
A person can read how many drafts a tenant holds, how long the oldest has waited, and which desk owns each one, without opening a single deal.
5. References
ores_trading_trades_tbl— the draft reason the report reads, and the trade date its age counts from.- ores.trading.draft_reason — the lookup that names the desk.
6. See also
- Add a draft reason and a structure hold — the task that stores what the report reads.