Trends Dashboard | FireFlight

Last updated: April 2026

Trends Dashboard

Tasks completed per day, tasks assigned per day, and cumulative tasks completed three daily trend lines that show whether task throughput is keeping pace with demand and whether the operation is on track against its planned completion baseline.

FireFlight's Trends Dashboard shows three task metrics plotted over time: Tasks Completed per Day, Tasks Assigned per Day, and Cumulative Tasks Completed. The daily view shows the rate of assignment versus completion. The cumulative view shows whether total completed work is tracking ahead of, behind, or on pace with where it should be at this point in the project or period. All three update in real time as tasks are assigned and completed. Most operations are running live task trend data in weeks, not months.

FireFlight Trends Dashboard showing daily task completion, assignment rates, and cumulative progress over time

A daily task count tells you how much work was finished today. It does not tell you whether that amount is enough to stay on schedule, whether assignment volume is creating a backlog that will become a problem next week, or whether the team is ahead of or behind where cumulative completion should be at this point in the month. Those questions require a trend view rather than a point-in-time count. The Trends Dashboard provides exactly that three daily metrics plotted over time, updated from real task data logged as work happens rather than from end-of-day estimates.

Schedule your free consultation

What does a gap between assigned and completed tasks actually signal?

The relationship between Tasks Assigned per Day and Tasks Completed per Day is the most direct measure of whether the operation is keeping pace with its workload. On any given day, if 14 tasks are assigned and 11 are completed, the open task queue grows by 3. That single-day gap is manageable. If the same pattern repeats for five consecutive days, the queue has grown by 15 tasks. By day ten, it has grown by 30 and the cumulative completion line is visibly tracking below where it should be against any planned baseline.

The trend view makes that accumulation visible as it is happening rather than after it has produced a schedule problem. An operations manager who can see that the gap between assigned and completed has been widening for three days in a row has time to respond by adjusting assignments, adding a resource for a specific category of tasks, or having a conversation about scope before the accumulation has reached the point where it requires a schedule restructure to address.

Operational tracking view in FireFlight showing task completion rates and daily trend data

The Cumulative Tasks Completed metric adds the baseline comparison that daily rates alone cannot provide. A project scoped for 150 tasks over 15 working days has an implied daily pace of 10 tasks per day. By day 7, cumulative completion should be approximately 70 tasks. If the cumulative line shows 54 tasks completed by day 7, the project is 23% behind its implied pace a fact that is visible from the cumulative chart without any calculation. The chart shows where the actual line is versus where the expected pace would place it.

For operations managers tracking multiple concurrent projects or managing a team against a monthly task target, the cumulative view answers the question they most need to answer early in the period: are we on track? Not whether today was a good day, but whether the cumulative body of work is where it needs to be for the overall target to be met. A strong daily count on a day when the cumulative line is already significantly behind the baseline does not represent recovery it represents the start of possible recovery, and the trend view makes that distinction clear.

Why does point-of-work task logging produce better trend data than end-of-day reporting?

The quality of the trend lines on this dashboard depends entirely on when task completions are recorded. If team members log task completions at the end of the day based on memory, three things happen consistently: some completions from late in the day get recorded the following morning, some completions from early in the day get forgotten by logging time, and the time distribution within the day is lost entirely. The daily count may be roughly accurate, but its timing is not and timing matters for trend analysis.

FireFlight's Time Tracking on Job app records task completions at the point of execution. A technician who marks a task complete in the field at 10:47am generates a completion record timestamped 10:47am. That record flows into the Trends Dashboard in real time. By midday, an operations manager can see actual morning completion rates rather than a blank screen that will be populated when someone remembers to log at 5pm. For operations managing daily task targets or time-sensitive project milestones, that intraday visibility is the difference between responding to a slow morning before it becomes a slow afternoon and discovering the slow day after the fact.

The trend lines on this dashboard are only as reliable as the task records that feed them. Operations that log task completions at the point of work produce trend data that reflects actual daily throughput patterns. Operations that batch-enter completions at end of day produce trend lines that are accurate in total but misleading in pattern. PCG's deployment process includes configuring the Time Tracking on Job app specifically to make point-of-work logging faster than the alternative because the dashboard is only valuable if the data it reads is current and granular.

