A Fiji event risk assessment covers five domains in one register: weather, medical, transport, political and regulatory, and supplier. Each row needs a trigger, a likelihood and impact rating, a named mitigation, a named owner, a residual rating and a review date. The template below gives the structure and the Fiji-specific rows most assessments omit.
Guideline only. This is a planning framework, not professional advice. Confirm weather with the Fiji Meteorological Service, medical arrangements with the Fiji Ministry of Health and Medical Services and your insurer, travel conditions with your own government's travel advisory service, and tax treatment with the Fiji Revenue and Customs Service. Last reviewed 9 October 2026.
The register structure
| Column | What goes in it |
|---|---|
| Risk ID | Sequential, so it can be referenced in minutes |
| Domain | Weather, medical, transport, political, supplier |
| Risk description | The event, not the fear - specific enough to be testable |
| Trigger or indicator | What tells you it is happening, and when |
| Likelihood | Your own scale, applied consistently |
| Impact | On delegates, on programme, on budget - rate separately |
| Mitigation | The action, already decided |
| Owner | A named person, never an organisation |
| Cost authority | Who can spend, and up to what |
| Residual rating | After mitigation, which is the number that matters |
| Review date | Per row, not per document |
The two columns that make the difference are trigger and cost authority. A register without triggers is a list of worries. A register without cost authority produces a conference call at 2am about who is paying for a replacement coach.
1. Weather and climate
Fiji's wet and cyclone season runs roughly November to April; the dry season roughly May to October. Verify the current outlook with the Fiji Meteorological Service rather than relying on seasonal averages.
Rows to include:
- Tropical cyclone forecast within the programme window. Trigger: a named-system advisory affecting Fiji. Mitigation is the decision tree - postpone, relocate, shorten - and the notice period each option needs. The real planning question is what you do with ten days' warning, not whether a cyclone lands.
- Heavy rain affecting an outdoor element. Trigger: forecast threshold plus a cut-off time for the switch decision. Mitigation: the named indoor alternative and whether it holds the same number.
- Heat and humidity affecting delegate welfare, particularly for outdoor team activities and midday sessions.
- Sea state affecting transfers, covered again below because it sits in two domains.
See what happens to a conference if there is a cyclone and wet weather contingency planning for outdoor programmes.
2. Medical and health
Assess this by site, not nationally. Medical depth varies sharply across Fiji, and an outer-island evacuation is a different proposition from a transfer to a city hospital.
For every location on the programme, record the nearest facility, the evacuation route and realistic time, the communications method, who holds delegate medical information and who authorises evacuation costs. Add rows for delegate pre-existing conditions declared in registration, food safety and allergen handling at each catered event, water and sanitation assumptions, and first-aid coverage and qualified staff on site.
Our regional picture is in healthcare and emergency services by region and security, medical and emergency cover at Fiji events.
3. Transport and access
- International flight disruption. Fiji's main international gateway is Nadi, so a disruption there affects most arrivals at once. Trigger: cancellation or diversion. Mitigation: accommodation hold and re-transfer, costed in advance.
- Sea transfer cancellation. The binding risk on island programmes. Scheduled services work to fixed daily windows - the Yasawa Flyer, for instance, departs Port Denarau in the morning and returns in the early evening - and a cancelled sailing can strand a group overnight. Record the last daily sailing, the operator's cancellation policy and the land-based fallback.
- Coach and fleet availability. The national fleet is finite and competing events draw on the same vehicles. Mitigation is contracting early with vehicle numbers in writing.
- Road conditions, including flooding and closures on the Queens and Kings roads, with alternative routes and revised journey times from the operator.
- Internal flight disruption for Taveuni, Vanua Levu and outer-island legs.
The operational detail belongs in the delegate transport plan template.
4. Political and regulatory
Do not assess this from news coverage. Use your own government's travel advisory as the reference point and record the advisory level and the date you checked it, with a review date before departure.
The regulatory rows are the ones planners most often miss, and 2026 is a good illustration. Fiji's VAT moved to 12.5% on 1 August 2025, and a 5% Tourism Services Tax commenced on 1 September 2026 for businesses above a prescribed F$2 million turnover threshold, per the Fiji Revenue and Customs Service. A tax change between contracting and delivery is a live budget risk on any long lead time. Include rows for:
- Tax or levy change between contract and delivery, with a named review date
- Visa or entry-requirement change affecting delegates - see visas and entry for conference delegates in Fiji
- Work-permit requirements for speakers, trainers and crew
- Customs clearance and carnet for imported equipment
- Currency movement, if you are contracting in FJD and budgeting in another currency
5. Supplier and commercial
- Single-supplier dependency, which in Fiji most often bites in AV and production. Record what is in-house, what is sub-contracted and what is freighted in, with lead times. Record the alternative supplier.
- Venue insolvency or change of ownership over a long lead time.
- Key-person dependency at the venue or DMC - the named co-ordinator who leaves three weeks out.
- Deposit exposure, mapped against the cancellation and force majeure terms you actually signed.
- Insurance gaps, assessed against the specific perils above rather than assumed. Event insurance for a Fiji conference sets out what cover usually does and does not include.
How to use it
Fill the register at contracting, not at the planning stage, because mitigations that are not in a contract are intentions. Then set per-row review dates: weather rows weekly in the final month and daily in the final week, supplier rows at contracting and at final payment, regulatory rows at every budget revision.
Pair it with duty of care for delegates in Fiji, and build the budget contingency line from the residual ratings rather than a flat percentage. The wider framework is in the Fiji business events guide.