Folio

VC Portfolio Monitoring: How to Run a Monthly Review That Catches Problems Early

3 November 2026· 11 min read

VC portfolio monitoring is a monthly routine: collect the same five numbers from every portfolio company, check them, score each company against written thresholds, and give every flag an owner and a date. It has four parts: a short data contract agreed with each founder, a fixed calendar with one owner, escalation rules written in advance, and a record that feeds quarter-end valuations and LP reports. Without them, a company with six months of cash left gets noticed with three.

This applies when companies are pre-seed to Series A, or have under 12 months of runway. Series B+ companies with a board pack, funds with fewer than about 10 companies, and stakes without information rights need a lighter version.

Summary

Collect five numbers monthly: cash, net burn, revenue, headcount and one agreed metric, with definitions written down at closing.
Calculate runway on a 3-month average burn, and run four validation rules before anyone reviews the numbers.
Run a fixed monthly cycle with one owner. Partners review only amber and red companies, in 30 minutes.
Escalate on written thresholds: under 12 months of runway is amber, under 6 is red, and two ambers make a red.
Every flag leaves the review with a one-line reason, an owner and a date.
For Series B+ companies, use their board pack and review quarterly; without information rights, use what the lead investor shares.

What is VC portfolio monitoring for?

VC portfolio monitoring is the recurring collection and review of each portfolio company's financial and operating data after the investment closes. It supports three decisions: where partner time goes this month, whether a company needs follow-on money or a plan change, and what goes into valuations and LP reports.

If a metric doesn't feed one of those decisions, don't collect it monthly.

What it is not

Not portfolio support. Monitoring shows where help is needed. Support is the help itself: intros, hiring and fundraising prep.
Not a board meeting. Boards approve budgets and strategy. A monthly check flags drift between board meetings.
Not a valuation. Monthly numbers are evidence for a valuation, which still follows your fund's valuation policy.
Not audited accounts. Monthly figures are unaudited management information. Label them that way in every report.
Not surveillance. In our view, founders who feel audited report late or send polished numbers. The routine works when founders get something back.

Why monitor monthly and not quarterly?

Monthly portfolio monitoring matters because the numbers that end early-stage companies move faster than a quarter. A seed company with $900k in the bank burning $150k a month has six months of runway. A quarterly check sees that number at most twice before the cash runs out. A monthly check sees it six times, and that margin is what a bridge round or a cost cut needs.

What data should you collect each month?

Each month, collect five fields from every company: cash balance, net burn, revenue, headcount and one agreed metric. Define them in a short data contract agreed at closing: which numbers, in which currency, defined how, due by which day.

The five monthly fields

Field	Definition to agree in writing	Common error
Cash balance	Cash and equivalents at month end, all entities	Leaving out a subsidiary or foreign account
Net burn	Starting cash minus ending cash, excluding equity or debt raised that month	Counting a new funding tranche as "negative burn"
Revenue	Recognised revenue, or MRR for subscription models (say which)	Mixing bookings, invoiced and recognised revenue
Headcount	Full-time employees at month end; contractors listed separately	Counting offers accepted but not started
Agreed metric	One metric chosen at closing, by business model (table below)	Changing the metric each quarter, which hides the trend

Every company reports in one currency. If it converts, it states the rate and the method. A converted number with no method can't be validated.

Choosing the agreed metric

Business model	Agreed metric (pick one)
B2B SaaS	MRR growth or logo churn
Marketplace	GMV or take rate
Consumer brand	Repeat purchase rate or contribution margin
Fintech	Transaction volume or loss rate
Deep tech or biotech	Milestone progress

What to add as companies grow

Stage	Add	Skip	Why
Pre-seed / seed	Nothing beyond the five	Unit economics, CAC	Revenue is too small to show direction; the agreed metric does that job
Series A	Gross margin, month-on-month revenue growth	Detailed cohort analysis	Tests whether growth is repeatable
Series B+ (quarterly)	ARR, net revenue retention, burn multiple, plan vs actual	Weekly activity metrics	Capital efficiency now drives the next round

