Security plan XXXX - XXX days
Created by Abraji (Brazilian Association of Investigative Journalism)
Basic contacts
Reporter's security contact XXXX: YYYY (relation/proximity): 00 0000-0000
Reporter's security contact XXXX: YYYY (relation/proximity): 00 0000-0000
Main contact for field reporting: Person who will monitor the reporter to deal with protocol and receive daily feedback on arrival and departure (arrange a time in advance).
Contact with the XXXX editor of the XXXX website, for editorial issues relating to the report (arrange directly with the editor).
Daily contacts (depending on the signal) between the team and the base contact will be made via the Signal app and the Life 360 app.
Contact for XXXX, from the XXXXX community/region : 00 0000-0000
=====================================
Dates:
(link to tickets for the trip, if available)
Departure from XXX: 00/00 (weekday) at 00h00. Arrival in XXX at 0h (estimated time of arrival)
Return to XXXX: 00/00 (weekday) at XXXh. Departure XXX at 00h.
Itinerary and contacts
Insert here an image of the map with the pins indicating the stop/stay locations. Example:
Day 1: Travel from XXX to XXX (date and number of days)
-Morning/Afternoon: Flight to XXX (name of people traveling)
-Night: rest
- Lodging: name of place with address, zip code, contact, social network of the place (if any)
Day 2: City/place/region XXXX (date and number of days)
-Morning/Afternoon: Specialist interview of XXX, in place XXXXX
-Night: Rest
- Accommodation: name of the place with address, postal code, contact, social network of the place (if any)
3rd day: Interviews in city/place/region XXXX (date and number of days)
- Morning/afternoon: Interview with XXX, in place XXX
- Morning/afternoon: Interview with XXXXX, in place XXXXX
-Evening: Departure from XXX, at 000h
Arrival in XXX at XXXXh the next day.
Journey by XXXX (specify whether by boat, motorcycle, car, van, etc + contact details of driver and/or transport company)
DETAIL EVERY DAY!
======================================
Health protocol
- Covid and Yellow Fever vaccinations already taken by reporters XXXX and XXX
- First aid bag in suitcase
- Repellent and sunscreen
- Hammock and mosquito net
- Health Insurance XXXX (link to the insurance contracted) in the name of XXX and XXXX
- Life Insurance XXXX (link to the insurance contracted) in the name of XXX and XXXX
- Take a covid test the day before the trip and the day after the return trip
==========================================
Security protocol
- XXX, community leader, will guide us on the ground.
- Boatman/driver (name), a local resident and XXXXX's husband, will also accompany us.
- Main contacts will be notified when there is an internet signal: So far, we know that we should have signal from XXXXX operator in XXXXXX communities/villages/towns.
- Checkpoints will be given according to signal availability on the ground and base contacts will be notified beforehand.
-Arrange contact times with the editor. We will use Signal for these contacts. A message exchange group has already been set up.
- Print out a sheet with all the emergency phone numbers to carry in your backpack.
==============================================
Protocol for contacting the base
Keeping the phone in airplane mode preserves battery life, minimizes the team’s digital footprint, and restricts communications to planned, secure checkpoints
Every day, by XXh, send a message in the Signal group to say if everything is OK and let them know what the plan is for the following day
If there is no contact by midday the following day, activate the following response plan:
Immediately call the numbers of XXXX (guide) and XXXXX (boatman).
Call local contacts relevant to the day's agenda, e.g. sources.
If there is no response, call the XXXXXX Environmental Police.
Note: the idea is that XXXXXs always return at the end of the day to XXXXXX, where there is internet. If they are in another community (without internet) and think it is worth spending the night, they should return no later than midday the next day to XXXXXXX to let them know that everything is fine.
Trips on the XXXXXXX will be made during the day, with the exception of the return trip to XXXXXXXX, as the boat only leaves at night.
Emergency message code: (phrase to be agreed)
Nearest police authority: address and telephone number: PM Battalion XXXXXXXXX - Contact Lt XXXXX
Tel: 00 0000-0000
Nearest hospital/health center: address and telephone number: XXXXXX
Tel: XXXXXXX
Storage of material
Photos and texts will be stored in a Google Drive folder with restricted access for reporters and editors.
During the field trip, data and photos will be duplicated and stored on an external hard drive.
================================================
Social networks
Social media accounts will be closed while the story is being investigated on site and photos will not be published while we are in XXXXXXXX
==========================================
More possibilities for improvement - study each case
1 – Overall assessment of the Model security plan – n days
Section | What it already covers | Strengths | Observed gaps |
Basic contacts | Personal “safety contact” for each reporter, monitoring desk, local fixer and Signal/Life360 group. | Clear hierarchy; includes proximity/relationship tags. | No alt-channels (sat-phone, HF radio); no contact for local consulate or embassy. |
Calendar & tickets | Outbound / inbound flights with links to e-tickets. | Links avoid copy errors. | No section for ground / river transport reservations or fuel contingencies. |
Day-by-day itinerary | Template encourages full detail (lodging, contacts, transport). | Forces granular planning. | Map image is optional; no coordinates list; no time-of-day estimates for each leg. |
Health protocol | Vaccines, first-aid kit, hammock, mosquito net, insurance, pre- and post-trip Covid tests. | Addresses tropical diseases & gear redundancy. | Lacks malaria prophylaxis decision, snake-bite kits, heat-stroke guidance, hydration plan. |
Security protocol | Local guide & driver, checkpoint logic, Signal group, printed emergency sheet. | Good digital-hygiene points. | No section for high-risk interview scenarios, photo/filming restrictions, or data-protection encryption. |
Escalation ladder | Three-step response if no daily check-in. | Simple, actionable. | No explicit time zones; no threshold for activating evacuation or insurance assistance. |
Nearest police / hospital | Identified with phone numbers. | Critical field logistics. | GPS coordinates missing; no backup facility if first point is unreachable. |
Data storage | Cloud folder + external HDD. | Dual copy. | No offline encryption passphrase; no SD-card rotation plan for cameras. |
Social media blackout | Accounts closed while in field. | Reduces digital trail. | No guidance on delayed publishing of sensitive data once back online. |
2 – Additional customisation fields to consider
Environment / scenario | Extra items to add to the template | Rationale |
River-based travel | • Tide tables, river-level forecasts • Life-jacket requirement & quantity • Outboard-motor fuel cache points • Local marina/boat-repair contacts. | Amazon and Pantanal assignments often hinge on river height, fuel range and vessel safety. |
Heavy-rain / flood season | • Daily rainfall probability (source: INMET/NOAA) • Landslide or road-closure alerts • Alternate overland routes with estimated times • Waterproof bag checklist for gear. | Sudden flooding can strand teams or destroy equipment. |
Arid / high-temperature zones (Cerrado, Caatinga) | • Heat index forecast • Minimum water-carry volume per person • Cooling-break schedule • Electrolyte sachets in medical kit • Fire-risk rating and escape plan. | Heat exhaustion and wildfire spread are the main hazards outside rainforest regions. |
Wild-animal exposure (jaguar, caiman, snakes) | • Local wildlife-conflict briefing • Approved camping zones • Boots with snake guards; gaiters • Flashlight protocol for night walks • Phone numbers of nearest wildlife-rescue centre. | Encounters can be mitigated with behaviour guidelines and proper gear. |
Areas needing high discretion (illegal mining sites, land-grab zones) | • Pre-agreed cover story & press-card concealment • Plain-clothes dress code (colours, logos to avoid) • “Silent” mode on camera shutters • Local intel source who can verify safe entry windows • No geotagging in raw photo EXIF. | Reduces the risk of being targeted by armed groups or tipoffs from informants. |
Rainforest road trips | • Vehicle make/model, 4×4 or not • Spare-tyre count, compressor, tow-rope • Fuel autonomy table • Known illegal checkpoints flagged on map. | Road blockades and mechanical failures are common in remote stretches. |
Mountain / canopy work | • Climbing harness check • Drone flight permissions and spare propellers • Altitude-sickness medication plan. | Elevation introduces new physical and regulatory risks. |
Night navigation | • Curfew hour beyond which team must not travel • Red-light torches to preserve night vision • Reflective tape requirements for boat or motorcycle. | Most assaults and accidents occur after dark. |
Clothing & PPE matrix | • Recommended fabrics (quick-dry, UPF 50) • Colour guidance (earth tones for discretion, high-vis for river) • Rubber boots vs trekking shoes decision • Mandatory head-net in mosquito-dense zones. | Standardises preparation and avoids culturally sensitive attire. |
Local political tension | • Summary of current land-conflict actors • List of municipalities under federal intervention • Emergency legal aid hotline • Secure-drop link for sending evidence out of country if needed. | Political or judicial harassment can escalate rapidly. |
Data-protection protocol | • AES-256 encryption passphrase escrow • Separate SD-card per day, labelled only by date • Cell-phone “clean” mode to present at checkpoints. | Minimises fallout if equipment is seized. |
3 – Implementation tips
- Modular annexes – create plug-in pages (“Rain-annex”, “Wildlife-annex”) so reporters add only what fits their route, keeping the core plan lean.
- Colour-coded urgency – red for life-threatening hazards, amber for logistical issues, green for routine tasks.
- QR codes – embed QR links to live river-level dashboards, rainfall radar or secured satellite messenger pages.
- Time-zone header – top of every page should state “All times = GMT-04 / Manaus time” to avoid confusion with editors abroad.
- Drill checklist – include a 10-minute tabletop drill script the crew must run with the desk before departure.
Also look for information on how to enter a small indigenous community or village. Community leaders, NGOs and organizations such as Funai - National Indian Foundation - should be approached