Back to the guides
Daily operations4 min read

Follow a resident request to closure.

Use one timeline for the issue, progress and resolution.

Illustrative example

These guides explain the documented Bunkfox workflows. The website is an interactive preview; it does not change live property records.

01

Record the issue.

The resident selects a category and describes the problem. A photo is optional. The owner can record a complaint received by phone and connect it to the resident’s property record.

Keep enough detail to act: what is wrong, where it is and any useful context. The queue uses Open, In progress and Closed without separate urgency levels.

02

Add a useful progress update.

Move the request to In progress when work starts. Use the timeline for actions taken, delays and the next step.

Choose between an internal note and a resident-visible update before posting. Mentioning a technician records context; it does not create a technician account or worker portal.

03

Handle related reports carefully.

Several residents may report the same property issue. The owner can link those reports to coordinate the work.

Keep each resident’s private details separate. Linking reports does not grant one resident access to another resident’s record or private conversation.

04

Close with a clear reason.

Record what was done and why the request is being closed. The resident does not need to approve closure before the owner closes it.

If the issue remains, the resident can reopen the same request. Earlier updates stay with that request so the next action has context.

Try it for yourself

See the records in context.

Explore the owner workspace with fictional property records.

Explore the workspace