How to use the Property Inspection Report Formatter.
Inspection notes should preserve observations, locations and evidence. Separate condition descriptions from repair recommendations and avoid certifying safety or compliance from incomplete notes.
Make the workflow fit your task.
Organize inspection notes by area and item, with observation, evidence reference and date. Separate recommendations from findings and record spaces not inspected. Preserve uncertainty and avoid certifying compliance or safety from limited notes.
- What you provide
- Actual inspection notes and photos described by user.
- What you get
- Organized observations without invented conditions.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Notes say bedroom window latch does not close and hallway wall has a scuff; photos are supplied.
Completed example
Bedroom window: latch did not close during the inspection; link photo and request assessment. Hallway wall: visible scuff; link photo. Record inspection date and areas not examined.
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 condition report label every visible defect as a safety violation?
Only a qualified assessment with the relevant basis can establish that. Record the observed condition and needed follow-up.
Why are photos difficult to match to the written inspection report?
They may lack room and item references. Use consistent labels connecting each observation to its evidence.
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 ↑