Tessera
tessera · noun, feminine · a small tablet; the token bearing the watchword
Every compliance request is passed from hand to hand and comes back answered — and you can see exactly where each one is.
Castrum Tessera is in early access. We’re rolling it out with a small group of lenders first — ask us about joining.
In the castrum
The watchword always came back.
Each evening a soldier called the tesserarius collected a wooden tablet — the tessera — inscribed with the night's watchword, and carried it from the tribune to the commander of the next unit. That commander passed it to the next, and so on through the camp, each one marking it, until it came back to the tribune before dark.
When every tablet had returned, the tribune knew the watchword had reached every unit. If one was missing, the marks told him exactly where the chain had broken, and who was answerable for it.
— As described by Polybius, Histories 6.34
In your company
Policy questions and exception requests tend to live in inboxes and hallway conversations, where they get lost. Castrum Tessera gives each one a ticket, passes it to the right person, records every status change, hand-off and reply, and shows you the moment one is overdue.
How it works
Four steps. Every time.
- Petitio
Raise
Your team logs a request in the workspace, on behalf of whoever asked, and it becomes a ticket with a due date.
- Traditio
Route
It's triaged and assigned to the person who owns the answer.
- Responsum
Work
Your team works it with internal notes, and replies by email to the requester, who answers straight back onto the ticket.
- Reditus
Return
It's resolved and closed. Every status change, assignment and reply is kept in a history that can't be edited.
Step by step
See what happens at each step.
A quick look at the screens your team actually uses.
Every ask becomes a ticket.
Your team logs a policy question, exception request or support request on behalf of whoever asked. It gets a type, a priority and a due date.
What's inside
Castrum Tessera, piece by piece.
Built for compliance requests
Policy questions, exception requests and general support, each tracked as its own type — and none can be closed without its outcome: the answer and the policy it rests on, or a resolution code.
Exception approvals with an expiry
An exception is approved or denied with a rationale, its scope and compensating controls, and an expiry no more than 12 months out. The person who asked can't approve their own, and expiring exceptions are easy to find.
An SLA clock that tells the truth
Every ticket gets a due date by priority. The clock pauses while you wait on the requester, and a ticket that went late stays marked late.
A history you can show an examiner
Status changes, hand-offs, priority changes, notes and replies are recorded as they happen and can't be edited. Export the register to CSV, or any ticket to a PDF report with its full history.
Email as a channel
Reply to requesters from the ticket by email. Email intake — your own address that turns incoming mail into tickets, with replies threading back — is being set up.
Internal notes vs replies
Keep the working discussion internal, and send only what the requester should see.
One queue for everything
Tickets sit alongside ad reviews, complaints and agreements in a single queue, so nothing waits unseen.
The rest of the castrum.
Every product shares the same review queue, audit trail and records. See the platform.
Make sure every question comes back answered.
We'll walk through compliance ticketing with your team's real use cases, and build a package around what you need.