Runway: use an average

Runway (months) = Cash balance ÷ Average monthly net burn over the last 3 months

The Business Development Bank of Canada (BDC) defines cash runway as cash balance divided by burn rate, which it describes as net cash outflow, typically monthly. Two choices here are our suggested defaults: net burn excludes funding raised, and runway uses a 3-month average, because a single month's burn swings with annual bills, prepayments or a delayed payroll. Show both figures when they differ by more than a month.

Four validation rules before review

1Cash this month should equal cash last month, minus net burn, plus any funding raised. If the gap is more than 5% of the month's net burn, ask. This catches burn reported as an accounting loss instead of cash.
2Revenue changed more than 50% month on month: confirm it isn't a change of definition or currency.
3Headcount down 10% or more with burn flat: ask what is being paid that isn't salary.
4Any blank field is missing, not zero.

How should the monthly cycle run?

A monthly portfolio monitoring cycle needs one named owner and fixed dates; without both, it slides a week every month until it becomes quarterly by accident. In the calendar below, Day 1 is the 1st of the month after the one being reported, and companies are asked to report by the 7th.

When	Step	Owner	What good looks like
Day 1	Send the same short request to every active company	Monitoring owner	Numbers taken from the founder's own investor update where one exists
Day 8	Automatic reminder to anyone who missed the 7th	Monitoring owner	No manual chasing yet
Day 10	Chase anyone still missing	Deal partner	90%+ response rate, logged every month
Days 10–12	Run the four validation rules; query failures	Monitoring owner	One-line questions, not meetings
Day 14	Score every company green, amber or red, with a one-line reason	Monitoring owner	Same person scores every month, for consistency
Day 15	30-minute review of amber and red only	Partnership	Every flag leaves with an owner and a date; green companies get one line in the record
Days 16–25	Follow up on every flag	Deal partner	Each action done by its date and logged: "Priya calls the CEO by the 20th"
Day 28	Close the month's record	Monitoring owner	Data, flags, actions and material events saved; restatements kept

Role	Owns	Time per month (40 companies)
Monitoring owner (platform lead or associate)	Request, validation, scoring, record	[SME: hours per month from a fund running this]
Deal partner	Day-10 chase, follow-up actions	Minutes per flagged company
Partnership	Day-15 review	30 minutes

If this calendar runs across a separate spreadsheet for every fund, validation and scoring on Days 10–14 can't start until someone copies numbers between files. For VC funds and family offices, Folio's portfolio monitoring module is where Folio handles this part of fund operations. See portfolio monitoring in Folio.

How do you get founders to report on time?

In our view, founders report on time when the monthly request is short, predictable and worth answering.

Five numbers and three lines. Anything longer belongs in the quarterly board pack.
Same date every month, so founders build it into their month-end close.
Accept their format. If the company already sends an investor update, take the numbers from it.
Give something back. End every request with "Where could we help this month?" and act on the answer.
Report once. Agree a shared field list with co-investors, so the founder fills in one form, not four.
Set it at closing. Put the routine and the fields in the welcome email or the information-rights terms, not as a surprise six months in.

Monthly request template

Subject[Fund] monthly check-in: [Month]

Hi [Founder], five numbers and three lines, by the 7th please.

1. Cash in bank at month end (all entities, [currency]):
2. Net burn this month (excluding any funding raised):
3. Revenue or MRR this month (same definition as last month):
4. Full-time headcount (contractors separately):
5. [Agreed metric]:

- Biggest win this month:
- Biggest worry:
- Where could we help this month?

Thanks, [Name]

The notes in brackets after each field carry the data contract, so founders see the agreed definitions every time they report.

When should a company be escalated?

A portfolio company should be escalated when a written threshold is crossed, not when someone has a feeling. The thresholds below are suggested starting defaults for an early-stage fund, not industry standards. Set your own, write them down, and review them once a year.

