Use Readable text for larger type, or zoom in on the pages.
Resilience Council
Evidence Submission: Delays in Reopening Support for Micro Businesses in the Philippines
Document type: Evidence submission
Author: Secretariat
Submitting group: Philippine Reopen Evidence Group, six consenting members
Subject: RS-001 Reopen Standard — time-bound insurance decisions, bridge funding, and continuity support for micro businesses
1. Purpose and scope
1.The Philippine Reopen Evidence Group submits this material to the Resilience Council’s consideration of RS-001. The six members consented to publication of their experiences in anonymized form. They are identified in this submission only as Members A to F. No member’s business is named, and no insurer, lender, platform, public agency, or other company is identified as the subject of an allegation.
2.The submission concerns the time between a disruptive event and the practical support a micro business needs to resume trading. It records two distinct processes: decisions on insurance claims, where a member had cover and made a claim, and access to temporary funds for immediate reopening costs. A claim decision and the transfer of money are not treated as the same event. The members also describe continuity planning support, but this submission does not assess a particular product or provider’s full service.
3.The six accounts are a small, consented group of member records, not a representative survey of businesses in the Philippines. Their purpose is to help identify a problem pattern and shape a standard. Dates and amounts reflect members’ records and recollections. The Secretariat has not
independently audited the underlying transactions or adjudicated the merits of any insurance claim.
4.Amounts are stated in Philippine pesos. For comparison only, this submission uses a conversion of ₱56 to US$1. It is not a statement of the exchange rate on any event date. Rounded US-dollar equivalents are provided to make the scale of the amounts easier to compare across settings.
2. Evidence submitted
2.1 Summary of the six accounts
5.The members described disruptions in three provinces and two broad types of incident: localized flooding and fire. Each account involved a micro business that relied on continuing sales to meet operating costs. The accounts do not establish that the events were part of one disaster or that the same service provider handled them. The common subject is the time and uncertainty involved in getting from damage to a workable reopening plan.
| Member | Incident and records described | Amount at stake | Reported timeline |
|---|---|---|---|
| A | Localized flooding; dated photographs, repair receipts, claim acknowledgment, and follow-up messages | ₱180,000 (about US$3,214) | Claim decision reported after 41 days; temporary funding sought after the event |
| Member | Incident and records described | Amount at stake | Reported timeline |
|---|---|---|---|
| B | Localized flooding; inventory notes, dated photographs, application receipt, and messages concerning missing documents | ₱425,000 (about US$7,589) | Claim remained undecided at the time of the member’s account; first bridge-funding response reported after 18 days |
| Member | Incident and records described | Amount at stake | Reported timeline |
|---|---|---|---|
| C | Fire; repair estimates, receipts for urgent replacement items, claim acknowledgment, and a dated decision notice | ₱96,000 (about US$1,714) | Decision reported after 33 days; member described borrowing to resume limited operations |
| Member | Incident and records described | Amount at stake | Reported timeline |
|---|---|---|---|
| D | Localized flooding; dated damage record, a claim form, transport receipts, and a record of a funding request | ₱610,000 (about US$10,893) | Claim decision reported after 52 days; funding request had no recorded decision within the first 10 days |
| Member | Incident and records described | Amount at stake | Reported timeline |
|---|---|---|---|
| E | Fire; photographs, purchase receipts, claim correspondence, and a handwritten continuity checklist | ₱275,000 (about US$4,911) | Claim decision reported after 27 days; member received no formal continuity-planning support |
| Member | Incident and records described | Amount at stake | Reported timeline |
|---|---|---|---|
| F | Localized flooding; repair and stock records, acknowledgment of a claim, and dated follow-up messages | ₱140,000 (about US$2,500) | Claim decision reported after 36 days; member described reopening in stages while awaiting funds |
6.The six stated amounts at stake total ₱1,726,000, or approximately US$30,821 under the conversion above. These amounts are not a verified measure of insured loss, unpaid benefit, or final damage. Members described them as the value they associated with the affected stock, repair needs, or immediate reopening exposure. The categories differ between accounts, and should not be added to any wider loss estimate.
2.2 Sequence described by members
7.Members’ timelines generally began with an incident, followed by immediate steps to protect people and salvage usable stock. The next recorded steps were documenting damage, contacting a relevant provider, and attempting to identify the documents needed for a claim or temporary funding. In more than one account, the member described needing to ask again what information was missing or whether a request had been received. The accounts do not establish why a particular request was delayed.
8.Members said that immediate reopening costs did not wait for a final claim decision. Cases in the records include replacement stock, basic repairs, transport, and expenses associated with a partial reopening. The six members did not use a common accounting method, and the submission does not assign a separate amount to each category. Their accounts nevertheless show why the interval before a decision may matter even where an eventual claim is accepted or a business later reopens.
9.The members’ reported claim-decision intervals were 27, 33, 36, 41, and 52 days for five accounts with a reported decision. Member B’s claim was reported as undecided when the account was submitted. The time figures are member-reported elapsed days, not independently verified processing-time measurements. They do not establish when a complete claim file was received, whether the provider sought additional information, or whether a delay was justified in an individual case.
10.In the accounts where a member described seeking temporary funds, the reported response interval was also material to reopening. Member A did not report a precise response time. Member B described a first response after 18 days, and Member D reported no decision recorded within the first 10 days. These are not comparable outcome measures: a response may not be an approval, and a funding request may involve different eligibility or documentation requirements from an insurance claim.
11.Members’ records include dated photographs, receipts, repair estimates, inventory notes, claim acknowledgments, application receipts, decision notices, follow-up messages, and a handwritten checklist. Personal information and identifying details are omitted. The submission presents no private correspondence as a statement by any named organization.
3. Context and limits
12.As of 20 July 2026, the Resilience Council had 95 members from 40 countries and 91 reports from 36 countries. Eight of those reports were from the Philippines. The Council’s median amount at stake was approximately US$4,882. These figures describe the Council’s evidence base at that date.
13.Across the Council’s 91 reports, all were classified as involving a disaster. Reported team sizes were mostly very small: 41% were “Just me,” 40% had 2–9 people, 18% had 10–49, and 2% had 50–249. The percentages are rounded and therefore do not sum exactly to 100. These council-wide data help explain why a reopening delay may affect a business with limited staff, but they cannot establish the circumstances of any one member.
14.The broader relevance of small-business resilience is also reflected in international guidance. The UNDRR has reported that small and medium-sized enterprises bear approximately 75% of business disaster losses, and that disaster risk reduction can reduce losses by up to a third.1 The Sendai Framework for Disaster Risk Reduction 2015–2030 calls for business continuity to be integrated into business practice, with particular attention to micro, small, and medium-sized enterprises (paras. 30(o) and 36(c)). These sources provide context; they do not verify the six member accounts or establish a duty on any particular provider.
15.The UNDRR’s SME resilience report also describes a Japan METI survey in which 8% of prepared SMEs had not recovered sales, compared with 19% of unprepared SMEs.2 The comparison supports the relevance of preparation and continuity planning as a subject for further work. It is not a result from this Philippine member group, and it should not be read as a forecast of the effect of the proposed RS-001 measures.
4. Five-part pattern test
4.1 Volume
16.The six accounts are sufficient to identify concrete process questions, but not to estimate prevalence. They sit within a council dataset of 91 disaster-related reports from 36 countries, including eight reports from the Philippines, as of the date of this submission. The overall dataset is still limited and is not a population survey. The case material adds detail about elapsed time and records, but does not justify a claim that most Philippine businesses face the same delays.
4.2 Frequency
17.Within this six-account set, five members reported a claim decision taking longer than 30 days; the sixth reported that the claim remained undecided. Two members described a bridge-funding process that had not produced a decision within 10 days or had received a first response only after 18 days. This repetition makes timing a reasonable issue for consultation. The small group, differences in the events, and absence of a shared start-point for measuring time mean that frequency should be treated as an indication, not a rate.
4.3 Consistency
18.The accounts share a practical sequence: disruption, damage documentation, contact with a provider or funding channel, and a period of uncertainty before a decision or usable support. Several records include follow-up activity or a request to clarify documentation. The evidence is less consistent on the outcome: some members reported a decision, one had no decision at submission, and the accounts differ in the type of expense and support sought. The recurring point is uncertainty during the reopening period, not proof of a single cause or uniform provider practice.
4.4 Spread
19.The six consenting members were located in three provinces and described flooding or fire. That provides some spread across locations and incident types within the group. It is not enough to establish national coverage, differences between regions, or a pattern across particular sectors. No member’s account is attributed to a named business or provider, and the submission makes no company-level comparison. Further evidence should seek a broader range of locations, disaster types, and business circumstances without identifying members without consent.
4.5 Corroboration
20.The records described include dated material that can support the sequence of events, such as receipts, acknowledgments, photographs, and decision notices. The records have not been independently authenticated, provider files have not been obtained, and reported intervals have not been matched against complete claim records. The six members’ consent to publication is not independent corroboration. For the pattern test, the evidence is therefore useful but incomplete; corroboration remains the principal evidentiary limitation of this submission.
21.Taken together, the five tests support drafting a practical standard for consultation, while requiring careful qualification. This submission supports asking whether clear time limits, status updates, and continuity guidance would reduce avoidable uncertainty. It does not establish that a particular service provider breached a legal requirement, that all reported delays were unreasonable, or that a proposed standard will prevent disaster losses.
5. Local legal context
22.The Council makes no claim about a Philippine statute, regulation, or locally applicable insurance rule governing the specific decision periods described by the members. The Secretariat therefore makes no claim here about a statutory deadline, a legal entitlement to bridge funding, or the legal status of any individual claim. No local-law proposition should be inferred from the members’ reported timelines.
23.Before the standard is finalized, the Council should invite qualified Philippine legal and insurance expertise to review any proposed language that could interact with existing consumer, insurance, disaster-response, or data-protection requirements. That review should distinguish voluntary service commitments from legal rights and obligations. Nothing in a voluntary standard should imply that it replaces, limits, or interprets applicable law.
6. Recommendations for RS-001 Reopen Standard
24.The group recommends that RS-001 translate reopening support into service commitments that a business can understand and track. The commitments should apply to the relevant organization’s own process, avoid promising a particular claim outcome, and explain what happens when a file is incomplete or a deadline cannot be met.
Insurance decision target. Include a target that an insurance claim be decided within 30 days after receipt of the information reasonably required to assess it. The standard should require a clear acknowledgment of receipt, a named or trackable point of contact, and an explanation of the decision. If additional information is required, the claimant should receive a specific request and a description of how the request affects the timetable. The standard should define how the 30-day period is counted and what constitutes a decision, without treating a target as a guarantee that every claim will be accepted.
Bridge funding after a declared disaster. Include a target for a decision on eligible bridge support within 10 days of a declared disaster. The standard should distinguish an application decision from the transfer of funds and should state what information is needed, how a business can apply, and how an applicant can check the status. It should also make clear that the standard does not itself create public funds, insurance coverage, or eligibility where none exists.
Short, accessible status updates. Require timely notice when a decision cannot be made within the stated target, including the reason for delay, outstanding items, the next expected update, and a route for escalation. Updates should use plain language and channels appropriate to micro businesses. A request for information should be consolidated where practicable, rather than issued in repeated, unexplained stages.
Continuity planning support. Require participating organizations to make practical continuity resources available to micro businesses before an incident. Resources should cover basic actions such as keeping essential contact and inventory records, identifying critical suppliers, protecting key documents, and planning for partial reopening. Guidance should be usable by an owner working alone or with a very small team, rather than assuming dedicated risk staff.
Measure elapsed time transparently. Ask participating organizations to record receipt dates, requests for additional information, decision dates, and any stated reasons for pauses. Publish aggregated performance measures that distinguish claims decisions from bridge-funding decisions and do not identify individual applicants. The standard should avoid comparisons that conceal differences in claim complexity or eligibility.
Provide a review and feedback route. A member should be able to ask for a status review where no update is received within the stated period. The process should identify a responsible contact and record whether the matter was resolved. A review route should not be framed as a substitute for any formal appeal or complaint process that may be available under applicable law.
Protect consent and confidentiality. Any monitoring or case study should use data minimization, informed consent, and safeguards against re-identification. The present accounts demonstrate why a member may need to describe a difficult process without publicly naming a business or provider. Aggregated reporting should preserve that protection.
7. Conclusion
25.The six members’ accounts describe a common reopening problem: a business may need to restore basic operations while waiting for a claim decision or a response to a request for temporary support. The evidence is concrete enough to inform draft language on timeframes, notice, and planning support, but too small and incompletely corroborated to establish prevalence, fault, or legal breach.
26.The Secretariat submits this evidence for consideration alongside the wider RS-001 record and public consultation. The recommended approach is a measurable, transparent minimum practice: timely decisions, clear explanations when timeframes cannot be met, and continuity guidance designed for micro businesses. The Council should retain the stated qualifications, seek further corroboration, and obtain local legal review before recommending final language to the Assembly.
Sources
[1] UNDRR, “Supporting disaster risk reduction and resilience practices for small and medium-sized enterprises.”
[2] UNDRR, “Resilience of SMEs” report, including the Japan METI survey result referenced above.
Notes and sources
Sources
This document has no standing until adopted under the Founders Charter. Reseated Councils is not affiliated with the United Nations.