Survey responder
DitchCarbon accepts a customer emissions survey by email or upload and tracks it through to submission, answering from the data already held on the organisation's profile.
Forward the survey by email or upload the file, and it joins a tracked queue with the requester and status on each row. Answers come from what is already on your profile rather than from a blank form, so the work is reviewing rather than compiling.
Surveys arrive as attachments from a dozen different customers in a dozen different formats, and each one is answered in isolation. Nothing accumulates, so the tenth is as much work as the first.
Two ways in: forward the email, or upload the file. From there each survey is a row with the requester named and a status, moving through in progress, action required, completed or cancelled. What was submitted stays attached, so the next version of the same customer's survey starts from the last one.
Answers draw on the data already held on your profile, which is why the disclosure to-do list and context answers are worth doing first. The better the profile, the less of each survey is actually blank.
This one is experimental and being refined, so treat it as a real workflow that is still moving rather than a finished feature.
Common questions
No. It is marked experimental in the app and is being refined, so treat it as a real workflow that is still moving. The disclosure to-do list and context answers are worth completing first, because they are what it answers from.
Forward the survey by email or upload the file, and it joins a tracked queue with the requester and status on each row. Answers draw on what is already on your profile rather than a blank form.
See it on your own suppliers or portfolio companies
Numbers you can defend within 2 weeks.
