Change control and the portfolio

The portfolio: decisions, milestones, capacity and the weekly brief

What needs deciding across your projects, where portfolio milestones stand, who is over capacity, and a weekly brief built from the facts.

Decisions required and portfolio milestones

Programs lists change requests waiting for a decision and decisions still pending in every project you can open, soonest first.

A portfolio milestone is a target -- "Regulatory approval, 30 Nov" -- linked to the project milestones that feed it. Its forecast is the latest of theirs, from each project's own schedule; it shows on track, at risk or forecast late against the target.

Capacity across projects

Capacity shows each person's estimated work over the next eight weeks, from every project, against a 40-hour week. A task counts when it has an owner and an estimate in hours; its remaining hours are spread over its remaining working days. Click a week to see the tasks that make it up. Owned work without an estimate is listed, not guessed. Nothing is rescheduled for you.

The weekly brief

Weekly brief builds a summary from the projects' own data: how many are off track, need attention or are on track; milestones that have moved; new risks this week; budget variance; decisions required; broken cross-project dependencies. Copy it or download it as a PDF. Nothing in it is estimated or written by AI.

Related articles

Change requests and the decision log

Propose a change to the agreed plan, see its impact from the schedule, decide it, apply it as one change -- with the decision on record.

Operating model: escalation, high risk and currency

Set once how a project is run -- when a late milestone is critical, what counts as a high risk -- and the currency it counts in.

Still stuck?

If this did not answer your question, tell us what you were trying to do and we will help.