B.4.b CSO NOFO Logic Model TEMPLATE - Annex B.xlsx
XLSX spreadsheet 23 KB Posted
- Opportunity number
- DFOP0014329
About this file
This document appears to be a logic model template for a Notice of Funding Opportunity (NOFO) related to a federal grant opportunity. The template includes sections for defining the program goal, overarching theory of change, objectives, outcomes, outputs, indicators, data collection tools, and risks/assumptions.
The related federal grant opportunity is titled "Combatting Economic Coercion and Corrupt Practices in the Pacific", solicitation number DFOP0014329. It is a cooperative agreement opportunity from the Department of State's Bureau of Conflict and Stabilization Operations (CSO) to support a program that will empower Pacific Island Countries to identify and prevent economic coercion and corruption, and build their resilience. The funding opportunity falls under the CSO's Conflict and Stabilization Operations program (CFDA 19.121). The applicant types are limited to for-profit organizations.
Logic Model
View the file
Other files
| File | Type | Posted |
|---|---|---|
| B.4.i CSO Combatting Sexual Exploitation and Abuse Policy - Annex I.docx | DOCX document | |
| B.4.g CSO Preferred Standard Indicators - Annex G.docx | DOCX document | |
| B.4.h CSO Data Collection Guidance - Annex H.docx | DOCX document | |
| B.4.d CSO Gantt workplan TEMPLATE - Annex D.xlsx | XLSX spreadsheet | |
| B.4.e CSO Gender Analysis of Conflict - Annex E.pdf | ||
| B.4.a CSO NOFO Detailed Line-Item Budget TEMPLATE- Annex A.xlsx | XLSX spreadsheet | |
| CSO Combatting Economic Coercion and Corrupt Practices in the Pacific NOFO (2).docx | DOCX document | |
| B.4.j CSO Proposal Submission Instructions - Annex J (1).docx | DOCX document | |
| B.4.c CSO Past Performance Reference Sheet TEMPLATE - Annex C.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| Program Title: | |||
| Program Logic Model | |||
| Level | Outcome/Output Indicators | Data Collection Tools | Risks and Assumptions |
| Goal: (overarching envisioned end-state) | |||
| Overall Theory of Change: IF we do x/y/z, THEN we will achieve a/b/c BECAUSE (project assumptions) | |||
| Theory of Change 1: (relates to Objective 1 logic frame) | |||
| Objective 1: (envisioned end-state contributing to goal) | OutCOME 1.1: |
Bruce Hemmer: Bruce Hemmer:
include both qualitative and quantitative indicators OutCOME 1.2:
Bruce Hemmer: Bruce Hemmer:
this section might include important intermediate outcomes that are short of objective but bridge several activities
| Activity 1.1: | OutPUT 1.1.1: |
| OutCOME 1.1.2: |
Bruce Hemmer: Bruce Hemmer:
add additonal outcome indicators as appropriate
| Activity 1.2: | OutPUT 1.2.1: |
| OutCOME 1.2.2: | |
| Theory of Change 2: (relates to Objective 2 logic frame) | |
| Objective 2: (envisioned end-state contributing to goal) | OutCOME 2.1: |
| OutCOME 2.2: | |
| Activity 2.1: | OutPUT 2.1.1: |
| OutCOME 2.1.2: | |
| Activity 2.2: | OutPUT 2.2.1: |
| OutCOME 2.2.2: | |
| Theory of Change 3: (relates to Objective 3 logic frame) | |
| Objective 3: (envisioned end-state contributing to goal) | Outcome 3.1: |
| Outcome 3.2: | |
| Activity 3.1: | OutPUT 3.1.1: |
| OutCOME 3.1.2: | |
| Activity 3.2: | OutPUT 3.2.1: |
| OutCOME 3.2.2: | |
| Notes: Adjust number of objectives and activities as needed. Objectives and goal must be worded as end-states to be achieved, not restatements of activities. There should be a minimum of one output and one outcome per activity, as well as at least one outcome at the objective level. Add more levels of outcomes if appropriate for monitoring needs or tracing causal processes, but keep number of indicators managable. |
Sheet2
Sheet3
File details come from the government source that posted it. Updated .