Create grant application — submit project description and budget

Before an applicant invests three hours in a detailed application, it should be quickly clarified whether the project even fits the funding line. Therefore build a short eligibility check at the beginning. Three to five questions usually suffice: Who is the applicant (association, company, private person)? In which state or country does the project take place? Which topic group is addressed (culture, education, social)? Which funding amount is requested?

The calculation engine evaluates the answers against the funding criteria and gives the user an honest assessment immediately. Anyone not eligible receives a friendly explanation with a reference to alternative programs. This saves applicants and funding administration hours of manual review. Mark the eligibility check explicitly as non-binding — final eligibility is decided only by the jury based on the complete application. However, this pre-check already filters out 30 to 50 percent of unsuitable applications without anyone losing much time.

A grant application rarely consists only of the application form. Project plan, budget plan, association statutes, exemption certificate, CVs of key people — the attachments can quickly comprise a dozen files. Define a separate upload field per attachment with clear designation, accepted file formats and maximum file size. A typical mix: PDF and DOCX up to 10 MB per file, a total of maximum 50 MB.

Formulate the requirements explicitly. "Please upload the budget as a completed Excel template" with a link to the template saves a lot of follow-up work later. Anyone uploading an unsuitable file should receive a clear error message immediately. Store the attachments encrypted and label them with application ID and document type in the file name — this makes later review by the jury much easier. After the end of the application period, all attachments of unapproved applications should be deleted promptly to comply with GDPR storage limitation.

Grant applications regularly contain personal data — applicants, project team, donors, beneficiaries. For social or educational projects, particularly sensitive information about the target group (children, refugees, disabled people) is often added. Stick to data minimization: collect only what is actually needed for the assessment and work where possible with aggregated information instead of individual data on beneficiaries.

Document the legal basis per processing purpose. For the grant assessment itself, Art. 6 (1) (b) GDPR (contract) usually applies; for any publications about funded projects, a separate consent of the applicant is needed. Build this in as a separate checkbox, with a clear note on the scope of publication. Store all applications in the EU, control access strictly and delete rejected applications after three to six months. Approved applications are usually subject to a longer retention obligation for use proofs — typically ten years after project end.

After submission, the actual funding process begins. Structure it into clear phases: receipt confirmation, formal completeness check, technical evaluation by jury or expert, approval notice. Trigger automatic status updates per phase to the applicant — this transparency massively reduces follow-up emails. But avoid promises about concrete processing times that you cannot keep; a rough range ("evaluation usually takes 8 to 12 weeks") is more honest than a fixed date.

The evaluation itself runs best via an internal tool that shows all applications in a list and records evaluations per jury member. Anyone without their own software for this gets far with a shared spreadsheet into which the data flows automatically via webhook. Approved applications receive a notice with conditions, rejected ones a factual reasoning — both should be formulated friendly and comprehensibly. Anyone who was rejected and reacts with good arguments is often invited to the next funding round, strengthening the community around the funder. Store the evaluation as an audit trail so that you can trace the decision path in case of queries.