Skip to main content

How to create a Requirement

Written by Max Kemplen

🎯 Goal

Create a requirement record in Kato with type, applicant, criteria and location so it is ready to match against your disposal portfolio and society supply.

We have a dedicated quick start video on creating a requirement.

❓ Why

Your requirement is your demand: a direct enquiry, tracked society acquisition, market demand note, or retained instruction. The more precisely you set it up, the better Kato's matching algorithm surfaces options, and the cleaner your applicant pipeline looks in reporting.

🔍 Overview: three things every requirement needs

A good requirement captures Who, What, and Where:

  • Who is the applicant company and contact

  • What tenure, property type, size range, budget

  • Where they are looking - search area, drawn or by district

You can add a lot more (fit-out preference, single-floor, spec needs), but these three are the minimum for useful matching.


📊 Step-by-step

1. Start a new requirement

Click + Create in the top right and choose the type of requirement.

2. Who — associate a contact

Link the applicant company and contact from your CRM, or create a new one. Add the tenant or company name in the requirement title so you can find it easily later, this part is private to you and your team, not shared on any society pages.

3. What — set the criteria

Select the tenure (To Let / For Sale / Investment), property type, size range, and budget. Add fit-out preference, single-floor if required, and any spec needs (grade, amenities).

4. Where — set the search location

Enter postcodes, districts, or draw a polygon on the map for a specific area. Drawn polygons give sharper matching than radius searches for central London or mixed submarkets.

5. Assign and save

Assign the primary and any secondary agents (multiple users can own a requirement). Save - Kato starts surfacing matches immediately.


✅ You've done it when…

The requirement appears in your Requirements list with Who / What / Where all populated, and the Find Matches tab shows auto-suggested properties within seconds.

💡 Common mistakes & pro tips

  • Blank preferences exclude matches, not include them. Leaving fit-out empty doesn't mean "any", it means the requirement won't match fit-out-specific disposals.

  • Use Market Demand for intel you want Kato to match against but aren't retained on. Keeps your Enquiries and Acquisitions lists clean for reporting.

  • Multiple assigned users - use the Secondary Assigned Users box for team coverage. Anyone assigned gets notifications on matches and activity.

  • More detail = better matches. Kato's match algorithm uses every field you fill in to find you matched within your records or across society pages. Even minor details like spec notes can sharpen results.

❓ FAQs

Can I add more than two users to a requirement?
Yes. In the Secondary Assigned Users box, select multiple people — each gets ticked and all receive match activity notifications.


💬 Need Help?

Did this answer your question?