π― Goal
Publish a completed lease transaction from Kato to Atlas, giving you access to the wider market's comparables library, benchmarking against peers via Rankings, and contributing to the UK's most complete CRE dataset.
β Why
Atlas is a shared, published data model: you publish your deals, you gain access to everyone else's. Publishing isn't just a contribution it's how your agency qualifies for the data, the rankings, and the comparables searches your team will use every day.
π Overview
Two ways to publish to Atlas: at the moment of close-out (recommended, one flow, no double-keying), or retrospectively from the Atlas Publishing tab within Leases (for leases already in Kato that you want to push through).
π Route A β Publish at close-out
Follow the close-out disposal/requirement flow as if you were recording a transaction at the end of an instruction.
When you reach the save step, click Save Transaction & Publish to Atlas.
Set privacy preferences β use Hide data only for fields under NDA.
Confirm. The transaction is live on Atlas immediately.
π Route B β Publish existing leases from Atlas Publishing tab
Open Leases β Atlas Publishing tab.
Leases are categorised into four saved views:
Ready to publish β meets mandatory fields, publish in a click
Not ready to publish β missing mandatory info
Published β Not on Rankings β live on Atlas but missing ranking fields
Published β On Rankings β fully qualified
Open a lease from Ready to publish. Check the Headline Details and Atlas ranking information.
Click Publish. Set privacy preferences. Confirm.
Bulk publish
For multiple ready-to-publish leases, tick the checkboxes and use the bulk publish option at the bottom of the page. Review data quality first.
π Required fields β headline details
Address
Property type
Transaction date
Our Acquisition / Our Disposal designation
π Confidential transactions
Three options for sensitive deals:
Confidential / Under NDA β mark on the Management page before publishing. Visible to your organisation only.
Internally confidential β visible only to you and immediate colleagues who worked on the deal.
Selective hide β publish but hide specific fields (use sparingly; overuse is monitored).
If acknowledging the deal's existence would breach NDA, don't publish. GDPR-sensitive data (personal contacts) is automatically stripped.
β You've done it whenβ¦
The lease shows as Published on Atlas, visible to Atlas users, and counted toward your agency's contribution. Check the Published On Rankings view to confirm it qualifies for rankings too.
π‘ Common mistakes & pro tips
Publish at close-out, not in a monthly batch. Real-time publishing benefits everyone, including you, when you search comparables.
Headline details unlock publishing. Ranking fields unlock Rankings. Two different bars, aim for both.
NDA isn't blanket, use Confidential settings. Most "under NDA" deals can still be shared internally or selectively. Outright non-publishing should be rare.
Atlas tracks timeliness. Delayed publishing affects your agency's volume, accuracy, timeliness, completeness scoring. Don't let deals pile up.
Flag incorrect data in Atlas directly β there's a flag-and-comment mechanism; the contributing agent gets notified.
π¬ Need Help?
π§ support@kato.app
π 0203 772 8898
