Status classifications in FireFlight are not manually assigned by a project manager filling out a RAG report. They are calculated from the project's own data: milestone progress against planned dates, budget consumption relative to the planned burn rate at the current stage, and deliverable completion percentages against the timeline defined when the project launched. A project that is consuming budget faster than its planned burn rate while falling behind on a key deliverable will surface as At Risk before either threshold is catastrophic.

The threshold logic is configurable per project type. A construction project may define At Risk differently than a software deployment or a service delivery engagement. Because FireFlight uses project templates to standardize structure at launch, those thresholds are built into the template rather than having to be defined individually for each new project. The result is that the status classifications on the dashboard mean the same thing across every project of the same type, which makes the portfolio view genuinely comparable rather than dependent on how optimistic each project manager's self-assessment happened to be that week.

A project that launches without a predefined structure stages built ad hoc, milestones added as the work progresses, budget allocated as a round number rather than broken down by phase produces a dashboard view that is difficult to interpret and impossible to compare across projects. The overview shows activity. It does not show whether that activity is ahead or behind, within budget or over it, because there is no baseline to measure against.

Project templates solve this at the source. A template defines the stages, the milestones that mark each stage's completion, the materials and labor requirements, the cost allocations by phase, and the expected timeline before any work begins. Every project launched from that template starts with the same structure. The Project Overview Dashboard can then compare progress and budget consumption across ten projects of the same type because all ten share the same baseline. That comparison is what turns a dashboard from a status display into a management tool.

Key deliverables are the defined outputs that mark meaningful progress within a project not every task, but the milestones that matter to the client, the regulatory record, or the next stage of work. In FireFlight, these are defined in the project template and carry into every project launched from it. The dashboard shows completion percentage for each deliverable across all active projects, which gives operations managers a view of where projects are progressing as expected and where specific outputs are lagging.

A deliverable that is behind relative to the project's timeline will contribute to an At Risk classification before the project's overall completion date has been missed. That early warning is what the dashboard is designed to produce. Operations managers who manage a portfolio of concurrent projects service engagements, construction phases, compliance deliverables, or production milestones need to know which specific outputs are at risk in time to redirect resources, adjust timelines, or have an informed conversation with the client. The overview dashboard provides that visibility without requiring each project to be opened individually.