A calendar is persuasive because it turns proposed work into a visible sequence. Names, dates and locations create the impression that the main uncertainty has been resolved. In occupied buildings, however, the date often sits at the intersection of several separate arrangements. An occupier needs to know what is proposed and confirm the relevant access. A contractor needs the right people and availability. The building has its own requirements for the work. A booking can exist before those conditions have actually come together.
I am concerned here with routine planned visits, not with a universal procedure for urgent incidents or safety-critical work. Those circumstances need their own authorised response. The ordinary schedule nevertheless matters because repeated unsuccessful visits consume money and attention without delivering the intended service. They can also make each participant less confident in the next appointment. A property operation should be able to explain why a date is credible, not merely point to the fact that it has been entered.
The conditions hidden inside the calendar
In 2016 we examined ninety-six planned visits in a defined review. Sixty-eight had been performed; twenty-eight had not. Eighteen of the unperformed group lacked confirmed occupier arrangements, and ten conflicted with contractor availability. The categories were deliberately specific to the review. We did not describe every missed visit as occupier refusal or contractor failure. Our own coordination had allowed the schedule to imply that unresolved conditions were already in place.
The first useful change was therefore in the account of readiness. The requested date, occupier confirmation and contractor availability needed to remain distinguishable. A property colleague might have sent a notice without receiving the appropriate response. A contractor might have accepted a general programme without being able to support a particular visit. The operating team needed to see which condition was missing while there was still time to resolve it. Combining them into one apparently complete appointment made the next difficulty arrive later and more expensively.
This was not an argument for collecting confirmations without judgement. A long chain of acknowledgements can become another administrative performance if nobody understands the proposed work. The relevant people need enough context to know what they are agreeing to and which requirements still apply. The arrangement should also identify who can change it when circumstances move. Otherwise a confirmed date may become stale while each participant assumes another person is keeping it current. I wanted a more credible conversation, supported by a clearer record, rather than a larger volume of messages.
There was resistance to changing the appointment account. A programme colleague thought retaining the original schedule would help protect momentum, whereas exposing the unconfirmed conditions would make the plan look less advanced. I understood the concern, but an optimistic calendar could not provide the access missing on the day. The institution was already paying for the uncertainty; it simply encountered the cost at the least useful moment. Showing it earlier gave management an opportunity to decide what could still be achieved.
The cost of an unsuccessful visit
The correction involved A$84,000 of additional coordination and repeat-visit expense. I kept that amount attached to the programme. It would have been easy to absorb it into a later routine account and report only the improved appointments. That would have concealed part of what the original scheduling approach had cost. It would also have encouraged the impression that coordination was free because its work did not resemble a physical repair. The expense was real even when the resulting improvement was an avoided unsuccessful journey rather than a new piece of equipment.
Responsibility for that cost could not be settled by the simplest label in the record. An occupier’s unconfirmed arrangement might reflect inadequate information, a changed contact or a legitimate operational constraint. A contractor conflict might reflect a change after the original booking. Our review did not eliminate the need to understand those circumstances. I wanted management to recognise its own role in the sequence instead of allocating every unperformed visit to the party absent at the final stage. Contractual rights and obligations still required the appropriate assessment; an operating category was not a legal conclusion.
The later follow-up used a separate cohort of ninety-six planned visits. Eighty-four were performed and twelve were not. That was an encouraging observation, but it was not a controlled experiment. The tasks, buildings and circumstances could differ, so I did not attribute the entire movement to one coordination change. The twelve remaining unperformed visits also deserved examination on their own terms. A better aggregate should not make the last difficult cases less visible or encourage a premature claim that the access problem has been solved.
A useful comparison keeps both the scope and the uncertainty intact. It states the population, the period and the actual event being counted. In this case the event was a performed visit, not certification of the work’s technical adequacy or completion of every related action. A visit can happen and still leave another task required. If the report allows these meanings to drift together, an improvement in attendance may quietly become a claim about service outcomes that the review never examined.
A better account of readiness
The operating question I now ask is what would prevent this particular visit from happening even though the date is agreed. The answer should bring the relevant dependency into view. It may concern the appropriate occupier contact, the contractor’s actual resources or a building-specific work requirement. The point is not to predict every possible disruption. It is to avoid presenting a known unresolved condition as though it were settled simply because the institution wants a complete-looking plan.
That approach also changes the conversation when a date cannot be supported. An early, specific explanation gives the parties a chance to consider another arrangement. A last-minute failure leaves less room and may damage confidence in the next commitment. The property team should neither promise access it cannot authorise nor assume that an occupier’s agreement replaces the other controls governing the work. Each responsibility remains distinct, but the operating organisation helps the people carrying them meet at a workable point.
I would judge the resulting practice by the credibility of the schedule and the quality of its explanations, not by the disappearance of all exceptions. Buildings are used by people whose circumstances change. Contractors face real constraints. The management task is to make those facts part of the plan while there is still a useful decision to make. A date is a necessary organising device. It becomes an operating commitment only when the relevant participants understand the work and the conditions required to carry it out.