Proposal submission Guide
This page guides proposers in submitting their proposal in ideascale
Submission Form Sections
These are the sections of the form you will in Ideascale to submit your proposal
GENERAL
Proposal title
Voters can see this in the voting app even without opening your proposal, so it is important. It should say very directly what your proposal is about.
Required
Name and Surname of Main Applicant
Please provide the name, surname of the Main Applicant. The Main Applicant is the individual responsible for the project and the person authorised to act on behalf of other Applicants (where applicable).
Required
Email address of Main Applicant
Please provide the email address of the Main Applicant. The Main Applicant is the individual responsible for the project and the person authorised to act on behalf of other Applicants (where applicable).
Required
Additional Applicants
Please list any persons who are submitting the proposal jointly with the Main Applicant. Make sure you have confirmed with these individuals / accounts before adding them here for their approval and awareness.
Required
Requested funds in ADA
Minimum ₳15,000 for any proposal
Maximum ₳75,000 for proposals made to Catalyst Open, review the challenge brief for other challenges carefully to see if any additional guardrails around funding requests are not part of it.
Required
Please specify how many months you expect your project to last
(from 2-12 months)
Maximum 12 months length.
The scope of your funding request and this project is expected to produce the deliverables you specify in the proposal in between 2-12 months.
If you believe your project will take longer than 12 months then consider reducing the scope of the project so that the scope is achievable within 12 months.
Required
Please indicate if your proposal has been auto-translated into English from another language.
Tick this box to remind readers that your proposal has been translated, and that they should be tolerant of any language imperfections.
You can either link a document with your proposal in its original language OR provide your response in your native language after the English language in each question if you wish.
Required
What is the problem you want to solve? (200-character limit including spaces)
Ensure you say what is a well defined problem. What is the core issue that you hope to fix? Remember: the reader might not recognise the problem you can see, unless you state it.
This answer will be displayed on the Catalyst voting app, so voters will see it even if they don't open your proposal to read it in detail.
Required
Summarize your solution to the problem (200-character limit including spaces)
Focus on what you are going to do, or make, or change, to solve the problem. So not 'There should be a way to....' but 'We will make a...'
Make sure it's clear how the solution addresses the specific problem you have identified - connect the 'why' and the 'how'.
This answer will be displayed on the Catalyst voting app, so voters will see it even if they do not open your proposal and read it in detail.
Required
Website/ GitHub repository, or any other relevant link
Here, you could include links to your website or that of a partner organisation, and/or a link to any whitepaper or other publication you have written about your proposal.
But please note, this is extra information, which voters and Community Reviewers might choose not to read. You should not overlook to include any of the questions in this form because the answers are in your website or your whitepaper.
Does your project have any dependencies on other organizations, technical or otherwise?
YES/NO
Required
If YES, please describe what the dependency is and why you believe it is essential for your project’s delivery. If NO, please write “No dependencies.” in this field.
Here you should list any dependencies and pre-requisites that you may need to make your project successful. These are usually external factors that may cause delay because a project has less control over them such as 3rd party suppliers, external resources, third party software etc. In case of third party software, please indicate whether you have the necessary licences and permission to use such software.
Required
Will your project outputs be fully Open Source?
YES/NO
Required
If NO, please describe which outputs are not going to be open source.
If YES, please write “Project will be fully open source.” in this field.
Please specify here any part of your project output that will NOT be open source with an explanation of why this is the case. It is important that the Community has a clear understanding and expectation of the allocation of rights over the project outcome as well as processes.
Required
There are a number of resources available to you to help navigate the proposal submission process.
To seek additional assistance please consider reviewing the following documents and support:
How to submit a proposal
Community Review Guidelines
IMPORTANT
Any largely blank proposals (empty drafts with many TBD/TBC/coming soon items) or ideas with titles such as "Placeholder" may be archived without notice at any time. Kindly submit drafts once you are ready to proceed with enough context for the community to be able to provide tangible feedback.
Last updated