Portfolio data health, checked against your rules.

What it does

For every company in your portfolio that is categorised as a “Portfolio Company,” the agent checks four things, in order.

1. Has the company submitted its KPIs for the most recently completed period? Quarterly, by default. If not, this is flagged as a blocking issue.
2. Are the required documents on file? The agent checks whether the documents attached to the company’s most recent KPI submission match the list of documents your fund requires.
3. Has a valuation been entered for the same period? If not, this is also flagged as blocking.
4. Should a reminder go out? If any items are still missing and reminders are turned on, the agent emails the portfolio company a single consolidated reminder listing exactly what is missing — but never more than once per day.

This agent never makes a call to an AI model, so you do not need an AI provider key for it to work. It also powers a few of the sample chat questions you will see on a portfolio company’s page — “Show latest KPIs,” or “What’s the current valuation?” — but that is a separate conversational feature, not the run-and-report behaviour described here.

What it needs

Four settings control the agent.

Field	Default	What it controls
Reporting Period	Quarterly	How often companies report: Monthly, Quarterly, Half-Yearly or Annually.
Start Checking After	15 days	How many days after a period ends before the agent begins checking.
Stop Checking After	60 days	How many days after a period ends before the agent stops checking and stops sending reminders.
Send KPI submission reminder	Yes	When Yes, sends a consolidated reminder email listing all missing items — KPIs, documents and valuations.

The older “Reminder days” setting — comma-separated day offsets such as “7,14,21” — is no longer used. Reminders are sent on every agent run inside the active window, so cadence is governed by the agent’s Schedule tab rather than by a list of dates. Re-running Setup All Agents fills the reminder toggle with its default on agents that never had it.

The agent’s General tab shows a yellow warning banner when reminder setup cannot work. The case it flags is a “Send KPI submission reminder” toggle that was never set: an unset toggle counts as off, so reminders silently never go out. Set it explicitly to Yes or No — an explicit No is not flagged.

Alongside that configuration, the agent reads three kinds of record:

• The company’s submitted KPI reports — used to find the latest submission for the period, and, through that report’s attachments, for the document check.
• The company’s uploaded documents — compared against your fund’s required-documents list.
• The company’s valuations — used to find a recent valuation within the period.

Turning it on

A Company Admin turns the agent on or off in the administration area, under the entity’s support agents settings. While it is off, the Run Now button and the matching trigger on a company’s page stay disabled. No AI provider key is needed.

Only users with the Company Admin role can configure and run support agents from the main Support Agents screen. When the agent is triggered from a portfolio company’s own page instead, it follows that record’s normal edit permissions.

Unlike most agents, this one is not created from scratch when you run Setup All Agents — it has been part of the product since before that setup flow existed and is provisioned separately. Running Setup All Agents only fills in the “Send KPI submission reminder” and “Reminder days” fields if they are missing; it will not create the agent if it is not already there.

Running it

• From the agent’s own page. Open the Portfolio Company Agent card under AI → Support Agents and click Run Now on the General tab. This agent’s natural scope is the whole portfolio, so a run from here processes every portfolio company in one batch, with no step-by-step view per company.
• From a single portfolio company’s page. Use Run Portfolio Agent from the company record. This runs the agent for that one company, and shows a live progress panel walking through each check: KPI Submission Check, Document Presence, Valuation Check, Send Reminder, Save Report.
• From the Portfolio Agent Run screen. Filter your portfolio companies by tag, sector or name, select one or more from the table, and run the agent on the selected companies. That queues a single batch job. There is no per-company progress view here either — you get one summary notification once all the selected companies have been processed.

A fund-wide or batch run processes every portfolio company in sequence. If one company hits a problem it does not stop the rest from being checked, and the portfolio dashboard refreshes once at the end for everything that succeeded.

Scheduling

The agent has the standard Schedule tab — frequency, run time, timezone and notification toggles — and you can set up a recurring schedule as with any other agent. Setup All Agents does not turn on a default schedule for this one, so if you want it to run automatically you have to configure that yourself. Scheduled runs always process the whole portfolio in one batch, and they skip the summary notification, since nobody is actively waiting on the result.

Where the output goes

