Trade Partner Performance Report
Understand the Trade Partner Performance report — how to read each section, and exactly how a partner's on-time timeliness is calculated, including the special handling for schedule tasks.
Overview
The Trade Partner Performance report gives you a complete picture of how one trade partner has performed over a stretch of time. Pick a partner and a date range, and the report gathers every task they completed in that window and shows — at a glance and in detail — how consistently that work finished on schedule. It's the place to prepare for a partner review, spot where a partner is slipping, and back up the conversation with specifics.
The report is read-only and always reflects your live task data, so there's no overnight refresh to wait for. For a ranked, side-by-side view of all your partners at once, see the Trade Grade Leaderboard — this report is the deep dive on a single partner.
Choosing what you see
Three controls at the top shape the report. All three are saved in the page's web address, so you can bookmark or share a link and land on exactly the same view.
Trade partner — the one partner the whole report is about. Until you pick one, the report just shows a prompt to choose a partner.
Date range — Last 30 days, Last 60 days (the default), Last 90 days, or Custom with your own From and To dates. Tasks are included based on the date they were completed.
Task type — chips for Schedule, Task, Inspection, and Procurement, plus All. Selecting one or more types instantly narrows every part of the report to just those tasks; All brings everything back.
What you'll see
Once a partner is selected, the report stacks several sections — every one of them built from the same set of completed tasks, so they all move together when you change a filter:
Scorecard — headlined by the on-time completion rate (a percentage shown in a ring gauge; there's deliberately no letter grade). Alongside it: how many tasks were completed, the on-time vs. late split, the typical (median) result, and the best and worst outcomes.
Timeliness distribution — a histogram showing the spread of results, with late finishes to the left, On time in the center, and early finishes to the right. It tells you at a glance whether a partner is steady or all over the place.
Breakdown — performance grouped by community (worst-performing first, so problem areas rise to the top) or by task type, each with an average bar and its own on-time rate.
Detail table — every completed task, one per row. Use Group by to collapse the rows by Community & Lot, Community, Lot, Task, or None; each group header shows the average timeliness of the tasks inside it. Grouping by Task lines up every instance of the same task (for example, every "Drywall punch") so you can see how a partner does on that specific kind of work.
A Print button next to the title opens your browser's print dialog. The printout hides the on-screen controls, expands every group so nothing stays hidden, and stamps the partner name and date range at the top — and your browser's "Save as PDF" option turns it into a shareable file.
How timeliness is calculated
Every number in the report comes from one value per completed task: its Timeliness. It's counted in working days — weekends and your builder's holidays are skipped — so a task due Friday and finished the following Monday is one day late, not three.
Finishing early shows as a positive number of days (for example, "2 days early").
Finishing right on the target is "On time".
Finishing late shows as days late.
The one thing that changes from task to task is what target the finish is measured against. There are two cases.
Regular tasks: measured against the due date
For Task, Inspection, and Procurement work, the target is simply the task's due date. Finish on or before it and the task is on time or early; finish after it and it's late. A standalone task's due date is its own commitment, so that's exactly what it's held to.
Schedule tasks: measured against the plan
Schedule tasks are handled with more care, because a due date on a live schedule moves around constantly as jobs shift. Instead of the live due date, a schedule task is scored against its planned finish — the plan that was captured the moment the task was created from a schedule template. That plan is frozen: once it's recorded, later edits to the task's "Days to complete" or its due date don't change the score.
Here's the key idea, using a simple week. Say a one-day schedule task can start Monday and is due Wednesday — a three-day planned window for one day of work:
ℹ️ Slack is the partner's. Notice the trade is never charged for Monday and Tuesday — the two days they had but didn't need. A schedule window is often wider than the job (a one-day task might sit in a three-day gap between the job before it and the job after). Because we don't record the exact day work started, that built-in slack belongs to the partner: finishing anywhere inside the planned window counts as on time.
A few more things follow from scoring against the frozen plan:
Padding the schedule can't buy a better score. If a project manager later stretches that task's "Days to complete" from 1 to 3 — pushing its due date out to Friday — a task finished Friday is still two days late. The score follows the original plan, not the new due date.
A late start isn't held against the partner. The plan is applied from the day the task could actually begin. If the whole task slid because the job before it ran long, the partner is judged from when they could really start — not against a date that quietly passed while they were still blocked.
Early finishes are a win. Beating the plan shows up as days early, right alongside every other result.