Know which projects need you this week.

It reads the PSA data TopLeft already syncs.

TopLeft syncs your projects, tickets, time entries, phases and cost rates. Project Health scores from that copy, so there is no extra load on the PSA. Statuses and budgets can be edited in place on the board, and those edits push back to the PSA.

Six checks score every project.

SchedulePast its end date with open work, or further behind than the calendar says.

BudgetHours logged against hours sold.

ActivityDays since any open ticket moved. Red after fourteen.

CompletionTickets closed against tickets total.

MarginRevenue less cost, using the project's billing method and each member's cost rate.

MilestoneA phase past its planned end, or due within a week.

Each check shows the reason behind its colour when you hover over it. The six roll up into a score out of 100. A check with no data is grey and left out of the score, so a project without cost rates synced is not marked down for it. Next to the budget there is a forecast of hours at completion.

An AI review explains what to do.

The review gets the raw facts rather than our score, and is asked to look for places where the facts disagree: 85% complete but half the tickets still open, status Active but no hours logged in a month, a phase marked done with tickets still in it, a fixed fee with more hours still needed than were sold. Where the tracking is too inconsistent to trust, it says so and makes fixing the tracking the first action.

It reads both the structured data (budgets, dates, assignments, the work breakdown structure and its dependencies) and the text your team writes in notes and time entries, and pulls blockers and next steps out of what people actually wrote. It also critiques how the project is being run against project management practice, PMBOK and Agile principles included.

Red Phones don't reliably work but phases say done.

TLDR: Cutover can't be scheduled until the recurring phone-only-works-once bug is fixed on the client's system.

Issues:

• Client impact: their new phone system still drops calls after the first one, so they can't yet rely on it for external calls.
• Two tickets, Configure DHCP for phones and Advanced Setup, are overdue with basic network config still unresolved.
• Deployment phase is marked done with only 1.17 of 22 budgeted hours logged, so the phase status is not credible.

Why: 98.69% complete and both phases marked done sit against zero closed tickets out of 18 and a live call-drop bug, so the percent complete number cannot be trusted.

Do this now:

1. Joseph Atkins: Fix the phone only works one time bug on 3CX Deployment before touching the cutover date.
2. Joseph Atkins: Merge or close the duplicate phone tickets on 3CX Deployment.
3. Joseph Atkins: Correct the Deployment phase status so it stops showing done at 1.17 of 22 hours.

The review from the screenshot, on demo data, with the Happening and Good news sections cut for space. A green project gets a few lines; an amber or red one up to two hundred words.

Then one review across the whole portfolio.

The portfolio review lists the themes across all projects, the projects that most need action in order with each one linked to its detail page, and three to five actions for the week. A separate card shows which projects declined, improved or are new since the last run, with the score change.

Reviews are refreshed overnight for projects whose data changed, and you can refresh one on demand. A one-line summary of each review appears as a column in the grid, so the whole portfolio can be sorted by it.