A maintenance job records a problem at a facility so somebody can fix it. This example reports a loose handrail in the main bathroom.

Two things decide whether the job is useful. The first is which facility it is on — a job is attached to the site it was raised at, so check the facility name before you start rather than after. The second is where in the building: whoever turns up has to find it, and "bathroom" in a building with six of them is a wasted visit.

Jobs move through Submitted → In Progress → Completed, and can be Cancelled. Every status change requires a note — the field is mandatory, and the note is kept in the job's status history alongside who made the change and when. That history is the record of what was done, so the note is worth writing properly.

Look at what is already on the Jobs tab before you add anything. A second job for the same handrail does not get it fixed twice.

If something is an immediate hazard, follow your organisation's urgent safety process as well. Logging a job does not make an unsafe area safe.

Step 1
Open the right facility
Open the facility the problem is at. The job attaches to this site, and moving it later is not a field you can edit.
Step 2
Check what is already reported
The Jobs tab lists what has already been raised here. Read it before adding — duplicates split the history of one problem across two records.
Step 3
Open the form
New Job.
Step 4
Describe the problem
Plainly, and in the words the person fixing it will read first. "Handrail loose at the wall bracket" beats "handrail issue".
Step 5
Say where it is
Where in the building, specifically enough that nobody has to hunt for it.
Step 6
Create it
The form also wants a job number and the date it happened. Then Create Job.
Step 7
Check it landed
The job appears on the list as Submitted — the starting status for everything raised here.
Step 8
What happens next
It moves to In Progress while somebody is on it and Completed when it is done, or Cancelled if it should not have been raised. Each of those changes needs a note before it will save, and the note lands in the status history with the person's name and the time.
Step 9
Reporting is not fixing
A submitted job is a request that somebody has seen. It is not a barrier, a repair, or a substitute for making an unsafe area safe now — do that through whatever urgent process your organisation runs, and raise the job as well so the fix is recorded.