1. Understand
Opportunity Decoder
A builder who has already tested a climate-related project and can explain community need, evidence, and next use of funding.
Specific proof matters more than broad motivation. The strongest answer should show learning from real users or field context.
Treat screenshots and drafts as useful context, not certification. High-impact claims need confirmation before reuse.
2. Map evidence
Evidence Map
| Source | What it proves | Does not prove | Confidence / context | Use in answer |
|---|---|---|---|---|
| CV excerpt | Applicant built a mobile prototype and led user interviews. | Does not prove long-term adoption. | High for role/activity; low for impact. | Use for builder credibility. |
| Project deck | Shows problem framing, workflow, and early pilot plan. | Does not prove funding or institutional partnership. | Medium; triangulate partner or funding claims. | Use for product clarity. |
| Community feedback screenshot | Shows real user pain and qualitative demand. | Does not prove representative sample size. | Medium; quote as early signal only. | Use as early evidence, not impact claim. |
3. Check fit
Fit and Claim Lock
Strongest fit
The applicant is strongest as a practical builder who has spoken to affected users and can turn evidence into a focused fellowship plan.
Claims to handle carefully
Adoption numbers and climate impact should be softened unless the applicant uploads a source that verifies them.
4. Prepare
Final Material Preview
I am applying as a builder who has already tested the problem with affected users, not only as someone interested in climate technology. My current prototype helps local coordinators collect and act on adaptation needs. The strongest evidence so far is qualitative: user interviews, a project workflow, and early feedback showing where existing tools fail. I would use the fellowship to turn this early proof into a more rigorous pilot, while keeping claims about adoption and impact clearly measured rather than overstated.
5. Record
Application Record
3 short answers, CV excerpt, project deck link, proof caption.
CV excerpt, project deck, feedback screenshot. Adoption claim left unverified.
After submission, attach confirmation email or portal screenshot to preserve reference details.
Private beta
The live workspace requires login.
This public workflow is read-only. Invited reviewers and beta users can test the real workspace with controlled access.