Signal	Amber	Red
Runway (3-month average)	Under 12 months	Under 6 months
Net burn vs approved budget	15–30% over for 2 months	Over 30% in any month, or over budget 3 months running
Revenue vs plan	15–30% under, or over 30% under for one month	Over 30% under for 2 months
Team	Net headcount down 10%+	Founder or C-level exit
Reporting	One month missed	Two months missed

Burn has the stricter red line because overspent cash can't be recovered. Two ambers on one company make it red (our suggested default).

Every amber or red carries a one-line reason, for example: "Red: runway 7.2 months on a 3-month average; MRR 20% under plan." A colour without a reason can't be checked next month.

Colour	Default response (suggested)	By when
Amber	Deal partner asks the CEO what's driving it and what the plan is	Within 2 weeks
Red	CEO call, revised budget or fundraising plan, decision on reserves or a bridge	Call within 1 week; decision within 30 days

Signals no field shows

Some of the most important flags never appear in the monthly numbers. Put these on the Day 14 list the same way, each with a one-line reason; owners and dates are set at the Day 15 review:

a key manager below C-level leaving
a quiet change of strategy
a funding round that keeps slipping
a founder who stops replying between reports

Worked example

An illustrative Series A software company reports at the end of September:

Input	Value
Cash balance	$3.0M
Net burn, July / August / September	$380k / $410k / $460k
MRR, plan vs actual	$120k vs $96k

Average burn($380k + $410k + $460k) ÷ 3 = $417k
Runway$3.0M ÷ $417k = 7.2 months. On September's burn alone, $3.0M ÷ $460k = 6.5 months.
Revenue vs plan$96k is 20% under the $120k plan.

Runway under 12 months is amber. Revenue 20% under plan is amber. Two ambers make the company red, with the reason "runway 7.2 months on a 3-month average; MRR 20% under plan".

Scored one at a time, each amber is a conversation a deal partner might postpone. Together they mean the company must raise or cut within six to seven months while missing the plan it would raise on. The red rating puts that conversation on this month's agenda.

Spotting two ambers on one company is hard when each company's numbers sit in a different file. For VC funds and family offices, Folio's portfolio monitoring module is where Folio handles this part of fund operations. How portfolio monitoring works in Folio.

How does monthly data feed valuations and LP reporting?

Monthly portfolio data becomes the evidence for quarterly valuations and LP reports. Three clean monthly records make quarter-end reporting easy; without them, the quarter starts with a round of emails asking founders for numbers the fund should already have.

Output	Built from monthly data	Still needs
Quarterly valuation review	Cash, burn, revenue trend, flags and how they were resolved	Your valuation policy, latest round terms, auditor expectations
Investment record	Material events flagged during the month: rounds closed, conversions, partial exits	Closing documents and the updated cap table: ownership after dilution, pro-rata rights
Board preparation	Plan vs actual, open actions	The company's own board pack
LP report	Company summaries, key metrics, material events	Fund-level LP reporting metrics (TVPI, DPI, IRR) from the fund accounts

Quarterly marks follow your fund's valuation policy, never one month's numbers. If your policy follows the IPEV Valuation Guidelines, check it against the current edition, published in December 2025.

ILPA's Portfolio Company Template is its template for reporting company-level data to LPs. ILPA is updating it: public comment on the draft closed on 16 October 2026, and ILPA plans to publish the final version in January 2027. ILPA has also updated its fund-level Reporting Template; the new version is meant for funds still in their investment period during Q1 2026 and funds starting operations on or after 1 January 2026. ILPA's template FAQs frame that timing as a recommendation. Consistent, defined company data each month is the groundwork for whatever the final template asks for.

One rule for the record: never overwrite a past month. If a founder restates a number, keep both figures and the reason. If an auditor or LP asks about a restatement, an overwritten file can't answer.

When does a monthly routine not fit?

Monthly portfolio monitoring is the default for early-stage companies and the wrong fit in several common cases, such as Series B+ companies with a board pack, very small funds and stakes without information rights. In each, change the routine or the fields instead of forcing the monthly routine.

