Non-Profits Sharing Grant Proposals
Grant deadlines are firm. The hours spent reformatting proposals from Notion to Google Docs could be spent strengthening the narrative.
Grant submissions formatted and delivered ahead of deadlines.
The Deadline Problem
Grant writing has a particular kind of time pressure. The deadline is fixed. The program narrative needs to be compelling. The budget justification has to be airtight. And the final document needs to be in a format the review committee can actually use — which is almost never "a link to our Notion workspace."
Most funders expect Google Docs or PDFs. Some foundations have online portals, but they still require document uploads. The review committee prints submissions, distributes them at a table, and discusses them in person. A Notion page doesn't fit into that process.
For non-profit teams that draft in Notion — and many do, because it's a strong tool for collaborative writing on a budget — the last step before submission is a reformatting exercise. And it happens at exactly the wrong time: the final hours before a deadline, when the grant writer should be polishing the narrative, not fixing table borders.
When Formatting Competes With Content
Grant proposals are structurally complex. A typical submission includes:
- A program narrative (10–15 pages with section headings, subheadings, and extensive prose)
- A budget and budget justification (3–5 pages with detailed line-item tables, often nested by category)
- An organizational background (2–3 pages)
- Supporting documents (logic models, letters of support, evaluation plans)
The budget tables are the hardest part to reformat manually. Multi-level line items (e.g., Personnel → Full-time Staff → Program Director → Salary + Benefits) need precise indentation. Copy-pasting from Notion flattens this hierarchy. A grant writer can spend an hour rebuilding one budget table to get the nesting right.
Across 20 proposals per year at 3–4 hours of formatting each, that's 60–80 hours — the equivalent of two full work weeks spent on reformatting rather than writing. For a two-person grant writing team, that's a significant portion of capacity.
A Cleaner Submission Process
Kami converts Notion HTML exports to Google Docs. For grant proposals, the important elements are:
- Headings and section structure — carries over, which matters when funder guidelines specify a particular outline
- Budget tables — column structure and content preserve, though column widths may need manual adjustment for very wide tables
- Nested lists — sub-items and indentation maintain their levels
- Callout blocks — useful for "NOTE" or "IMPORTANT" sections that some proposals include
What doesn't convert: Notion databases, formula fields, and relation properties. If your budget is built as a Notion database with calculated totals, export it as a regular table before converting.
The process: finalize the proposal in Notion, export as HTML, upload to Kami, review the Google Doc. For a full proposal package (narrative + budget + appendices), batch-upload everything and get the complete set back.
What to Watch For
A few practical considerations specific to grant submissions:
Funder formatting requirements. Many foundations specify font size, margins, line spacing, and page limits. Kami produces a cleanly structured Google Doc, but it uses default formatting — you'll need to apply the funder's specific requirements in Google Docs after conversion. This is still faster than formatting from scratch, but it's not zero additional work.
Page counts. Notion pages don't have "pages" the way Google Docs does. A 15-page Notion document might be 12 or 18 pages in Google Docs depending on font size and margins. Check page count against funder limits after conversion and adjust before submitting.
Version control near deadlines. It's common to make last-minute content changes in Notion and re-convert. That's fine — but make sure you're replacing the right Google Doc and not accidentally submitting a stale version. Name your files clearly (e.g., "Smith Foundation — Program Narrative — FINAL") and delete intermediate versions.
Budget table precision. Always verify that numbers in the converted budget table match the Notion original. Kami preserves the text content, but a quick check that totals and line items are in the right cells is worth the 5 minutes, especially when grant amounts are on the line.
For grant writing teams
Keep a checklist of funder-specific formatting requirements (font, margins, page limits) alongside each grant in your Notion database. After converting with Kami, work through the checklist in Google Docs. This separates content work (Notion) from formatting compliance (Google Docs) and prevents last-minute scrambles.
Try converting a proposal draft with the demo to see how your formatting comes through. The free tier covers enough conversions for smaller organizations; larger teams with 20+ annual proposals may want to look at Pro. See the supported blocks reference for the full list of Notion elements that convert. For non-profits that also distribute internal policies to staff, the HR & People use case covers a related distribution workflow.
Ready to streamline your workflow?
Start converting for free — upgrade when you need more.