🎯 Goal
Take a requirement off your active pipeline cleanly, whether the applicant has transacted, dropped out, or simply gone quiet, without losing the historical record or inflating future reporting.
❓ Why
Not every requirement ends in a deal. Applicants drop out, decisions get deferred, mandates change. Closing requirements deliberately, rather than letting them rot in your Search column, keeps your pipeline reporting honest and your match notifications meaningful.
🔍 Overview — three ways to close
Complete with a transaction — the applicant transacted. [how to log a deal through a requirement].
Archive without a transaction — applicant dropped out, changed plans, or is no longer active. No deal to record.
Move to On Hold — not closing, pausing. Use when the applicant has paused rather than pulled out, so you can reactivate easily.
📊 Step-by-step
Complete (with a transaction)
Once the transaction is logged, the requirement auto-moves to Completed.
Archive (no transaction)
Open the requirement.
Click Actions → Archive requirement.
Optionally note the reason (e.g. applicant withdrew, scope changed, completed elsewhere unknown).
Save. The requirement moves out of your default Requirements list.
Move to On Hold
From the requirement's status, switch to On Hold. The applicant stays eligible for matching but moves out of your active Search column — so your pipeline view reflects real active demand.
Find an archived requirement later
Archived requirements are retrievable via the Requirements search — either text search by applicant/company, or by expanding the Status filter to include archived states.
✅ You've done it when…
The requirement no longer appears in your active pipeline, match notifications for it stop, and (if applicable) the archived/completed record is still searchable when you need to revisit.
💡 Common mistakes & pro tips
Close deliberately, not by neglect. Leaving a stale requirement in Search is worse than archiving — it distorts your team's pipeline reporting and triggers irrelevant match notifications.
On Hold is your friend. For applicants who are paused but live — new mandate coming, awaiting internal approval, waiting for a building to complete — use On Hold rather than archive.
Record the reason. Even a one-line note explains to your team (and future-you) why the requirement closed without a deal.
Reactivate if they come back. Archived requirements can be reactivated rather than re-created — preserves the history and any match intelligence you'd captured.
💬 Need Help?
📞 0203 772 8898