Example hold state
Hold activeA-1204
- Request receivedBuyer context and CP identity attached.
- Decision window openBuilder sees the request and can approve or decline.
- Expiry enforcedStale holds become visible instead of silently blocking sales.
Unit hold management
A hold should create confidence, not a race condition.
BricDesk treats the hold state as shared operational truth: who requested it, for which buyer, when it expires, who can approve it, and what happens when it is released.
ONE UNIT / ONE CURRENT STATE
Protect the deal without hiding the decision.
When two channel partners ask about the same unit, a screenshot and a phone call are not enough. The system needs a single current state, a clear sequence, and a visible outcome.
Read our security postureThe non-negotiables
Every hold needs a responsible next action.
- Atomic state: one unit cannot be simultaneously available and held for competing claims.
- Expiry: a hold has a real deadline and a visible owner.
- Approval: the builder decides with the buyer and unit context in view.
- Audit: the team can reconstruct when and why the state changed.
Built before a full inventory workspace.
Hold logic touches every major workflow, so it belongs in the foundation rather than as a late-stage feature.
Private pilot
Bring your real hold process into a defensible system.
Start with the policies your team already uses and replace ambiguity with one live state.