Universal Grant Application Data Elements
Enable grantseekers to provide standard information once, in machine-readable form, for use by any grantmaker.
Other Information
Prior efforts have addressed parts of this problem. In 2003 the Office of Management and Budget standardized the data elements of Standard Form 424 for federal grant applications, and OMB Watch and the National Council of Nonprofit Associations urged a "common application" model like that used for college admissions. In private philanthropy, regional associations of grantmakers, collaborative funder groups, and platforms such as JustFund offer common applications, but each covers only its own participants.
The Technology Association of Grantmakers (TAG) has pursued a different approach: a common grantee database and open data standard from which funders pull what they need, without agreeing on a common proposal format. No open, universal set of data elements yet spans government and private grantmakers alike.
This plan proposes such a set, comprising a minimal core common to all applications plus a mechanism for funder-specific extensions, so that grantseekers can publish their information once and grantmakers can query it, while each grantmaker retains full discretion over its own priorities and decisions.
Because a grant application is essentially a proposed performance plan, the goals, objectives, and performance indicators of proposed projects can be expressed in StratML Part 2 format rather than in narrative prose. StratML Part 2, Performance Plans and Reports (formerly ANSI/AIIM 22:2017) extends the goals and objectives of Part 1 with performance indicators, including target and actual results.
Moreover, a grantee's subsequent report is a performance report on the same plan. Thus, a single Part 2 document can serve both purposes: the applicant states target results when applying and records actual results when reporting, enabling common reporting to multiple grantmakers as well as common application.
A Part 2 authoring form developed with Claude.ai is available at https://stratml.us/forms/Claude/Part2.html and could be adapted for grant applications.
To make authoring as easy as possible to do, ChatGPT has provided a prompting guide that enables users to convert unstructured text into StratML format: https://stratml.us/references/StratML-Prompting-Guide.html
This plan complements the U.S. Strategy Data Fellowship initiative of the General Services Administration -- https://stratml.us/docs/USSDF.xml -- which aims to make public-sector strategic plans AI-ready and interoperable in order to improve coordination and execution across governments.
Grants are a principal means by which agencies execute their strategies. If applications were expressed in the same machine-readable format as agencies' strategic plans, the alignment of applicants' objectives with grantmakers' goals could be identified automatically. That would extend the Fellowship's cross-government alignment and opportunity identification objectives to the nonprofit organizations it recognizes as stakeholders. The same logic applies to private grantmakers that publish their priorities in StratML format.
This plan shares the aim of effective altruism: directing charitable resources where they will do the most good, based on evidence.
However, evaluators associated with that movement conduct costly analyses of relatively few organizations, partly because comparable performance data is scarce. By making applicants' intended and actual results available in a standard, machine-readable format, this plan could lower the cost of such comparisons and extend them to many more organizations.
Rather than relying on a few evaluators to rank causes and charities, implementation of this plan would empower grantmakers to apply their own values to commonly available data, distinguishing verifiable findings about results from contested judgments about which results matter most.
While no measure is perfect, failing to seek objective measures is a prescription for continuous, opinion-based mediocrity. Donors and intended beneficiaries alike have a right to expect better: measures that are continually refined so that they track the outcomes that matter rather than merely those easiest to count.
The relationship between effective altruism and verifiable accountability is also addressed, with respect to AI developers, in the plan entitled Verifiable Virtue: https://stratml.us/docs/VV4AI.xml
In a LinkedIn post, Vineeta Gupta asks why the financial and operational burden of discovery falls almost entirely on grantseekers rather than funders. She cites MacKenzie Scott's 2024 open call, in which 6,353 organizations applied and 361 were funded, consuming an estimated 60,000 or more hours of unfunded applicants' time. Open calls reach organizations unknown to funders but at great cost to applicants, while invitation-based funding spares applicants but leaves those outside familiar networks invisible.
https://lnkd.in/p/egUW7qyk
By enabling organizations to publish their information once in a standard, machine-readable format that any funder can query, this plan offers a way out of that dilemma: it shifts the cost of discovery toward funders while reducing that cost through structured data and AI-assisted search. It does not change the odds of success, but it reduces what an unsuccessful application costs and keeps unsuccessful applicants discoverable by other funders.
Submitter's Note: This plan was drafted and rendered in StratML format in dialog with Claude.ai. It has been reviewed in the form at https://stratml.us/forms/Claude/Part2.html
🏢Owen Douglas Ambur ODA Proponent of this plan
Stakeholders:
👥 👥 👥 👥 👥 👥 👥 👥 | Source & SubmitterSource:https://stratml.us/docs/UGADE.xml Period: to Published: |
Vision
A highly dynamic and effective market for the realization of public good
Mission
To specify, publish, and promote an open, universal set of data elements by which applications for charitable funding can be submitted to, and results reported to, any grantmaker or donor
Values
Goal 1: Data Elements 🔗
Specify the minimum set of data elements common to all grant applications.
Stakeholders:
👥Grantseekers
👥Grantmakers
Other Information
The core should be limited to information that is stable across applications and needed by nearly all grantmakers, such as the applicant's identity, contact information, legal status, mission, and financial summary, while project-specific information is expressed as a performance plan under Goal 2. Elements that grantmakers can obtain from authoritative public sources, such as IRS Form 990 filings and the System for Award Management, should be referenced rather than re-entered.
Objective 1.1: Inventory 🔗
Identify the data elements used in SF-424, regional common grant applications, collaborative funder applications, JustFund, TAG's open data standard, and Candid nonprofit profiles.
Stakeholders:
👥Contributors Researcher : Identify and document the data elements used in existing application forms and data standards (Performer)
👥Philanthropy-Serving Organizations Source Provider : Provide access to common application forms and data standards (Performer)
Other Information
Potential sources include: • Standard Form 424 and related forms • Common grant applications of regional associations of grantmakers • Collaborative funder applications, such as the Common App for the Arts and the Tahoe Truckee regional grant cycle • The JustFund Common Application • TAG's open data standard for grantee information • Candid nonprofit profiles • IRS Form 990
Performance Indicators
1.1.1: Sources Inventoried
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Number of application forms and data standards whose data elements have been documented | |||
| Actual | TBD | Not yet measured. |
Objective 1.2: Crosswalk 🔗
Map equivalent elements across the inventoried forms to reveal which are truly common.
Stakeholders:
👥Contributors Analyst : Map equivalent elements across inventoried sources (Performer)
👥Grants Management System Vendors Crosswalk User : Use the crosswalk to map fields in existing systems to the standard (Beneficiary)
Other Information
For each element, record its name and definition in each source, the sources in which it appears, and any differences in data type or permissible values. Elements appearing in most sources are candidates for the core, while those appearing in few are candidates for grantmaker-specific extensions.
Performance Indicators
1.2.1: Elements Mapped
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Number of distinct data elements mapped across inventoried sources | |||
| Actual | TBD | Not yet measured. |
Objective 1.3: Core Set 🔗
Define the core elements, with names, definitions, and data types, limited to those that nearly all grantmakers require.
Stakeholders:
👥Contributors Drafter : Define the names, definitions, and data types of the core elements (Performer)
👥Grantmakers Reviewer : Confirm that the core elements meet their common needs (Performer, Beneficiary)
👥Grantseekers Applicant : Provide core information once for use by many grantmakers (Beneficiary)
Other Information
Element names should be nouns consistent with StratML naming conventions, and definitions should be precise enough to support automated validation. Where an equivalent element already exists in StratML Part 1 or Part 2, such as Organization, Mission, Stakeholder, and Performance Indicator, it should be reused rather than redefined. The core elements can serve as the brief expression of interest that Gupta recommends as the first step, with full proposals and grantmaker-specific extensions requested only when there is a serious prospect of funding.
Performance Indicators
1.3.1: Core Elements
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Number of elements in the core set, kept as small as nearly universal need allows | |||
| Actual | TBD | Not yet measured. |
1.3.2: Coverage
| Type | Start Date | End Date | Percent | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Percentage of the information commonly requested by inventoried sources that is captured by the core elements | |||
| Actual | TBD | Not yet measured. |
Objective 1.4: Extensions 🔗
Provide a mechanism by which grantmakers can add their own questions and attachments without altering the core.
Stakeholders:
👥Grantmakers Extension Publisher : Publish additional questions and attachment requirements in machine-readable form (Performer)
👥Grantseekers Applicant : Discover each grantmaker's requirements before applying (Beneficiary)
👥Beneficiaries Protected Party : Protected against disclosure of information that could endanger them (Beneficiary)
Other Information
Grantmakers' additional questions and attachment requirements can themselves be published in machine-readable form, so that applicants and their tools can discover what each grantmaker requires before applying. The JustFund model, in which grantmakers may add a limited number of questions to a standard application, illustrates one approach. Limiting the number of extensions helps preserve the benefits of the core. The core elements should be suitable for public disclosure, while extensions may include information made available only to grantmakers authorized by the applicant. For example, organizations serving vulnerable populations must be able to participate without publishing information that could endanger those they serve. See Objective 6.3 (Access Control) of the Model Plan for Virtual Organizations: https://stratml.us/docs/MP4VO.xml
Performance Indicators
1.4.1: Extensions Published
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Number of grantmakers publishing their extensions in machine-readable form | |||
| Actual | TBD | Not yet measured. |
1.4.2: Extension Questions
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Average number of grantmaker-specific questions per extension, to be minimized | |||
| Actual | TBD | Not yet measured. |
Goal 2: Machine-Readability 🔗
Render the data elements in open, machine-readable form.
Stakeholders:
👥Grants Management System Vendors
Other Information
The schema should build upon existing standards rather than replace them, with StratML Part 2 as the primary candidate for expressing proposed projects and the identifiers already used in federal grantmaking serving to identify applicants.
Objective 2.1: XML Schema 🔗
Publish an XML schema for the core elements and extensions.
Stakeholders:
👥Contributors Schema Developer : Develop, validate, and publish the schema (Performer)
👥Grants Management System Vendors Implementer : Support the schema in grants management systems (Beneficiary)
Other Information
The core organizational elements could be published as a small schema that references the StratML Part 2 schema (currently version 2.2.10) for project information.
Performance Indicators
2.1.1: Schema
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | Published | Schema for the core elements and extensions published and validated | |||
| Actual | TBD | Not yet measured. |
Objective 2.2: Identifiers 🔗
Use existing identifiers, such as the Employer Identification Number and the Unique Entity Identifier, rather than creating new ones.
Stakeholders:
👥Grantseekers Identifier Provider : Supply Employer Identification Numbers and Unique Entity Identifiers (Performer)
👥Grantmakers Data User : Retrieve authoritative information by identifier rather than asking applicants to re-enter it (Beneficiary)
Other Information
The Unique Entity Identifier is assigned through the System for Award Management, which GSA administers, and is already required for federal grants. The Employer Identification Number links applicants to their IRS Form 990 filings. Using both allows grantmakers to retrieve authoritative information without asking applicants to re-enter it.
Performance Indicators
2.2.1: Elements Retrieved
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Number of core elements retrievable from authoritative sources by identifier rather than re-entered by applicants | |||
| Actual | TBD | Not yet measured. |
Objective 2.3: Performance Plans 🔗
Express the goals, objectives, and performance indicators of proposed projects in StratML Part 2 format.
Stakeholders:
👥Grantseekers Plan Author : State intended outcomes, performance indicators, and targets, and later report actual results (Performer)
👥Grantmakers Reviewer : Compare proposed and reported results across applications (Beneficiary)
👥Beneficiaries Intended Beneficiary : Benefit from results that are planned, measured, and reported (Beneficiary)
Other Information
StratML Part 2 enables applicants to state the outcomes they intend to achieve, the performance indicators by which progress will be measured, and their target results, in a form that grantmakers can compare across applications. The same document can later be updated with actual results to serve as the grantee's performance report, eliminating the need for separate reporting formats. The Part 2 form at https://stratml.us/forms/Claude/Part2.html can be used to author, update, and maintain such plans.
Performance Indicators
2.3.1: Applications Published
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Number of applications published in StratML Part 2 format | |||
| Actual | TBD | Not yet measured. |
2.3.2: Reports Updated
| Type | Start Date | End Date | Percent | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Percentage of funded applications later updated with actual results to serve as performance reports | |||
| Actual | TBD | Not yet measured. |
Goal 3: Tools 🔗
Demonstrate that applications can be authored once and queried by many grantmakers.
Stakeholders:
👥Grantseekers
👥Grantmakers
Other Information
Working tools are more persuasive than specifications alone. Demonstrations should show the complete cycle: an applicant authors an application once and publishes it, and multiple grantmakers find and evaluate it using their own criteria.
Objective 3.1: Authoring Form 🔗
Build an HTML form that produces valid application instances.
Stakeholders:
👥Contributors Developer : Extend the Part 2 form to produce valid application instances (Performer)
👥Grantseekers Form User : Author applications, including by AI-assisted conversion of existing proposals (Beneficiary)
Other Information
The form could extend the existing StratML Part 2 form by adding the core organizational elements and support for grantmaker-specific extensions. Its AI-assisted population feature could draft an application from an applicant's existing narrative proposal, reducing the burden of converting legacy documents.
Performance Indicators
3.1.1: Form
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | Released | HTML form producing valid application instances, including AI-assisted population | |||
| Actual | TBD | Not yet measured. |
3.1.2: Completion Time
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Average hours required to complete an application using the form | |||
| Actual | TBD | Not yet measured. |
Objective 3.2: Query Service 🔗
Demonstrate XQuery-based retrieval of published applications according to the criteria of grantmakers and donors.
Stakeholders:
👥Contributors Developer : Build and operate a demonstration query service (Performer)
👥Grantmakers Scout : Find organizations doing effective work outside existing networks (Beneficiary)
👥Donors Searcher : Identify charities they choose to support (Beneficiary)
👥Grantseekers Published Applicant : Remain discoverable by other funders after unsuccessful applications (Beneficiary)
Other Information
Grantmakers could query published applications by geography, subject area, stakeholder group, performance indicator, or alignment with their own published goals. A BaseX and XQuery service like that at https://aboutthem.info/ would demonstrate this capability. Query services enable grantmakers to scout for organizations doing effective work that do not appear in their existing networks, including rural organizations, which Gupta estimates receive about 3% of philanthropic funding while serving about 20% of Americans. Regional grantmakers could pool the cost of such discovery while making their own grant decisions.
Performance Indicators
3.2.1: Query Service
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | Operational | Demonstration query service operating against published applications | |||
| Actual | TBD | Not yet measured. |
3.2.2: Queries
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Number of queries executed by grantmakers and donors | |||
| Actual | TBD | Not yet measured. |
Objective 3.3: Verification 🔗
Enable reported results to be substantiated through provenance, supporting evidence, beneficiary feedback, and independent review proportionate to the size of the grant.
Stakeholders:
👥Grantseekers Reporter : Substantiate reported results with supporting evidence (Performer)
👥Beneficiaries Feedback Provider : Provide feedback on whether reported results reflect actual outcomes (Performer, Beneficiary)
👥Evaluators Reviewer : Independently review reported results, particularly for large grants (Performer)
👥Grantmakers Relying Party : Rely on substantiated results in making funding decisions (Beneficiary)
👥Donors Relying Party : Rely on substantiated results in choosing charities to support (Beneficiary)
Other Information
Self-reported results are only as credible as the means of checking them. Verification need not be uniform: small grants may warrant little more than supporting evidence, while large grants may justify independent evaluation. The principle that accountability should not depend on trusting anyone's stated good intentions is developed further in Verifiable Virtue: https://stratml.us/docs/VV4AI.xml
Performance Indicators
3.3.1: Substantiated Results
| Type | Start Date | End Date | Percent | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Percentage of reported actual results accompanied by supporting evidence | |||
| Actual | TBD | Not yet measured. |
3.3.2: Beneficiary Feedback
| Type | Start Date | End Date | Percent | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Percentage of performance reports incorporating beneficiary feedback | |||
| Actual | TBD | Not yet measured. |
Goal 4: Adoption 🔗
Invite grantmakers, grantseekers, and their intermediaries to review, use, and improve the standard.
Stakeholders:
👥Philanthropy-Serving Organizations
👥Grants Management System Vendors
Other Information
Adoption should be voluntary and incremental. Grantmakers already using common applications have demonstrated their interest in reducing applicants' burden and are the most likely early adopters. GSA's U.S. Strategy Data Fellowship, which seeks to foster a community supporting interoperable public-sector strategy data, offers a potential venue for considering how grant applications might be aligned with agencies' strategic plans.
Objective 4.1: Comment 🔗
Publish the draft elements for public comment.
Stakeholders:
👥Contributors Editor : Publish the draft and respond to comments (Performer)
👥Philanthropy-Serving Organizations Reviewer : Review and comment on the draft elements (Performer, Beneficiary)
👥Grants Management System Vendors Reviewer : Review the draft for implementability (Performer, Beneficiary)
👥Evaluators Reviewer : Help refine the performance indicators by which results are reported (Performer, Beneficiary)
Other Information
Potential reviewers include: • Regional associations of grantmakers • The Technology Association of Grantmakers • Candid • Grants management system vendors • Nonprofit associations • Participants in the U.S. Strategy Data Fellowship • Charity evaluators, such as GiveWell and Giving What We Can Charity evaluators have a particular interest in comparable performance data and could help refine the performance indicators by which results are reported.
Performance Indicators
4.1.1: Draft
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | Published | Draft elements published for public comment | |||
| Actual | TBD | Not yet measured. |
4.1.2: Comments
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Number of substantive comments received | |||
| Actual | TBD | Not yet measured. |
Objective 4.2: Pilot 🔗
Invite grantmakers already using common applications to accept submissions conforming to the standard.
Stakeholders:
👥Grantmakers Pilot Participant : Accept conforming applications alongside existing forms and compare the results (Performer, Beneficiary)
👥Grantseekers Pilot Applicant : Submit conforming applications to participating grantmakers (Performer, Beneficiary)
Other Information
Pilots need not require grantmakers to change their internal systems. A grantmaker can accept a conforming application alongside its existing form and compare the results. Lessons learned should inform revisions to the core elements and extensions.
Performance Indicators
4.2.1: Participating Grantmakers
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Number of grantmakers accepting conforming applications | |||
| Actual | TBD | Not yet measured. |
4.2.2: Conforming Applications
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Number of conforming applications received by participating grantmakers | |||
| Actual | TBD | Not yet measured. |
4.2.3: Applicant Hours Saved
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Estimated hours saved by applicants submitting one conforming application to multiple grantmakers rather than separate applications | |||
| Actual | TBD | Not yet measured. |
Objective 4.3: Funder Transparency 🔗
Encourage grantmakers to publish, in StratML Part 2 format, the planned number of awards, numbers of past applicants, estimated effort required at each stage, actual results, and the number of grantees previously unknown to them.
Stakeholders:
👥Grantmakers Discloser : Publish award odds, applicant numbers, effort estimates, and actual results (Performer)
👥Grantseekers Prospective Applicant : Judge whether applying is worth the effort (Beneficiary)
👥Donors Observer : Compare grantmakers on the burdens they impose as well as the results they fund (Beneficiary)
Other Information
Gupta also recommends that grantmakers balance program officers' gatekeeping authority with accountability for applicants' uncompensated time. Publishing these figures enables grantseekers to judge whether applying is worth the effort and enables grantmakers to be compared on the burdens they impose as well as the results they fund.
Performance Indicators
4.3.1: Disclosing Grantmakers
| Type | Start Date | End Date | Number | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Number of grantmakers publishing the specified figures in StratML Part 2 format | |||
| Actual | TBD | Not yet measured. |
4.3.2: Previously Unknown Grantees
| Type | Start Date | End Date | Percent | Status | Description |
|---|---|---|---|---|---|
| Target | TBD | Percentage of awards made to grantees previously unknown to the grantmaker | |||
| Actual | TBD | Not yet measured. |