The quiet things a program officer reads first.

There is a sequence most grant writers assume. The program officer opens the proposal. She reads the cover letter, then the executive summary, then the narrative, then the budget, then the appendices. She forms a view. She makes a recommendation.

That is not what happens.

What happens is that she has forty of these to get through before a committee meeting, she already knows roughly how many she can advance, and her first pass is not a reading at all. It is a triage. She is looking for reasons to set your application down, because setting applications down is the only way she gets to the end of the pile.

Here is the order I have come to believe she actually moves in.

First, the amount you asked for against the size of you. Before she has read a sentence about your mission, she has seen your request and your operating budget on the same screen. If you are a $400,000 organization asking for $350,000, something is wrong, and she now reads everything that follows looking for what it is. If you are a $4M organization asking for $15,000, she wonders why you bothered and whether you will still care about this grant in eighteen months. The ratio sets her frame before your program gets a word.

Second, the board list. It takes eleven seconds. She is not counting names. She is checking whether it reads like a governing body or a courtesy list: whether there is anyone with financial expertise, whether the terms suggest turnover or a founder who has never let go, whether the people affected by your work are represented anywhere on it. A board list is one of the few documents in an application that is difficult to write your way out of.

Third, your outcome statements. Not your goals. Your outcomes, and specifically whether they measure anything. "Participants will gain confidence" tells her you have not built an evaluation. "Seventy percent of participants will complete all eight sessions, measured by attendance" tells her you have. She is not judging whether the target is ambitious. She is judging whether you would know if you failed.

Fourth, the budget, looking for one thing. Whether it reconciles with the narrative. If the narrative describes a full time coordinator and the budget has a line for twelve hours a week, she has found a seam, and a seam is the cheapest possible reason to decline. This is the single most common unforced error I see, and it is almost always because the budget and the narrative were written by different people on different days.

Fifth, and only fifth, your narrative. By this point she has a hypothesis about your organization and she is reading to confirm or break it. This is the part everyone spends their time on, and it is being read last, quickly, by someone who has already half decided.

Two practical consequences follow, and they are not what most people expect.

The first is that the attachments deserve more of your attention than the prose. Your board list, your financials, your evaluation plan, your organizational chart. These are read earlier, trusted more, and revised less often than the narrative. Most organizations update the narrative every cycle and let the attachments go three years without a look.

The second is that your executive summary should be written last and should contain the answers to the four checks above. Not a summary of your narrative. The ratio, the governance, the measurable outcome, and the reconciliation, stated plainly in the first paragraph she reads. You are not summarizing. You are pre-answering the questions she is about to go looking for.

None of this means the writing does not matter. It means the writing is what decides between the applications that survive triage, and triage happens somewhere else entirely.