For carriers
The Carrier Portfolio page is where a carrier organization works its book: released reports across insureds, deadlines that need attention, decisions waiting for a second approver, and a feed of rating-relevant events. It shows consent-scoped snapshots only, never an insured's live data.
Becoming a carrier
Carrier access is a vetted platform action, not a setting. Until SolveGRC has enabled your organization as a carrier, the page shows Carrier access required and nothing else, whatever roles your users hold. Onboarding an insured (the invitation, and the agreement versions you send) is set up with SolveGRC as part of your carrier program today; the portfolio page takes over once an insured has accepted.
The portfolio
The top of the page summarizes the book: active insureds, the average score across those with a released report, how many sit in the high or critical band, and the most recent release. The Portfolio list shows each insured's latest released headline (score, band, confidence, date) and its relationship state. Selecting an insured opens everything below for it.
Released disclosures lists that insured's reports by release date with score, confidence and a degraded marker where inputs were stale. Open one to read the full packet: the same view the insured previewed before release, described in What your carrier sees. The download button fetches a self-contained document rendered from the frozen snapshot. SolveGRC re-verifies the stored document against its recorded hash before it issues a link, and a mismatch is refused and logged on both audit chains.
Every view and download you make is written to both organizations' audit chains, and the insured sees your reads on its own page.
Release mode
Per agreement, reports release automatically on the agreed cadence, or you can require manual release. In manual mode a generated report is held and appears under Awaiting release decision with its period and generation date. A user with an elevated role can request a release or a withhold with a reason; a different person must approve it under Pending release decisions. The requester cannot approve their own request. A decision left waiting past two days raises a nudge to your administrators.
Manual mode only ever delays or withholds a report. It cannot change what a report contains, and it does not need the insured's consent because it never widens disclosure.
Deadlines and grace
The Deadline workbench at the top gathers obligations across the book that need attention: reportable failures first, then open grace and pending extensions, then anything due within 14 days. Selecting one opens that insured.
Under Obligations and grace for the selected insured you can Offer extension on an obligation in grace or already extended, giving a new due date, and Declare time's up on a reportable failure. The declaration is accepted only once the ledger shows the grace clock has run out and the recorded notice has aged past the agreement's minimum; the ledger decides, not the caller. Pending extension requests lists insureds asking for more time, with their proposed date and reason, for you to grant or decline.
The Extension auto-grant policy per agreement grants requests automatically when they ask for no more than the days you allow, and no more often than the count you allow, without reaching your queue. Set both to zero to review every request.
The same ledger is described from the insured's side in Obligations and grace.
Rating feed and underwriting signals
The Rating feed lists events worth an underwriter's attention: band improvements and deteriorations, breaches, cures, withheld reports, and rebaselines. Each is emitted once, only after a baseline exists, and deduplicated, so the feed does not repeat itself.
Underwriting signals for the selected insured are computed from its released reports and rating events only: score trajectory with a sparkline, volatility, average time from breach to cure, band moves, current confidence with the share of degraded reports, and breach recurrence. They are signals, not prices. Pricing rules, eligibility decisions and machine feeds to underwriting systems stay outside SolveGRC pending carrier counsel review.