A document vault that behaves like part of the grant workflow.
Files are shown as versions, not isolated uploads. The point is to keep the funder record, the AI extraction step, and the compliance trail on the same page.
Ready for AI review and grant assembly
Awaiting human confirmation before lock
Canonical files with version history
Most core documents are parsed and attached to grant records.
Canonical files protected after review and approval.
Documents waiting for final compliance confirmation.
Document vault
Files are tracked with version history, linked to grants, and surfaced with a review status.
| Document | Grant | Status | Updated |
|---|---|---|---|
PDF RFP-2026-0847.pdf Award notice and deadlines extracted. | Housing Stability Grant | parsed v1 | March 30, 2026 |
DOC Budget_Narrative_v3.docx Locked after extraction review. | Youth STEM Program | locked v3 | March 28, 2026 |
XLS Q4_Financial_Report.xlsx Shared with finance and program leads. | Community Health Initiative | shared v1 | March 27, 2026 |
DOC Evaluation_Framework.docx Needs a final compliance pass. | Environmental Justice Fund | needs review v2 | March 24, 2026 |
PDF Strategic_Plan_2024-2026.pdf Canonical source document for proposal framing. | Arts & Culture Endowment | locked v2 | March 20, 2026 |
XLS Impact_Report_Year1.xlsx Outcomes table ready for report assembly. | Food Security Network | parsed v1 | March 18, 2026 |
Readiness checklist
These cues mirror the live product: parse, confirm, lock, and share.
Versioned files stay in the vault once the extraction review is approved.
Award letters, reports, and budgets can be indexed before handoff.
Human sign-off keeps the demo aligned with the real product flow.
The vault should feel like a working archive, not a flat upload table. This interaction mirrors the live portal by making versions and related evidence feel physically connected.