RAG status across 20 projects without chasing PMs

The problem

Every Friday you ask the project managers for a one-line update. They're busy, the updates are late or optimistic, and by Monday you have no real view of which projects are actually in trouble. By the time something goes properly red, it's too late to act.

How EF-Projex solves it

Three steps. One outcome.

Status calculated from real data

EF-Projex computes RAG from facts: schedule variance, cost variance, open risks, late deliverables, missed approvals. No PM is asked to "rate" their own project.

Drill from portfolio to root cause

Click any red project — see the exact reason (which milestone slipped, which cost overran, which risk crystallised) and who owns it. No more "what does red actually mean?" conversations.

Auto board pack

EF-Projex generates the monthly portfolio board pack — RAG dashboard, top risks, financial summary, executive summary — formatted to your template. You review and send.

The outcome

What you should expect

Real RAG, not PM-massaged RAG
Spot trouble 4-6 weeks earlier on average
Friday status meeting becomes a 15-minute exception review
Board pack assembly: hours → minutes

Common questions

Frequently asked

What thresholds drive RAG?▼

You set them per project type — a 10% schedule slip might be amber on construction, red on software. EF-Projex ships with sensible defaults you can tune.

Can PMs override the auto-RAG?▼

Yes — with a comment. The override and the comment are logged, so you know when reality and "the PM's view" differ, and why.

Does it work with non-EF projects?▼

Yes — EF-Projex can ingest schedule and cost data from MS Project, Primavera, Smartsheet, Asana, Jira via the Integration Hub, and apply the same RAG engine.