Who can contribute?
Leasing and investment agents contribute their transactions and availability data to Atlas.
Contributing is a prerequisite for accessing the full market dataset and benefiting from the Atlas Rankings and insights.
Do you use any data sources outside of agent contributions?
Yes. In addition to agent-contributed data, Atlas also incorporates:
EG Radius historic transactions - sensitive information has been removed.
EIG Auctions - auction results are being integrated into Atlas Sales transactions.
These sources complement agent data while maintaining Atlas’s data-at-source foundation.
How can I contribute?
There are three ways to contribute data to Atlas:
1. Kato workflows
Agents who manage their transactions in Kato can publish to Atlas in one click.
Agents without a CRM can also enter transactions into Kato using simple, intuitive forms.
2. Spreadsheet loader
Agencies without a CRM or who don’t use Kato workflows can send transaction schedules to our onboarding team, who will import them into Atlas.
3. API integration
Agencies using systems like Agency Pilot or proprietary CRMs can publish directly to Atlas via API, eliminating double-keying.
What data is contributed?
Agents contribute:
Lease and sale transactions
Live disposals (coming soon)
All standard fields for transactions and availability can be added and published.
Atlas distinguishes between:
Mandatory fields required for publishing
Ranking fields required for appearing in the Atlas Rankings (live leaderboards showing activity by deals, value and sq ft transacted)
How are you policing the quality of the data?
Atlas’s data-at-source model is naturally self-governing. Agents input data as part of their normal workflows (e.g. closing a disposal), which increases accuracy, completeness and timeliness because it also powers their own internal systems.
To support this, Atlas uses:
Contractual obligations
If contributing firms fail to meet contribution requirements, Atlas reserves the right to remove access.
Data governance models
Our data science team monitors four key metrics:
Volume
Agencies must provide at least 80% of their completed transactions (20% allowance for confidentiality or NDA cases).
Accuracy
Atlas automatically flags anomalous or suspicious values.
Timeliness
Atlas aims for near real-time capture.
The expectation is that transactions are published as soon as they are completed.
Completeness
Mandatory fields must be provided at a minimum.
Ranking eligibility requires additional fields.
How can I protect the confidentiality of sensitive transactions?
If the existence of a transaction cannot be shared
If a deal is under NDA and acknowledging the existence would breach confidentiality, do not publish it to Atlas.
If the transaction can only be shared internally
If it can be shared internally, simply mark it as Confidential or Under NDA in the transaction Management page and publishing it will not be visible to other organisations, but visible for your own.
If the transaction can only be shared between those who have worked on the deal
If you would like it visible for you only and your immediate colleagues, mark the record as internally confidential in the transaction management page and publishing it will only be visible to you.
If the transaction can be shared but some data points are sensitive
When clicking Publish to Atlas, you can choose to hide specific fields.
This should only be used when absolutely necessary. Overuse will be monitored.
Note: Any data that is not GDPR-compliant (e.g., personal contact details) is automatically removed from Atlas.
Will market intel be available on Atlas?
Yes, some users store market intel (informal, unverified insights) within Kato. This will be visible for your organisation only, shortly after launch.
Visibility to other organisations
Market intel is never visible in Atlas to users outside your business.
Visibility to colleagues
At launch, internal market intel may not be visible to your colleagues in Atlas.
Post-launch, we aim to publish internal intel automatically, subject to user feedback.
Do internal transactions need to be published for colleagues to see them in Atlas?
For launch, yes. Only published Atlas records appear in Atlas.
Post-launch, we plan to automate this process (subject to user feedback).