How to use the Property Maintenance Request Formatter.
A maintenance request should describe the location, symptoms and timing clearly. Separate the resident's observations from a diagnosis and use the property's approved urgent reporting route when necessary.
Make the workflow fit your task.
Describe the affected location, observable symptoms, start time and changes over time. Add permitted evidence and access availability, keeping cause unconfirmed unless established. Use the property's approved urgent route when the situation meets its stated criteria.
- What you provide
- Tenant's issue description and known facts.
- What you get
- Structured request with location, symptoms and access constraints.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Tenant reports water dripping below the kitchen sink since this morning; source is unknown.
Completed example
Location: kitchen, below sink. Symptom: visible dripping since this morning. Cause: unconfirmed. Add permitted photos, access availability and the appropriate maintenance contact; follow supplied urgent procedures if the situation worsens.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a maintenance request diagnose a leaking pipe from a photograph alone?
Describe the visible leak and location; the responsible technician can determine the cause. Avoid presenting a guess as a confirmed fault.
Why does the maintenance team need a follow-up message before visiting?
The exact location, timing or access arrangements may be missing. Include those practical details in the initial request.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