Lesson 43 · The Grant Architect

43. Narrative Alignment

30 min

By the end you'll be able to

  • Use the logic model as a table of contents for the project narrative.
  • Run an alignment audit in both directions (diagram to text, and text to diagram).
  • Discipline the narrative structure using the logic model columns.
  • Detect and fix inconsistencies that quietly lower reviewer scores.

The logic model and the project narrative have to tell the same story. In this lesson you learn to use the logic model as a table of contents for the narrative, ensuring that every element in the diagram appears in the text and every claim in the text traces back to an element in the diagram. Internal consistency between visual and prose is one of the cleanest signals of organizational discipline a reviewer can pick up.

You will practice the alignment audit: print the logic model, read the narrative with a highlighter, and confirm that each input, activity, output, and outcome is named and explained in the prose. The reverse check matters too. If the narrative introduces a new activity that does not appear in the diagram, either the diagram is incomplete or the narrative is padding. Either way the inconsistency will be caught.

By the end you should be able to run an alignment pass on a real proposal, fix the gaps in both directions, and use the logic model to discipline the narrative structure (one paragraph per activity, one evaluation section per outcome tier). Reviewers who can move between the visual and the text without friction tend to score the proposal higher on clarity, feasibility, and evaluation, because the document reads as a single coherent argument.

Common mistakes

These are the traps learners hit most often on this topic. Knowing them in advance is half the fix.

  • Skipping the second direction of the audit.

    Most teams check that the diagram appears in the text, but forget to check that the text does not introduce new elements. Run both directions.

  • Allowing label drift between sections.

    Calling the same outcome "Outcome A" in the diagram, "Outcome 1" in the narrative, and "the financial literacy goal" in the evaluation plan confuses the reviewer. Use one label everywhere.

Practice problems

Try each on paper first. Click Show solution only after you've made a real attempt.

  1. Problem 1
    Describe the three-step alignment audit you would run on a finished proposal the night before submission.
    Show solution

    Step 1 (diagram to text): print the logic model, then read the narrative with a highlighter and confirm that every input, activity, output, and outcome in the diagram is named and explained in the prose. Step 2 (text to diagram): read the narrative again and confirm that every activity, output, and outcome mentioned in the text is present in the diagram. Add or remove items so the two match. Step 3 (label consistency): confirm that the exact labels used in the diagram (Outcome 1, Outcome 2, and so on) are used identically in the narrative, the evaluation plan, and the budget narrative.

Practice quiz

  1. Question 1
    What is the alignment audit the lesson describes?
  2. Question 2
    Why does the lesson recommend organizing the narrative around the logic model columns?
  3. Reflection 3
    What does a reviewer conclude when the narrative introduces an activity that does not appear in the logic model?

Lesson 43 recap

Alignment between the visual and the prose is one of the cheapest scoring wins available, and a disciplined two-direction audit catches almost all the inconsistencies that hurt proposals.

Coming next: Lesson 44 — AI Spotlight

Finally, we look at how AI accelerates logic model brainstorming without taking over the design judgment that only a human practitioner can supply.

Saved in your browser only — no account, no server.