A last-mile portal update check for UK listings
May 25, 2026
9 min read
The dangerous listing update is rarely the first upload.
It is the price reduction agreed at 5:20pm. The replacement hero photo after the photographer sends a new set. The vendor’s instruction to pause viewings but keep the property visible. The switch from available to sold STC after a negotiator has already left for an appointment.
Everyone thinks the listing is ready, so the final check becomes a glance. That is how public mistakes get published.
A branch is deciding whether a changed listing should be sent, held, or escalated before the update reaches buyers, vendors, landlords, applicants, and the portals.
For a newer agent, the distinction is simple: the listing record is the internal version of the truth, and the portal listing is the public version people act on. Property portal software in the UK can push data through a feed, but it can’t decide whether a changed price has approval, copy still matches the photos, or a status change needs manager review.
Last-mile checks are different from listing preparation
A full portal-readiness check asks, “Do we have everything needed to market this property properly?” That belongs earlier. Authority, AML evidence, EPC, floorplan, media, material information, description, and approval should not be discovered for the first time when someone is about to press send.
The last-mile check asks a narrower question: “What changed, and is that change safe to publish now?”
That difference matters because branch teams are busy. If every update requires a full re-check, people will skip it. If the check fits inside 5 minutes, it can become a habit.
The changed item might be obvious:
| Change | The real question before sending |
|---|---|
| Price reduction | Has the vendor approved this exact figure and timing? |
| Status change | Does the public status match the latest sales or lettings instruction? |
| New main photo | Does the new image still represent the property fairly and match the description? |
| Description edit | Did the edit add a claim that needs evidence? |
| Material information field | Is the new value verified, or is it a placeholder someone meant to revisit? |
| Viewing availability | Does the public wording match access, key holder, tenant, or landlord constraints? |
A generic integration checklist misses this decision. Whether a team talks about a Rightmove integration, a Zoopla integration, an OnTheMarket integration, or a feed to several destinations, the branch still needs a human call at the point where an internal change becomes public.
Use the source record
Most final update errors come from a split record. The CRM says one thing, the property software says another, the vendor email says something more recent, and a colleague remembers a phone call that was never written down.
The final check should start from one source record. In AvaroAI, the listing record can hold the property data, photos, documents, notes, tasks, events, and approval state together. The person sending the update can see the changed field beside the evidence and the next action.
If the price field changed, the checker should be able to find the vendor approval. If the status changed, they should see who authorised it and when. If the description changed, they should see the notes, photos, and documents that support the wording.
If a photo was reordered, they should know whether the public copy still points buyers to the right feature. A listing that says “first image shows the open-plan kitchen” looks careless when the first image is now a street shot with a wheelie bin cropped out badly.
This is also where UK material information makes the final check more than a cosmetic review. The GOV.UK consultation on material information in property listings makes the practical point that buyers need key information early enough to make informed decisions. National Trading Standards has also published material information guidance for sales and lettings agents covering information that may need to appear in listings.
Agents are not expected to turn into lawyers or surveyors. Before a public update goes live, the branch should know whether a changed field is verified, still being checked, or unsuitable for publication.
Run a send, hold, or escalate decision
The fastest useful final check is a three-way decision. Skip the broad question, “is the listing ready?” Ask whether this update should be sent, held, or escalated.
| Decision | Use it when | Next action |
|---|---|---|
| Send | The changed field is supported by the record, approval is clear, and the public display will not mislead | Send the update and note the time |
| Hold | Something is missing, but the owner is obvious and the issue is easy to clear | Create a linked task and do not send until cleared |
| Escalate | The update changes price, status, claim, legal-sensitive wording, material information, or vendor/landlord expectation | Ask the manager or senior owner to approve the decision |
Here is the practical version a branch can use tomorrow:
- Filter for listings with portal updates pending.
- Open only the changed fields, not the whole record.
- Check each change against the latest instruction, approval, and supporting evidence.
- Decide send, hold, or escalate.
- If held or escalated, create a task with the exact blocker.
- After sending, check the public listing once the portal has had time to receive the update.
The final step is easy to miss. Portal feeds can lag public display. Rightmove’s customer guidance on listings not showing notes that an update may not have been received, may have feed errors, or may take time to appear through its data feed process. Zoopla’s member support gives similar advice when property content has not updated, including identifying what is missing, such as status or a primary photo.
Manual portal troubleshooting all day would be a waste. Important updates still need a short public-display check after they leave the branch system.
The changed-field list should be visible before the feed run
Managers need an exception list they can scan quickly.
Useful filters include:
| Filter | Why it catches risk |
|---|---|
| Pending public update | Shows listings waiting to be sent or checked |
| Price changed today | Catches reductions, increases, and typo risk |
| Status changed today | Catches available, under offer, sold STC, let agreed, withdrawn, or paused changes |
| Public description edited | Catches new claims and copy-media mismatches |
| Media changed | Catches wrong hero image, duplicate photos, old floorplan, or missing approval |
| Material information changed | Catches values that buyers may rely on before viewing |
| Approval missing | Stops the update becoming public without the right person signing off |
AvaroAI’s search and filtering are useful here because the branch can pull an update queue by state, change, owner, or missing approval instead of relying on whoever remembers to ask. The listing itself should show the reason an update is being held.
For teams using UK property listing software alongside portal feed tools, this is the handoff point that often gets blurred. The internal system helps organise the decision. The portal or feed carries the public update. The quality of the public result depends on the discipline of the source record and the final exception check.
Make held updates specific enough to clear
“Do not send yet” is a delay with no owner.
A held portal update should say exactly what is blocking it. Good examples are:
| Weak hold note | Useful hold task |
|---|---|
| Check price | Confirm vendor approved GBP 425,000 reduction for publication today |
| Need photos | Replace hero photo with approved kitchen image and remove duplicate exterior |
| Status unclear | Confirm whether property should show as sold STC or remain available until memorandum issued |
| Description issue | Remove unverified “new roof” claim or attach evidence from vendor |
| Material info missing | Confirm tenure wording before update is sent |
This is where task and event management earns its place. A held update should be linked to the listing, assigned to a named person, and visible in the branch’s update queue. If the task is cleared, the listing can move back to send. If it exposes a judgement call, it moves to escalate.
The team should also agree which changes always escalate. A sensible starting list is price, public status, tenure, council tax, lease length, ground rent, service charge, known restrictions, seller-requested wording that softens a problem, and anything that changes how a buyer would understand the property before booking a viewing.
A five-minute final update routine
Use this when a listing has already been prepared and the branch is about to send a public change.
| Minute | Action |
|---|---|
| 0-1 | Identify the changed fields only |
| 1-2 | Check the latest vendor, landlord, or manager instruction |
| 2-3 | Compare the changed fields with photos, description, material information, and approval state |
| 3-4 | Decide send, hold, or escalate |
| 4-5 | Record the decision, assign any blocker, and schedule the public-display check |
This routine is small: a branch habit for the moment a record is about to become public. Proper listing preparation and legal advice still sit earlier in the process.
The best test is whether a colleague could understand the decision tomorrow. If the update was sent, the record should show why it was safe. If it was held, the task should show what had to be fixed. If it was escalated, the manager should see the exact judgement needed.
Portal updates stay cleaner when the final public-change decision is visible, owned, and specific. The feed can carry the update. The branch still has to decide whether the update should leave the building.
Related reading
Disclaimer: This page may contain AI-assisted content. The information is provided solely as a general guide and may not be correct, complete, or current, including, but not limited to, our full or applicable service offerings. While we strive for accuracy, no guarantee is made regarding correctness or completeness, and no expectation should be made as such. Please contact us directly to confirm any details before utilizing our service.
