A Project in Dapple is one opportunity end-to-end. It's the submission form, the stages submissions flow through, the review panel, the payments, the messaging. Every open call, award, residency, grant, or contest you run is its own Project. You can run as many in parallel as you need, and each project keeps its own analytics, settings, and pipeline.
When should I use one project vs many?
Use one project when… | Use multiple projects when… |
You're running a single open call or opportunity with one form and one pipeline. | You have sub section of a programme where you need separate analytics, review panels, and stages. |
You want a single set of stages, automations, and review settings. | You're running multiple programmes simultaneously (e.g. a residency and a grant) with different forms and rules. |
You only need one submission form for the entire opportunity. | You're collecting CVs, demos, and entries for different things — each needs its own form, stages, and reviewers. |
What can I configure inside a project?
Submission form — fields, file uploads, payments, conditional logic.
Stages — the pipeline submissions move through (e.g. New → Longlist → Shortlist → Selected).
Review Panels — who reviews submissions, with what scoring and voting.
Automations — actions that fire when submissions enter a stage (send a message, assign a user, request feedback).
Payments — submission fees, optional add-ons, tip jars, or donations.
Visibility — Draft, Private (link-only), or Public.
Availability — Anytime, Closed, or Between specific dates.
How are starter projects created?
When you first create an Organisation in Dapple, we look at the primary industry you select and auto-create a small set of starter projects to get you going. These are templates — edit them, duplicate them, or delete them and start from scratch. New Projects can also be created from the dashboard at any time using New Project and you can look through the library of templates.
Where to go next