Grant Application Template

Grants / Bounties
1

Grant Application Template

Name of Grant

  • What is the work being proposed?
    • Title of the project
    • Brief project description
  • Why do you think this work is necessary?
  • Is there any related work this builds upon?
  • Will the results of this project be entirely open source? ([MIT], [GPL], [Apache], [CC BY] license or similar)?

Benefits to Pod

  • If this grant is successfully completed, how does it help the pod involved?

Benefits to Arrow

  • If this grant is successfully completed, how does it help Arrow?
  • Which other non-Arrow DAOs, projects, or individuals, would stand to benefit from this grant?

Assignee & Background

  • Who is doing the work?
    • Name/Username
    • Email address
    • Organization (if applicable)
    • Website (if applicable)
  • What is the background of the person(s) doing the work? What experience do they have with such projects in the past?
  • Have you examples of similar work you have completed in the past?

Work Details

  • Do you need any input from another bounty/grant before the final submission?
  • What is the breakdown of the proposed work, in terms of milestones and/or deadlines?
    • Please include specific dates for milestones.
    • Milestone 1
    • Milestone 2
    • Milestone 3
    • Milestone 4
  • List the details of the problem and what you want to accomplish with this grant.
  • What will be the outcomes of the grant? List all the deliverables and include specific dates for their delivery. For example;
    • CAD designs (Jan 4th)
    • analysis results (Jan 12th)
    • manufacturing guide (Jan 20th)
    • necessary documentation (Jan 27th)
  • In which areas can this work be used? What is the scope of its applicability?
  • What metrics will be used to evaluate the outcomes of the project? E.g. how the GBC would measure the impact of your project.

Risk Assessment

  • What are the potential risks or challenges for this project?
  • How will these risks be managed or mitigated?
  • How will you handle unforeseen obstacles or delays?
  • Is there a long-term plan for updating or improving the work over time?
  • What steps can be taken to ensure the longevity and sustainability of the work?

Costs

  • How many work hours will be spent on this grant?
  • How much USDC/ARROW is the applicant requesting?
  • How does the amount requested represent good value for Arrow?
  • What is the proposed payment schedule for the grant?
  • How will the GBC verify that the work delivered matches the proposed cadence?
  • What alternatives or options have been considered in order to save costs for the proposed project?
  • Have you examples of similar work you have completed in the past?
3 Likes
2

Thank you for putting this together! Looks very thorough. I canā€™t think of any additions or edits.

1 Like
3

Looks great sleety. It seems to have all the essential bits.

One good detail to put for relatively big chunks of grants is putting some in-between review gates, where those review gates are tied to certain deliverables. Deliverables generally have an estimate timeline starting from T0 (approval of grant). So for those gates GBC and grant owner might get together and assess the progress & status of deliverables & status of risks, adjust if deemed necessary and set the payments accordingly. Each gate pass might release the planned allocated payment.

Then, for the template, only thing I could propose is adding ā€œPlease include specific datesā€ comment under the deliverables section also to enable such planning.

2 Likes
4

yeah, agree with this, this is how upwork operate as well to allow intermediary work package submissions, and then the give the option of chunk pay-outs or all at the end

1 Like
5

Does the grant applicant choose the review gates or does the GBC impose these?

Should each deliverable/milestone have a review gate built into it?

E.g.
Deliverable: Produced research document on Topic X
Paid 33% of grant amount
Review Gate 1 :arrow_right_hook:

Next Deliverable: Created CAD design based on research on Topic X
Paid 33% of grant amount
Review Gate 2 :arrow_right_hook:

Next Deliverable: Further modify and finalize CAD design post-review
Paid final 33% of grant amount

6

I think this makes sense. Especially when we use the word ā€œgrantā€ for bigger tasks, almost like small projects, it makes sense to set some milestones and pay people for each step. It may feel overwhelming to people otherwise.

1 Like
7

I edited this bit to include emphasis on ā€˜specific datesā€™ for deliverables (based on above feedback)

8

Iā€™ve included the above comments in the revised Application Template.

This thread will remain open for ongoing suggestions on how we could improve this template.

1 Like