A Rebate or Credit Programme Ends
Why this matters
Of every shock in this group, this is the one with a date printed on it, and shops still get caught by it every time. A programme ends, the last eight weeks are the busiest of the year, and then two things happen: a run of rebates gets denied on paperwork nobody had time to check, and the quarter that follows comes in well under a normal quarter rather than back at it. Both are foreseeable weeks in advance from records you already hold. The whole card is about spending an afternoon on that now instead of a quarter arguing about it later.
Two kinds of ending, and only one has a calendar
A dated ending. The programme states a termination date, usually keyed to when the work is done rather than when it is sold. You can plan against it, and everything below assumes this case.
A funded-out ending. Many utility and state programmes run on a fixed budget, first come first served, and simply stop when the money is gone - often mid-quarter, with an announcement rather than a notice. There is no calendar to plan against, only queue position. Where the programme offers a reservation at application, the reservation date is the only date that protects you, and a shop that installs first and applies later is gambling with someone else's money. Find out which kind you are in before you sell anything on it, because the operational answer is completely different: a dated ending rewards sequencing, a funded-out ending rewards filing early.
One caution about published end dates in general. Federal energy tax credits in particular have been created, extended and terminated by statute inside a single cycle in recent years, so any expiry date you are carrying in your head is the single most likely thing here to be out of date. Pull the current date from the administering authority's own publication rather than from memory, a supplier flyer or an article, and check it again before each selling season.
The demand shape: a rush that borrows from the quarter after it
An announced end date does not create demand. It moves it. Customers who were going to buy in the next several quarters buy now, so the final period runs hot and the periods after it run cold, and the hole is deeper than a normal slow spell because the work that would have filled it has already been done.
Put numbers on it. Suppose the affected product line normally does 25 units a quarter and the final quarter does 40 under the deadline rush. That is 15 units pulled forward. If they came evenly out of the following two quarters, each of those runs at 25 minus 7.5, or 17.5 units - 70 percent of normal for that line, for two consecutive quarters.
Now size it against the business. If that line is 30 percent of total revenue, a 30 percent fall in it is 9 percent of total revenue (30 percent of 30 percent), sustained for two quarters. That is a large enough hole to be worth a plan and small enough that a plan actually covers it, which is precisely why it is worth making one during the rush rather than after.
The same mechanism runs through this whole group: the split between work that can wait and work that cannot decides how far demand can be moved in time, and Deferrable Versus Non-Deferrable Work and What a Downturn Touches derives it in full. Incentive-driven replacement is the most movable work a shop sells, which is exactly why a deadline moves so much of it.
Which date the programme actually keys to
Programmes key to different dates and the difference decides whether a job qualifies. The candidates are date of purchase, date of installation or in-service, date of application, and sometimes date of a required inspection or utility verification. Many programmes also impose a submission window measured from installation.
Read the programme rules and write the governing date and the submission window at the top of your pipeline sheet in plain words, because every decision below depends on it, and because supplier and distributor summaries of a programme are marketing documents rather than programme rules.
Where the money goes wrong
The job that misses the governing date. Backorders, a dependency on another trade, a customer who wants the install after a holiday. The rebate fails and somebody absorbs it.
The paperwork that was never going to pass. Model and serial numbers, a certificate of matched-system performance where one is required, an invoice that itemises what the programme demands, proof of the old equipment's disposal, a pre-installation photograph. What a processor actually checks is its own subject - see related: What a Rebate Processor Actually Checks - and the point here is that the last eight weeks before a deadline is when that discipline slips, on the highest volume of the year.
The customer who believes the rebate is yours. If it was quoted as part of the price, they will treat a denial as your failure regardless of whose paperwork was late, and they are not being unreasonable: you put it on the quote.
The product mix that existed because of the incentive. The tier that only ever sold with the credit attached, plus the stock and the training behind it. After the deadline that tier does not sell at the same rate at the same price, and inventory of it becomes slow-moving rather than worthless, which is a cash problem rather than a write-off.
The quoting language that puts the risk where it belongs
Rebate risk is allocated by your contract, and if the contract is silent it lands on you by default in practice, because the customer has one document and it has your name on it. The shape that works, and that customers accept:
- The contract price stands on its own, with no rebate netted against it.
- The rebate appears as a separate, clearly labelled estimate, stated as subject to the programme's rules and to funds remaining.
- The conditions are named - the governing date, the submission window, the documentation required - rather than gestured at.
- Who files is stated. If you file on the customer's behalf, say so and say by when.
- What happens if it is denied or the programme closes is stated: the contract price does not change.
Then say the sentence out loud at the kitchen table: we will file it for you, and we will not price your job on it. That is what stops a denial from becoming a dispute, and it sells better than a rebate-inclusive number that later has to be defended. What you must not do is guarantee an outcome a third party decides - and where a customer pushes for exactly that, or where a denied rebate turns into a demand for money, the contract question is for your own attorney rather than for a form of words you improvise on the spot. That is the one legal fork in this card.
The pipeline audit, worked
Run this once when the end date is announced and again weekly inside the final month. Governing date here is installation, with applications due within 60 days of installation, and the audit is run 45 days before the installation deadline.
| Job | State today | Days to install | Slack to deadline | Disposition |
|---|---|---|---|---|
| A | Sold, equipment in stock, scheduled | 12 | 33 | Safe. Confirm the documentation fields at install, not after |
| B | Sold, equipment on backorder, supplier ETA 38 days | 41 | 4 | At risk. Offer a qualifying in-stock model today, or reset it in writing |
| C | Sold, waiting on a panel upgrade by another trade, no date | unknown | unknown | Not promisable. The dependency is not yours. Write to the customer this week |
| D | Quoted, not sold. Normal close 21 days, lead time 14 | 35 | 10 | Sellable with a stated order-by date in the proposal |
| E | Installed 3 days ago, application not filed | done | 57 of 60 | Safe only if filed. File this week |
| F | Installed 71 days ago, application not filed | done | expired | Lost. Decide who absorbs it and tell the customer before they ask |
Six jobs, and they need four different actions. A and E are administrative - do the paperwork on time and nothing else happens. B and D are commercial - both are saved by a decision made today and lost by one made in three weeks. C is a communication problem, and the failure mode is saying nothing because the outcome is still technically possible. F is already lost, and the only remaining decision is whether the shop absorbs it or holds the customer to the contract.
Row F is why the audit exists. It was not lost at day 71, it was lost around day 45 when nobody was tracking filed-versus-installed, and the shop will not discover it at all unless someone reconciles installations against applications. That reconciliation is the single most valuable line in this card: every week, list installs with a rebate attached and tick the ones filed. It takes minutes and it is the only control that catches an expired window before the customer does.
Planning the trough while you are still in the rush
The rush is the worst time to sell anything and the best time to book something, because you are in more customers' homes in eight weeks than in the rest of the year. Two moves, both made during the rush:
Schedule into the hole rather than selling into it. Every rebate install is a chance to put a maintenance visit, an agreement start, or a deferred second-phase job on the calendar for the quarter after the deadline. You are not asking for a decision, you are asking for a date.
Decide the crew plan before the last week. A hole of roughly 9 percent of revenue across two quarters, as sized above, is absorbable by holding hiring and using the quiet weeks for training, the price-book review and the maintenance backlog. It is not absorbable if you hired for the rush - see related: The Boom That Is More Dangerous Than the Slump.
What not to do is discount into the trough. The customers who were price-sensitive about that product line already bought, with help. Cutting price afterwards spends margin on demand that is not there.
When the incentive was the whole value proposition
The hardest version of this is the shop whose selling story was the rebate. The conversation was the incentive, the comparison against a competitor was the incentive, and the product tier existed because of it. When it ends, that shop has no story and discovers it during its slowest quarter.
The test is worth running before you need it: describe the highest tier you sell, out loud, without mentioning any incentive. If the case does not stand up - operating cost, comfort, reliability, warranty, what the customer actually experiences - then the incentive was not helping you sell it, it was selling it, and you have a product problem that the programme was hiding. Build the case now, while the rebate is still there to close the gap, because after the end date you will be building it in front of customers who are saying no.
References
- The administering authority's own programme rules - the utility, the state energy office, or the statute itself - for the governing date, submission window and documentation, rather than a supplier or distributor summary
- See related: What a Rebate Processor Actually Checks, The Paperwork Chain Behind a Rebate and Who Owns Each Link, The Cash Flow Shape of Rebate-Heavy Work, Explaining Rebates and Incentives Without Overpromising
- See related: Deferrable Versus Non-Deferrable Work and What a Downturn Touches, The Boom That Is More Dangerous Than the Slump