Ask your book a question.
Filter, sort and total any object you have modelled, then save the answer as a view the whole team reads. No export, no pivot table, no ticket for the data team.
From a question to a saved view. Every step happens in the grid your team already works in, against live records rather than last night's extract.
Start from any object.
Submissions, policies, claims, locations. Every object you have configured opens as a grid, and every grid answers the same way.
Filter until it is the question.
Stack conditions, nest them into groups, and drop in a saved segment as a single chip rather than rebuilding it.
Pull columns from two objects away.
Step through a relationship in the column picker and keep going. The join is resolved for you, and the column filters and sorts like any other.
Total what survived the filter.
Sum, average, min, max, or how many rows are still empty, computed over the whole filtered set rather than the page in front of you.
“A carrier question used to mean an export and half a day. Now it is a view, and it is still right next month.”
The views a team builds in week one. Three questions that used to be a spreadsheet, each one a filter and a sort over records you already hold.
What renews in ninety days.
Filter policies by expiration date, sort by premium, and bring the producer across from the account two relationships away. Save it once and it is waiting every Monday.
What is sitting with whom.
Filter submissions by status, add the user column so the queue shows who touched each one last, and sort by how long it has been waiting. The count at the foot moves as the queue does.
Which claims moved this month.
Filter claims to the ones touched since the first, bring the policy and the program across the relationship, and total the amounts at the foot of the grid.
Views your team can trust. A saved view is configuration, so it moves through releases and carries a history like everything else you set up.
Save for everyone
Change a filter for yourself, or push it to the whole team from the same button.
Segments you reuse
Name a filter once and apply it to any view on the same object, instead of rebuilding it condition by condition.
Views bound to a record
A view can require an account or a policy at run time, so one definition serves every record it sits on.
The reports you owe somebody else. Premium and loss bordereaux, produced from your own records on a cadence and reconciled against what comes back.
Map the layout once.
A bordereau template holds the column mapping, the output format and the cadence. Your carrier's spreadsheet stops being something a person maintains by hand.
Produced on a cadence.
Each monthly or quarterly run takes the period, writes one line per policy or per claim, and renders the file. Premium and loss are separate runs, and every run is kept.
Check what comes back.
Bordereaux you receive are matched line by line against your own records. Anything outside tolerance is marked a discrepancy and opens for a person to look at.
One graph, asked every way.
The records you filter are the records the workbench edits and the assistant reads. Nothing is copied into a reporting store overnight.
Bring the report you dread.
Send us the monthly spreadsheet you build for your carrier. We will rebuild it as a saved view on your own records, live.
Usually 30 minutes, with an underwriter on the call.