🎯 Goal
Create Requirement lists to help group occupiers by an attribute or by their strategic importance and share these lists across your team so they can review and contribute intel to ensure targets are kept up to date and knowledge is shared across your team.
❓ Why
Requirement lists make it easy to put enquiries into buckets so they can be located easily or periodically updated as a group.
For example, use this to track 'named occupier demand' to centralise team intel on which key occupiers are out in the market. A single shared location for your team to view, contribute, and update the latest intel on groups of occupiers.
📊 Step-by-step
Create a Requirement list to help track groups such as 'Named demand', grouping requirements into lists with a common attribute, type or size of requirement.
In the Filter section of the Requirements page, scroll to Lists and either select a list to view or create a new list and share with your team, if appropriate.
2. Requirements can be added to a List when creating the requirement or at any time by heading to the Intel section of the requirement in the slide-out panel.
3. If you and your team require easy and regular access to the requirement list, you can save the List as a Saved View, filtering the page by the relevant List and then click 'save view' on the requirement page. You can then name the view as you want and share it with your team.
4. For easy locating, you can pin the saved view to your requirements page so you can keep going back to it without having to reapply the filters from scratch. Click 'all saved views' where you will see a list of all your saved views and those that you have shared. Here you can pin them to your requirements page and reorder as required.
✅ You've done it when…
You will be able to filter your requirements by list groupings and save this selection as a Saved View to allow for periodic review and intel maintenance.
💡 Common mistakes & pro tips
Not using requirement lists. You will miss out on the efficiencies of being able to group requirements by an attribute or by strategic importance, allowing you and your team to keep them up to date as intel develops.
Not sharing a list with your team. Keep your team collaborating with a shared view of requirements.
Ambiguous list names. Simple titles for lists can help teammates locate the correct groupings and gives them a clear overview of the list's purpose.
Duplicate lists. Check to see if a requirement list or a saved view already exists before you create a duplicate; this will avoid any requirements falling through the net for specific lists/views.
Named Demand. Once you or your colleagues have identified the occupier of an important requirement, it can be added to a list that is updated with closer focus under regular review.
💬 Need Help?
📞 0203 772 8898