• General tab. A “View Report” link to the most recent run.
• Execution History tab. Every past run, manual or scheduled, with its status and duration; open any row for the full report.
• Portfolio Agent Reports tab. On this agent’s own page, reports organised by the portfolio company they belong to.
• Portfolio Company Dashboard. A standalone dashboard reached from the Investors menu, with stat cards, a compliance chart, a searchable company table and a Send Reminders action.

Each report is attached to the portfolio company it covers, and the most recent run per company is always the one marked as current.

Reading the result

Each report has three groups of findings.

• KPI findings. Submission status and reminder outcome for the period. A successful submission, or a note that no reminder was due yet, shows as a success. A missing submission shows as blocking.
• Document findings. One entry per required document that is missing, shown as blocking — or a single success entry if everything required is present.
• Valuation findings. Either a recent valuation was found, which is a success, or none was found, which is blocking.

The report’s overall status is ready if nothing across all three groups is blocking, or blocked if anything is. That status feeds the Completed, Partial and Failed badges in Execution History.

The summary widget on the portfolio company page pulls three counters straight from these findings: how many KPI issues are blocking (“Missing KPIs”), how many valuation issues are blocking (“Missing Valuations”), and how many documents are flagged as missing (“Missing Documents”).

The portfolio dashboard

A standalone dashboard, separate from the agent’s General tab, gives a view of the whole portfolio’s compliance health. The first row of stat cards covers Total Companies (everything categorised as a Portfolio Company, whether or not the agent has run against it), Validated (companies the agent has checked, with a percentage bar for how much of the portfolio has been processed), Up to Date (zero blocking issues across KPIs, valuations and documents) and Not Yet Validated. The second row breaks the issues out: KPI Not Submitted, Valuation Missing and Documents Not Uploaded. Where the documents figure shows zero but KPIs are overdue, the card’s subtitle explains that the document check requires a KPI submission first. Every card is clickable and filters the table below it.

The company table can be filtered by status — All Statuses, Up to Date, Has Issues, KPI Not Submitted, Valuation Missing, Documents Not Uploaded — searched by company name, and expanded row by row for the full KPI, document and valuation breakdown. It paginates at ten companies per page.

Three actions sit on the dashboard. Run Validation triggers the agent across all portfolio companies as a batch and the dashboard refreshes when it completes. Send Reminders emails companies with any missing items, listing only what is missing for that company; it deduplicates, so a company already reminded today is skipped, and the button label shows the exact count of companies that will receive a reminder. Afterwards you see either “Reminders sent to N companies” or “Reminders were already sent today.” View Pending Issues filters the table to companies with at least one blocking issue. A “Send Now” shortcut in the Recommended Next Steps section at the bottom of the dashboard does exactly the same thing as Send Reminders.

The dashboard simplifies each company to one of three statuses: Up to Date (the agent ran and found zero blocking issues), Has Issues (the agent ran and found at least one) and Not Validated (the agent has not processed this company yet).

Where it can fail

• No KPI report on file means the document check is skipped, not failed. If the agent cannot find a KPI submission for the period, it deliberately skips the document check rather than reporting a confusing “document missing” message against a submission that does not exist. The missing-KPI flag is then the only signal you see.
• The wrong category on a company causes a silent skip. If a company’s category is not set to “Portfolio Company” (case-insensitive), the agent stops before doing anything and records no findings at all — just a quiet log entry your technical team could look up. This happens when someone changes a category partway through, or a run is pointed at the wrong record.
• Reminder timing follows the checking window, not a calendar date. Reminders go out on every run inside the active window. If the agent is scheduled weekly, companies get at most one reminder per week. The window boundaries are calculated using the application’s configured time zone, not necessarily yours or your server’s, which can cause a one-day difference around period boundaries.
• “Already sent today” tracking depends on having a prior report. The agent checks the most recent report to see whether a reminder already went out today. If reports have been deleted, or the entity is brand new with no report history, there is nothing to compare against — so a reminder could go out again on a day it normally would not have.
• Changing the reporting period affects all three checks. KPIs, valuations and documents are all checked against the same period. There is no way to use different periods for different check types.
• One company’s failure during a batch run is easy to overlook. The rest of the batch keeps going, but that failure shows up only in the batch summary notification, not as its own failed report, unless that company’s individual run also produced one.

Questions