THE WEEKLY BELLOWS /
The Weekly Bellows: Before the Next File Arrives (11/11/26)
A software version, a new sender address, and an accountability list can each prompt a different question in a financial aid office. This edition follows an explicitly fictional campus team as it prepares for three Federal Student Aid updates: the December 7 SAIG software preparation deadline, changing email senders, and the first chapter of the NSLDS Earnings Accountability User Guide. A dated Veterans Day service note distinguishes the November 11 processing schedule from local problems.

Listen & watch.
Read the episode.
The Innovation Forge Article edition for November 11, 2026
Three Federal Student Aid updates give campus teams useful work to do before December. The work begins with a software version, moves through an inbox, and ends with knowing how to review an accountability list when it arrives.
The campus and people in the following scenes are fictional. Lower Midwest Directional is a Forge institution; Nora, Amal, Lou, and Eli are new illustrative characters. These scenes do not describe a real institution, student record, or aid delay.
Nora has claimed the end of the conference table closest to the outlet. Her laptop is charging. Her coffee is doing the opposite. Beside it sit three federal notices that she would very much like to understand before the office gets busy.
At our fictional Lower Midwest Directional, Nora works in financial aid. Amal from IT has brought a laptop and the expression of someone who has been invited to a meeting described as “probably five minutes.” Lou from the registrar's office brings a pencil. They are waiting for a colleague from institutional research.
“What are we trying to finish?” Amal asks.
Nora turns over the first notice. “I want us to know what we have checked before we tell somebody everything is fine.”
That seems a reasonable use of a morning. It also describes the opportunity in three recent Federal Student Aid updates. Each asks a different kind of attention from the institution. Reading them together gives the people responsible for student aid operations a practical November agenda, provided we keep their dates and limits straight.
Check the software that is actually running
On November 6, Federal Student Aid told Student Aid Internet Gateway users to upgrade to EDconnect 8.6.1 or TDClient 3.5.0, as applicable, by December 7, 2026. FSA plans an infrastructure upgrade in early 2027. Older software versions will lose access, but the announcement does not identify December 7 as the shutdown date. It is the preparation deadline. Users already running the specified current version need no further action under this notice.¹
There is enough specificity there to act without inventing a crisis. Find the software your institution actually uses. Verify the deployed version. If an upgrade is needed, identify who can perform it and how the institution will confirm it works.
The operating system belongs in that conversation. EDconnect 8.6.1 requires Windows 11 or Windows Server 2016 or later. TDClient has its own platform requirements, which need to be checked against the relevant documentation. An instruction for one product should not quietly become an assumption about the other.¹
Amal points to the version number on Nora's page.
“Is this what we downloaded, or what is running?”
Nora looks at the note she had written beside it. “That is an excellent and slightly irritating question.”
It is also a useful question to ask before December. A download, an installation request, and a verified deployment describe different stages of work. Our recommendation is for financial aid and IT to record the installed version, the responsible person, any needed platform work, and the result of an approved test. Those are practical local checks, not extra federal requirements announced here.
An already current installation may make this a very short conversation. An older installation may need coordination. Either way, the point is to leave with a known answer. Nobody needs to weaken a security control or improvise an unsupported workaround to make a checklist look finished.
Recognize the new sender without trusting the display alone
The second notice concerns something students and staff may actually see: a different email sender address.
FSA announced on November 5 that, during this fall, messages from noreply@studentaid.gov are moving to three addresses: noreply@login.studentaid.gov, noreply@mail.studentaid.gov, and noreply@info.studentaid.gov. Beginning in 2027, partner communications will use noreply@info.nsldsfap.ed.gov, noreply@mail.nsldsfap.ed.gov, noreply@info.fsapartners.ed.gov, and noreply@mail.fsapartners.ed.gov.²
Those dates matter. The student-facing transition is described as happening this fall. The partner addresses are identified for 2027. Combining them into a single “everything changes now” message would make the office's explanation less accurate.
Nora imagines Eli, a returning student who has an appointment later in our fictional week, holding up a phone. The question is easy to hear: “This looks different. Is it really them?”
A list of authorized addresses helps staff recognize the change. The displayed From address alone does not authenticate an email, however. FSA's notice also points readers toward its guidance on avoiding scams.² A sensible response to a suspicious message is to open the known official service independently, rather than follow a questionable link, and involve the institution's IT or security team when needed.
That means the local preparation has two parts. Staff need an accurate explanation of the changed addresses, and they need to preserve the habit of checking a message safely. A blanket exemption from email filtering would not follow from this announcement.
“Could we put the notice where the people answering phones will find it?” Lou asks.
They can. Nora adds a link to the official announcement in their staff reference material. Amal offers to review the routing question through the normal security process. They resist turning a change in correspondence into a rule that every message bearing a familiar-looking label should be trusted.
For Eli, the useful answer will be brief: some official sender addresses are changing, and the office can help him check without asking him to gamble on a link.
Learn the review routes before the list arrives
The third item deserves a slower read. On November 4, FSA released the first chapter of the National Student Loan Data System (NSLDS) Earnings Accountability User Guide, covering the Completers List. Additional chapters on reporting and calculations are to follow. This is implementation guidance, not a study reporting institutional outcomes.³
The list draws on NSLDS enrollment and Title IV data for applicable completers. It is not simply a roster of every person who graduated. The guide describes aggregation toward 30 non-excluded completers, expanding award years and, when needed, grouping by Classification of Instructional Programs codes. A Completed CIP and an Evaluated CIP can differ.³ ⁴
That distinction is worth understanding before somebody sees a grouping they did not expect and announces that the data must be wrong. The guide provides a reason to investigate the construction of the list carefully. It does not establish that any particular institution has errors.
The review window also needs careful handling. The guide currently anticipates approximately 60 days, with the actual start and end dates set by the Department of Education. The release of this chapter does not announce that the window is open, and it does not establish one universal deadline that an office can safely paste onto its calendar.⁴
Lou moves the coffee cups away from the middle of the table.
“Let us make room for the part where we decide who knows what.”
This is where aid, the registrar, and institutional research can usefully work together. Our recommendation is to identify who will examine the relevant records, who understands the underlying enrollment reporting, and who can document the basis for a proposed action in the institution's approved systems. Each institution needs to fit that work to its own responsibilities and access controls.
The guide distinguishes correcting underlying enrollment data from exclusions or removals. Adding a missing student uses enrollment reporting. Re-adding a previously removed record through the web interface is a different operation. The buttons and routes do not all repair the same thing.⁴
Suppose our fictional team eventually encounters a record that calls for review. They will need to establish what the record shows and why an action is appropriate before choosing a route. For now, they can read the guide together and use a made-up training example to check their understanding. There is no need to put identifiable student information into a public worksheet, slide, or shared demonstration.
Nora draws a small square on the paper and writes “question” inside it. Lou writes “evidence” beside it. Their colleague from institutional research, now seated, asks where the answer will be saved so the next reviewer can understand it.
The meeting has become more useful. Nobody has promised that every future list will be perfect. They have started arranging a review that someone else will be able to follow.
Keep the holiday on the right date
One dated service note belongs beside these preparations. For Veterans Day on Wednesday, November 11, FSA says the FAFSA Processing System will accept data but will not process it or send Institutional Student Information Records until Thursday, November 12. FSA offices and contact centers are closed November 11, while websites remain operational.⁵
The Common Origination and Disbursement System is scheduled to accept and process school data and send responses and acknowledgments on November 11, but schools will receive no federal funds that day. Funding changes are to resume November 12. The services do not all follow the same pattern.⁵
This service note describes the announced schedule for November 11, with processing and funding changes to resume November 12. If you read this afterward, use it to interpret records and monitoring from November 11. An expected holiday processing gap should be labeled as such before someone treats it as evidence of a local failure. The notice alone does not tell us whether an individual institution experienced a separate problem.
Leave the next person an answer they can use
When Eli arrives in our fictional scene, he does not see the three notices. He sees Nora, an open chair, and a place to put his bag.
“If I get a message I don't recognize, should I bring it in?” he asks.
“You can ask us,” she says. “We can check it with you.”
For the real teams reading this edition, that preparation can be similarly concrete. Confirm the software version before December 7. Put the sender-address notice within reach of the people who explain it. Read the new guide with the colleagues who will help interpret and review the records. Keep announced service dates attached to the services they actually affect.
Then leave a short record of what was checked, what remains open, and who will do the next piece of work. When the next file or question arrives, the person answering it should not have to reconstruct the entire morning.
References
1. Federal Student Aid. November 6, 2026. “SAIG Users - Upgrade to EDconnect 8.6.1 and TDClient 3.5.0 Software by Dec. 7, 2026.” Electronic Announcement GENERAL-26-70. https://fsapartners.ed.gov/knowledge-center/library/electronic-announcements/2026-11-06/saig-users-upgrade-edconnect-861-and-tdclient-350-software-dec-7-2026
2. Federal Student Aid. November 5, 2026. “Update to Federal Student Aid Sender Email Addresses.” Electronic Announcement GENERAL-26-69. https://fsapartners.ed.gov/knowledge-center/library/electronic-announcements/2026-11-05/update-federal-student-aid-sender-email-addresses
3. Federal Student Aid. November 4, 2026. “NSLDS Earnings Accountability User Guide.” Publication page. https://fsapartners.ed.gov/knowledge-center/library/guides-worksheets/2026-11-04/nslds-earnings-accountability-user-guide
4. Federal Student Aid. November 2026. NSLDS Earnings Accountability User Guide, Chapter 1, Completers List. Printed pages 4 and 15–21 for scope, aggregation and anticipated review window; pages 20–21 and 32 for action routes. https://fsapartners.ed.gov/sites/default/files/2026-11/NSLDSEarningsAccountabilityUserGuideChapter1CompletersList.pdf
5. Federal Student Aid. November 4, 2026. “Veterans Day Federal Holiday Processing and Customer Service Hours.” Electronic Announcement GENERAL-26-68. https://fsapartners.ed.gov/knowledge-center/library/electronic-announcements/2026-11-04/veterans-day-federal-holiday-processing-and-customer-service-hours
From the workbench.
pdf / Version 1 / 102 KB
Student-aid readiness workshop — printable PDF
A practical worksheet for checking software readiness, explaining sender changes safely, and preparing for the NSLDS Completers List review.
Download Student-aid readiness workshop — printable PDF (pdf)docx / Version 1 / 41 KB
Student-aid readiness workshop — editable DOCX
An editable worksheet for documenting local readiness checks without including identifiable student records.
Download Student-aid readiness workshop — editable DOCX (docx)