How to manage contractual technical hours without losing track
A technical-hours bank is the most common format in assistance contracts. The provider sells an annual number (for example, 72 hours) and the client consumes them as needed. The problem usually appears at the end of the second quarter, when the institution realises it has already spent 70% of the hours with half the year still ahead.
What makes an hours contract healthy
Three things separate a sound contract from an accidental one:
- Continuous balance visibility. Management must know, at any moment, how many hours remain and at what rate they are being consumed.
- Early warnings. When the balance drops below 25%, an automatic alert should open a renewal conversation.
- Written monthly report. Totals aren't enough. You need to know on what kind of action the hours were spent (preventive, corrective, advisory, emergency).
Mistakes that cost dearly
The most common mistake is closing the contract without distinguishing types of hour. When all hours are equal, preventive ones tend to be sacrificed to feed corrective ones, and the breakdown cycle feeds itself again.
Best practice is to structure at least two lines in the contract: preventive hours (fixed calendar) and corrective hours (flexible bank). That way, even in a year with many breakdowns, preventive maintenance never stops happening.
Renewal aligned with reality
At the end of the period, the contract should be renewed based on actual consumption, not on last year's history. If the institution used 90 hours and had contracted 72, the next renewal adjusts. If it used 50, next year can be lighter. The contract lives in dialogue with operations, not on autopilot.