October at the Resilience Council: Four Tests Met, One Still to Prove

Dear members,

October brought us to a precise point in the RS-001 work: four of the five pattern tests are met, and corroboration remains pending. That is real progress, but it is not a finished finding. We will not turn an incomplete test into a conclusion simply because the need is urgent. Our task is to make the evidence strong enough that people responsible for claims, bridge funding and continuity support can act on it.

What moved this month

On 20 October, the Trade Council’s TR-001 passed its pattern test. That matters beyond one council: it shows the Assembly’s shared process continuing to move from reports to a tested pattern, rather than from an appealing idea straight to a demand. For our own work, the key October milestone came on 26 October, when the Resilience Council’s pattern review update recorded four of five tests met, with corroboration still pending. On 27 October, we wrote to members about that result and the plan to close the evidence gap.

Our work sits within a larger conversation about small-business resilience. UNDRR has reported that small and medium-sized enterprises bear about 75% of business disaster losses, and that disaster-risk reduction can cut losses by up to a third.¹ The Sendai Framework also calls for business continuity to be built into business practice, with particular attention to micro, small and medium-sized enterprises. These are not substitutes for our members’ evidence. They are context for why it is worth gathering that evidence carefully.

The numbers behind the work

As of 27 October, 1,786 members were seated across 49 countries. Members had filed 5,436 reports from 50 countries. The Resilience Council has 156 members in 47 countries and 381 reports from 49 countries. There were 106 resilience reports filed in the last 30 days.

The median amount at stake in those reports is approximately US$3,968. Reports by country include 66 from the United States, 24 each from Spain and Canada, 23 from the Philippines, 19 from the United Kingdom, 16 each from India and Japan, and 15 from Mexico. The reported business sizes are varied: 36% of reports come from owners working alone, 45% from teams of two to nine, 16% from teams of 10 to 49, and 3% from teams of 50 to 249. All 381 reports concern disaster situations.

Those counts help us see the breadth of the problem, not its full shape. A report count does not tell us how long a business stayed closed, whether an insurance decision was timely, or what kind of support helped the owner reopen. That is why the next part of the work is corroboration, not simply collecting a bigger number.

A member’s experience, carefully protected

After floodwater damaged a small workshop, the owner could not restart at once. The space needed cleaning and repairs; meanwhile, bills continued and customers waited. The owner had to work out what could be done with the money and help available, while also trying to learn when the insurance claim would be decided. A faster decision would not have repaired the workshop by itself, but it could have made the next steps clearer. A small bridge payment could have helped with immediate costs while the longer recovery continued.

That is the practical distinction at the centre of RS-001. The proposed Reopen Standard asks for insurance claims to be decided within 30 days, bridge funding within 10 days of a declared disaster, and continuity-planning support suited to micro businesses. These are proposals, not adopted commitments. They need evidence, consultation and the Assembly’s decision before they can be presented as a standard.

What we learned

First, recovery is not one event. “Reopened” can mean that a door is unlocked, while the owner is still short of working capital, staff or reliable supplies. Second, the same amount of delay can have very different consequences depending on the size of the business. An owner working alone may have no spare person to handle forms, repairs and customer communication at the same time. Third, the figures about amounts at stake and team size are useful, but they cannot establish by themselves which intervention works or how quickly it needs to arrive.

We also learned to keep the limits of our evidence visible. The interim review on 15 September was followed by the 26 October update: four tests met, corroboration pending. That gap is not a weakness to hide. It tells us exactly where to focus. Our May letter to UNDRR offered days-to-reopen data as a contribution to the Sendai Framework review; the current task is to make our evidence sufficiently clear and comparable to be useful in that kind of work.

What comes next

• Through the remaining corroboration work, we will check whether the pattern is supported beyond members’ reports and whether the evidence can be compared responsibly. We will publish an update when that work supports one; there is no RS decision date to announce today.

• The Fair Play Council’s FP-001 consultation, which opened on 13 October, runs through 12 November. The Cashflow Council’s CF-001 adoption ballot runs through 9 November. These are Assembly-wide milestones, not Resilience Council decisions, but they give members a chance to follow the same process at work elsewhere.

• The Platform Council’s Wave 2 CEO letters are scheduled for 17 November. For Resilience, our immediate focus remains the evidence and the next responsible step toward a proposal—not a promised date we cannot yet substantiate.

I am grateful to everyone who filed a report, helped check the pattern, or made time to read the 27 October update. In particular, thank you to the members who have stayed with this work even when the honest answer is “corroboration pending.” Your patience helps protect the credibility of what we build together.

Notes and sources

Sources

1. UNDRR, Supporting disaster risk reduction and resilience practices for small and medium-sized enterprises
2. UNDRR, Resilience of SMEs report