# data[].attributes.body
Requesting a few bullet points, like Hilton, on interim or final reports regarding progress, challenges, and lessons learned came up came up. Is it a potential model for us to explore? Jenn recommended the foundation engagement group touch base with
Allison Gister, Director, Grants & Knowledge Management, Hilton Foundation.

# data[].attributes.body
Simplify interim and final reports for grantees. It's a huge lift to aggregate and analyze results and even then what is collected/submitted requires grantee follow-up to learn more.

# data[].attributes.body
Grantees have acknowledged that Irvine’s grant process is not the easiest, but they feel like after going through our grants process, they have something as an organization that clearly outlines its work for other funders.

# data[].attributes.headline
different process for smaller size grants and renewals

# data[].attributes.subject
different process for smaller size grants and renewals

# data[].attributes.body
clarify more explicitly what we need out of necessity to give a grant money versus what we as P-team want so we can better support your organization's work

# data[].attributes.body
Asking applicants during the due diligence process (even before an application is invited) about their organization's philosophy on racial equity and inclusion, economic justice, what is their commitment and point of view, is key to make sure we’re working with aligned partners.

# data[].attributes.headline
Alternative reporting methods for grantees who would prefer a format other than submitting a  written report to share about their successes, challenges, etc. such as a virtual meeting, an in person meeting, or a call.

# data[].attributes.subject
Alternative reporting methods for grantees who would prefer a format other than submitting a  written report to share about their successes, challenges, etc. such as a virtual meeting, an in person meeting, or a call.

# data[].attributes.body
There was a thought to make an organizational profile section in the portal where grantees can update information as needed. This can eliminate the need to ask for the same information every grant, especially if this is not necessary.

# data[].attributes.body
A good amount of the additional proposal prompts and support docs can be removed since the portal marks them as required.

# data[].attributes.body
Final report and renewal should feel timely. Especially for RGAs

# data[].attributes.body
Portal can ask grantees some of the parts we code in the grant in order to eliminate them needing to write it out. For example audience, partnerships, etc. This can avoid the grantee needing to write this section out to support our coding process.

# data[].attributes.body
Given the increase in P-team staff over the past two years, implementing check-in calls in lieu of interim reports is a practice that may be more feasible than it was in the past.

# data[].attributes.body
Folks had different viewpoints on the need for supporting documents. Some folks on my team thought the Organizational Chart and the Board of Directors List could be optional, though others felt like they could be useful in ascertaining the racial equity commitment of an organization.

# data[].attributes.body
One PO suggested the idea of having a grant writer on staff that could join the calls with small orgs and translate their ideas into the type of proposal we need. This way orgs wouldn’t have to spend time writing their proposal narratives, and they could leverage the polished proposal the grant writer churns out to apply for additional funding sources

# data[].attributes.body
Extraneous information in proposal - grantees often duplicate information because they want to answer every sub-question/prompt, leading to unnecessarily long proposals

# data[].attributes.body
Bandwidtch - the narrative portion can be burdensome for smaller orgs that do not have a grant writer