Institutional Memory & AI Tools

Why Institutional Memory Matters in Active War

In a neighbourhood Emergency Response Room (ERR), operational conditions shift rapidly. An artillery strike closes a primary supply route, an internet blackout cuts communications for weeks, or a volunteer responsible for kitchen purchasing is forced to relocate overnight. When operational knowledge exists only in the minds of individual volunteers, the loss of one person can freeze community kitchens, disrupt water distribution points, or misplace scarce funds.

Institutional memory is not bureaucratic paperwork or administrative overhead. It is the practical, shared habit of recording essential information so that the response room continues serving the community regardless of who rotates out or how long communications remain down. In active conflict zones across Sudan, clear documentation is an essential tool for community resilience, resource protection, and volunteer safety.

The Four Essential Records

To keep a response room operating reliably without overburdening exhausted volunteers, your team only needs to maintain four core records. Each record addresses a specific operational need.

1. Decision Logs

A decision log is a brief, dated record explaining why specific choices were made. When resources are tight, volunteers frequently face tough choices: reducing meal portion sizes, shifting a water delivery point to a safer street, or switching fuel vendors. Recording the rationale behind these decisions prevents repetitive debates and maintains transparency among team members.

Rules for decision logging:

• Record the decision within 12 hours of making it.
• Keep the record strictly operational.
• Focus on four elements: Date/Time, Operational Problem, Action Chosen, and Rationale.

Field example: "14 May, 09:00 - Main flour route from Central Market blocked. Action: Approved buying sorghum from Neighbourhood Market B at a 10% higher price. Rationale: Avoids active transit risks while securing three days of food for the communal kitchen."

2. Operational Lessons Learned

Every day at a community kitchen, health point, or emergency shelter, volunteers discover what succeeds and what fails under field conditions. Operational lessons capture practical insights so that future shifts or neighbouring response rooms do not repeat preventable mistakes.

Lessons must focus on processes, storage conditions, and logistics—never on assigning personal blame to individual volunteers.

Field scenario at 6:00 AM:
A shift leader notices that two sacks of lentils spoiled because they absorbed moisture from a damp floor.
Wrong response: Blaming the volunteer who unloaded the truck.
Correct response (Lesson Logged): "Lesson: Store all dry legumes on wooden pallets elevated at least 15 cm off clay floors to prevent moisture damage during humid periods."

3. Safety and Incident Logs

Incident logs record security events, road closures, market disruptions, or access delays affecting your room's work. These records allow team coordinators to identify dangerous trends—such as recurring checkpoint delays on specific days—and modify delivery schedules or routes accordingly.

The Principle of Data Minimization: In conflict environments, physical or digital documentation can become a major safety risk if searched at a checkpoint or accessed by unauthorized actors. You must strip all sensitive data from incident records:

• NEVER record names of military units, armed groups, or political factions.
• NEVER record full names, phone numbers, or addresses of individual volunteers or local residents.
• Use functional, generic descriptions: "unidentified armed individuals", "commercial road inspection", "district border crossing".

| What to Record | What NOT to Record | | :--- | :--- | | "12 June, 08:30: Water tanker delayed 3 hours at eastern crossing due to vehicle inspection." | "12 June: Armed group [Name] commanded by [Name] detained driver [Name] at the bridge." | | "15 June: Cooking oil price rose 30% across local markets following fuel supply disruption." | "15 June: Merchants linked to [Faction] are manipulating market prices." |

4. Handover Notes

A handover note is a concise, one-page summary written when a volunteer holding an operational role (such as a kitchen manager, medical coordinator, or logistics lead) must rotate out or leave the area. A sudden handover without written notes often leads to lost vendor deposits, duplicated purchases, or broken community agreements.

A complete handover note contains five elements:

1. Operational Contacts: Verified local vendors, water truckers, and neighborhood elders (listed by first name or code and functional role).
2. Inventory Status: Physical count of food, fuel, or medical stock currently present at the site.
3. Pending Commitments: Unpaid vendor bills, planned inventory arrivals, or promised community distributions.
4. Routine Operational Schedule: Key operating hours, generator run-times, or distribution procedures.
5. Emergency Information: Location of backup paper logs and physical safe keys.

Formats: Paper versus Digital in Network Blackouts

When electrical grids fail and mobile networks are unavailable for extended periods, response rooms must use simple, reliable documentation methods:

1. Physical Logbooks: Use hard-cover bound notebooks kept in a secure, dry box. Write with waterproof ballpoint pens. Physical notebooks remain fully functional during total power blackouts.
2. Offline Digital Notes: If using mobile devices, write simple plain-text (.txt or markdown) files or basic offline spreadsheets saved directly to local storage. Keep devices password-protected.
3. Daily 5-Minute Closing Routine: At shift change or facility closing, take five minutes with the team to record daily totals, decisions made, and any incidents before leaving.

Standard Principles for Record-Keeping

• Promptness: Record events on the day they occur while details are clear.
• Neutrality: Stick strictly to observable facts (quantities, times, physical locations, operational actions). Avoid political commentary or speculation.
• Physical Protection: Store paper logs out of public view. Establish a clear rule for which volunteer is responsible for securing or destroying sensitive records if safety is threatened.

