Proposal Development & Advocacy

Moving from Unmet Needs to a Logical Framework

Every morning at 6:00 AM, volunteers at a neighbourhood response room gather to light cooking fires, check water pump fuel levels, and clear supply lines before local curfews or active shelling disrupt movement. You see hundreds of displaced families waiting outside the communal kitchen with empty pots. You know exactly what the community needs: food, clean water, trauma kits, and shelter sheeting. However, when an international partner or local grant manager asks for a funding proposal, listing these immediate needs as a shopping list is not enough.

Funders and pooled fund administrators need to see a clear chain of logic. They want to know how money transferred via informal cash networks will turn into specific activities, how those activities produce direct outputs, and how those outputs lead to measurable outcomes. A logic model is not corporate bureaucracy; it is a tactical roadmap. It proves that your response room understands the local context, anticipates security bottlenecks, and can track progress even when the internet is cut and phone networks go dark.

1. Framing the Problem Statement Without Political Risk

A proposal starts with the problem statement. In an active war zone, writing a problem statement requires strict neutrality and precision. If your statement uses partisan language, attributes blame to specific armed actors, or uses exaggerated claims, international partners may reject the proposal to protect their neutral mandate, or local authorities may view your room as a target.

The Problem Statement Formula

To write a safe and compelling problem statement, combine three facts:

1. The Specific Need: Who is affected, where, and what essential service is missing?
2. The Field Evidence: Recent local counts, market price spikes, or emergency registry data.
3. The Immediate Consequence: What happens if assistance does not arrive within days?

Dialogue in the Room:

• Volunteer A: "We should write that the army shelling destroyed the main market, so people are starving because of the blockade."
• Volunteer B: "If that paper gets leaked or read at a checkpoint, our kitchen will be shut down. Let's frame it on human impact: 'In District 4, food prices have risen by 300% in six weeks while daily labor opportunities have collapsed. Over 450 displaced households in three school shelters receive less than one meal per day, leading to severe malnutrition risks among children under five.'"

Notice the difference: Volunteer B focuses on verified humanitarian impact without making political accusations or collecting unsafe intelligence.

2. Setting Objectives that Match Real Operational Limits

An objective states what your emergency response room intends to accomplish. In war contexts, objectives must be strictly realistic. Promising to "eliminate food insecurity across the entire city" will sink your proposal because no funder believes a single room can achieve it under active bombardment.

Use the modified SMART rule for emergency response:

• Specific: Target a defined neighborhood or shelter cluster.
• Measurable: Include simple counts (liters of water, hot meals, hygiene kits).
• Achievable: Match the objective to your actual volunteer capacity and supply routes.
• Relevant: Align directly with the immediate survival priorities identified by the community council.
• Time-bound: Limit the timeframe to realistic operational windows (e.g., 30 to 90 days).

Example Objective: "Provide 1,200 daily hot meals to 400 displaced and host community families in District 4 communal shelters over a 60-day period using local market procurement."

3. Activities: Concrete Steps Under War Conditions

Activities are the specific actions your volunteers take to fulfill the objective. Donors look at your activity list to assess whether your room has genuine access and operational capability.

When listing activities, write them in chronological, operational sequence:

1. Establish community procurement agreements with local merchants in safe market zones.
2. Receive cash transfers through verified local channels or merchant credit arrangements.
3. Procure daily bulk ingredients (sorghum, lentils, oil, firewood) and secure storage.
4. Prepare meals daily using rotating volunteer shifts, maintaining strict hygiene standards.
5. Distribute meals using identity-blind token systems managed by women-led shelter committees.

Decision Rule on Safety and Activities: If an activity requires volunteers to cross active frontlines or aggregate sensitive population data on digital devices, modify the activity immediately. Focus on localized, decentralized delivery that keeps volunteers safe.

4. Outputs versus Outcomes: The Critical Distinction

Confusing outputs and outcomes is the single most common reason logic models fail. Proposal reviewers check this distinction first.

