🖋️

Approving & Tagging Grants: Ecosystem & Cause Rounds 1

Context

In GR12, we have ten rounds running simultaneously - the main round, six ecosystem rounds, and three cause rounds.

In order to make the ecosystem & cause rounds successful, many of us have been manually yolo-approving & tagging grants we know to be legit.

Currently, our process for this is inconsistent which (a) puts us at some level of relationship risk with our funding partners if we have grants in their rounds they didn't want in there, and (b) messes with FDD's established approval process.

This page will outline how Grants Ops can/should add new grants and tag them for each type of side round.

Ecosystem Rounds

Ecosystem rounds (Uniswap, ZKTech, Polygon, Forefront, Synthetix, and Gitcoin Building Gitcoin) are assigned in the system using tags.

Projects can self-select into these tags in the grants application.

These tags cannot be edited after a grant has submitted an application, and sometimes we receive requests to do this manually on the backend.

If you are manually approving a new grant, please:

Go into FDD's New Grant Approval Page

Find the grant you are approving

Move Platform Status to "Approved",

Add a comment saying "Approved by Grants Ops"

Add a tag in notion to either the Ecosystem or Thematic field which it is eligible

If you are manually tagging a grant, please:

Generally use your best judgment to make sure the grant is relevant to the ecosystem it is being tagged for. We should create a better process for this in the future - but we don't have one yet. The mitigant for this is the next step below 👇

Ecosystem Partner Check-in:

Each round lead should review the grants in the round every couple days, and if there are a number of new ones or any that are questionable, they should check in with the Ecosystem Partner to have them do a run-through and make sure they are good with the grants listed in their round. 💡

(Why do this? We don't want to come to Day 16 of the round and have, say, Uniswap say "we don't want that grant in the round" after they've already received a bunch in matching fund. That's a miserable grantee experience we want to avoid.) 

Cause Rounds

Cause Rounds (Climate, Advocacy, Longevity) are assigned in the system using Collections. 

These collections have been manually created by leads of the three rounds.

While we do also have tags for each of these that people can self-select into, tags do NOT systematically render a grant eligible for matching within that round - the grant also needs to be added to the relevant Collection.

If you are manually approving a new grant, please:

Go into FDD's New Grant Approval Page

Find the grant you are approving

Move Platform Status to "Approved", and add a comment saying "Approved by Grants Ops" and add the Round name to the "Thematic" field

Add it to the cause-specific list so it can be added to a collection:

Climate List — add your grant as a new row, write "active" under the "onboarded" column, and write "N" beside "added to collection". Xavier will go in and batch add these to the collection every day or two.

Advocacy (Scott to add details)

Longevity (Scott to add details)

If you are manually tagging a grant, please:

Don't do this - manually tagging a grant does nothing for a cause round. Follow Step 4 above to get it added to the collection instead of tagging it.

Daily grant applications review:

Since grants can self-select with the climate, advocacy, and longevity tags but it doesn't actually add them to matching, it's important that we review new grant applications every few days and manually add any to the collection that should be there.

We will have one member of the Gitcoin team review these each day. If they find grants that should be added, they should do Step 4 of adding it to the cause-specific list so it can be added to a collection.

Approving & Tagging Grants: Ecosystem & Cause Rounds 1

Context

In GR12, we have ten rounds running simultaneously - the main round, six ecosystem rounds, and three cause rounds.

In order to make the ecosystem & cause rounds successful, many of us have been manually yolo-approving & tagging grants we know to be legit.

Currently, our process for this is inconsistent which (a) puts us at some level of relationship risk with our funding partners if we have grants in their rounds they didn't want in there, and (b) messes with FDD's established approval process.

This page will outline how Grants Ops can/should add new grants and tag them for each type of side round.

Ecosystem Rounds

Ecosystem rounds (Uniswap, ZKTech, Polygon, Forefront, Synthetix, and Gitcoin Building Gitcoin) are assigned in the system using tags.

Projects can self-select into these tags in the grants application.

These tags cannot be edited after a grant has submitted an application, and sometimes we receive requests to do this manually on the backend.

If you are manually approving a new grant, please:

Go into FDD's New Grant Approval Page

Find the grant you are approving

Move Platform Status to "Approved",

Add a comment saying "Approved by Grants Ops"

Add a tag in notion to either the Ecosystem or Thematic field which it is eligible

If you are manually tagging a grant, please:

Generally use your best judgment to make sure the grant is relevant to the ecosystem it is being tagged for. We should create a better process for this in the future - but we don't have one yet. The mitigant for this is the next step below 👇

Ecosystem Partner Check-in:

Each round lead should review the grants in the round every couple days, and if there are a number of new ones or any that are questionable, they should check in with the Ecosystem Partner to have them do a run-through and make sure they are good with the grants listed in their round. 💡

(Why do this? We don't want to come to Day 16 of the round and have, say, Uniswap say "we don't want that grant in the round" after they've already received a bunch in matching fund. That's a miserable grantee experience we want to avoid.) 

Cause Rounds

Cause Rounds (Climate, Advocacy, Longevity) are assigned in the system using Collections. 

These collections have been manually created by leads of the three rounds.

While we do also have tags for each of these that people can self-select into, tags do NOT systematically render a grant eligible for matching within that round - the grant also needs to be added to the relevant Collection.

If you are manually approving a new grant, please:

Go into FDD's New Grant Approval Page

Find the grant you are approving

Move Platform Status to "Approved", and add a comment saying "Approved by Grants Ops" and add the Round name to the "Thematic" field

Add it to the cause-specific list so it can be added to a collection:

Climate List — add your grant as a new row, write "active" under the "onboarded" column, and write "N" beside "added to collection". Xavier will go in and batch add these to the collection every day or two.

Advocacy (Scott to add details)

Longevity (Scott to add details)

If you are manually tagging a grant, please:

Don't do this - manually tagging a grant does nothing for a cause round. Follow Step 4 above to get it added to the collection instead of tagging it.

Daily grant applications review:

Since grants can self-select with the climate, advocacy, and longevity tags but it doesn't actually add them to matching, it's important that we review new grant applications every few days and manually add any to the collection that should be there.

We will have one member of the Gitcoin team review these each day. If they find grants that should be added, they should do Step 4 of adding it to the cause-specific list so it can be added to a collection.