ScheduledHVAC
    Analytics

    Your HVAC Revenue Forecast Needs a Dispatch Board

    Dale Whitmore looks at the number for his banker and says, "Forty-five jobs a week times our average ticket. That's the forecast." It is a reasonable place to start when the schedule is the clearest picture of the business.

    A blended ticket hides the work.

    Dale is an illustrative five-technician owner, not a client. He once put his capacity calculation in a drawer because it conflicted with the number he had given his banker. This hypothetical four-week model brings the pad back out and asks whether hours, completed work, revenue, and cash actually reconcile.

    What must the forecast count before dollars?

    Build separate rows for the work you sell. For each row record qualified labor hours, elapsed time or person-hours per booked job, demand sufficient to fill those bookings, expected completion within the period, and expected realized invoice value.

    Be consistent about units. A two-person installation requiring ten hours per person consumes twenty person-hours. A consultation does not become an installation simply because a proposal was accepted. Keep uncompleted projects and future bookings out of the current month's completed-work revenue case.

    Dale's established weekly baseline begins with 200 paid hours and roughly 117.5 raw billable hours. The historical mix and scheduling headroom produce an approximately 45-job planning target. That target already includes a buffer; multiplying it by another automatic reserve would duplicate the deduction.

    For the new example, build directly from hours. Four identical assumed weeks provide 470 raw billable hours. Set aside seventy hours as an explicit scheduling allowance, leaving 400 net schedulable person-hours. This is an illustrative monthly capacity assumption, not a productivity benchmark or an additional deduction from forty-five jobs.

    Use true weekly capacity to replace those inputs.

    Dale writes HOURS above the first column. The forecast cannot buy its way around a shortage by increasing the average ticket in the next column.

    How do hours become a monthly revenue case?

    Assume 240 of the 400 net hours go to service and 160 to installation, with enough suitable demand and ready work to book them. All installation labor comes from Dale's same five-person pool. These are allocation assumptions, not an additional crew.

    For this simplified worksheet, service uses two billable person-hours per booked job. Installation uses twenty. Non-billable travel and administration are already outside this billable-hour baseline, so they are not deducted again from these durations.

    Assumed monthly inputServiceInstallation
    Allocated schedulable person-hours240160
    Person-hours per booked job220
    Bookings supported1208
    Complete within the month90%75%
    Expected completed jobs1086
    Realized invoice per completion$500$9,000
    Modeled completed-work revenue$54,000$54,000

    The total is 128 bookings, 114 expected completions, and $108,000 modeled revenue. Do not add bookings and completions together. This work mix differs from the historical forty-five-job week, so the two job totals are not interchangeable.

    The model assumes no speculative refill of cancellations or delays. Scheduled work consumes the allocated blocks; lower completion leaves uncertainty and unused time, not guaranteed replacement sales. Use service versus install planning to check the mix.

    Dale replaces one average-ticket multiplication with two rows. Equal modeled revenue now comes from very different numbers of jobs and different completion assumptions.

    What changes when demand or completion slips?

    Capacity is a limit, not proof that enough suitable customers will book. Tie the 128-booking case to existing orders and a work-specific demand forecast. Use how many leads your company needs to show the inquiry and booking assumptions behind any unfilled portion.

    Then test uncertainty without inventing extra hours. Holding the same bookings and prices, suppose service completion falls to eighty percent and install completion to fifty percent. That yields ninety-six service jobs at $500, or $48,000, plus four installations at $9,000, or $36,000. Downside revenue is $84,000.

    For a separate upside case, assume ninety-five percent of service bookings and 87.5% of install bookings complete. That gives 114 service jobs producing $57,000 and seven installations producing $63,000: $120,000 total. It still uses the same allocated booking capacity. Those rates are assumptions, not targets or a promise.

    Test demand, price, job duration, staffing, and equipment delays too. Change one input at a time when explaining the cause. If a longer install consumes more hours, reduce the supported projects instead of retaining eight and quietly exceeding 160 hours.

    Dale has three totals he can explain: $84,000, $108,000, and $120,000. He does not choose the largest because it looks better in the application. He shows what would have to be true for each.

    When does the invoice become usable cash?

    Return to the $108,000 base case. For simplicity, assume all modeled completed work is invoiced within the month and belongs in that month's revenue under the accounting basis being illustrated. Your accountant must align the actual forecast with your accounting method and contracts.

    Now assume seventy-five percent of the $54,000 service revenue is collected that month: $40,500. Assume fifty percent of the $54,000 install revenue is collected: $27,000. Current-work cash receipts total $67,500, leaving $40,500 uncollected from those invoices.

    Suppose opening receivables are $30,000 and $20,000 of them are collected. Total cash receipts become $87,500. The remaining opening receivables of $10,000 plus new uncollected invoices of $40,500 produce $50,500 closing receivables, assuming no other movements.

    With $15,000 opening cash and $92,000 in assumed payments due during the month, closing cash is $15,000 + $87,500 − $92,000 = $10,500.

    That is a cash illustration, not a profit calculation. Payments can include items treated differently in financial statements. Deposits, financing payouts, credits, bad debt, taxes, and payment timing need their own actual records; this simplified case assumes no other receivable or receipt movements.

    Dale sees why a $108,000 revenue case cannot be placed unchanged in the cash-receipt column. The invoices and the bank balance answer different questions.

    What should a lender be able to trace?

    Keep the operating worksheet behind the financial statements. Show the staffing roster, hour assumptions, work mix, existing commitments, forecast bookings, completion evidence, realized prices, and collection schedule. Identify the source and owner of each input.

    SBA business-plan guidance describes historical income statements, balance sheets, and cash-flow statements for established businesses, plus forecast statements and capital expenditure budgets. It recommends more detailed first-year quarterly or monthly projections. Use that as planning guidance, then ask the prospective lender for its specific documentation requirements.

    Reconcile forecast revenue to the books with the person responsible for accounting. Explain one-time events, seasonality, and the timing of the proposed use of funds. A vehicle purchased this month may need recruiting, equipment, and a ramp period before it adds independent production. Use the hiring worksheet when expansion depends on a new employee.

    This operating model alone does not establish profit, debt-service coverage, credit eligibility, or approval. Do not label the remaining cash available for a new payment without modeling existing obligations and the lender's required analysis.

    Dale can now show how the number was built and where it is vulnerable. That is a stronger conversation than defending a revenue target with “we can do forty-five.”

    Who updates the forecast when the board changes?

    Give dispatch responsibility for usable hours and commitments, the office responsibility for booking and outcome status, and the financial owner responsibility for invoices, collections, and payment dates. A shared identifier should connect the records.

    Use call tracking and attribution to trace the demand side without counting repeat contacts as extra opportunities. Use service and install reporting to maintain the split. If the month contains different weekly constraints, use seasonal capacity planning rather than assuming four identical weeks.

    Update near-term operations weekly and reconcile the financial forecast to actual statements monthly. Retain the previous version, explain the variance, and change the next decision. A forecast that never changes may be a target in disguise.

    Dale leaves the legal pad out. Beside the banker's total are the hours that support it, the jobs that might not complete, and the invoices that might not be collected yet. He can finally explain the forecast without asking the reader to believe the board is fuller than it is.