Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a process for planning and writing grant reports #805

Open
1 task
choldgraf opened this issue Feb 16, 2024 · 0 comments
Open
1 task

Create a process for planning and writing grant reports #805

choldgraf opened this issue Feb 16, 2024 · 0 comments
Assignees

Comments

@choldgraf
Copy link
Member

choldgraf commented Feb 16, 2024

Context

2i2c has many grants and restricted funds, which often come with additional reporting requirements. For example, most grants have annual reports where we must provide a narrative about the work that's been done, challenges we've faced, unexpected changes, etc. We also need to submit a budget that describes how the funds were spent.

Traditionally this work is done by the grant's "Principal Investigator", who oversees the process. However, many roles within 2i2c now serve as PI on a grant, and this means we need ways to share this responsibility across our team so that it doesn't become invisible work for the person who happens to be listed as PI.

We need to define a process tracking the report itself, the actions needed to complete it, and dividing them amongst our team according to who is in the best position to do it.

Suggestion: Use our NASA TOPS-T report to prototype this

We have a NASA TOPS-T grant report due in April. @jmunroe is the PI on the grant. Shall we use this opportunity to experiment with a process that distributes reporting responsibilities across the team? Even if James is the final person to "submit" the report, I think we'll do a better job by being intentional about planning the work as a team.

Tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants