Wrong owner

What it is

A listing is linked to one agent in our data, but the property's original REA record names a different agent as the lister. The listing is sitting on the wrong profile.

Where it came from

Either the repair framework held the move back because it was not sure enough to apply it on its own, or the classifier found the contradiction while checking listings against their REA records.

What to do

1. Compare the two cards. The red card is where the listing sits now. The green card is who the REA record says listed it.
2. If the green card is clearly the right person — the agency matches the listing, the area makes sense, the co-listers fit — use Approve move.
3. If both cards are the same real person with two REA profiles (same face, same agency, overlapping dates), use Reject with the reason "same person". Moving the listing would only shuffle it between two profiles of one person.
4. If you cannot tell, leave it. Nothing happens until someone decides.

What a correct outcome looks like

The listing ends up on the profile whose REA id matches the raw lister on the property's own REA record, and the agent's sales count and suburb statistics follow it.

Shared person

What it is

One person record holds two agent profiles with different REA ids. This might be one real person with two REA profiles (for example after moving agency), or two different people who were joined by mistake.

What to do

1. Compare each profile card: agency, suburbs and states, the first and last listing dates, and the photo.
2. One person: the photos match, the date ranges follow on from each other (old agency then new agency), the areas overlap. Use Keep together.
3. Two people: different faces, both profiles active at the same time in different places, or different first names. Use Separate.
4. Not sure: use Skip. It stays in the queue for someone else or for later.

What a correct outcome looks like

Every agent page shows one real person, with all of that person's listings and none of anyone else's.

Never-absorbed contradictions

What it is

The listing's original REA record names another agent, but nothing moved the listing recently. It has always sat where it is. Often this is the same person whose REA profile id changed, so the "other agent" is really an older or newer profile of the same person.

What to do

• Treat these carefully. Because nothing moved, there is no recent action to undo; approving changes data that has been stable for a long time.
• Approve the move only with strong evidence: the green card is clearly a different real person, the agency on the listing matches the green card, and the co-listers agree.
• If the two cards look like the same person with two REA profiles, Reject with the reason "same person".
• When in doubt, leave it undecided.

No agent record

What it is

The property's REA record names a lister whose REA profile is not in our data at all. There is no green card because we have nobody to move the listing to.

What to do

The only decision is Needs profile collection. It queues a fetch of that REA profile. Once the profile is in our data the case comes back as a normal Wrong owner case with both cards filled in. There is nothing else to decide here.

Decided

This tab is the history of every decision made on this page: who decided, what they chose, the reason, and when.

• Nothing in the data changes at the moment a decision is made. Decisions are collected and applied by the next gated repair run, which an engineer starts by hand.
• Until that run, a decision can be reversed from this tab. After the run has applied it, only the engineer can roll it back from the run's backup.

Buttons

Every button records a decision. None of them change agent or listing data on the spot; the next gated repair run applies them. Decisions can be undone from the Decided tab until that run. Applied runs are backed up and the engineer can roll them back.

Approve move

Records that the listing should move from the red card to the green card. Takes effect at the next gated repair run.

Reject

Records that the listing should stay where it is. A reason is required; "same person" is the usual one. Takes effect at the next run by closing the case with no change.

Separate

Records that the two profiles on a shared person are two different people and should get their own person records. Takes effect at the next run.

Keep together

Records that the profiles on a shared person are one real person. Closes the case at the next run with no data change.

Needs profile collection

Queues a fetch of the missing REA profile. The case reopens with both cards once the profile is in our data.

Skip

Leaves the case undecided and moves it down the queue. Records nothing permanent and can be picked up again any time.

Claim next 10

Holds the next ten unclaimed cases in the current tab for you so two reviewers do not work on the same case. A claim expires on its own if you leave.

Export selection

Downloads the selected rows as a spreadsheet for review outside the page. It records nothing.

Reading the evidence

Raw lister

The agent named on the property's own REA record. This is the ground truth: REA publishes the listing with the agent who actually listed it. Everything else on the page is measured against it.

REA profile id

The number in the agent's REA profile address. Two cards with different REA ids may still be one person, so use the id together with the photo and agency.

Agency on the listing

The agency REA shows on the listing. If it matches the green card's agency and not the red card's, that supports the move.

Co-listers

Other agents named on the same REA record. If they are colleagues of the green card's agency, that supports the move.

Photo

The quickest way to tell one person from two. Missing photos prove nothing either way.

CRM contact and statistics rows

A CRM contact means staff and customers can see this agent. Statistics rows are the suburb sales figures built from the listings; they follow the listing when it moves.

Impact badges

CRM-linked

One of the agents in the case has a CRM contact. Whatever we show that contact, or show customers about them, is affected.

Referral-eligible

The agent can receive referrals. A wrong listing changes their sales figures and can change which agents a customer is offered.

Recently emailed

A customer email went out recently naming this agent. A wrong link here is already in front of a customer.

Cases with these badges sort first because a mistake there reaches a customer or an agent we work with, not just a statistic.

When to escalate

Skip the case and flag it to Felix when any of these apply:

• A customer email is involved (the Recently emailed badge, or you know one went out).
• A live referral is attached to either agent.
• More than two profiles sit on one person.