What is hidden in this price request?
Three different promises, often in one workbook. A lump sum is a price for a defined scope, payable whether that scope was easy or not. A schedule of rates is a price per unit for work the buyer may or may not instruct. A provisional item is a rate or sum the buyer may activate later. The comparison total that the evaluation team will add up is not the revenue you will earn.
The pack’s pricing instructions control the meaning. If they say quantities are indicative, they are indicative. If they are silent, write the assumption and ask. Do not repair silence by treating the comparison total as a forecast.
How does a lump sum fail you?
It fails when the task list is not closed. “Planned preventative maintenance of mechanical plant” is not a quantity. It is a list in another schedule, plus every asset the buyer later says was obviously included. Rise-and-fall, if any, is a separate clause. If the lump is fixed for three years with no index, the labour assumption inside it is a bet. That is the recurring-service problem on thin-margin FM tenders, read here as a scope question rather than a margin question.
How does a schedule of rates fail you?
It fails when you staff and overhead-recover as if the indicative hours will occur. Four hundred business-hours on a comparison sheet is a scoring device. Payment is for hours instructed. Under-run is idle labour and stranded overhead. Over-run is a roster problem, not a windfall, if the rate was built on a quiet mix. Mix is the second trap: the same total hours with twice the after-hours share is a different job.
How does a provisional item fail you?
It fails when the bid case includes it as expected revenue, or when the rate is used to subsidise the firm work. If the buyer never instructs the chiller overhaul, you have performed a discount in public and collected nothing. Price provisionals to stand alone. Leave them out of the base comparison you take to the gate.