One record. Two levels that read from it.

Level 01 · Agent

Producers running their own book. Everything an agent tracks by hand today, kept in one place.

• Transactions An agent's active transactions are listed in deadline order, with each date pointing back at the clause it was read from.
• Documents A filed document lands against the right transaction, and the file names what is still outstanding rather than leaving it to memory.
• Deadlines A date becomes a tracked date when a person confirms it against the cited clause. A proposed date is not a tracked date.
• Morning summary A daily account of what changed on the agent's own files. It summarises the record for the agent, and is not sent to anyone else.
• Pipeline activity Lead and message activity appears from the systems the brokerage connects, under written terms.
• Scope of view An agent sees their own transactions and clients, not another agent's business.

Level 02 · Brokerage

Broker and operations staff. The whole office in one view, ordered by what could go wrong first.

• Office view Leadership opens one list of every active transaction instead of asking five people for a status update.
• Workload Each agent's open files and the dates sitting on them, so load is visible before it becomes a missed deadline.
• Exceptions Approaching deadlines, documents that are not in the file, and items with no response are raised for a person to decide on.
• Any file A broker can open any transaction in the office and see the same record the agent sees, including the source of every date.
• Reporting Office-level reporting across the transaction record.
• Broker controls Which systems connect, what may be read from them, and for how long, stays with the broker. Email, calendar and transaction systems are switched on per brokerage under written terms.

1. Documents and communications enterContracts, disclosures and messages arrive by upload and from the systems the brokerage authorises. Nothing connects without broker approval.
2. The record is written, with a citationTerriv reads the dates, obligations and parties out of the executed documents and files them against one transaction, with every item pointing back at the page and clause it came from.
3. Each level reads its sliceThe agent sees their own book. The brokerage sees the whole office. Both read the same underlying record rather than two versions of it.
4. Exceptions rise for reviewA date about to pass, a document that is not in the file, or an item with no response would be put in front of a person. Nothing is designed to be tracked until someone confirms it against the source.

Those four steps describe the intended path, not a running pipeline. Software that reads documents will sometimes miss a date or misread a clause, so a quiet list is only as complete as what the software actually caught.

What exists of this today

• Screens The screens run on sample data and show the two views described above. Every file, name, party and date in them is fictional.
• Demo requests The request form on the demo page posts to a real endpoint that emails us. If delivery is not configured it returns an error and says so, rather than showing a false confirmation. Built

Written terms come before anything of yours moves, a closed file comes before a live one, and a pilot does not start until document reading actually works.