Where the saving comes from
A price tells you what the supplier intends to charge. It does not, by itself, tell you everything the arrangement will require, consume or leave behind.
Part of this saving is real: a system that runs largely on sunlight burns far less fuel. But suppose the lower fee also depends on a smaller battery bank. That may reflect careful sizing to what the organisation actually uses. It may also leave too little power for the evenings, or for a run of cloudy days. The same applies to battery quality and maintenance: are they in the price, or left out to reach it?
Both explanations are plausible, and the proposal alone cannot tell you which is true. A lower price is not a warning sign; it is a claim about how the system will perform. Your task is to distinguish between those explanations, using evidence. A recommendation that settles the question by assumption asks the approver to trust what nobody has checked.
Who pays for the saving
If the saving comes from an undersized system, cheaper batteries or missing maintenance, someone absorbs it.
The people who depend on power absorb it first: colleagues whose systems fail in the evening, customers who cannot pay at the counter, staff who leave after dark when the security lights go out. The switch itself also has a cost for the person whose job is running the generator. Ask what it means for that role, and whether they could look after the new system instead.
The surrounding community can absorb it last. Batteries do not disappear at the end of their life. Where spent batteries are broken down informally, what is inside them ends up in the soil, the water and the people nearby.
Staying with diesel has its own absorbers: the staff and neighbours who breathe its fumes and hear its noise whenever the power goes. Either way, cost that moves onto people outside the contract has not been removed. It has been relocated.
What the evidence has to show
Not every gap deserves the same attention. Start with what could change the recommendation, the terms of the contract or the safeguards it needs. Some questions need no business case: you do not need to prove that someone’s safety will affect the budget before raising it.
Take reliability. You know which equipment has to stay on through an evening outage. The proposal appears to include a smaller battery bank, but it does not explain how long that equipment would run on it after dark.
That does not make the proposal unsuitable. The supplier may have sized the system well for what you actually use. It does give you a specific question to ask: how long will the system carry your critical equipment after dark, including after several cloudy days?
You can then explain the gap clearly: “The fee is attractive, but we need to confirm backup for critical equipment during rainy-season evenings before recommending this option.” You have used your knowledge of the work to improve the decision.
A savings target rewards the first half of that sentence. The second half is what makes the recommendation trustworthy. How it is received can depend on who is saying it; a specific condition, in writing, is harder to dismiss than a general concern.
The environmental claim needs the same test. Lower emissions count only if the system keeps critical equipment running; if the generator ends up covering the gaps, both the emissions saving and the fuel saving shrink. Output also changes with the seasons: cloud in the rains, dust in the dry months. Ask for figures that cover the whole year, not the best month. A claim about responsible battery disposal needs a clear explanation of where the batteries go. The question is not whether each claim sounds reasonable. It is whether the arrangement works as a whole.
Hold both options to that test. Familiarity is not evidence, and a lower price is not grounds for suspicion. The diesel arrangement should also show how fuel use is recorded and how often the generator actually fails. Test the process too: were all bidders given the same specification, and have any interests in a bidder been declared? Framed that way, the question concerns the process rather than a person, which is what makes it possible to ask.
The social questions here concern the people who depend on the power, the person who runs the generator and the installers working on your roof. The environmental questions concern emissions and batteries. Climate enters twice: in what each option releases, and in how it copes with the weather. How the decision is made, recorded and checked is governance. None of it requires a sustainability specialist.
Who checks after approval?
Asking a question before approval is only the beginning. If your recommendation depends on agreed capacity, performance standards or battery disposal, someone needs to check that those conditions are met during delivery. Otherwise, the reasoning behind the approval never becomes an operating practice.
That check needs a name and a date. Some conditions belong in the contract, such as a performance guarantee with consequences if it is missed. Others depend on someone looking: at outage and output records through the first rainy season, at how often the generator still runs, at whether maintenance visits happen as promised.
A serious safety or misconduct concern is not a condition to be monitored. Escalate it to whoever has the authority to act. Your role is not to privately decide how much harm is acceptable to secure a saving.
Not every organisation has a contract manager, written requirements or a formal escalation route. Where they are missing, your recommendation may be the only record of what was checked, what was assumed and what was agreed. Write it that way.
The aim is a recommendation colleagues can trust because the benefits, uncertainties and responsibilities are clear. That kind of trust accumulates. What colleagues come to know about your judgement is not whether you backed the new option or the familiar one, but whether your decisions held up in practice.
Try it on a live decision
Take one recommendation you are working on now and add four short statements:
- The benefit we expect.
- The consequential issue we still need to verify.
- The condition we recommend before proceeding.
- Who will check delivery, and when.
For the power decision, it might read: We expect lower monthly energy costs and far fewer generator hours. We still need to verify how long critical equipment will run during rainy-season evening outages. We recommend approval subject to a performance guarantee covering that equipment. The operations lead will review outage and output records after the first rainy season.
That produces a usable decision note, for this contract or any other. Progress is visible when a significant uncertainty is resolved, an appropriate condition is agreed, or follow-up confirms that the promised benefit has been delivered.
A question raised and then forgotten has not yet done its work.
