Update an existing requirement, criteria, location, contacts, assigned agents, status, so matching, reporting and notifications stay accurate as the applicant's needs evolve.

Applicant requirements rarely stay static: size windows tighten, budget moves, a new submarket opens up. Keeping the requirement record current means Kato's match algorithm serves up relevant properties, and your landlord/occupier reports reflect the current brief, not the one you took three months ago.

Edits fall into four common categories, all accessed from the requirement's edit view:

Open the requirement for editing

Update criteria or location

Adjust size, budget, fit-out preference, or spec requirements. For location, edit postcodes/districts or redraw the polygon. Changes feed the match algorithm on save.

Update contacts

Add additional applicant contacts or swap the primary contact — useful when a client changes representative or involves a colleague mid-search.

Change status

Move the requirement between Search, On Hold, Viewing, Offer, and Completed. Status drives which pipeline column the requirement sits in and what notifications fire.

Reassign agents

Update the primary or secondary assigned users. Newly assigned users start receiving match notifications; unassigned users stop.

Save

Save the edit. Changes flow to the match schedule, applicant pipeline, and any active reports within seconds.

The requirement summary card reflects the updated criteria, the match list refreshes based on the new parameters, and the requirement sits in the correct pipeline column.