Organise the common evidence used in funding applications.
On this guide Browse sections
The wrong way to manage funding documents is to create a new folder from scratch for every application.
The better system is:
Master evidence library → funder-specific checklist → controlled submission pack
Funding documents checklist: the practical answers
Short answer: Keep one master library of the documents funders ask for again and again: registration and governing documents, tax and other registrations, audited accounts, bank proof, policies, and evidence of past projects. Track each document’s validity, refresh the set every year and whenever something changes, and build a separate controlled pack for each funder from that library. Never edit an official certificate. Use the grant application checklist for the final review of one application.
- Who this page is for
- NGO staff who maintain the standing evidence that every grant, CSR or Government application draws on.
- Who should go elsewhere
- About to submit one application? Use the grant application checklist. Answering a funder’s due-diligence questions? Use the due-diligence checklist. Still registering the NGO? See documents for NGO registration.
- What to keep current
- A validity register with each document’s issue date, validity, renewal owner and source, as in the validity register section below, plus the current versions of policies and audited accounts.
- Common mistakes
- Sending the wrong year’s audit, an expired registration, different organisation names across files, or a large unindexed ZIP with sensitive records.
Useful next links
- Grant application checklist – the final review for one application.
- Due-diligence checklist.
- Documents required for NGO registration.
- Complete NGO Documentation Toolkit.
- NGO Finance and Audit Readiness Pack.
- 12A/80G registration.
By Vekho P. Ringa, Editor. Last verified 22 Oct 2026. Sources: funders’ own document lists, which always prevail. General information only, not legal advice.
1. Master evidence library
Create folders:
- Entity
- Governance
- Tax / Registrations
- Finance
- Bank
- Policies
- Project Experience
- Programme Team
- Project Design
- Budget
- Monitoring
- Infrastructure / Assets where relevant
2. Entity documents
Possible:
- certificate;
- governing instrument;
- amendments;
- PAN;
- registered office;
- organisation profile.
3. Governance
Possible:
- current governing body;
- appointment/election evidence;
- resolution authorising signatory;
- conflict policy;
- key governance records.
4. Registrations
Possible:
- Darpan;
- tax orders;
- CSR-1;
- FCRA;
- GST/TDS or other, where applicable.
Do not include every registration automatically.
If a funder asks for tax approvals your NGO does not hold yet, our page on 12A and 80G registration explains the application route.
5. Financial records
Possible:
- audited statements;
- audit report;
- annual report;
- management accounts;
- grant schedule;
- donor schedule;
- asset schedule;
- advance ageing.
6. Bank evidence
Possible:
- cancelled cheque;
- bank certificate;
- account confirmation.
Never share passwords or OTPs.
7. Policies
Possible:
- finance;
- procurement;
- conflict;
- HR;
- safeguarding;
- grievance;
- data/privacy;
- whistleblowing.
8. Project experience
Prepare 2–3 project sheets.
Fields:
- project title;
- funder;
- period;
- geography;
- budget;
- target group;
- activities;
- outputs;
- outcomes;
- evidence;
- contact/reference where appropriate.
9. Project design
Prepare:
- concept note;
- proposal;
- needs assessment;
- geography;
- beneficiary selection;
- work plan;
- risk;
- sustainability.
10. Budget
Prepare:
- detailed budget;
- narrative;
- assumptions;
- cash flow;
- co-funding;
- quotations where required.
11. Monitoring
Possible:
- logframe;
- indicator matrix;
- data collection plan;
- baseline;
- previous project report.
12. Team documents
Where requested:
- CVs;
- role descriptions;
- organisation chart;
- staffing plan.
Do not collect/share identity records unless necessary.
13. Infrastructure evidence
Possible:
- land/occupancy;
- owner consent;
- estimate;
- drawing;
- permission;
- asset plan.
14. Submission pack
Build a separate folder for each funder:
Funder - Programme - Date
01 Application Form
02 Proposal
03 Budget
04 Entity
05 Finance
06 Registrations
07 Policies
08 Experience
09 Other Requested15. Submission index
| Requested Item | File | Version | Ready | Notes |
|---|
16. File naming
Use:
NGOName_AuditedStatements_FY2025-26.pdf
Not:
scanfinal2new.pdf
17. Validity register
Track:
- document;
- issue date;
- validity;
- renewal;
- owner;
- source;
- updated file.
18. Do not alter official documents
If:
- old address;
- old name;
- historical governing body;
explain with supporting current evidence.
Do not edit certificates.
19. Common mistakes
- Wrong year audit.
- Expired registration.
- Different NGO name across files.
- Huge ZIP with irrelevant documents.
- Sensitive records shared too early.
- Budget/proposal mismatch.
- Partner letter fabricated.
- Project report copied.
- No submission index.
20. Build a document control register
Recommended fields:
| ID | Document | Version | Date | Valid to | Owner | Location | Access | Notes |
|---|
This makes it easier to identify outdated files before submission.
21. Annual refresh cycle
At the start of each financial year or after audit:
Update:
- latest audit;
- annual report;
- governing body;
- organisation profile;
- registration status;
- bank evidence;
- policy register;
- project experience;
- current staff chart.
22. Event-driven update
Refresh immediately after:
- address change;
- governing-body change;
- bank signatory change;
- registration renewal;
- FCRA/tax/CSR status change;
- major policy adoption;
- audit qualification;
- new major project.
23. Funder-specific pack
Never send the full master library.
Build a pack using only the requested items.
Example:
CSR-ABC-2026
01_Application.pdf
02_Project_Proposal.pdf
03_Budget.xlsx
04_Registration.pdf
05_CSR1.pdf
06_Tax_Order.pdf
07_Audit_2025-26.pdf
08_Annual_Report_2025-26.pdf
09_Bank_Proof.pdf
10_Project_Experience.pdf24. Sensitive information protocol
Mark:
- identity document;
- bank;
- personal tax ID;
- employee record;
- beneficiary data;
- property/title;
as restricted where appropriate.
Use secure transfer.
25. Submission version
Once submitted:
- freeze submitted pack;
- save exact version;
- do not overwrite;
- create a new revision if funder requests changes.
26. Cross-check against application
If the application says:
- 12 staff;
- 8 years experience;
- 5 districts;
- ₹40 lakh turnover;
the evidence should support those statements.
27. Historical documents
Keep old versions separately.
Historical audit or previous registration can be important.
Do not delete old documents simply because newer versions exist.
28. Translation
Where a funder requires English but source documents are in another language, use appropriate translation/certification where required.
Do not alter the original.
29. Document quality
Before sending:
- readable;
- complete pages;
- correct orientation;
- reasonable file size;
- no password unless agreed;
- clear filename;
- correct year.
30. Funding documents are evidence, not decoration
A polished proposal cannot compensate for inconsistent underlying records.
The evidence library should be maintained as part of ordinary NGO administration.
Funding documents: common questions
What documents does an NGO need for funding applications?
Usually the registration certificate and governing document, PAN, the tax and other registrations that apply, recent audited accounts, bank proof, key policies and evidence of past work. Each funder’s own list decides.
How do we keep funding documents up to date?
Keep a validity register, refresh the library every year, and update it whenever the address, name, governing body, registrations or accounts change.
Should we send every document with every application?
No. Build a funder-specific pack from the master library with only what that funder asks for, and add an index.
Can we correct an old address on a certificate?
No. Do not edit official documents. Attach current supporting evidence and explain the change instead.
How is this different from a grant application checklist?
This page maintains the standing document library. The grant application checklist is the final review of one application before it is submitted.
NGOGrant boundary
The funder’s current checklist controls. NGOGrant can help maintain the reusable evidence library and produce a clean funder-specific submission pack. General information only, not legal advice.
Practical next steps
Continue with the related task or checklist that fits your organisation. Verify current official requirements before submitting anything.