Board and committee reporting your directors can trust.
Directors get a committee-scoped, read-optimized oversight surface with lineage back to the source.
| Pack section | Source | Status |
|---|---|---|
| §1 Risk posture | Risk register · KRIs | Traced |
| §3 Exam status | Exam prep · Findings | In review |
| §5 Consumer compliance | CMS scorecard · Complaints | Attention |
| §7 Model risk | Model inventory · Governance | Traced |
A committee-scoped board portal
The board portal is read-optimized and scoped by committee: directors see only the committees they sit on, and a pack is sealed once it is approved.
- 01Access is set per committee, so nobody sees material outside their mandate.
- 02The read-first surface is built for directors rather than operators.
- 03Packs are sealed on approval, so the record cannot drift.
Board packs with claim lineage
Every figure and assertion in a board pack links back to the source record it was drawn from, so a director can trace a claim instead of taking it on faith.
- 01Each pack claim carries lineage to its underlying record.
- 02The lineage panel shows the path from claim to source.
- 03Numbers stay reconcilable to the systems they came from.
Decision register and advisory log
Governance decisions are recorded as they are made in the Decision register, which sits in the Risk group of the sidebar. The Advisory log in the Compliance group records self-identified items. Together they are a durable memory of what the board decided and what it was told.
- 01The Decision register in the Risk group captures each governance decision.
- 02The Advisory log in the Compliance group records self-identification and guidance.
- 03Governance configuration sets committees and cadences.
The obligations calendar
Board and committee obligations, including filings, reviews, approvals, and attestations, sit on one calendar so nothing owed to a regulator or a committee slips.
- 01Filings, reviews, and approvals share one calendar.
- 02Each obligation links to the owner accountable for it.
Board-portal connectors
Zovos sits alongside the portal your board already uses and delivers approved packs and materials to it, rather than asking directors to learn a new tool.
- 01Connectors cover BoardEffect, OnBoard, and Diligent Boards, plus FDICconnect and NCUA MERIT.
- 02BoardEffect receives approved packs by API, published into a workroom library with the publish history kept.
- 03OnBoard, Diligent Boards, FDICconnect, and NCUA MERIT have no public write API. For those, Zovos builds a package with a hashed manifest that you download and upload yourself.
Grounded in shipped behaviour.
- 3 board-portal connectors (BoardEffect, OnBoard, and Diligent Boards), plus FDICconnect and NCUA MERIT regulator portals.
- Every board-pack claim carries lineage back to its source record.
- The shared corpus behind the reporting holds 54 frameworks and 754 citations.
Counts come from the platform's regulatory corpus, connector registry, and seed template library at release. See the documentation for the current values.
Questions, answered first.
- Can directors trust the numbers in the pack?
- Yes. Every claim in a board pack links back to the source record through the lineage panel, so a figure can be traced to where it came from rather than just read.
- Is the board portal committee-scoped?
- Yes. Directors see only the committees they sit on, and packs are sealed once approved so the record cannot change after the fact.
- What is the decision register?
- It is an append-only record of governance decisions, in the Risk group of the sidebar. It sits alongside an advisory log of self-identified items and an obligations calendar of what the board owes and when.
- Which board portals does Zovos integrate with?
- Zovos integrates with BoardEffect, OnBoard, and Diligent Boards through three board-portal connectors, plus the FDICconnect and NCUA MERIT regulator portals. BoardEffect receives approved packs by API. For the other four, Zovos builds a package with a hashed manifest that you download and upload yourself.
See board reporting on your library.
Bring your controls, a policy, and one regulator paragraph that gives you trouble. We target two-week onboarding.