Not every facilities task needs to become an occurrence
A simple light-replacement request can be handled as a task: the action is clear, little extra context is needed, and closure is straightforward. Repeated water infiltration involving photographs, an internal team, and a provider—and requiring later comparison—calls for a different kind of record.
The difference is not the name of the service. It is whether context must survive beyond task completion.
This distinction also separates a request that stays in a communication channel from an occurrence that needs history, as discussed in when fragmented channels start creating risk.
When context must survive completion
Include the location, space, equipment, or asset when it helps locate the case. Record the responsible team, provider, evidence, decisions, and ownership changes when relevant. The aim is to let someone understand what happened after the work order or task was marked complete.
Not every case needs every field. A well-chosen minimum is better than a large form the team avoids.
The critical point is often the handoff
An occurrence may begin with an internal observation, move to a provider, return to a supervisor, and end at another location. At each handoff, context may be oversimplified, an attachment may remain in one person’s email, or ownership may change without a clear record.
Define what travels with the handoff: initial description, location, evidence, decision, current owner, and next action. This does not turn the process into a maintenance work order or prevent other tools from executing the task.
When a helpdesk or work order is still enough
A helpdesk, work order, or task tool remains appropriate when the main need is assigning work, tracking an internal target, and marking completion. Facilities does not need to turn every activity into occurrence history.
Structured occurrence follow-up becomes useful when an issue repeats, involves several parties, requires evidence, crosses locations, or may prompt questions after closure. In that setting, the task is only one part of the story.
Test a case that crosses team and provider
Choose a generic case that starts as an internal request and ends with a provider. Follow it from first report through completion, then try to review it without speaking to the people involved. Can you find the location, observed problem, evidence, ownership handoff, decision, and reason for closure?
The gaps show whether the problem is the handoff routine, the record, or the tool used to execute the work. The answer may be a better rule, a process connection, or a dedicated record—not necessarily replacing the maintenance system.
For work across several locations, compare this case with how to preserve context across locations.
Where CGS fits
CGS can be evaluated when facilities needs occurrence history beyond completion of a simple task. It is not a CMMS, work-order system, or helpdesk replacement. Its focus is keeping the occurrence, owners, evidence, interactions, and context available for review across the parties involved.
