# Consultant Portfolio Dashboard decision sheet

Worked example companion. Fictional scenario; no measured results.

A combined portfolio is useful when each concern leads to evidence, an owner, and a next action.

## How to use this sheet

Replace the example rules with your own. Keep each acceptance decision linked to its owner and evidence. Use the blank CSV to record your actual process; the example CSV contains teaching material.

| Situation to test | Expected behavior | Review and ownership |
| --- | --- | --- |
| Stale snapshot | Display the last refresh time | Consultant verifies before acting |
| Unavailable source | Keep other signals visible | Integration owner restores access |
| Conflicting owners | Show the discrepancy | Project lead confirms accountability |

## Workflow

1. **Gather signals** (Connected systems): Collect project context with source timestamps.
2. **Assemble snapshot** (Portfolio application): Join records without hiding missing data.
3. **Review blockers** (Consultant): Identify the dependency and accountable owner.
4. **Take action** (Project owner): Follow through in the source system.

Exception: An unavailable integration is labeled explicitly. Other source signals remain visible with their own freshness indicators.

## Measurement

Measure status-preparation time and the proportion of flagged blockers with a confirmed owner. Test source freshness and reconciliation independently; no delivery-performance improvement is claimed.

## Limitations

- This worked example is a proposed design, not access to a production application.
- Implementation depends on source data, access rules, and policies agreed with the responsible team.

Source page: https://www.opsautomators.com/work/consultant-portfolio
Prepared September 16, 2026.