The flood has cut the district road and disabled the substation. Residents are moving neighbours by boat while the clinic shares fuel with the water utility. Your warehouse has dry space, vehicles and a generator, and your continuity plan claims every asset.

The public operating picture claims them too, and the vehicles can move patients. The generator can support a treatment point, while the warehouse can receive relief. An engineer appears in your recovery team, the utility roster and the volunteer rescue group.

This collision begins before either system meets its objective. Public response protects life and coordinates scarce public resources. Your continuity plan protects critical business outputs. If each plan assumes exclusive access, both plans claim the resource simultaneously.

Begin with the capacity already responding. Outside plans fail when they treat residents, municipalities, clinics and utilities as demand. These actors hold the first transport, local access and the best account of who has been missed. A corporate site may also be part of that local capacity.

Section 3 of the IDRL Guidelines gives the affected state primary responsibility and preserves its right to coordinate and regulate foreign relief. The same guidelines call for affected people to participate in design, implementation, monitoring and evaluation. Start your operating picture with their work. Keep territorial direction above any company allocation preference.

Representation needs a test. Ask which municipal service, clinic, utility, disability organisation and community group supplied the requirement. The 2024 Core Humanitarian Standard has nine commitments, and Commitment 5 covers safe complaints and their resolution. A warehouse allocation can change when a previously unheard community shows that the planned delivery point excludes it.

Keep each kind of authority separate. Confusion starts when a coordination meeting sounds like a command post. The territorial authority sets public priorities under domestic law. Each participating organisation commands its own people and assets, subject to lawful direction. Your company separately decides which business outputs receive its remaining capacity.

Those relationships vary by jurisdiction. In India, the Disaster Management Act 2005 creates national, state and district institutions. Its National Executive Committee can require government departments to provide personnel or material. That Indian power describes a statutory public relationship. It does not create a universal power over every private asset elsewhere.

Write the local answer before the event by naming the competent public resource coordinator, company liaison and company crisis director. The liaison exchanges requests and consequences, while the public coordinator resolves a lawful public-priority collision. The crisis director resolves competing corporate claims, but the liaison acquires no command by carrying information.

Make the business claim prove an output. Continuity plans overclaim because asset lists detach from the harm the assets prevent. An Australian National Audit Office audit of three entities found about 80 percent of one department’s listed functions had negligible-to-moderate impact ratings. A long critical list makes a weak allocation instrument.

For every employee, vehicle, generator and facility, record the owned output and minimum acceptable level. Add MTPD, RTO, the latest useful start time and the validated alternate process. ISO/TS 22317:2021 allows an organisation-specific BIA method, but requires a formal and documented process. The output owner approves the need, and the asset owner confirms capability.

Keep the clocks distinct. The UK BCM toolkit assesses consequences across the first 24 hours, 24–48 hours, up to one week and up to two weeks before setting MTPD and RTO. NIST SP 800-34 also separates MTD, RTO and RPO. An approaching RTO shows corporate urgency. It does not automatically defeat a public requirement to protect life.

Resolve collisions through the recorded route. Parallel phone calls reward seniority, speed and personal access. They conceal the consequence imposed on the losing system. Use a collision record in the shared operating picture, with separate approval fields for public priority and corporate allocation.

For an employee, record any statutory role, personal safety, consent, trained substitute and latest useful arrival. For a vehicle, record driver, fuel, route and task. For a generator, record load, connection, fuel and operator. For a facility, record access, utilities, safeguarding, occupancy and the output each proposed use enables.

Where a competent authority gives a lawful direction, the public decision governs. Your liaison states the resulting business impact and requests review if the facts are wrong. Where no such power is used, the asset owner remains in command and the crisis director decides the corporate claim. Record who decided, when, on what facts and when review occurs.

Bound every outside capability. International labels create false confidence when nobody states the gap, entry condition or exit. A requested UNDAC team can deploy within 24–48 hours and normally stays up to four weeks in a natural disaster. Its coordination, assessment and information work can include an OSOCC and a Reception and Departure Centre. Territorial government still directs the response.

Specialist search-and-rescue teams arrive as defined capabilities. General Assembly Resolution 57/150, adopted on 16 December 2002, recognises the INSARAG Guidelines as a flexible reference and reaffirms affected-state primacy. Your interface should specify the effect required, reception needs, operating area, reporting line and departure condition.

Clusters require two IASC activation conditions: serious response or coordination gaps, and national capacity unable to meet needs consistently with humanitarian principles. Cluster Lead Agency accountability continues while the cluster is active. IASC guidance seeks an outline transition or deactivation strategy at 90 days and review of sudden-onset architecture within three months.

Military support needs a tighter gate. The 2018 UN-CMCoord Field Handbook incorporates the 2007 Oslo Guidelines. Foreign military assets fill a critical gap only when no comparable civilian alternative exists in time or capability. State the civilian effect, duration, scale and exit strategy before the aircraft, engineers or transport enter the plan.

Test release as hard as entry. Resources linger because activation has an owner and handback has a hope. The response keeps a generator after the clinic reconnects. The company retakes a warehouse while relief stock still lacks a receiving site. Both failures disappear inside separate logs.

Use an explicit release test. Confirm that the public effect is complete or covered by another capability. Name the receiving owner, obtain successor acceptance, and check people, inventory, fuel, damage, access and safety. Then validate that the resource can deliver the next approved business or public output.

Validation comes before declaration. In its US federal information-system context, NIST SP 800-34 requires the recovered system to be tested and validated before normal operation resumes. Apply the same discipline to the alternate process. Run real work, confirm downstream acceptance and reconcile records created while the resource served the other system.

Keep review running until both sides close their claims. The public coordinator confirms that release will not reopen the response gap. The output owner confirms that return supports minimum output within RTO and before MTPD. The asset owner records condition and defects, while the liaison records the time and communicates the changed operating picture.

Exercise the collision, then the handback. Discussion alone lets every owner assume the resource arrives. NIST SP 800-84 distinguishes quantifiable tests, discussion-based table-tops and simulated functional exercises. Use all the evidence you need to show actual allocation, operation and release.

Give the clinic your generator during the exercise, and make the road closure remove the alternate vehicle. Put the engineer on a lawful public roster when your recovery procedure starts. Then require the named decision owners to expose consequences, choose, review and hand back without merging command.

The result should be uncomfortable and legible. A system may accept delay so the other can protect life. The record shows whose authority applied, which output moved, what alternate worked and when the resource returned. That is the operating picture your finished plans never supplied.