Forms for applications and collaborative work

When several people prepare an application, they need more than a list of fields: they need the current version, ownership and appropriate access to attachments. We design forms and collaborative workflows around the agreed requirements of the process.

Describe your application process

An application with a review stage
01 Scope02 Rationale03 Review
Draft application

Applicant
To be completed
Rationale
To be checked by the author

A completeness check is not a funding decision.

An example application: see what is ready and what needs checking.

Sections follow the application requirements

We organise questions, required fields and conditions for moving forward. We explain what users need to prepare and how to correct a missing or invalid answer. The tool can help collect material, but it does not automatically confirm its substantive quality or eligibility for funding.

Versions and collaborative roles

We agree who edits, who reviews and who can pass material to the next stage. History and statuses should identify the current state rather than create unlabelled copies. One person’s changes should not overwrite another’s approved work without an agreed rule.

Attachments with defined access

We establish document types, permissions, retention and transfer arrangements. We define which roles can view each attachment and test access, including after permissions change. Do not send a private application or participant documents with an initial enquiry.

Completeness before handover

Validation can identify an empty field or an unmet condition. A person checks facts, reasoning and requirements that a simple rule cannot assess. A “complete” message should state what was checked rather than imply approval by the organisation running the application process.

Export and acceptance

We agree the export format, included data and the person responsible for handover. You receive a form structure, roles, configuration within scope, guidance and acceptance scenarios. Prepare the process requirements, document classes, access and retention rules, and an approver.

We check access only to authorised data, change history, versions, validation, export and handover between roles. A completed prototype remains described as a prototype until the agreed implementation has passed acceptance.

Demonstration example: a section for review

In fictional material, “Section A” describes a task. The “Editor” role adds content and the “Reviewer” identifies a missing rationale. After revision, the material can proceed to the agreed checks. This is an invented example without programme or organisation names, private documents or an active submission function.

The form supports preparing and handing over information. It does not guarantee funding, application acceptance or legal compliance. Responsibility for the content and final submission follows the agreed process.

Next step

Describe the preparation stages and team roles. Start with a description rather than a private application or attachments.

Describe your application process

Have a quick question? Get in touch.