Read the label as an indication, not a complete story.
The planned PixelKnock workspace separates owner occupied, non-owner occupied and unknown. These are information states about occupancy, not three grades of prospect quality. The actual data source and its definitions need to be established before relying on a result.
A clear interface should explain what an indication means and preserve uncertainty. It should not make an unstarred home appear to be a confirmed rental or an unsuitable prospect. A missing field is also not a reason to guess.
Owner occupied does not mean interested.
An identified owner-occupancy indication is intended to receive a star in the planned selection experience. That marker concerns occupancy only. It does not show that a homeowner is considering a project, qualifies for an offer or wants a conversation.
It also does not verify the current user of a phone number, establish a relationship with the rep or create permission to contact someone. Those are separate questions. Keeping them separate avoids giving a small map symbol more meaning than the available information supports.
Non-owner occupied does not prove renting.
The planned non-owner-occupied state must remain distinct from unknown. It must also avoid a different shortcut: calling a property rented without separate evidence.
An interface may use a dot or another labeled marker for an established non-owner-occupancy indication, but the label should describe the information actually known. A renter classification would need evidence of its own; the absence of an owner-occupied star is not that evidence.
Unknown should remain an honest answer.
Unknown means the occupancy state has not been established in the result. It is not automatically non-owner occupied, a failed contact attempt or a measure of the home’s relevance.
For a fictional example, Home 4 might have occupancy unknown while the rep has manually saved a Callback outcome. Both can be visible at once. The outcome reflects recorded work; it does not resolve the occupancy question.
Similarly, a home could have an owner-occupied indication but no established cell/mobile number available. Occupancy and contact availability answer different questions.
Keep three layers independent.
A useful property view distinguishes the supplied occupancy indication, the availability of contact information and the rep’s manually entered outcome. Color can help, but visible labels must carry the meaning.
PixelKnock is being developed with disposition colors and filters for saved work. A Callback, Sold or Wrong number label should never silently replace the occupancy state. Notes also remain user-entered observations, not an automatic correction of supplied data.
- Occupancy: owner occupied, non-owner occupied or unknown.
- Contact availability: what is available, missing or of an excluded/unknown type.
- Recorded work: the rep’s outcome and notes.
Questions worth asking about a result.
Before building a workflow around a marker, understand its source and limits. These questions are relevant even when the interface looks confident.
- How does the source define this occupancy indication?
- What is actually established, and what remains uncertain?
- Is the marker independent of contact availability and saved outcomes?
- Can the user understand the result without relying on color alone?