Build a rolling equipment-rental forecast from tickets, POs, and work plans

By RentalSpend · October 7, 2026

Use three buckets: expected work, committed spend, and actual on-rent charges. For rental spend, forecast the full charge set from the contract, not just the base rate, and roll the buckets forward each week or month.

Build the forecast in three layers: expected, committed, and actual. Put open tickets and unapproved planned work in expected, move approved purchase orders and confirmed reservations into committed, and put only billable on-rent time plus approved add-ons into actual. For equipment rentals, do not forecast from the base rate alone: the contract usually controls when time starts and stops, and many agreements treat fuel, delivery and pickup, surcharges, environmental fees, cleaning, damage, and similar items as separate charges, so the forecast needs each of those pieces, not just the daily or weekly rental rate.^{[1][2][3][4][5][6]}

Set up the forecast buckets

The cleanest way to build the forecast is to separate every expected rental dollar into one of three buckets. That keeps you from double counting the same job as both planned and committed, and it makes the weekly roll easier to explain to operations and project managers. Commitment systems are commonly used this way: they track future spend against budget, and many project systems can substitute open commitments for estimated-to-complete amounts when you roll a forecast.^[1][7][8][9]

1. Expected: open tickets, planned equipment moves, planned lifts, or other work that has been requested but is not yet committed.
2. Committed: approved purchase orders, confirmed reservations, and other amounts your process treats as a formal spending commitment.
3. Actual: equipment already on rent, plus invoice-ready charges that are supported by the contract, the rental agreement, and the documented rental period.

Sources: ^[1][2][7]

The exact trigger for moving an item from expected to committed depends on your process. Some companies move work only when the PO is issued. Others reserve spend when the request is approved, then convert to committed when the supplier accepts the order. Use one rule consistently so the same job does not sit in two buckets at once.^[1][2][7]

Build the base forecast from current work

Start with the work you already know about. Pull open tickets, open requisitions, approved but unissued POs, confirmed reservations, and active rentals. Group them by project, cost center, branch, or whatever rollup your close process uses. Then assign each item to a bucket based on status, not on guesswork. If a ticket is still open and no PO exists, keep it expected. If a PO exists, move the committed amount to committed. If the equipment is already on rent, move the contract-supported charges into actual.^[1][2][7]

1. List all open tickets and planned work for the forecast period.
2. Match each item to a PO, rental agreement, or reservation if one exists.
3. Separate active rentals from not-yet-started work.
4. Remove any canceled, closed, or final-closed items so they do not stay in the forecast.
5. Keep a log of what moved from expected to committed so the roll-forward is explainable.

Sources: ^[2][7]

Forecast the full rental charge set, not only base rent

This is where many forecasts go wrong. Rental terms often allow extra charges beyond base rent, and the contract controls whether they apply. Common examples include refueling, delivery and pickup, transportation surcharges, environmental fees, mileage, cleaning, taxes, damage, and other miscellaneous charges. Some suppliers also make off-rent timing depend on a specific confirmation step or return condition, so the day charges stop may not be the day the field crew says the machine is no longer needed.^[3][4][5][6]

Use the current rental agreement and rate sheet, then check recent invoices for recurring line items that may not be obvious from the base rate alone. If a cost appears on invoices only under certain conditions, forecast it only for jobs where those conditions are likely to happen. If the charge depends on fuel level, pickup timing, or delivery distance, estimate it separately instead of burying it inside the rent rate.^[3][4][5][6]

Roll the forecast forward each week or month

A rolling forecast should refresh on a fixed cadence, usually weekly for active projects or monthly for a broader management view. On each cycle, do three things: age the open tickets, replace any newly issued PO amounts in the committed bucket, and update actuals from invoices, off-rent confirmations, pickup records, and equipment return dates. The point is not to predict every invoice perfectly; it is to keep the forecast current enough that budget owners can see which dollars are still flexible and which are already tied to real work.^[1][2][7][3]

1. Age open tickets: push work that slipped into the next period, and remove work that was canceled or deferred.
2. Replace planned amounts with committed amounts when a PO, reservation, or signed rental agreement exists.
3. Book actuals only when the rental is truly billable under the agreement and the charge is supported by the invoice evidence.
4. Carry forward any unbilled on-rent time and any approved add-ons that have not yet hit the invoice.
5. Reconcile the roll to the prior period so the change is visible and explainable.

Sources: ^{[1][2][7][3][4][5]}

Illustrative example: a one-month forecast roll

Suppose you are forecasting next month for one project. You have 3 open tickets for planned equipment work at 1,800.00 each, 2 approved POs for confirmed rentals at 4,500.00 each, and 1 active rental already on site with 900.00 of billable on-rent time expected next month. You also expect one delivery charge of 250.00 and one refueling charge of 75.00 on the active rental because the contract allows those items when the machine is delivered and returned under less-than-full fuel conditions. The monthly forecast would be built from those pieces, not from a single blended rate.^{[1][2][3][4][5][6]}

In that example, the forecast total is 15,625.00. If the 3 tickets later become approved POs before month-end, move 5,400.00 out of expected and into committed. If one active rental is returned early, reduce actuals and, if the contract allows, keep only the charges that still apply. If a delivery fee was already billed this month, do not carry it again into next month’s forecast.^{[1][3][4][5][6]}

What to do when the forecast does not tie out

When the forecast looks too high or too low, start with status mismatches. The most common issue is double counting the same job as both open and committed. The next most common issue is using the base rent rate while leaving out charges that the contract treats separately. A third issue is timing: the field team may think the rental ended, while the contract says charges continue until off-rent notice, pickup, or return confirmation is recorded.^{[2][3][4][5][6]}

1. Check whether any open ticket already has an approved PO or reservation and should be moved out of expected.
2. Compare the forecasted rental days to the contract language on when rent starts and stops.
3. Review recent invoices for recurring line items that your model is missing.
4. Confirm whether your organization wants soft commitments at approval stage or only after PO issuance.
5. Look for canceled, closed, or final-closed items that were never removed from the forecast.

Sources: ^{[1][2][7][3][4][5]}

A good control is to keep a simple variance note for every major change in the roll. If a ticket moved from expected to committed, record the date and status change. If a rental ended, note the off-rent confirmation or return record. If extra charges were added, note the contract term or invoice support. That makes the forecast useful for management and easier to defend at close.^{[1][2][3][4][5][6]}

Next steps: choose one status rule for expected versus committed, pull your open tickets and active rentals into one file, and test the forecast against the last two or three invoices for the same jobs. If the invoice shows charges you did not forecast, update the template before the next roll so the same miss does not repeat.^{[1][2][3][4][5][6]}

← All resources