| Level | Definition | Kitchen Example | Water Point Example | | :--- | :--- | :--- | :--- | | Activity | What volunteers do | Cooking lentils and sorghum daily | Repairing handpump and installing solar panel | | Output | Direct, tangible product or service delivered (counts) | 36,000 meals served over 30 days to 1,200 individuals | 10,000 liters of safe drinking water produced daily | | Outcome | The change in condition, behavior, or status resulting from outputs | Reduced acute hunger among displaced families in 3 shelters | Decreased incidence of waterborne diarrhea among children in the sector |

Remember this rule: Outputs count what you did; outcomes describe what changed for the people you served. You control your outputs directly; outcomes depend on whether your outputs were sufficient, timely, and appropriate.

5. How Donors and Grant Officers Read Your Logic

When a grant officer at a humanitarian pooled fund reads your logic model, they do not read top-to-bottom. They read in a vertical line test:

1. If you carry out these activities, then will they reliably produce these outputs?
2. If these outputs are achieved, then will they logically contribute to this outcome?
3. If this outcome is reached, then does it solve the problem stated in Section 1?

If there is a gap in this chain—for example, proposing water purification tablets (output) to solve a lack of wheat flour (problem)—the logic fails. Grant officers also look for assumptions and risks. In your proposal, explicitly state assumptions like: "Assumes local markets remain stocked with local grain" or "Assumes safe morning movement windows allow cooking fires to operate."

Summary Checklist for Logic Model Review

• [ ] Is the problem statement neutral, focused on human impact, and backed by local counts?
• [ ] Does the objective specify location, target group, quantity, and time limit?
• [ ] Are activities written in clear, step-by-step operational order?
• [ ] Are outputs strictly counted units (meals, liters, visits, kits)?
• [ ] Do outcomes describe actual improvements in community survival or health?
• [ ] Can the logic model pass the vertical "If-Then" test from bottom to top?

Introduction: Why Budgets Fail in Siege Conditions

When you submit a budget for a community kitchen, emergency water point, or mobile health post, donor finance committees look for transparency, verifiable unit costs, and formal receipting. However, operating under active war and siege in Sudan means bank branches close, physical cash carries heavy transaction surcharges, and local market prices fluctuate daily due to fuel shortages and blockades. Standard commercial invoices rarely exist at small neighbourhood markets.

A budget that survives review must bridge two realities: the strict compliance standards of external donors and the unpredictable, cash-starved reality of local response. This lesson shows you how to build realistic unit costs, account for financial cash-out commissions, structure donor-acceptable contingency buffers, and write clear budget narratives that justify every Sudanese Pound required to keep your community alive.

Step 1: Building Realistic Unit Costs in Volatile Markets

A primary reason donor finance officers reject grassroots proposals is the use of unverified lump sums or outdated peaceful-period price estimates. In active conflict zones, a sack of sorghum or a container of cooking fuel in a besieged district can cost twice as much as in an adjacent accessible area.

To build unit costs that pass technical review:

1. Establish a Three-Trader Market Average: Survey three local traders in your immediate area over a 7-day period. Average these prices to establish a baseline unit cost rather than relying on a single quote.
2. Deconstruct Compound Activities: Never write "1 Meal = 600 SDG" as a single lump sum without breakdown. Donors reject lump sums because they cannot verify value for money. Always break down a composite service into its physical components.

| Item Component | Quantity per 100 Meals | Base Unit Cost (SDG) | Total Cost per 100 Meals (SDG) | | :--- | :--- | :--- | :--- | | Sorghum / Grain | 12.5 kg | 2,500 per kg | 31,250 | | Cooking Oil | 2 Liters | 7,000 per Liter | 14,000 | | Onions & Spices | 4 kg | 2,000 per kg | 8,000 | | Firewood / Gas | Share per batch | 10,000 | 10,000 | | Total Direct Cost | 100 Meals | -- | 63,250 SDG (632.5 SDG/meal) |

