Digitising a foundation's grant process: a six-step guide

Many Finnish foundations still run their grant calls with email, Excel sheets and paper printouts. It works until application volumes grow, data protection requirements tighten, or the administrator changes and the tacit knowledge walks out the door. This guide goes through the grant process step by step and shows what digitising each step means in practice.

The guide is written from the perspective of a foundation’s administrator and board. It also works as a checklist when you compare systems. Every step described below is a point to verify before you sign a contract.

Why should a foundation digitise its grant process?

The same three reasons come up whenever we talk to foundations:

• Workload. Collecting applications from email, chasing attachments and moving data between spreadsheets eats weeks every year.
• Data protection. Grant applications contain personal data and often sensitive plans. A mailbox and shared files are not a controlled environment from a GDPR perspective.
• Continuity and transparency. When the process lives in one person’s inbox, the foundation is vulnerable. In a system, applications, evaluations and decisions stay in one place, and the board sees the whole picture.

Step 1: How is a grant call opened in an electronic system?

A digitised call starts by defining the round: name, application period, instructions and the application form. In a good system the administrator builds the form without programming. Fields, attachment requests and mandatory values follow the foundation’s own needs.

In AAPU, several calls can run in parallel, and last year’s call can be copied as the base for a new one. The form is published as a link on the foundation’s own website, and applicants never create an account. That keeps the barrier to applying low and support requests rare.

What about the applicant’s experience?

Digitisation changes the applicant’s experience as much as the foundation’s workload. A clear form states up front which details and attachments are needed, and the applicant receives a confirmation of a successful submission. A researcher or artist completes the form in half an hour without separate usernames and passwords.

This is worth checking when you choose a system. If applicants first have to register, confirm their email and remember a password next year, some of them give up, and the foundation’s support inbox fills with password reset requests just before the deadline.

Step 2: What changes when applications are received electronically?

When applications arrive in the system, every application has the same shape: the same fields, the same attachments, the same numbering. Nobody stitches PDF attachments together from email threads or asks for missing information afterwards, because the form requires the mandatory data at submission time.

The applicant receives a confirmation, and the foundation sees in real time how many applications have arrived. When the call closes, the material is already assembled. There is no separate collation step.

The data protection gain is concrete. Personal data no longer circulates in mailboxes and attachments. It stays in one controlled environment, where access is restricted by role and retention periods are managed centrally. The foundation can also answer a data subject’s access request in minutes when all of an applicant’s data is in one place.

Step 3: How do evaluation and committee meetings work?

In the evaluation phase, applications are distributed to reviewers or a committee. In an electronic process, reviewers read applications directly in the system and record their assessments in the same place, with no email attachments and no version chaos.

In AAPU, applications can be scored, commented on and filtered. A conflicted reviewer is bypassed for the individual application, and the conflict remains visible for the minutes. For the meeting, the system produces a summary where applications and assessments sit side by side, and the committee can discuss applications inside the system instead of scattering comments across email threads.

Foundations usually feel the biggest change here. An evaluation round that used to mean mailing attachments and preparing a summary meeting now starts with one share and proceeds at the reviewers’ own pace.

Step 4: Decisions and notifying applicants

In the decision phase, awards and rejections are recorded in the system and notifications go out to applicants centrally. Successful applicants can be asked for additional details, such as a bank account number for payment, through a secure form instead of email.

Contracts and commitments are signed electronically in the system with strong authentication. The applicant’s identity is verified in the same step, and nobody scans and archives signed paper by hand. The annual fee includes 100 electronically signed documents, and each document beyond that costs €2. There are no other per-item fees in the process.

Rejections are easier to communicate too. When the message goes out to everyone at once, nobody is left waiting for an answer.

Step 5: Payments without manual work

In the payment phase, the system produces a payment file with recipients’ details, account numbers and instalments. Grants paid in instalments and payment preconditions (an interim report, for example) stay under control when they are recorded in the system rather than on sticky notes.

The payment file reconciles with the decisions, so it is easy to verify afterwards what was paid, to whom and when. The auditor gets an unbroken, documented chain from award to payment in one place.

Step 6: Reporting, monitoring and statutory notifications

The grant process does not end at payment. The foundation needs to monitor how grants are used, collect final reports and handle statutory notifications: annual notices to the tax authority and notifications of working grants to Mela.

With the full history in one system, reports take seconds: awarded amounts by field, applicant volume trends, committee workloads. The same data serves the annual report and board meetings.

Many foundations realise at this point how much information has accumulated in old rounds. When previous years’ applications and decisions are searchable, evaluating new applications can lean on history: has the same applicant received a grant before, how was the previous project reported, what was the amount awarded. Digging that out of a paper archive usually never happened.

Where to start?

Digitisation does not require an IT project from the foundation, and it does not have to happen all at once. Some foundations start with just the application form and extend to evaluation and payments the following year. Others move the whole process into the system right away. In practice the transition goes like this:

1. Mapping. We review the foundation’s current process and forms.
2. Onboarding. The system is configured to match the foundation’s process and the forms are built ready to use. In AAPU this is included in the setup fee, and onboarding typically takes a few weeks.
3. First call. The first application round runs on the new system, with support where needed.

The fate of old materials is a common concern. Not all history needs to be migrated. For many foundations it is enough that new rounds start in the system while the old archive stays as a reference. If earlier years’ awards need to come along, for applicant history for example, the migration is planned as part of onboarding.

The most important thing is to start early. If the spring call is meant to run on the new system, start onboarding the previous autumn. That leaves a calm schedule for building the forms, testing and familiarising the committee.

AAPU is developed and supported in Finland and built for the grant processes of foundations. If you would like to see what your own process would look like in the system, book a free demo and we will walk through it with your own material.