Goal
Identify and assess key requirements including budget, preferences, and space needs to ensure effective planning and decision-making.
Why
As a requirement drops into the system your teams' aim is to progress them through their life-cycle, from initially enquiry through to completion.
Identifying Opportunities
Requirements can be classified as a 'Prospect' requirement.
This classification allows you to monitor individuals or entities that you are not yet assisting with their search but are likely to engage in future discussions.
Keeping Requirements Updated
Move requirements through the pipeline ➡️
Make sure your requirements are categorised appropriately.
You can use the drag-and-drop feature in board view or the status drop-down in the requirement quick-view to keep everything organised.
Handy Tip: Aim to keep un-actioned enquiries to a minimum whenever possible.
Enhance Collaboration with Requirement Notes 🗒️
Keep your colleagues and yourself informed by adding updates to the notes stream for each requirement.
Handy Tip: With each interaction with your applicants try to add a note so you know where you are at!
Navigating the 'Search', 'On Hold', and 'Unsuccessful' Phases 🧭
When you respond to applicants, their requirement transitions into the 'Search' phase. If there are no updates for more than 30 to 60 days, it is advisable to move the requirement to the 'On Hold' status. Following this, if there are still no developments, consider marking it as 'Unsuccessful'.
Handy Tip: You can continue to report and match applicants even when their status is 'On Hold'. This approach allows you to maintain a more manageable number of 'Active' requirements.