3. Define Clear Units of Measurement: Use precise, verifiable physical units (e.g., kilograms, liters, vehicle round-trips, daily volunteer transport stipends) instead of vague descriptors like "lot", "lump sum", or "global allocation".

Step 2: Accounting for Procurement Realities and Cash Movement

In siege conditions, moving physical cash to purchase supplies involves real operational costs and safety risks. External donors frequently question line items for financial intermediary fees unless they are explicitly structured and justified.

Financial Intermediary and Cash-Out Commissions

When commercial banking systems collapse, response rooms must transfer funds digitally via mobile banking applications and rely on local financial brokers (hawala or cash-out agents) to convert digital balances into physical banknotes needed at daily markets. Agents charge commissions ranging from 10% to 30% depending on cash liquidity.

• How to budget it: Include a distinct operational line item titled "Cash Access and Financial Intermediary Service Fees". Calculate this as an explicit percentage based on verified local market broker rates.
• Narrative Justification: "Due to the complete shutdown of commercial bank branches in the targeted area, physical cash for food purchases must be obtained through verified local brokers who charge a 15% cash-out fee. This fee is necessary to secure physical currency for local market purchases where digital payments are not accepted."

Transit Surcharges and High-Risk Transport

Moving goods across frontline zones or through informal checkpoints increases transport costs due to driver risk premiums and detours.

• Avoid improper terminology: Do not list payments under names that violate donor compliance policies or legal rules.
• Use clear operational framing: Label these expenses as "Hazardous Route Transport Surcharges" or "Local Feeder Logistics (Donkey Cart / Small Vehicle Surcharges)". Detail the exact breakdown: number of trips, distance, and local risk-adjusted transport rates.

Step 3: Structuring Honest Contingency Lines

Donor finance guidelines generally reject generic budget lines named "Contingency - 10%" or "Miscellaneous Emergency Fund". Finance reviewers view unassigned funds as high compliance risks. However, operating without a price buffer during hyperinflation or supply blockades leaves your room vulnerable to sudden shortfalls.

To preserve flexibility while meeting donor compliance, replace generic contingency lines with Risk-Adjusted Operational Lines tied to specific field conditions:

1. Price Volatility Buffer: Build a clear buffer (typically 10% to 15%) directly into high-volatility direct costs like fuel or imported staples. Explain in the narrative that this buffer accounts for documented weekly price swings.
2. Equipment Maintenance and Wear Buffer: Rather than a general buffer, create specific maintenance lines for high-use equipment, such as "Solar Inverter Fuse Replacement and Generator Maintenance" or "Kitchen Cookware Replacement under Continuous Operation".
3. Secondary Logistics Provision: Budget for alternative transport options if primary supply roads are suddenly blocked.

Decision Rule for Contingency Framing

• Rule: If a financial buffer cannot be tied to a documented, observable field risk (such as fuel price surges or equipment breakdown under continuous community use), remove it as a separate line and incorporate it into the direct unit cost narrative with supporting market data.

Step 4: Budget Narrative and Avoiding Common Rejections

The budget narrative is the text document that explains every calculation in your budget table. A thorough narrative answers reviewer questions before they trigger a formal rejection.

Checklist for a Review-Ready Budget

• [ ] Direct Alignment: Every line item corresponds directly to an activity described in your proposal narrative (e.g., if you budget for phone data, the narrative must mention daily volunteer reporting and coordination).
• [ ] Explicit Mathematical Formulas: Every line displays the exact formula used: [Number of Units] x [Unit Cost] x [Frequency/Duration] = Total Line Cost.
• [ ] Complete Operational Coverage: Includes indispensable operational support costs—such as volunteer communication stipends, transport support, and cooking fuel—rather than only raw commodities.
• [ ] Alternative Verification Methods: Explains how expenses will be verified when commercial receipts are unavailable, such as signed three-person community witness logs and local vendor price certificates.

