Make a contingency list for the closure
- Reading time
- 2 minutes
- Last reviewed
On this page
"Allow some contingency" does not tell anyone what to do when a closure task changes. Name the event you are preparing for and the decision it would require.
Start with a few plausible disruptions to the current plan. A customer approval may arrive late. A key contact may become unavailable. A proposed site date may still need agreement. Choose events grounded in your actual dependencies rather than compiling every imaginable problem.
Write the trigger in observable terms
A trigger should be something someone can recognise. "Customer response has not arrived by the review date" is clearer than "customer risk". The review date must be described as an internal planning point unless it has another verified basis.
For each trigger, identify the person responsible for obtaining an answer, who decides the response and which people need to know. The response may be to seek advice or reconsider the sequence. It should not prescribe actions beyond the person's competence or authority.
A fictional plan expects a records handover before the office closes. Its fallback question is who can provide authorised access if the nominated contact is unavailable. The useful preparation is to establish a legitimate alternative route, not to collect everyone's passwords.
Check that the fallback is real
Does the alternative person know about the proposed role? Does the business have permission, access and budget for the alternative arrangement? Has an adviser identified any restrictions?
A fallback that depends on an unasked favour is still an unanswered question. External dependencies should show what confirmation is needed.
If the fallback involves technical work, ask the competent specialist to assess it. Moving equipment, changing services or altering site arrangements should not be improvised from a general contingency list.
Review the cost of changing course
A fallback may protect one outcome while affecting another. Keeping a machine available for possible rework could alter the disposal or premises sequence. Record that relationship in the dependency map.
Avoid presenting a contingency as a promise to a customer or supplier before the authorised person has considered the actual terms. Some situations require professional advice before a response can be agreed.
The change-impact note is useful when a trigger occurs. It shows which assumptions and commitments need to be revisited rather than simply moving a task on the calendar.
Share relevant contingencies with UK Auction Group where they affect asset availability or site access. Explain the trigger and the person who will confirm a change. That gives the disposal plan a clear update route if the expected sequence no longer holds.
Explore closure planning.
Sources
This guide is general information and education only. Legal, tax, employment and safety decisions may need a qualified adviser who knows your situation. Read the disclaimer.