Yes. One dashboard can show project health, milestones, risks, and overdue deliverables for all of your client projects, provided every project records the same fields against the same written rules. The one condition the listed guides do not settle is whether a tool can keep each client's rows away from the others, so test that before you commit to a tool.
Can one dashboard show health, milestones, risks, and overdue deliverables for every client project?
Yes. A single dashboard can hold all four signals for every client project when each project lead enters the same rows, using the same definitions, and each row has a value. The listed guides describe these views for portfolio tools in general, but none covers client separation, so check that on the tool yourself.
The ProofHub guide lists a project status field with on track, delayed, completed, and at risk values, a milestone timeline, a risk and issue tracker, and an overdue-tasks view. Those match the signals in your question, so use the same rows for every project.
| Field | What the project lead enters |
|---|---|
| Health | Green, amber, or red, chosen from the rules page |
| Next milestone | Name, baseline date, current forecast date |
| Open risks | Risk, owner, next step, date of last review |
| Overdue deliverables | Deliverable, planned date, owner, agreed new date if moved |
| Decisions needed | Decision, sponsor, date needed by |
Write "none" in any cell where a project has no open risks or decisions, so a blank cell never reads as a clean result. The milestone row asks for a baseline date and a forecast date so slippage shows. The ClearPoint guide names milestone slippage among its leading signals.
How do you define green, amber, and red so they mean the same thing?
A single color rules page, which every project lead can open, defines green, amber, and red for the whole portfolio. Each lead picks a color from that page rather than from memory, and the page records the agreed values and the date of the last review.
Put the rules page above the project list, so every lead and partner reads the definitions before they read a color. Green means no amber or red trigger applies. Use checks anyone can make without a meeting, such as a forecast date later than its baseline, or the number of days a blocker has been open.
The ONES guide uses red for fix now, yellow for check within 24 hours, and green for carry on. It does not say what puts a project in each color. The monday.com guide describes automated status based on timeline adherence and budget consumption, but gives its thresholds only as examples. Set your own from your contracts and budgets.
What triggers move a project to amber or red?
Amber applies when any one amber trigger is met. Red applies when any red trigger is met or when more than one amber trigger is met. A deliverable past its planned finish date with an agreed new date is amber, and it becomes red only if the new date is missed.
Set the values on the rules page first, and the color follows from them.
Amber, when one of these is true:
- The next milestone's forecast date is more than [number] days after its baseline date.
- A deliverable is past its planned finish date and has an agreed new date that has not yet passed.
- A blocker has been open longer than [number] days and has a named owner.
- Budget spent is ahead of progress by more than [margin].
Red, when one of these is true:
- A deliverable is past its planned finish date and has no agreed new date.
- A deliverable has missed its agreed new date.
- A blocker has no owner.
- A decision requested from the sponsor is past its date needed by.
Note on the red rule: none of the listed guides sets the rule that more than one amber trigger means red. This guide recommends it. Change it if your contracts set a different rule.
What does a project look like when it moves from green to amber?
A project moves from green to amber when one amber trigger is met at the next cycle. In the illustrative example below, a milestone forecast slips past its baseline, the lead changes only that row, and the color changes with a reason written beside it. Replace every bracketed value with your own.
Illustrative example, placeholders only
Client: [client name]
Project: [project name]
Last cycle: green
This cycle: amber
Changed row: Next milestone, [milestone name], baseline [date], forecast [date]
Trigger met: milestone forecast later than baseline by more than [number] days
Lead's reason: [one sentence on the cause]
Next step: [action] by [date]
Decision needed from sponsor: [decision], needed by [date]
Send the changed row to the partner who owns that client before the roll-up is built, so the change reaches the roll-up with its reason.
How do you keep each client's view separate?
Keep each client's projects in their own group, and limit each group to that client's sponsors. If your tool cannot limit a sponsor to one group, keep one file per client, owned by that client's delivery lead. The firm-wide roll-up stays with partners and delivery leads.
- List each client and its active projects in one place.
- Check whether your tool can create a group or folder per client and restrict a sponsor to that group. Write the answer beside the tool's name on your shortlist.
- If it can, create one group per client and add only that client's sponsors. If it cannot, keep one file per client.
- Keep the portfolio view with partners and delivery leads only.
- Before the first real load, open the client's group or file, check what a sponsor would see, and confirm that no other client appears.
A hidden column or hidden tab does not protect a client's data. The rows are still in the file, so a file sent to one client carries every other client's rows with it.
Some blockers sit on the client's side of the work. Record each one as a blocker, name the client contact by role, and write the date you asked for help. A blocker that waits on the client is still a blocker, so do not hide it under a green status.
How do you roll up overdue deliverables without retyping them?
An overdue deliverable is one that is not marked complete and whose planned finish date has passed. Pull that list from each project tool before each roll-up, sort it by client, project, and owner, and give every item a named owner.
Keep items that have an agreed new date on the list, with that date beside them, so the amber and red rules can be applied. Write the rule on the rules page.
The Triskell guide shows overdue work only at task level in its examples, so a list across projects is something you build. The monday.com guide says little about who owns an overdue item that spans several projects. Decide that owner yourself and write it on the rules page.
If the owner is on the client side, name the client contact next to the item. Settle these details in writing: whether an item due on a non-working day counts as overdue on the next working day, and which time zone the list is cut in, such as [time zone]. Use this line for each overdue item:
[Client] / [Project] / [Deliverable] / due [date] / owner [name] / next step [action] by [date]
Which kind of tool can show every view, and what limits each one?
The listed guides describe three kinds of tool: PMO dashboards, PM suites with Gantt and milestone views, and template spreadsheets. Whether each can hold all four views is this guide's judgment, and each passes only if it meets the checks below. None of the guides confirms per-client access, so test that first.
Portfolio or PMO software: check that a sponsor can see only their client's group, and that milestones show across projects. The Triskell guide describes a portfolio overview that counts ongoing and completed projects and compares budget allocated with budget used. Its examples keep milestones at project level, so confirm the milestone view on the tool itself.
PM suites: check that you can set your own color thresholds rather than use examples. The monday.com guide describes milestone synchronization across projects and dependency views in Gantt charts, and gives its thresholds only as examples.
Shared spreadsheet: check that each client has its own file and that one named person owns the master copy. The ProofHub guide includes a template with marketing categories such as social media and email, so replace those with your delivery stages before use. Every row in one file is visible to anyone who opens it, so split the file by client.
Setup cost depends on each tool's current pricing, so check the vendor's pricing page before you shortlist. Ask each shortlisted tool these questions, and record the answers from its documentation or from a trial you run:
- Can a client sponsor see only their own client's group?
- Can a partner see the firm-wide roll-up without the sponsor seeing it?
How do project tools feed one view without manual rewriting?
Each client project keeps its own tracker, and the portfolio view reads from those trackers through a connector, a scheduled export, or a shared sheet that each lead updates. Set the refresh rule before you load anything, and confirm each connection yourself.
- List each client and the tool or file where its projects live.
- Map each source's fields to the rows in the fields table. Where a field is missing, the lead enters it in the agreed place, not in a new file.
- Set the refresh day and time, in [time zone].
- Load one client end to end, compare the roll-up with its project tool, then add the other clients.
Trace a few overdue deliverables from the project record to the roll-up. If a date or owner changes along the way, fix the mapping before you add more clients. The ONES guide favors real-time updates, but its FAQ suggests a daily refresh, so choose the cadence yourself and write it on the rules page before the first load.
What does each lead enter, and what do partners see?
Each project lead enters only the rows that changed since the last cycle, and partners see projects by color, milestones due soon, overdue deliverables, open risks, and decisions waiting on a sponsor. Each client receives only its own projects, in the same layout.
What each lead enters
Each project lead changes only the rows that moved since the last cycle and confirms each unchanged green project in one line. Unchanged rows keep their earlier entry and date, so nobody retypes them. Write full entries only for amber and red items. Pull the overdue list from the project tool rather than rebuilding it by hand, and reuse the same deliverable names so the list matches from one cycle to the next. A lead who skips the one-line confirmation makes green look more current than it is.
Time the first cycle before you roll the routine out to every client:
- Pick one client and run its first cycle, with each lead entering only changed rows.
- Record the minutes each lead spends, in a note on the rules page.
- Compare that client's roll-up with its project tool, and fix any mismatch.
- Add the other clients only after the comparison matches and the minutes are recorded.
What partners see
The ClearPoint guide describes a portfolio summary that counts projects in each color. A roll-up for partners follows the same pattern:
Portfolio roll-up, week of [date]
Projects by color: green [count], amber [count], red [count]
Milestones due by [date]: [client] / [project] / [milestone] / forecast [date] / lead [name]
Overdue deliverables: [count], taken from the overdue list for this cycle
Open risks needing a decision: [risk] / owner [name] / decision needed from [sponsor] by [date]
If a sponsor has not answered a decision line by its date, the partner who owns that client raises it with the sponsor directly. The line stays on the roll-up until an answer is recorded and the team has its next step.
How do you keep a green status from hiding a late deliverable?
A green status hides a late deliverable when the project shows green despite a deliverable past its planned finish date with no agreed new date, a missed new date, or a blocker with no owner. Check every green line against the color rules before the roll-up goes out, and move any line with those gaps to red.
For each amber and red line, write one sentence that says why the project is off track and what is being done about it. Before each portfolio review, pick a few green projects at random and compare their risk lists and overdue items with their color. If the color does not match the evidence, change it and note the reason in the project record.
Who approves the color rules before the first roll-up?
One named person, such as the head of delivery, approves the color rules before the first roll-up goes out. Write that name and the date at the top of the rules page, then send the fields table and color rules to each project lead and ask for confirmed or changed rows by [date].
Ask each lead to reply with any changed row and the reason for the change. Hold the first roll-up until every lead has replied, so every color on it traces back to rules one person has approved.