Pipeline reporting is a structured view of every opportunity that is not yet a sold job: where it sits, what it is worth, who owns it and how long it has been there. For an HVAC, plumbing, roofing or restoration company, a good pipeline report answers four questions on one screen: are new leads arriving, are they answered fast, are estimates moving toward signed work, and will the next 60 days of revenue cover the payroll and trucks you already have.
Most small service businesses do not need a sales-team dashboard with forty widgets. They need a short set of numbers that tie the phone, the estimate and the completed job together. This guide shows which reports to build, which metrics go on them, how to lay out the dashboard and how to keep the numbers trustworthy when your data lives in several tools.
TL;DR
- A pipeline report lists open opportunities by stage, value, owner and expected close date, then adds velocity, stage conversion, deal age and slippage.
- Start with five views: pipeline by stage, stage conversion, lead response time, pipeline coverage and a weekly movement report.
- Connect the pipeline to field service reporting (completed jobs, completed revenue, canceled jobs, future scheduled jobs) so a won estimate becomes a measurable outcome.
- Keep the first screen to six to eight panels, label weighted versus unweighted values, and build separate views for technicians or dispatchers, managers and owners.
- Reports are only as good as the data under them: define stages, merge duplicates and sync systems before you chart anything.
Table of Contents
- What pipeline reporting means for a service business
- The five reports to build first
- Tying the pipeline to completed jobs
- Building a pipeline dashboard that people use
- Keeping the numbers reliable across systems
- Our perspective
- Where Equinox fits
- FAQ
- Sources
What pipeline reporting means for a service business
In a software company, the pipeline is a list of deals. In a service business it is every inbound call, web form, text and referral that could become a booked job or a signed estimate. A sales pipeline report is a structured view of active opportunities by stage, value, owner and expected close date, and it becomes useful once it moves beyond a static list into velocity, conversion, age and slippage.
For contractors the same idea is described as tracking opportunities that are not yet under contract, staged by progress and weighted by the chance of winning, so you can forecast future bookings and decide where to spend pursuit effort. It is also the forward-looking partner of backlog: backlog is work you have already sold, and pipeline is work you are still chasing. A roofer with a full backlog and an empty pipeline looks healthy in March and desperate in July. Reporting on both is what shows it early.
The practical definition for your shop: a pipeline report tells you how much potential work exists, how real it is and how fast it is turning into scheduled jobs.
What the report must show
Every pipeline report, whatever the tool, should carry the same backbone:
- Stage. Where the opportunity is right now (new lead, contacted, estimate scheduled, estimate sent, follow-up, won, lost).
- Value. The estimated job value, so you can total open pipeline.
- Owner. The estimator, CSR or salesperson responsible for the next step.
- Age. Days since the opportunity was created and days since it last moved.
- Source. Where it came from: Google Ads, Google Business Profile, referral, repeat customer, lead marketplace.
- Expected close date. Even a rough one lets you see slippage when it keeps getting pushed.
If you have not yet defined your stages, do that first. Vague stages produce vague reports, and our guide to pipeline stage design for service business deals walks through the criteria that make a stage something a person can actually verify.
The five reports to build first
Research on pipeline management points to a consistent core: pipeline volume by stage, stage conversion, deal velocity, slippage and win rate by segment. Translated for a service business, that gives you five reports.
| Report | Question it answers | Core metrics | Review rhythm |
|---|---|---|---|
| Pipeline by stage | Is there enough work in the funnel? | Count and dollar value per stage, open pipeline total | Daily glance, weekly review |
| Stage conversion | Where do opportunities stall? | Percent moving from each stage to the next | Weekly or monthly |
| Lead response | Are we answering fast enough? | Time to first response, missed calls, after-hours handling | Daily |
| Pipeline coverage | Can we hit the revenue target? | Open pipeline divided by target revenue | Weekly |
| Weekly movement | What changed this week? | New, advanced, won, stalled, lost, net change in count and value | Weekly |
Pipeline by stage
This is the picture most people mean by a pipeline dashboard: bars or columns showing how many opportunities, and how many dollars, sit in each stage. One thing to watch is the mix. Raw totals alone can reassure people without predicting performance when the underlying composition is different, for example when most of the dollars are in one large commercial bid, or when half the value is in estimates that are six weeks old.
Stage conversion
Stage-conversion reporting shows the percentage of opportunities that advance from one stage to the next. It is more diagnostic than overall win rate because it points to the stage where deals stall. If 90 percent of booked estimates happen but only 20 percent of sent estimates get a reply, your problem is follow-up after the quote, not lead generation. A deeper look at stage-by-stage conversion rates shows the same logic in another industry: the stage with the sharpest drop is where you fix the process first.
Lead response
Lead response time measures how quickly a new inbound lead receives a reply. The point is simple: slow response can reduce conversion from leads you already paid to generate. For a plumber or restoration company, where the customer is often calling three companies at once, this is the report with the most direct dollar impact. Track median time to first response, the share of calls answered live, the share of missed calls that got a text or callback, and how after-hours inquiries are handled. Our piece on call center KPIs for service businesses covers the phone-side measures in more detail.
Pipeline coverage
Pipeline coverage compares total open opportunities with target revenue. A 1x coverage ratio means pipeline equals projected revenue, which leaves no room for the deals you will lose. Because most opportunities do not close, you generally want a multiple of your target, and the right multiple comes from your own historical win rate. If you win one in three estimates, you need roughly three times the target in qualified pipeline. For more on pipeline coverage ratios and how forecast confidence relates to target revenue, that explainer is a good companion.
Forecast views often split the number into confidence bands: commit, best case and worst case. A service business can use a simple version: signed or scheduled work, estimates with a verbal yes, and everything else.
Weekly movement
A weekly movement report is the one your Monday meeting should run on. It lists new opportunities, deals advanced, deals closed, deals stalled or lost, and net changes in count and value. It replaces the question "how are we doing?" with "what changed since last Monday, and why?"
Tying the pipeline to completed jobs
A sales pipeline stops at "won." A service business does not. Revenue is recognized when the truck rolls, the work is finished and the invoice goes out. That is why field service reporting and pipeline reporting belong together.
CRM insights in one major field service platform's documentation list pipeline KPIs such as Won Total, Close Rate, Average Opportunity Value, Average Days to Close and Open Pipeline Total, where open pipeline total is the estimated value of all open opportunities. The same vendor's month-over-month template shows how the other half is measured: completed jobs and completed revenue, sold estimate totals, lead calls, canceled jobs and future scheduled jobs within a selected date range.
Read those together and you get a chain you can audit:
- Lead calls come in.
- Some become opportunities with an estimate.
- A share of estimates are sold.
- Sold work becomes future scheduled jobs.
- Scheduled jobs become completed jobs and completed revenue, minus cancellations.
When revenue disappoints, the chain tells you which link broke. Plenty of leads but few scheduled jobs points to response and estimate follow-up. Plenty of scheduled jobs but high cancellations points to expectation-setting or scheduling. If your scheduling is manual, automated appointment scheduling for US service businesses can tighten the handoff from sold estimate to calendar slot.
Field service metrics worth adding
Do not add them all at once. Start with the numbers you already trust, then add one when it will change a real decision:
- Average ticket: completed revenue divided by completed jobs.
- Estimate close rate: sold estimates divided by estimates presented.
- Completed jobs and cancellations: a weekly count, with reasons for cancellations.
- Gross margin by job type: shows which services deserve more marketing.
- Average days to close: how long the sales cycle really runs for repairs versus replacements or large projects.
A clean rule is to ask, before each new metric, which decision it changes: hiring, pricing, marketing spend or quality control. If none, leave it off the first screen.
Building a pipeline dashboard that people use
A dashboard should be a shared reference point, not decoration. One practical framework builds the first screen around decision questions: is there enough pipeline, is it real, is it moving, and is enough new pipeline arriving. The same source suggests six to eight panels on the first screen, such as coverage, creation, aged share, size gap, stage mix, slippage, concentration and source mix.
A starter layout for a service company
| Panel | Decision question | What a bad reading looks like |
|---|---|---|
| Open pipeline total vs. target | Is there enough? | Coverage well below your historical win-rate multiple |
| New opportunities this week | Is new pipeline arriving? | Several weeks of decline, especially in peak season |
| Median response time | Is lead handling working? | Response measured in hours rather than minutes |
| Stage conversion | Is it moving? | A sharp drop between estimate sent and sold |
| Aged opportunities share | Is it real? | A large share untouched for 30 days or more |
| Source mix | Where should we spend? | One source producing most leads but few sold jobs |
| Slippage | Are expected close dates honest? | The same estimates pushed week after week |
| Completed revenue vs. sold | Is booked work becoming revenue? | Sold totals rising while completed revenue is flat |
Weighted or unweighted: label it
A weighted pipeline multiplies each opportunity's value by its probability of closing. An unweighted one just adds the dollar amounts. Both are legitimate, but mixing them is how a meeting goes sideways. Label every number on screen as weighted or unweighted, and keep the same convention month to month.
Separate views for separate people
One dashboard for everyone ends up serving no one. Guidance on CRM reporting recommends that reps see their own pipeline and tasks, managers see team pipeline and conversion, and owners see revenue, source return and trends, along with a three-second rule: a headline number should be understandable at a glance. Looking at dashboard views for individual reps, managers and leaders in other kinds of small businesses shows the same split.
In a plumbing or HVAC shop, that becomes:
- Front desk and dispatch: calls answered, callbacks due, leads awaiting first response, appointments tomorrow.
- Estimators and sales techs: their open estimates, follow-ups due today, personal close rate.
- Owner or GM: coverage, source return, completed revenue, margin and trend lines.
Keeping the numbers reliable across systems
The common failure in small service businesses is not the chart. It is the data underneath. Calls sit in a phone system, forms land in an inbox, estimates live in field service software, ad clicks sit in Google Ads and the books are somewhere else. A dashboard that pulls from all of them will show whatever the weakest connection allows.
Five habits keep a cross-system dashboard honest:
- Pick one record of truth per fact. Customer identity lives in one system. Job status lives in one system. Other tools read from them rather than keep their own copies.
- Write stage definitions down. "Estimate sent" should mean one verifiable event, not a judgment call. The pipeline stage criteria guide shows how.
- Clean before you merge. Duplicate contacts inflate lead counts and distort conversion. Set rules for matching, required fields and what wins in a conflict before combining records, as in our CRM data cleanup guide.
- Track the source from the first touch. Paid calls that never get tied to a job make your source report meaningless. Call tracking connected to Google Ads and your CRM closes that gap, so you can compare sources by sold jobs rather than raw calls.
- Map the process before you automate it. If a lead can take three different paths depending on who answered, the report will reflect that mess. Process mapping comes first.
Assignment matters too. When leads are handed out unevenly, response times and conversion differ by person for reasons that have nothing to do with skill. Testing your rules on a small sample, as described in our round robin lead assignment walkthrough, avoids chasing phantom performance gaps.
How often to refresh
Match the refresh rate to how fast the number moves. Open pipeline and composition metrics are worth refreshing daily, while slower-moving components can update weekly, and a dashboard should not refresh in the middle of a meeting because the numbers people just discussed would change under them. For a service shop, lead response and missed calls deserve a daily look, the weekly movement report belongs to Monday's meeting, and coverage and source return can be reviewed monthly.
Data-quality checks to run monthly
- Opportunities with no owner or no value.
- Opportunities with no activity for 30 days or more that are still marked open.
- Estimates marked sold without a scheduled job.
- Completed jobs with no matching opportunity or source.
- Duplicate customer records created by repeat callers.
- Lost deals with no reason recorded.
Each item on this list is a way for the dashboard to look better or worse than reality. Fix the pattern at the source, usually a required field or an automated sync, instead of correcting the data by hand every month.
Our perspective
Most reporting problems we see in service businesses are not reporting problems. They are handoff problems. A call is missed, a form never reaches the estimator, a sold estimate does not hit the calendar, and then the dashboard shows a number nobody believes.
That is why we build in this order: scope the workflow, write down the data map, connect the systems with least-privilege access, then report. Every build is documented, consent flows are explicit and there is a rollback plan, so a change to a tool does not quietly corrupt your numbers. One accountable technical lead owns the whole chain, which means the answering, the follow-up, the records and the reporting all agree with each other.
Our view is that a pipeline report should be the output of a working system, not a project in itself. When voice answering, qualification, follow-up, unified customer records and calendars run end to end, reporting becomes a by-product you can check, rather than a spreadsheet someone rebuilds every Friday.
Felix
Where Equinox fits
If your reports disagree because the phone, the CRM and the schedule do not talk to each other, the fix is upstream. We design lead generation systems, AI voice and messaging agents, done-for-you automations and custom software for US service businesses, built around unified customer records, calendars and reporting.
See how the pieces fit on our services overview, or review the way we scope and document each build before you talk to us.
FAQ
What are pipeline reports?
Pipeline reports show every open opportunity by stage, value, owner and expected close date. Good ones add velocity, stage conversion, deal age and slippage so you can see not only how much is in the pipeline but how fast it is moving and where it stalls.
What should a service business track on a pipeline dashboard?
Start with open pipeline versus target, new opportunities per week, lead response time, stage conversion, aged opportunities and source mix. Then add completed jobs, completed revenue and average ticket so sold work connects to finished work. Keep the first screen to six to eight panels.
How is field service reporting different from sales pipeline reporting?
Pipeline reporting covers opportunities before they become work: leads, estimates and follow-up. Field service reporting covers what happens after: scheduled jobs, completed jobs, cancellations, revenue and margin. Reading them together shows whether leads turn into finished, paid work.
How often should I update my pipeline report?
Refresh open pipeline and composition metrics daily, slower-moving components weekly, and avoid refreshing during a meeting. Lead response and missed calls deserve a daily check, while coverage and source return suit a monthly review.
Do I need a separate dashboard for each role?
Usually yes, though they can share one data source. Front desk staff need callbacks and response times, estimators need their own open estimates, and owners need coverage, source return and revenue trends. Role-specific views with a few headline numbers are easier to act on than one crowded screen.
Sources
- What is a sales pipeline report: metrics and templates
- Pipeline report definition for contractors
- CRM insights overview and pipeline KPIs
- Month-over-month analysis report template
- Sales pipeline management best practices
- Pipeline coverage and reporting guide
- Sales pipeline reporting and forecast confidence
- Sales pipeline report examples
- How to build a pipeline dashboard
- CRM reporting and analytics guide
- Sales pipeline stages and conversion rates
- Pipeline coverage and revenue forecasting
- Dashboard views by role