Dialogue Snippet: Correcting a Rejected Line Item

• Donor Finance Officer: "We are flagging Line 2.3 'Logistics Lump Sum: $2,000' for rejection. It lacks breakdown details and offers no standard vendor receipting mechanism."
• Response Room Finance Lead: "We will adjust Line 2.3 into three explicit sub-lines: local water truck deliveries (15 trips at $80/trip), alley distribution by local cart operators for areas unreachable by trucks (20 days at $15/day), and weekly phone data packages for 2 logistics coordinators ($25 x 4 weeks x 2 people). For documentation, our community oversight committee will co-sign daily delivery logbooks alongside cart operators and water sellers."
• Donor Finance Officer: "Thank you. The adjusted breakdown clarifies the operational logic and provides an acceptable alternative verification log. Line approved."

Why Framing Matters: Beyond Requesting Funds

When your response room submits a funding proposal to an international donor or humanitarian intermediary, you are doing more than asking for money to buy sorghum, lentils, or medical supplies. You are explaining how frontline survival works in Sudan under active conflict. Every proposal narrative is an advocacy document. It shapes how external actors understand your community's reality, your operational risks, and your role as neutral, self-organized responders.

International donors often default to standard contracting models designed for large international non-governmental organizations (INGOs). These models assume clear supply chains, legal registration, stable bank access, and formal security management. In a war zone where power grids are down, telecommunications blackout for weeks, and volunteers face arbitrary detention or harassment at checkpoints, standard donor templates fail. Your task in proposal development is to frame your technical request around three core advocacy pillars: volunteer protection, flexible direct funding, and women-led leadership.

By embedding these advocacy frames directly into your project summary, risk matrix, and budget narrative, you push donors to adapt their practices to fit your reality, rather than forcing your volunteers into dangerous or impossible compliance requirements.

---

Pillar 1: Framing Volunteer Protection and Risk-Sharing

In many standard donor proposals, risk management is treated as risk transfer: the donor gives funds, and the local implementer assumes all physical, legal, and operational risks. When writing your proposal, you must explicitly challenge this pattern and frame protection as a shared responsibility.

Field Dialogue: Shifting the Narrative

Donor Representative: "We see in your proposal that transport drivers face detention at neighborhood checkpoints. Can you guarantee safe delivery of flour to the kitchen?"

Response Room Volunteer: "We cannot guarantee absolute safety in an active war zone. What we provide is an active community risk mitigation strategy—using local neighborhood routes, unbranded transport, and local dialogue. To maintain this, our budget must include volunteer emergency support, legal aid reserves, and flexible delivery schedules rather than fixed delivery deadlines that force drivers to travel during high-risk hours."

How to Write Protection into the Proposal

1. Reframing 'Volunteers' as Frontline Humanitarian Responders: Clarify that volunteers are not free labor; they are community members risking their lives. Request coverage for medical care, transportation stipends, and trauma support.
2. Budgeting for Security and Neutrality: Explicitly include line items for operational security—such as unbranded vehicles, secure phone credits, satellite connectivity fees, and emergency evacuation funds.
3. Rejecting Unsafe Compliance: Plainly state where standard compliance requirements (such as taking photos of beneficiaries or recording national ID numbers) put volunteers and residents in danger. Frame non-collection of sensitive data as a core protection and neutrality measure.

INCORRECT FRAMING: "Volunteers accept full personal risk to deliver aid in conflict areas without additional cost."
CORRECT ADVOCACY FRAMING: "To sustain aid delivery safely, the project includes a risk-sharing budget for volunteer emergency medical care, legal assistance, and non-sensitive monitoring protocols that protect community confidentiality."

---

Pillar 2: Framing Flexible, Direct Funding for Mutual Aid

Mutual aid relies on speed, trust, and adaptability. A community kitchen operating at 6:00 AM may need to shift from cooking beans to distributing clean water if a shelling incident damages the local water main. Traditional proposals require rigid activity lines that prevent this agility.