PCG has been building task tracking and labor management systems for field operations since 1995. The pattern of end-of-day batch logging producing unreliable trend data is one of the most consistent findings across 31 years of implementations in industrial, environmental, and service environments. The fix is not better reporting it is removing the friction from point-of-work logging so that the behavior change is easier than the old behavior, not harder.

How does this dashboard work alongside other time tracking and operations views?

The Trends Dashboard occupies a specific position in FireFlight's time tracking and operations dashboard suite. Volume and Status shows current-state work order counts. Types and Mix shows how logged time is distributed across step type categories. Trends shows the daily and cumulative trajectory of task completion against assignment volume over time.

The three dashboards address different questions that share the same data source. Volume and Status answers where things stand right now. Types and Mix answers how time is being allocated across work categories. Trends answers whether the operation is moving in the right direction over the past days and weeks. An operations manager who starts with Volume and Status to check current state, then checks Trends to see whether the current state reflects an improving or worsening trajectory, then checks Types and Mix to see whether the time allocation supports the throughput rate the Trends dashboard shows that sequence gives a complete operational picture without requiring a custom report for each layer of the question.

Meet Ikhana

Your Personal Guide on Every Page

From the first click to the final step, Ikhana, your on-screen tutor, shows you how it all works. Every field, every button, every page explained with clarity, right where you need it.

On the Trends Dashboard, Ikhana explains how to read the gap between assigned and completed trend lines, what the cumulative completion line means relative to a planned pace, and how to use date range filters to isolate a specific project period versus the full operational history. New team members understand what the charts are telling them before they make a management decision based on a misread of the data.

Learn more about Ikhana

What the three metrics give your operation

Tasks Completed per Day. The daily count of tasks moved to completed status, plotted over the selected period. Shows the throughput rate of the team on a day-by-day basis whether completion volume is stable, accelerating, or declining. High-completion days and low-completion days are both visible in context, which distinguishes a normal day-to-day variation from a pattern of consistently declining daily throughput that warrants investigation.
Tasks Assigned per Day. The daily count of new task assignments over the selected period. Plotted alongside Tasks Completed per Day, this metric shows whether the team is receiving more work than it is completing each day. A persistent gap between assigned and completed where assigned consistently exceeds completed is the trend signal that a backlog is actively accumulating before it appears in overdue counts or missed deadlines.
Cumulative Tasks Completed. The running total of all tasks completed since the start of the selected period. Compared against a planned baseline pace, this metric shows whether total completed work is ahead of, behind, or on track at any point in the project or period. The cumulative view is what converts daily rate data into a project health indicator showing not just what happened today but whether the full body of completed work reflects the pace required to meet the end-of-period target.

What PCG learned across 31 years of operations tracking system builds: the teams that hit their task targets consistently were not the ones that worked harder on the last day of the month. They were the ones where the gap between planned and actual pace was visible early enough to act on it.

The Trends Dashboard provides that early visibility. A cumulative line that is 15% behind its planned pace by day 8 of a 20-day period is a recoverable situation 12 remaining days to close a gap that amounts to roughly 1.5 extra tasks per day. The same gap discovered on day 18 is not recoverable without extraordinary effort. The difference between those two outcomes is not the size of the gap. It is when the gap was visible and therefore when the decision to close it could be made.

What operations see after deployment

Backlog accumulation is visible as it begins rather than after it has compounded. The gap between assigned and completed trend lines widens visibly before the accumulated backlog shows up in overdue counts. The management response happens at day three of a widening gap rather than at day ten when the backlog has reached the point where closing it requires pulling resources from other work.
Project and period targets are tracked against actual pace throughout the period rather than discovered at the end. The cumulative completion line shows project health in real time. A project that is on track by mid-period stays on track because the trend has been visible and managed. A project that fell behind mid-period had the opportunity to be corrected before the deadline made correction impossible.
Daily throughput patterns become legible rather than invisible. A team that consistently completes fewer tasks on Mondays and Thursdays than on other days has a pattern visible in the trend chart that is invisible in weekly totals. That pattern may reflect scheduling decisions, task type distribution on those days, or team composition and it is a management conversation that the daily trend data makes possible.
End-of-period surprises decrease. When cumulative completion is tracked in real time throughout the period, the final day is a continuation of a known trajectory rather than a revelation. Operations managers who check the Trends Dashboard regularly arrive at month-end or project close with an accurate expectation of where things will land rather than discovering the final number for the first time when the period closes.

