The ready-made dashboards
Each one is a laid-out set of charts from the library, sized for a 12-column grid and ordered so the headline numbers sit at the top.
Browse templates. Each card shows the dashboard's layout, who it is built for and the jobs it covers.
Every dashboard in detail
Executive TPRM Overview
The one-screen answer to how third-party risk is trending: portfolio size, risk mix, assessment throughput and where the gaps are.
Executive TPRM Overview. Built for executives and the board.
Vendor Risk Portfolio
The portfolio in depth: risk tiering, domain exposure, growth and how the book is split across analysts.
Vendor Risk Portfolio. Built for risk analysts and the TPRM lead.
Assessment Operations
Run the assessment queue: volume, outcomes, who is loaded and whether high-risk vendors are getting the scrutiny they should.
Assessment Operations. Built for assessment team leads.
Cycle Time & SLA
Where the time goes. Median and tail cycle times, the phase-by-phase breakdown, and the outliers that break an SLA.
Cycle Time & SLA. Built for program managers tracking SLAs.
Contract Spend & Renewals
Committed spend, where it is concentrated, and the renewal runway: the view to take into a negotiation.
Contract Spend & Renewals. Built for procurement and vendor managers.
Savings & Value Capture
What the program saved, where it came from, and how much of it landed rather than staying on paper.
Savings & Value Capture. Built for procurement leadership and finance.
Third-Party Exposure
Risk and money on one screen: how much spend sits with high-risk vendors, and which of them carry the open control gaps.
Third-Party Exposure. Built for risk and finance leaders.
Intake & Demand
The front of the funnel: what the business is asking for, where requests stall, and the assessment load coming next.
Intake & Demand. Built for intake owners and program managers.
Control Assurance
Which controls and frameworks vendors fail, how that is trending, and the vendors carrying the most gaps.
Control Assurance. Built for control owners and compliance.
Tag & Ownership Coverage
Data-quality and accountability: what is classified, what is owned, and which segments are quietly going unassessed.
Tag & Ownership Coverage. Built for TPRM program owners.
Monthly Executive Report
Built to be exported into a monthly pack: portfolio size and tier mix, findings raised against findings resolved, assessment effort by tier, and where the remediation sits.
Monthly Executive Report. Built for executives and the board.
Findings and Remediation
The remediation book end to end: what is open, what closed, how severe it is, where it came from and who owes the work.
Findings and Remediation. Built for the TPRM lead and risk analysts.
Supplier Tier Review
Everything sliced by supplier tier, for a program that has to show its effort and its exposure follow criticality.
Supplier Tier Review. Built for the TPRM lead and the risk committee.
Relationship Owner Accountability
The business owner’s view: how many suppliers each owner is accountable for, the assessments run on them, and the remediation they owe.
Relationship Owner Accountability. Built for business relationship owners and their leadership.
Radar Signal Triage
What Radar raised about your vendors, where each signal stands, and which detectors and vendors keep the queue full. It opens on the last three months.
Radar Signal Triage. Built for analysts triaging Radar signals and the TPRM lead.
The chart library
The dashboards above draw on 93 of the library’s charts. Every one of them is also available on its own, along with 17 more that no packaged dashboard uses. Open Chart library from a dashboard, search or pick a shelf, select as many as you want, and they are added below whatever is already on the grid, so an add never lands on top of a widget you positioned. Charts are filed by the question they answer, not by the table the data comes from, so a spend chart and a vendor chart can sit on the same shelf if they answer the same question.
The chart library. Shelves across the top, cards in the middle, and the selected chart drawn against your own data on the right.

Chart cards in the library. Each one previews the shape of the chart, says what it shows, and lists the jobs it is meant for.
What is on each shelf
Risk posture · 18 charts
Risk posture · 18 charts
Throughput & outcomes · 12 charts
Throughput & outcomes · 12 charts
Cycle time & SLA · 11 charts
Cycle time & SLA · 11 charts
Workload & ownership · 14 charts
Workload & ownership · 14 charts
Spend & renewals · 16 charts
Spend & renewals · 16 charts
Savings & value · 9 charts
Savings & value · 9 charts
Control assurance · 20 charts
Control assurance · 20 charts
Intake & demand · 7 charts
Intake & demand · 7 charts
Coverage & data quality · 3 charts
Coverage & data quality · 3 charts
What you will and will not see
The library hides templates your workspace cannot fill, so you never add a chart that can only ever render empty.Making them yours
A template is a starting point, not a fixed report. Once a chart is on your dashboard:- Retitle it. The shipped names are descriptive, not fixed. “Median Assessment Cycle Time” may be “Time to clear a vendor” in your program.
- Change the slice. Most charts group by one dimension and split by another. Swapping either (tag, department, analyst, risk tier, quarter) usually gets you a different question answered by the same chart.
- Resize and rearrange. Drag any widget; the grid reflows around it.
- Set the date range on the dashboard rather than per chart. Every chart on it follows.
- Mix shelves freely. Nothing stops a savings chart sitting next to a cycle-time chart if that is the story your review needs.
Use the library from MCP or the API
You can browse the library and copy dashboards and charts from an MCP client or with an API key. An MCP client reads withquery_platform(kind="dashboard_library") and writes with mutate(entity="report", action="apply_template") and mutate(entity="report", action="add_chart_templates"). The API routes are GET /v1/dashboard-templates, POST /v1/dashboard-templates/{template_slug}/apply and POST /v1/reports/{report_id}/chart-templates. See Dashboard templates and exports.
Before an MCP client sends a write, it shows you the change and waits for you to confirm it. The MCP tool reference lists every field.
Browsing the library needs report:read:org, which organization API keys hold. Copying a dashboard or adding charts needs report:create:org or report:update:org. API keys do not hold those, so for that use a key created by a person whose role holds it.