Constructing the Flexible Funding Argument

When writing the budget narrative, frame flexibility not as a lack of planning, but as operational necessity and fiscal responsibility in a fluid environment:

• Unearmarked Operational Contingency: Advocate for a flexible contingency allowance (typically 10% to 15%) that can be reallocated between health, food, and water emergency lines without waiting weeks for written donor approval.
• Direct Cash and Local Procurement: Explain why local market purchases or cash transfers via informal networks are faster, cheaper, and safer than long-distance shipping or formal bank transfers that remain blocked due to banking system collapses.
• Fair Institutional Support (Overhead): Insist on direct core coverage for the response room's organizational needs—generator fuel, rent for safe community spaces, phone cards, and ledger management supplies. Mutual aid cannot survive on zero-overhead funding.

---

Pillar 3: Elevating Women-Led Response

In Sudanese emergency response rooms, women are frequently the primary organizers of community kitchens, reproductive healthcare delivery, trauma support, and local protection networks. However, traditional proposal models often reduce women to passive aid recipients or isolated 'vulnerable groups'.

Concrete Approaches for Women-Led Framing

• Highlight Leadership, Not Just Vulnerability: Document women as active decision-makers who design menu schedules, negotiate local access, manage kitchen security, and run health points.
• Integrate Gendered Protection Costs: Include specific budget lines that enable women to participate safely—such as secure, accompaniment-based transportation to kitchens, safe childcare options during operational hours, and female-led healthcare supplies (dignity kits, reproductive health items).
• Autonomous Decision-Making: Ensure the narrative reflects women-led committees having direct control over their operational budgets rather than acting under secondary approval from male-dominated structures.

| Standard Donor Frame | Response Room Advocacy Frame | | :--- | :--- | | "Providing food aid to 500 vulnerable women and children." | "Funding a women-led community kitchen network that feeds 500 households while prioritizing female volunteer safety and local leadership." | | "Distributing dignity kits to affected populations." | "Supporting women-led health points with reproductive healthcare supplies, flexible transport, and peer-to-peer counseling services." | | "Including women in community consultation meetings." | "Ensuring female coordinators hold direct budget approval and operational oversight over emergency response activities." |

---

Writing Strategy: Translating Field Realities into Policy Language

To build a convincing proposal, you must translate daily field practices into language that international aid officers understand and can defend to their board members.

Translation Guide for Proposals

1. Field Reality: "We buy lentils from local vendors using cash transferred through neighborhood trust networks because banks are closed."
   • Policy Frame: "Utilizing localized, market-based procurement and informal financial service providers to maintain supply chain continuity during formal banking disruptions."
2. Field Reality: "We do not collect names or ID numbers of people coming to the kitchen because armed groups might search our notebooks."
   • Policy Frame: "Applying strict 'Do No Harm' protection principles and data-minimization protocols to shield beneficiaries and volunteers from targeting and political interference."
3. Field Reality: "Women volunteers run the kitchen every morning and decide what to cook based on market prices that change daily."
   • Policy Frame: "Decentralized, women-led operational governance ensuring real-time adaptive management based on rapid local market assessments."

---

Common Pitfalls to Avoid

• Promising Unrealistic Verification: Never promise photos, GPS tags, or biometric records if doing so puts a volunteer or beneficiary in physical danger. State clearly in the proposal what monitoring methods are safe.
• Using Partisan or Accusatory Language: Avoid political claims or naming specific armed factions in your proposal text. Focus strictly on humanitarian need, civilian protection, and neutral aid delivery.
• Underestimating Core Costs: Do not exclude volunteer stipends, transport, fuel, or communications from your budget out of fear that the donor will reject them. A project that starves its own operational network will fail in the field.
• Treating Advocacy as an Afterthought: Do not leave gender, protection, and flexibility to the narrative background sections. Ensure your budget lines explicitly mirror the advocacy points made in your proposal narrative.