Questions operations and project teams ask before deploying FireFlight

What does the Trends Dashboard show in FireFlight?

The Trends Dashboard shows three daily task metrics over time: Tasks Completed per Day, Tasks Assigned per Day, and Cumulative Tasks Completed. Together they show whether task throughput is keeping pace with assignment volume, whether daily completion rates are trending up or down, and what the running total of completed work looks like against the project or period baseline.

What does it mean when Tasks Assigned per Day consistently exceeds Tasks Completed per Day?

When assignments consistently outpace completions on a daily basis, the team's open task queue is growing every day. The gap between the two lines on the trend view is the net daily accumulation. A small and stable gap may be acceptable. A widening gap over multiple days signals a capacity problem. Catching that widening gap on day three is considerably less disruptive than catching it on day fifteen when the accumulated backlog requires a schedule restructure to clear.

What does Cumulative Tasks Completed show that daily counts cannot?

Daily completion counts show how much work was finished on a specific day. Cumulative Tasks Completed shows the running total of all completed work against the period or project baseline, making it possible to see whether the team is ahead of, behind, or on track relative to where completion should be at this point in the timeline. A project planned for 200 tasks over 20 days should show a cumulative line of approximately 10 tasks per day. If the cumulative line is running below that pace by day 8, the project is already behind a fact that daily counts alone would not make immediately obvious.

How does this dashboard connect to point-of-work time tracking in FireFlight?

The Trends Dashboard reads from the same task records that the Time Tracking on Job app writes to. When a technician marks a task complete in the field, the completion registers in the Trends Dashboard immediately. Because time is logged at the point of execution rather than at end of day, the daily completion count reflects what actually happened during the day rather than what someone reported having done when filling out a timesheet after the fact.

How does the Trends Dashboard differ from the Volume and Status Dashboard?

The Volume and Status Dashboard shows four current-state work order counts at a point in time. The Trends Dashboard shows task-level daily rates over a period, which reveals the direction of change rather than the current state. Volume and Status answers the question of where things stand right now. Trends answers the question of whether the operation is improving, holding steady, or declining over the past days or weeks. Both views are needed for different management decisions.

Can the Trends Dashboard be filtered by team, project, or date range?

Yes. The three trend metrics can be filtered by team member, project, work order type, site, or date range depending on the configuration deployed for the operation. Filtering to a specific project shows whether that project's daily task throughput is tracking to its planned completion rate. Filtering to a specific team member shows individual daily productivity trends. The unfiltered view shows the aggregate trend across all tasks in the system.

How long does it take to deploy FireFlight task trend reporting?

Most operations are running live task trend dashboards in weeks, not months. The Trends Dashboard reads from the task and time tracking records that the broader FireFlight deployment captures. No separate data pipeline or reporting configuration is required beyond the base system setup. The trend lines begin populating from the first day tasks are logged and completed in the system.

If your current view of task completion shows you today's count but not whether that count is moving in the right direction or whether cumulative progress is on pace with your target, you are managing by point-in-time data when trend data is available. FireFlight's Trends Dashboard shows assigned versus completed rates and cumulative progress in real time from task records logged as work happens. Configuration takes weeks, not months.

Schedule your free consultation

Allison Woolbert

Principal, Phoenix Consultants Group | Developer, FireFlight Data Systems

PCG founded 1995. 500+ applications built across 31 years, roughly one-third in regulated environments where software failure carries direct operational and compliance consequences. FireFlight is the platform built from that body of work. When you contact PCG, Allison is the person who answers.

phxconsultants.com LinkedIn

FireFlight Data Systems is a product of Phoenix Consultants Group. PCG founded 1995. All system configurations are custom-built for each deployment. Implementation timelines, module availability, and integration scope vary by organization. Contact PCG directly to discuss requirements specific to your operation.