Introduction: AI Tools in the Midst of Crisis

As a volunteer in an Emergency Response Room (ERR), your daily workload is immense. Between managing community kitchens, coordinating emergency medical points, and securing clean water, you are often asked to write activity reports, draft grant proposals, translate updates for international partners, or digest long technical manuals. When internet connectivity becomes briefly available via satellite connections or local networks, AI text models can serve as powerful tools to reduce administrative friction and save hours of work.

However, using AI in a active conflict environment carries extreme risks. AI platforms run on external, cloud-based servers. Every piece of text you paste into a prompt can be stored, analyzed, or exposed through data breaches. In an environment where armed actors scrutinize phone data and community members face severe protection risks, a single mistake—such as pasting a volunteer's name or a kitchen's location into an online AI tool—can lead to harassment, arrest, or targeted attacks. This lesson provides clear, practical guidelines on how to leverage AI tools productively while enforcing ironclad security standards.

Core Capabilities: What AI Can Help You Do Responsibly

When used correctly, AI models act as rapid administrative assistants. They excel at processing structure, grammar, and generic information. You can responsibly use AI for four primary tasks:

1. Drafting and Formatting Reports

AI tools can transform bullet points into well-structured paragraphs. If you log daily kitchen outputs (e.g., number of meals cooked, firewood consumed, hours operated), you can paste anonymous, sanitized notes into an AI tool and ask it to format them into a standard narrative report.

2. Translation and Language Bridging

Many funding opportunities and international reports require written English, while local operational logs are kept in Arabic. AI models can quickly convert draft text between Arabic and English. However, translated text must always be reviewed by a human to ensure context, tone, and technical terms are accurate.

3. Summarising Heavy Manuals and Technical Guides

When guidelines on water chlorination, disease outbreak response, or protection standards are distributed as long PDF documents, you can copy sections into an AI model and ask for a 5-bullet summary focused on immediate practical actions.

4. Structuring Meeting Agendas and Planning

AI can help build operational templates, risk assessment frameworks, or meeting agendas. For example, you can prompt the tool: "Provide a structured 30-minute agenda template for a community volunteer debriefing on water distribution challenges."

The Absolute Red Lines: What Must NEVER Be Input Into an AI Model

To safeguard your team and your community, you must adhere to the Zero-Leak Rule. Assume that any information entered into a cloud-based AI model becomes public domain immediately.

| Restricted Data Category | Examples of Dangerous Inputs | Safe Alternative / Substitution | | :--- | :--- | :--- | | Personal Identities | Names of volunteers, drivers, cooks, doctors, local council members, or displaced persons. | Use generic roles: "Volunteer A", "Kitchen Manager", "Resident". | | Specific Locations | Neighborhood street names, exact GPS coordinates, building landmarks, safe houses, or delivery routes. | Use high-level zones: "Zone 2", "District B", "Sector North". | | Financial Details | Bank account numbers, e-wallet account details, exact cash transfer amounts, or trader names. | Use generic labels: "Local Vendor X", "Transfer Channel 1", "Budget Item A". | | Protection & Incidents | Details of armed incursions, military movements, shelling incidents, or sensitive protection cases. | Do not input sensitive security incidents into AI under any circumstances. |

The Verification Rule: Never Trust AI Outputs Unchecked

AI models do not understand real-world facts; they generate text based on statistical patterns. They frequently create "hallucinations"—plausible-sounding statements that are entirely false. An AI model might invent non-existent health protocols, miscalculate budget totals, or mistranslate sensitive political terms in ways that violate humanitarian neutrality.

Follow these three verification principles before sharing or using any AI-generated text:

1. Verify All Numbers and Math: Never rely on AI to calculate total expenditure or food ration totals. Re-check every calculation manually.
2. Check Neutrality and Nuance: In conflict zones, specific words carry heavy political weight. Ensure translations do not adopt partisan language, military terminology, or biased phrasing.
3. Confirm Operational Accuracy: Ensure any recommended action fits local reality. An AI model does not know if a specific road is blocked or if electricity is down in your district.

+-----------------------------------------------------------------------+
|                      THE 4-STEP SAFE AI WORKFLOW                      |
+-----------------------------------------------------------------------+
|  1. SANITIZE  --> Remove names, exact locations, dates, and finances. |
|  2. PROMPT    --> Input only anonymized structure and generic text.   |
|  3. VERIFY    --> Check output manually for errors and political bias.|
|  4. LOCALIZE  --> Adjust language to fit local field realities.      |
+-----------------------------------------------------------------------+

Managing AI Constraints in Low-Bandwidth Environments

Internet access in Sudan is frequently cut or limited to brief windows near satellite points. To use AI effectively under these constraints:

• Prepare Prompts Offline: Write and sanitize your prompt in a local text editor on your phone or laptop before connecting to the internet.
• Copy, Don't Browse: Connect to the network, paste your prepared prompt into the AI tool, copy the output immediately into a local document, and disconnect to save data and battery.
• Use Offline Templates: Keep pre-approved narrative templates on encrypted USB drives so you do not rely on AI tools for routine, daily reporting.