A self-monitoring portfolio is a portfolio where the monitoring work runs inside the firm's system of record without waiting for a person to start it. A document lands, the numbers are extracted the firm's way, the checks run, and what moved is staged for review. The team's time goes to the decisions with the data. The portfolio monitors itself. You manage it.
The term describes the fund's own portfolio. The portfolio companies keep reporting the way they always have. Lumonic starts the monitoring work when a document arrives, so the firm does not have to wait for someone to begin the next review.
Why portfolio monitoring is still a human workflow
Excel was the original portfolio monitoring tool. Analysts entered reported numbers in Excel and applied their firm's definitions before reviewing the portfolio.
Gen 1.0 platforms put spreadsheet numbers on the internet.
Gen 2.0 platforms added tooling for the manual workflows of portfolio teams, including data extraction and dashboards. Excel plugins, APIs and Model Context Protocol connections (MCPs) give people more ways to work with the data.
The software got better, but the workflow stayed human. Gen 3.0 adds a 'power user' in the platform that runs monitoring inside the same system of record. Lumonic carries the firm's decisions about reported numbers into the next review, starts configured jobs when documents arrive, and stages changes for approval. Each generation builds on the tools that came before it.
The three problems a self-monitoring portfolio answers
Context can live in people's heads. Two analysts may calculate different adjusted EBITDAs from the same reporting pack if they treat an add-back differently. Lumonic carries forward the firm's calculation rule, including whether the agreement permits that add-back, for the next pack.
Every portfolio question can become a project. Once the data is collected, someone still has to assemble the answer and check its sources. A portfolio team can request a report in plain English through Lumonic and receive an output with the source page behind each number, in Lumonic, Excel, or through MCP.
Nobody is on call for the portfolio when each review depends on someone starting it. Lumonic can run a configured job when a document arrives or a number changes, check what moved, and stage proposed changes for review.
How the loop works
A Lumonic monitoring job moves from a trigger to a proposed record update in five steps.
A job starts. A document arrives, a schedule fires or you ask in chat.
The power user works. Lumonic's power user reads the documents and proposes numbers using the same tools your team uses. It follows your firm's permissions and extraction rules.
Lumonic checks the work. Lumonic checks proposed changes for restatements, missing values, changed mappings and formula health. Each change comes back as a proposal.
You approve. You can review each run before publishing. You can also set rules that allow automatic publication when every required check passes.
The record updates. Dashboards, Excel, deliverables, and the MCP read the same published numbers. Events in the record can then start the next job.
Where approvals sit
Your approval policy determines when proposed changes can be published. Lumonic stages them for review, and you can publish them yourself or set rules that permit publication when the required checks pass.
Kevin Hsu, Lumonic CEO, describes where a firm's approval policy applies.
“You decide how much of this runs on its own and where manual approvals sit. Some teams review every publish. Others set the rules, let the health checks publish when nothing fails, and only look at exceptions. Depending on your internal controls like maker-checker sign-off or SOX documentation, the approval steps go where your policy puts them, and every step Lumonic takes is logged for review.”
Maker-checker review means one person prepares a change and another reviews it before publication. Lumonic keeps proposed changes separate from published data and logs the steps taken. Your policy determines where maker-checker review is required.
How Lumonic monitors the portfolio
Lumonic introduced Lumonic 12.0 as the self-monitoring portfolio. You can attach a document in chat for data extraction under your firm's rules or ask a portfolio question there. Lumonic stages proposed values in a review queue under your approval rules. Lumonic can also draft reporting requirements and covenants from a credit agreement for review.
By the time the portfolio team logs in, Lumonic has extracted the previous night's documents and staged what needs attention. Lumonic stages new values and restatements for review. The firm publishes them, or its configured approval rules permit publication when the required checks pass. Every published number traces to its source page.
Lumonic's team sets up workflows with you so jobs can run when documents arrive or schedules fire.
Published customer outcomes
For Avante Capital Partners, portfolio review prep went from two to three weeks to two to three days. Trinity Capital traces every questioned number back to its source document.
Lumonic built its system of record over 3.5 years and 12 major releases. Roughly 60% of the private credit funds still run monitoring in spreadsheets. By Lumonic's estimates, spreadsheets start to become difficult to manage at around 20 to 40 borrowers as reporting cycles add documents and calculation decisions to carry forward.
Frequently asked questions
Does a self-monitoring portfolio mean the borrower monitors itself? No. The portfolio companies keep sending their reporting packs the way they always have. The portfolio monitors itself. You manage it.
What is the power user? Lumonic calls the part of the platform that runs monitoring on your behalf the power user. It uses the same tools your analysts use and follows your firm's permissions and extraction rules. Proposed numbers are staged for review, with each number traced to its source page.
Does anything reach the record without a person approving it? Yes, if your firm's rules permit publication when every required check passes. Otherwise, you review the staged changes and publish them. Lumonic logs the steps taken in either path.
How does Lumonic run portfolio monitoring? Lumonic supports data extraction from chat, portfolio questions in chat, and a review queue with a publish gate. It also supports firm-specific extraction rules, credit-agreement parsing, and MCP connections. Lumonic's team sets up workflows with you.
How is this different from Excel plugins, dashboards and an MCP? Excel plugins, dashboards and an MCP give you ways to use published numbers. A configured Lumonic monitoring job can start when a document arrives or a record event occurs. Lumonic checks proposed changes and stages them for review before the published record updates.
Test it on your own documents
Give Lumonic the documents from your last reporting cycle. Lumonic will run data extraction on your own documents so you can check every number against the page it came from. Hold anyone else you're evaluating to the same test.
Disclaimer
This article was written by Lumonic, a PitchBook company, and reflects Lumonic's views as of October 2026. Statements about third-party products and companies are based on publicly available information, including the vendors' own websites, press releases and documentation, and on the sources linked in the text. Lumonic has not independently tested third-party products, and their capabilities, pricing and positioning may have changed since this article was last updated. Statements about Lumonic's own product describe the platform at the time of writing, and customer outcomes are taken from the published customer stories linked in the text. Nothing here is a guarantee of results. Third-party names and trademarks belong to their respective owners and are used for identification only. If you represent a company named here and believe a statement is inaccurate, contact support@lumonic.com and Lumonic will review and correct it.
A self-monitoring portfolio is a portfolio where the monitoring work runs inside the firm's system of record without waiting for a person to start it. A document lands, the numbers are extracted the firm's way, the checks run, and what moved is staged for review. The team's time goes to the decisions with the data. The portfolio monitors itself. You manage it.
The term describes the fund's own portfolio. The portfolio companies keep reporting the way they always have. Lumonic starts the monitoring work when a document arrives, so the firm does not have to wait for someone to begin the next review.
Why portfolio monitoring is still a human workflow
Excel was the original portfolio monitoring tool. Analysts entered reported numbers in Excel and applied their firm's definitions before reviewing the portfolio.
Gen 1.0 platforms put spreadsheet numbers on the internet.
Gen 2.0 platforms added tooling for the manual workflows of portfolio teams, including data extraction and dashboards. Excel plugins, APIs and Model Context Protocol connections (MCPs) give people more ways to work with the data.
The software got better, but the workflow stayed human. Gen 3.0 adds a 'power user' in the platform that runs monitoring inside the same system of record. Lumonic carries the firm's decisions about reported numbers into the next review, starts configured jobs when documents arrive, and stages changes for approval. Each generation builds on the tools that came before it.
The three problems a self-monitoring portfolio answers
Context can live in people's heads. Two analysts may calculate different adjusted EBITDAs from the same reporting pack if they treat an add-back differently. Lumonic carries forward the firm's calculation rule, including whether the agreement permits that add-back, for the next pack.
Every portfolio question can become a project. Once the data is collected, someone still has to assemble the answer and check its sources. A portfolio team can request a report in plain English through Lumonic and receive an output with the source page behind each number, in Lumonic, Excel, or through MCP.
Nobody is on call for the portfolio when each review depends on someone starting it. Lumonic can run a configured job when a document arrives or a number changes, check what moved, and stage proposed changes for review.
How the loop works
A Lumonic monitoring job moves from a trigger to a proposed record update in five steps.
A job starts. A document arrives, a schedule fires or you ask in chat.
The power user works. Lumonic's power user reads the documents and proposes numbers using the same tools your team uses. It follows your firm's permissions and extraction rules.
Lumonic checks the work. Lumonic checks proposed changes for restatements, missing values, changed mappings and formula health. Each change comes back as a proposal.
You approve. You can review each run before publishing. You can also set rules that allow automatic publication when every required check passes.
The record updates. Dashboards, Excel, deliverables, and the MCP read the same published numbers. Events in the record can then start the next job.
Where approvals sit
Your approval policy determines when proposed changes can be published. Lumonic stages them for review, and you can publish them yourself or set rules that permit publication when the required checks pass.
Kevin Hsu, Lumonic CEO, describes where a firm's approval policy applies.
“You decide how much of this runs on its own and where manual approvals sit. Some teams review every publish. Others set the rules, let the health checks publish when nothing fails, and only look at exceptions. Depending on your internal controls like maker-checker sign-off or SOX documentation, the approval steps go where your policy puts them, and every step Lumonic takes is logged for review.”
Maker-checker review means one person prepares a change and another reviews it before publication. Lumonic keeps proposed changes separate from published data and logs the steps taken. Your policy determines where maker-checker review is required.
How Lumonic monitors the portfolio
Lumonic introduced Lumonic 12.0 as the self-monitoring portfolio. You can attach a document in chat for data extraction under your firm's rules or ask a portfolio question there. Lumonic stages proposed values in a review queue under your approval rules. Lumonic can also draft reporting requirements and covenants from a credit agreement for review.
By the time the portfolio team logs in, Lumonic has extracted the previous night's documents and staged what needs attention. Lumonic stages new values and restatements for review. The firm publishes them, or its configured approval rules permit publication when the required checks pass. Every published number traces to its source page.
Lumonic's team sets up workflows with you so jobs can run when documents arrive or schedules fire.
Published customer outcomes
For Avante Capital Partners, portfolio review prep went from two to three weeks to two to three days. Trinity Capital traces every questioned number back to its source document.
Lumonic built its system of record over 3.5 years and 12 major releases. Roughly 60% of the private credit funds still run monitoring in spreadsheets. By Lumonic's estimates, spreadsheets start to become difficult to manage at around 20 to 40 borrowers as reporting cycles add documents and calculation decisions to carry forward.
Frequently asked questions
Does a self-monitoring portfolio mean the borrower monitors itself? No. The portfolio companies keep sending their reporting packs the way they always have. The portfolio monitors itself. You manage it.
What is the power user? Lumonic calls the part of the platform that runs monitoring on your behalf the power user. It uses the same tools your analysts use and follows your firm's permissions and extraction rules. Proposed numbers are staged for review, with each number traced to its source page.
Does anything reach the record without a person approving it? Yes, if your firm's rules permit publication when every required check passes. Otherwise, you review the staged changes and publish them. Lumonic logs the steps taken in either path.
How does Lumonic run portfolio monitoring? Lumonic supports data extraction from chat, portfolio questions in chat, and a review queue with a publish gate. It also supports firm-specific extraction rules, credit-agreement parsing, and MCP connections. Lumonic's team sets up workflows with you.
How is this different from Excel plugins, dashboards and an MCP? Excel plugins, dashboards and an MCP give you ways to use published numbers. A configured Lumonic monitoring job can start when a document arrives or a record event occurs. Lumonic checks proposed changes and stages them for review before the published record updates.
Test it on your own documents
Give Lumonic the documents from your last reporting cycle. Lumonic will run data extraction on your own documents so you can check every number against the page it came from. Hold anyone else you're evaluating to the same test.
Disclaimer
This article was written by Lumonic, a PitchBook company, and reflects Lumonic's views as of October 2026. Statements about third-party products and companies are based on publicly available information, including the vendors' own websites, press releases and documentation, and on the sources linked in the text. Lumonic has not independently tested third-party products, and their capabilities, pricing and positioning may have changed since this article was last updated. Statements about Lumonic's own product describe the platform at the time of writing, and customer outcomes are taken from the published customer stories linked in the text. Nothing here is a guarantee of results. Third-party names and trademarks belong to their respective owners and are used for identification only. If you represent a company named here and believe a statement is inaccurate, contact support@lumonic.com and Lumonic will review and correct it.
