Case Study 2 — RYCC Navigates a Foundation Portal's Surprises
Composite, for teaching. RYCC and the Hartwell Foundation are illustrative.
The Situation
Denise Okafor has written RYCC's full proposal for the Hartwell Foundation and assumes submission will be simple — upload the document, click submit. This chapter warns that foundation portals are full of surprises, and that "the writing is done" is not the same as "ready to submit."
Applying the Chapter
She opens the portal early — and finds surprises. Days before the deadline, Denise logs into Hartwell's online application system to see exactly what it wants. Good thing: the portal doesn't accept her two-page narrative as an upload; instead it has a series of fields, several with character limits (a 2,500-character "statement of need," a 4,000-character "program description"). Her carefully written narrative is too long for the fields. Had she discovered this on deadline day, she'd have had no time to adapt.
She drafts to the portal's actual constraints. Denise condenses her need and program sections to fit the character limits — preserving the so-what chain and the specifics, cutting to the field's actual length (the "earn its place" discipline, Chapter 5). She writes everything in her own document first and pastes into the portal, never composing directly in a web form that might time out and lose her work.
She inventories the attachments. The portal requires the budget, the IRS determination letter, the board list, the most recent audited financials, and the commitment letters from the three schools. Denise gathered the slow ones (audited financials, from her bookkeeper) early (Chapters 4 and 13), so all are ready. She uploads each, checking format.
She runs her checklist and submits early. Her checklist — built from Hartwell's guidelines and the portal's actual fields — confirms every field is complete, every attachment uploaded, no leftover placeholders, the budget totals matching. She submits two days early, receives the portal's confirmation, and saves a copy of everything.
The Trap She Avoids
Had Denise treated "the writing is done" as "ready to submit" and opened the portal on deadline day, she'd have discovered the character-limited fields with no time to adapt her narrative, possibly missed a required attachment, and risked the portal timing out mid-entry. Instead, by getting into the portal early and treating submission as its own task, she submitted calmly and completely.
The Payoff
RYCC's proposal lands in Hartwell's system complete, within every field limit, with all attachments — ready to be read. Denise learned that a foundation portal is not a formality but a distinct task with its own surprises, and that the final mile deserves real time even for a "simple" foundation application.
Discussion Questions
- Denise's narrative didn't fit the portal's character-limited fields. Why is discovering this early so important, and what would have happened on deadline day?
- Why does she draft in her own document and paste into the portal, rather than composing directly in the web form?
- Compare RYCC's foundation submission to Hernandez's federal one (Case Study 1). What's identical in discipline (early registration/portal check, attachments, checklist, submit early), and what differs (federal routing/AOR vs. foundation portal)?