Is Excel Enough for Portfolio Reporting at 15 Projects?

At 15 client projects, Excel stays workable only while one named owner keeps every project row current on the same day each cycle. Move to a PPM tool when the register goes stale, several people edit it at once, or rebuilding the summary before each review takes more hours than the decisions it supports. That line is editorial judgment. The published sources disagree on project counts, so your own hours and your checklist score should settle it.

Is Excel still enough for 15 client projects?

That is a judgment, not a published limit. Whether the file stays true each cycle, without extra hours from the same people, is the test that counts.

Check these conditions before you decide to stay:

1. One person owns the register and can say when it was last updated.
2. Each project lead confirms their row on the same day each cycle, before the portfolio review.
3. The summary is rebuilt from the register, not typed by hand.

If all of them hold, keeping Excel with guardrails is a reasonable choice for now. If one fails, work through the checklist in the next section before you decide.

Which signs show Excel has stopped being enough?

Excel has stopped being enough when the register is out of date more often than leads read it, or when someone rebuilds the summary by hand before each review. Answer the questions below for your own portfolio.

Answer each question once each cycle:

1. Does more than one person edit the register in the same week? Portfolio Hub names many people editing at once as one of its hard limits for spreadsheets.
2. Can you say who changed a forecast or budget figure, and when? Portfolio Hub also lists an audit trail of forecast changes among those limits.
3. Do two or more projects draw on the same people, with a conflict found only after it causes a delay? Portfolio Hub lists resource conflicts across projects as a hard limit too.
4. Do leads update their rows only before a review, because updating costs more than reading? Portfolio Hub says that when updating the sheet costs more than reading it, people stop updating it.
5. Does someone rebuild the portfolio summary by hand before each review? Editorial judgment, not a listed source: a summary rebuilt by hand each cycle is where hours accumulate.
6. Do client reports need a separate version for each client? Editorial judgment, not a listed source. See the client section below.
7. Do you need billing, margin, or utilization in the same view as status? Editorial judgment, not a listed source.

Give each yes one point and total the score once each cycle, before the portfolio review. Before you score, decide which total will start a tool review, write it in the note to the sponsor, and keep to it. The score is a judgment aid. It is not a published threshold, and the cut-off should not move after you see the result.

Where does a spreadsheet portfolio break first?

Portfolio Hub argues that the real failure is data going stale, not size. The breaking points Portfolio Hub names are many people editing at once, no audit trail of forecast changes, and resource conflicts across projects. Hand-built totals are one more point, added as editorial judgment.

• Shared edits. Two leads overwrite each other's status, and nobody knows which version is current.
• Forecast history. A forecast changes after a call with the client, and no one can show what it said last month.
• Shared people. The same designer appears on two or more projects, and the sheet shows each one as fully staffed.
• Hand-built totals. A total built by formula can miss a row that was added later.

Triskell's comparison says that building portfolio controls in Excel, with macros and complex formulas, takes a lot of hours and may require an outside party, such as an Excel consultant. Keep that in mind when someone proposes a better spreadsheet before a tool.

How do client reports change the decision?

Client reports change the decision when each client needs its own version or must see only its own projects. Excel can produce separate copies, but a shared file offers little control over who sees which rows. The guidance here is editorial judgment, since none of the listed sources covers client access.

Walk through these questions with the sponsor before the next client status report goes out:

1. Which clients receive a report, and how often? Keep the list by client name.
2. Which fields may each client see? Budget, margin, and staffing are usually the sensitive ones.
3. Does the client need billing or margin beside status? If yes, the cost table grows, and a tool that holds billing data may fit better.

If a client must see only its own rows, treat a shared Excel file as visible to everyone who can open it. Build each client copy from the register, and have the project lead check it before it is sent.

What does staying on Excel cost in hours?

Staying on Excel costs the hours your team spends each cycle on updating rows, rebuilding the summary, and answering status questions. Add the hours spent correcting errors and rerunning reports, which is easy to leave out. Measure these for a few cycles, then price them at your own hourly cost.

Fill one line per task and per person:

Portfolio reporting cost, per [cycle length]
Updating project rows:                   [name] [hours]
Rebuilding the portfolio summary:        [name] [hours]
Answering status questions:              [name] [hours]
Correcting errors or rerunning reports:  [name] [hours]
Total hours:                             [total hours]
Cost at [hourly cost]:                   [total hours] x [hourly cost] = [cost per cycle]

An illustrative entry, with every value left as a placeholder: [Lead name] updates [number of project rows] in [hours] each cycle, and [coordinator name] rebuilds the summary in [hours]. Replace each bracket with your own figures.

Compare the total with the tool's licence and setup quote, over the same cycle length. Triskell notes that Excel is included by default in Microsoft 365, so the licence line for Excel itself may be small. The time of the people who keep the file current is the cost to measure.

How do you keep Excel with guardrails?

Keep Excel with guardrails by holding one row per project, adding a forecast at completion column, naming an owner for each column, and building client reports in a copy. Portfolio Hub recommends trimming the sheet, or connecting it to source systems, before buying a tool. Review the guardrails on a set date.

1. Use one row per project. Do not create a tab per project, because the portfolio view disappears once you do.
2. Add a forecast at completion column beside budget and actual. Portfolio Hub lists fourteen columns for a tracker, and forecast at completion is one of them.
3. Write a refresh contract. Name who updates each column and the day it is due.
4. Add data validation to the status column, so only the agreed status values can be entered.
5. Keep a change note column for any forecast change: who changed it, when, and why.
6. Build client reports in a copy, never in the register, and have the project lead review each one before it is sent.

A refresh contract can be as simple as this:

Column                  Owner               Updated by
Status (RAG)            [project lead]      [day before portfolio review]
Forecast at completion  [finance contact]  [same day as budget change]
Risks and blockers      [project lead]      [day of weekly check-in]
Change note             [project lead]      [same day as any forecast change]

What would a PPM tool take in effort?

A PPM tool adds setup and upkeep effort on top of its licence fee. WorksBuddy says setup typically takes 2 to 4 weeks, so plan the move around that window rather than around a client deadline. Write down these four items before you choose.

1. Which fields the register needs, and which are optional.
2. How the current sheet moves into the tool, and who checks the first load.
3. Who updates each field, and by which day.
4. Who trains the project leads, and when the old sheet becomes read-only.

A tool does not remove the need for an owner. Portfolio Hub argues that the tipping point depends more on how many people edit the file than on how many rows it holds, so a tool with no owner goes stale too.

Does a project count settle the question?

No. The published thresholds disagree. Portfolio Hub gives roughly 30 to 50 projects as a spreadsheet's ceiling, while WorksBuddy describes IT company owners running 10 to 20 concurrent projects. Use your checklist score and cost table to decide instead.

In our reading, neither range tests client work at this size. Portfolio Hub's figure is an assertion in its guide, and WorksBuddy's band describes its own audience. Your hours and your answers to the checklist say more about your portfolio than either range does.

What should the sponsor decide before the next portfolio review?

The sponsor should decide between keeping Excel with guardrails until a set review date and starting a tool review now. Bring the cost table and the checklist score, so the decision rests on hours and answers rather than opinion. Ask for that decision in writing.

1. Write the decision as one sentence: "We keep Excel with these guardrails until [review date], then compare the hours against [threshold]."
2. Fill the cost table for [cycle length] and send it to the sponsor before [meeting name].
3. Name the owner of the register: [name].
4. Ask the sponsor to answer yes or no at [meeting name], and record the answer in the change note column.

Start with the owner and the refresh contract this week, then bring the cost table to [meeting name].