Summary
A Unit Status records what happened with a unit during a visit — for example, whether it was serviced, skipped, refused, or couldn't be accessed. Where Unit Condition describes the state of a unit, Unit Status describes the outcome of the service. Defining these here gives techs a consistent set of options in the mobile app and produces a clear, unit-by-unit account of every visit.
Key Points
Create a unit status for each possible service outcome at the unit level
Techs select these on the mobile app as they work through a multi-unit account
Consistent statuses make completion tracking and client reporting reliable
How to Get to Unit Status
How to Create a Unit Status
Click the New Unit Status button in the upper right.
Enter the Unit Status Name
Click the green Create Unit Status button to save
Choosing Good Unit Statuses
Cover every real outcome so a tech always has an accurate option, including the "couldn't service it" cases.
Keep them distinct from Unit Condition — status is what happened (serviced, skipped), condition is what the unit was like (cluttered, vacant).
Make non-service outcomes clear (No Access, Refused) so you can follow up and show clients which units still need attention.
Examples
Common unit statuses include:
Serviced
Not Serviced
Skipped
No Access
Refused Service
Vacant — Not Treated
Follow-Up Required
Important Note: Anytime you change something in Settings, your techs must Reload Data in the mobile app to see the change.
Need more help? Reach out to Fieldwork support, and we'll be happy to walk you through these settings.




