A closed request is a useful operating fact. It tells us that a defined process has reached its recorded conclusion. The difficulty begins when we ask that fact to establish more than the process actually examined. A contractor may have performed the assigned task correctly while an occupier continues to experience a problem with a different cause. A user may return with the same concern because the earlier response was incomplete. Both possibilities deserve examination. Neither becomes clear merely because the previous record says closed.
I learned this distinction while following routine property-service requests early in my career. The list gave me a sequence of tasks, but the next conversation could reveal that the person’s question had survived them. As my operating responsibility grew, I found the same tension in larger reports. A portfolio could show a convincing volume of completed activity while the experience in a particular building remained difficult to explain. I wanted the institution to preserve both accounts rather than choose the more convenient one.
Two accounts of the same place
In 2023 we followed a defined group of 420 closed non-urgent comfort requests across twelve buildings. Within thirty days, eighty-three reports came from the same locations. That was enough to warrant attention, but it was not enough to call all eighty-three failed repairs. The location linked the observations; it did not establish that their causes were identical. We asked the relevant technical colleagues to examine the available account and distinguish what could be supported from what remained uncertain.
Fifty-two reports were supported as the same problem. Thirty-one concerned something different or were not sufficiently established. Those categories mattered because each implied a different next question. The supported recurrence needed consideration of the earlier response and the continuing condition. A different concern needed its own examination. An uncertain account could not honestly be pushed into either conclusion just to make the table add up neatly. The population also remained bounded: these were selected non-urgent comfort requests, not every fault or all building safety conditions.
The original 420 closures did not disappear. We retained them as a record of the actions recorded at that time and put the later account beside them. This avoided a false choice between defending every closure and declaring the entire reporting system unreliable. The new evidence did not have to invalidate the earlier administrative fact to change our understanding of the operating problem. It showed that completion and subsequent experience answered different questions, and that management needed to see the relationship between them.
What the later report can establish
A later contact has value before it supplies a final explanation. It tells us where an experience has continued or changed, and it may suggest whom to involve next. It does not automatically identify a technical cause, establish a contractor’s liability or determine the appropriate remedy. I want an operating organisation to be responsive without acquiring certainty it has not earned. That requires the person receiving the report to preserve useful context and route it to the participants whose judgement can move the matter forward.
The review cost A$310,000 in investigation and coordination. That expense was uncomfortable because the initial completion account had appeared settled. A colleague worried that revisiting the matter would cast doubt on the work already reported. I thought refusing the examination would create a larger gap between the report and the building. The money funded a better basis for the next decision. I did not attach an invented return to it or claim that the review permanently removed every supported problem. The immediate result was a more useful distinction between what we knew and what still required action.
There is also a human question in the way recurrence is discussed. If every return is immediately treated as proof that someone failed, colleagues may spend their time defending the earlier classification. If every return is dismissed as a new ticket, the organisation may never recognise a pattern. I wanted the conversation to examine the condition and the response before assigning a convenient explanation. That did not remove accountability. It made accountability depend on the actual sequence and evidence rather than on whether the latest report was welcome.
The period of follow-up needs an explanation too. Thirty days provided a defined window for this review; it was not a universal standard for every building system or type of request. A different problem might need a different observation period and a different qualified assessment. The chosen period limits what the result can say. Without that limit, a selected review can quickly become a broad claim about repair quality that neither its population nor its method supports. I would rather present a narrower result that another operator can examine than a larger percentage whose meaning changes with each reader.
Keeping the question open without keeping every task open
It would be impractical to leave every administrative task permanently open in case another concern arises. The answer is not to make closure impossible. It is to state what closure means, preserve the relevant history and allow a subsequent report to reconnect with that history when appropriate. The operating record can then support completion of an assigned action while the broader problem remains subject to observation or further assessment. Different responsibilities can conclude at different times without the institution pretending that nothing has been completed.
That distinction is particularly useful when an asset decision follows repeated operating attention. The recurrence account can explain why qualified condition review is warranted, but it cannot replace that review. Nor should a capital proposal treat every repeated contact as evidence that replacement is the only course. Management needs the relationship between experience, diagnosis, available responses and their implications. My role is to help bring those accounts together and ensure that the cost of understanding the problem is not omitted simply because it is less visible than the eventual work.
I would design the follow-up question earlier now. Before presenting a programme as complete, I would ask what later experience would cause us to reconsider the account and who would notice it. The answer should fit the building and the work, not become another generic form that nobody uses. A closed request remains a useful fact. A property operating organisation becomes more credible when it can explain what that fact settles, what it leaves open and how the next relevant observation will reach someone able to act on it.