Your system of record.
The mirror carries every object on the record, including the ones your platform does not list as related, because the relationship graph is discovered by sweep rather than hand picked.
The chase list stops being a question people ask each other.
Every organisation runs on a chase list, and in most of them the list lives in somebody's head and a spreadsheet they update on Fridays. Mayeshal keeps it as a queue that maintains itself: every record where an expected document never arrived, an approval never moved, or an answer never came back, sorted by how long it has been sitting.
Shipped and running in production today
No model call, so no token cost
Sorted by how long it has waited
The problem
Nobody is missing the thing they know about.
Work does not usually go wrong because somebody made a bad decision. It goes wrong because a document nobody chased never arrived, a mandatory field was left blank at the moment the record was opened, an approval sat with someone who was on leave, or a counter offer never got an answer. None of those has an owner, because none of them is an event. They are absences.
The standard response is a report somebody runs once a month, which finds the problem four weeks after it started. A quality record opened in January with the units held not recorded and no closure in the file is not a reporting failure. It is a record that nothing was watching.
This is also the most evidenced request in our research, across every industry we have worked in, and it is the one people describe most consistently in their own words. Somebody always says some version of what I do every month right now is run a report to see if something is missing.
How it works
Define, watch, rank, act.
It runs continuously against the mirror rather than against a query somebody remembers to execute, and it does not call a model, which is why it costs nothing.
- 01
Define what "expected" means here
Outstanding is specific to your business: a certificate that should have come back from a supplier, a form with mandatory fields blank, an engagement letter never returned, a counter offer never answered. The rules are configured against your real records.
- 02
Watch continuously
The mirror is already refreshed on a five minute tick, so the queue is reading current data rather than a nightly extract. The document completeness audit reads the local catalogue for a record in about half a second.
- 03
Rank by age, not by arrival
A queue sorted by how long something has been waiting puts the oldest problem at the top, which is the opposite of an inbox and is the whole point of the component.
- 04
Hand it to a person, or draft the chase
Each row opens the record with the missing item named. Where the next step is a letter or a reminder, the draft assembles from your own language and waits for a person to approve it.
What it connects to
What it watches.
The queue is only as complete as the systems feeding it, so this is what feeds it.
The document catalogue.
What arrived, when, and what should have arrived and did not. The audit reads your own indexed catalogue rather than re-crawling the source system every time somebody asks.
Calendar events and tasks.
Real dates read from real events, because a date field on a record goes stale the moment somebody forgets to update it, and the schedule people actually work to is in the calendar.
Mail, once it is connected.
Whether a request went out, and whether anything came back. The mail connector is authorised in your own tenant during implementation.
Where it matters most
Every industry calls it something different.
Outstanding records, open non conformances, missing client documents, files nobody answered. It is one component underneath.
Legal
Records, deadlines, negotiations and the document file never sit in one place, and the client is asking one question about all of it.
Legal pack, live in productionFinancial services
Client records, a books and records obligation, and an examiner who wants to see what you knew and when.
Pack built and signedProduct and manufacturing
Specification, supplier and quality data spread across systems that were never introduced to each other.
First customer buildAccounting and tax
Client documents arriving as PDFs and email, and a person moving them into a spreadsheet by hand.
First customer build
Said plainly
Where the honest edges are.
It can only see absences in systems that are connected. A document that was expected by email and is invisible to the platform stays invisible until mail is authorised in your tenant, and the queue does not pretend otherwise.
The rules are configured with you rather than authored by you. There is no drag and drop workflow editor today, so changing what counts as outstanding is a configuration task we do together, versioned and logged. Some buyers prefer that. Some do not, and they should know before they sign.
It also does not close anything on its own. It finds the gap and puts it in front of a named person. Where the next step writes back into your system of record, that write is staged and approved before it lands.
Get started
See it read one of your own matters.
Thirty minutes, on a screen share, on a matter you pick. We connect nothing, install nothing and ask for no credentials to have that conversation. If it is not obviously useful in the first ten minutes, we will tell you so and you get your afternoon back.