To export submission data for a single project, open the project card on the Projects page, click the three-dot menu, then Export Submissions. Choose Received submissions only to download completed submissions, or All submissions to include drafts as well. Dapple emails you a link to download the CSV once the export is ready. In the file, the Submitted At column tells drafts apart from completed submissions — rows with no timestamp there are still in draft. Exporting drafts lets you see how far creators have got and estimate unconverted volume on a project.
How do I export submissions for a project?
Export submissions from the project's More menu on the Projects page:
Go to the Projects page and find the project you want to export.
Click the three-dot (More) menu on the project card.
Click Export Submissions.
Choose Received submissions only or All submissions.
Dapple emails you a link to download the CSV once the file is ready.
What's the difference between "Received submissions only" and "All submissions"?
Both options export a CSV of submission data for that project, but they cover different sets of rows:
Option | What it includes | Best for |
Received submissions only | Completed, submitted entries | Reporting on finished submissions |
All submissions | Completed entries plus submissions still in draft | Gauging total volume and following up with creators mid-application |
How do I tell which rows are drafts in the exported CSV?
Check the Submitted At column. Every completed submission has a timestamp in this column. Draft submissions don't — the cell is empty because the creator hasn't submitted yet. Filter or sort the CSV by Submitted At to separate the two groups: rows with a timestamp are completed submissions, rows without one are still in draft. The Created At and Updated At columns stay populated for drafts, so you can also see when a draft was started and when it was last touched.
Why would I export draft submissions?
Exporting All submissions gives you visibility into activity that hasn't converted into a completed submission yet. This is useful for:
Gauging the potential volume of unconverted activity on a project — how many creators have started but not finished.
Seeing who has begun an application, even if they haven't submitted it.
Checking which fields a draft has filled in, so you can tell how far along a creator is.
Following up directly with creators who are close to finishing but have stalled.
Exporting and then importing into a CRM or email marketing tool to send them a nudge to complete. This can also be done through Dapple using Draft Reminders.
Best practice
Export All submissions periodically on high-volume projects to catch stalled drafts before the deadline.
Sort by Updated At to find drafts that have gone quiet, rather than ones still in active progress.
Cross-reference the Organisation ID and Team ID columns if you manage submissions across multiple teams.
Re-export closer to the deadline for the most current picture of who's still completing their application.