The Weekly Bellows: Before You Ask for One More Thing

Read the episode.

October 28, 2026

Tessa has an envelope of documents under her arm and a shift that starts in forty minutes. She has read the message from the college twice. It asks for more information, but she still cannot tell which pages she needs to copy.

“Before I leave work early tomorrow,” she asks, “can somebody tell me which of these you actually need?”

Omar, an aid colleague, pulls up the message template. A familiar paragraph is doing more work than it should. It lists several possible documents in a way that makes them all sound required. The message went out before anyone translated the request into the particulars of Tessa’s case.

Across the hall, Beth is reviewing a different sentence. This one appears in a draft program page. It says graduates can expect strong earnings. She wants to know whose earnings, measured when, and what happened to the people who are missing from the underlying data.

Tessa, Omar, and Beth are fictional people at an unnamed college. Their morning gives us a practical way into this week’s Weekly Bellows: before asking a student for another document, or asking them to trust another value claim, check what the words actually support.

Read the annual guidance carefully

Federal Student Aid’s October 26 guidance covers verification for the 2027–28 award year. It continues existing requirements and reminders; its separate real-time fraud tool adds no verification-document requirements. Aid verification and fraud resolution remain separate processes.¹

For the local review, aid staff should also check any separate fraud-resolution requirements before explaining next steps. This general summary cannot establish whether a particular application is ready for aid.

The October 23 Federal Register notice makes the assigned tracking group relevant to what must be verified. Unedited IRS-transferred information generally needs no further verification; manually entered rollovers remain an exception. Individual cases still require an aid professional’s review.²

Those distinctions matter when an office turns guidance into a message. A long checklist can feel reassuring to its author because it appears to cover every possibility. The person receiving it may read it as a set of instructions that all apply right now.

In the aid office, Omar stops the next generic message before it goes out. He does not promise Tessa an award or decide from a glance at her envelope that her file is complete. He checks the applicable requirement and the status of her case in the approved system. He also checks whether the wording in the message matches the action the office needs from her.

A template is a pattern; the fit still needs checking before the cut. Removing a sentence because it sounds inconvenient would be careless. Keeping a sentence because the template has always included it can be careless, too. The responsible colleague needs enough context to decide whether the request belongs here.

Give each request a reason

The reviews that follow are suggested local practices, separate from the federal requirements. Choose one message your office already sends and review it together. Bring the aid colleague who owns the requirement and the person who maintains the message. Use a fictional example for the discussion, rather than putting a real student’s record into a shared presentation.

Start with the condition that triggers the request. Write that condition in plain language for the reviewers. Add the current source and its version or publication date. Then read the student-facing sentence aloud. Can a reader tell what they need to do, how to do it securely, and whom to contact if their situation does not fit?

Leave an unresolved question visibly unresolved. If nobody in the room can explain why a document is being requested, assign the question to the appropriate reviewer before changing the workflow. A confident rewrite cannot supply a missing policy determination.

Omar finds that the template’s broad list is only part of the review. For a Slate or other CRM team, inspect the condition that selects the message as well as the words inside it. A corrected template can still reach someone whose case no longer needs that request. Test with fictional records in an approved environment, and let the aid owner approve the rule.

There is a privacy check here as well. Keep real documents and case notes in approved institutional systems. A useful worksheet records the question and the responsible role; it does not need a student’s tax information, identification image, or personal account details.

Give the value claim the same care

Beth’s program-page question belongs beside Omar’s template review. Both are about asking a person to act on a sentence. In one case, the action might mean arranging time away from work. In the other, it might mean deciding whether a program deserves a closer look.

An October 26 article from the Institute for Higher Education Policy recaps an October 6 webinar with state leaders. It discusses looking beyond median earnings, considering student costs, choosing manageable questions, and building staff and data capacity. It reports practices and perspectives rather than a new evaluation of outcomes.³

Start with one public-facing value claim and put its supporting evidence next to it. Give the review a manageable scope so the team can finish it. A question about a single sentence may be enough for the first meeting.

Ask who appears in the reported population. A statement about completers needs to remain a statement about completers. Check the period when earnings were observed and the geographic coverage of the data. Make a note of people whose outcomes are unavailable. If the claim discusses affordability, ask what student costs are included and which costs remain outside the measure.

Then ask the communications owner to read the sentence without the chart or the explanatory notes beside it. Would a prospective student reasonably hear a personal promise? If so, the sentence needs more work, even when the underlying number is accurately copied.

Beth does not invent a stronger number to rescue the draft. She marks the population question as open and sends it to the analyst responsible for the source. The page owner keeps the unsupported wording out of the next revision while that question is answered. The goal is a claim the team can explain, including its limits.

Finish with a usable next step

This week’s worksheet gives each review a place to start. One page follows a document request. The other follows a value claim. Both ask for an owner, the source version, the condition or scope, the words the student sees, an unresolved question, and a review date. Those are suggested working fields, not a new compliance form.

Keep the first review small enough to finish. Choose a message that is already in use or a claim that is waiting for approval. Record what changed and who can approve it. If the evidence is incomplete, record what must be checked before the wording moves forward.

Tessa asks when she should expect an answer. Omar agrees to call after her shift. He records the open question and the next contact in the approved system, then reads back what he will check. The review is still open, but Tessa knows who is following it and when they will speak again.

Tessa slides the envelope into her small rust-colored backpack. “After five?” she asks. “After five,” Omar says. She heads for work.

References

1. Federal Student Aid. “2027–28 Award Year FAFSA® Information To Be Verified and Acceptable Documentation.” Dear Colleague Letter GEN–26–06. October 26, 2026. Read source

2. U.S. Department of Education, Office of Postsecondary Education. “Free Application for Federal Student Aid (FAFSA®) Information To Be Verified for the 2027–2028 Award Year.” Federal Register 91(204), pages 66836–66839, document 2026–21678. October 23, 2026. Read source

3. Bell, Lauren. “Five Lessons from State Leaders Leveraging Data to Improve Postsecondary Value.” Institute for Higher Education Policy. October 26, 2026. Read source