Situation	What to do instead
Series B+ company with a board pack	Take the numbers from the board pack instead of sending a request; review quarterly unless a threshold is crossed
Very small fund (under about 10 companies, one partner)	Quarterly data plus a monthly two-line check-in on cash and the biggest worry
Pre-revenue deep tech or biotech	Report spend against the programme budget in place of revenue; milestone progress is the agreed metric
Minority stake with no information rights	Ask; without information rights you usually can't require monthly data. Use what the lead investor shares, with their agreement
Lead investor already collects the data	Agree a shared form with co-investors, so the founder reports once
Company in a fundraise, sale or restructuring	Keep the monthly report and add a weekly cash check for the duration
Company that has pivoted	Reset the plan baseline; old plan-vs-actual flags no longer apply
Family office holding direct positions	Same cycle; the principal's review replaces the partner review, and thresholds follow the family's liquidity policy

Known limits of this approach

Thresholds measured against plan are only as good as the plan. A sandbagged budget hides real problems.
A green rating means "nothing crossed a line", not "healthy".

Monthly portfolio monitoring checklist

Once, at closing

Data contract agreed: the five fields, definitions, currency, due date
Agreed metric chosen for the company's business model
Escalation thresholds written and shared with the partnership

Every month

Day 1: standard request sent to every active company
Day 8: automatic reminder sent to anyone who missed the 7th
Day 10: deal partner chases missing companies; response rate logged
Days 10–12: four validation rules run; failures queried
Day 14: runway on a 3-month average; every company scored with a one-line reason; signals no field shows added
Day 15: 30-minute review of amber and red companies only; every flag leaves with an owner and a date
Days 16–25: every follow-up done by its date and logged
Day 28: month closed; material events saved to the investment record; restatements kept

Every year

Thresholds, fields and agreed metrics reviewed against what actually predicted trouble

Run this routine from one place. The monthly cycle works in a spreadsheet, but it gets harder with every new fund and every founder email. For VC funds and family offices, Folio's portfolio monitoring module is where Folio handles this part of fund operations. Copy the checklist above, then see portfolio monitoring in Folio.

FAQ

Can a small fund run portfolio monitoring in a spreadsheet?

Yes. As our suggested default, a spreadsheet works up to 15–20 companies if one person owns it and the form never changes. Past that, in our view, the version control, missed reminders and copy-paste errors of manual portfolio data collection start to cost more time than the spreadsheet saves.

Check what your investment documents require; information rights usually set the minimum. Then offer a lighter ask, such as the five fields only or reuse of their existing investor update. Persistent refusal is a governance signal to raise with the deal partner.

How is portfolio monitoring different from portfolio management?

Portfolio monitoring is tracking the numbers and flagging change. Portfolio management is wider: reserves, follow-on decisions, founder support and exits. Monitoring is one of its inputs.

Can portfolio monitoring be automated?

Parts of portfolio monitoring can be automated: recurring requests, reminders, portfolio data collection from multiple startups into one place, runway arithmetic and threshold checks. Reading an exception, deciding what it means and talking to the founder stay with people.

When should we stop sending the monthly request to the company?

Our suggestion is when the company is fully exited or written off. Record the last figures and the date you stopped, and move it to a closed list. Before that, change the routine rather than stop it: for a Series B+ company with a board pack, take the numbers from the pack, as the table above says. A missing update is itself a signal.

About Folio

Folio is Incentiv's fund platform for private market investors: VC funds, family offices and their LPs. It covers deal flow, portfolio, LP and fund management. Its portfolio monitoring module is where Folio handles this part of fund operations. Explore portfolio monitoring in Folio.

Thresholds and response times are editorial suggestions, not financial or legal advice. All company figures are illustrative.

Next Step

See how Incentiv can help

Infrastructure for cap tables, ESOP management, and secondary markets in India's private markets.

Request Demo