Whether you run a grant program, scholarship, fellowship, award, accelerator, or pitch competition, the quality of your decisions depends on how the application and selection process is designed. Define eligibility, evidence, scoring, review stages, and applicant communications before building the form.
In short: Design an application process backward from the decision you need to make — who or what should be selected, funded, admitted, or awarded, and what evidence should support that decision. Before building the form, define eligibility requirements, scored criteria, metadata, rubric weights, review stages, applicant communications, and piloting rules. The same framework applies to grant programs and RFPs, scholarships, fellowships, awards, accelerators, and pitch competitions. The form is the last thing you build, not the first.
By Sopact Academy · Updated September 11, 2026. This lesson combines cited public guidance with practical workflow recommendations. Figures and teaching scenarios are illustrative unless explicitly identified as a published case.
Grant Intelligence · Chapter 2
Your output: a short process specification containing eligibility rules, scored criteria, required evidence, reviewer responsibilities, dates, and applicant messages.
Bring: the evidence map from chapter 1, or one existing application and its selection rules. The same method works for awards, scholarships, fellowships, accelerators and pitch competitions.
The walkthrough shows the end-to-end shape: collect from any source, read each application on arrival, then ask the assistant for a ranked, evidence-backed pool your committee can decide from.
In short: A complete application process has ten stages. Most teams over-invest in the form and under-invest in the decisions around it.
The rest of this chapter walks the decisions that matter most — starting with the one everything else hangs on.
Before a single field, write down what makes an applicant — a person or an organization — the right choice, and state the intended contribution rather than treating presentation quality as a substitute for evidence. Every field then has to earn its place by informing that decision. If you start with questions alone, you may collect answers that cannot support the selection decision.
In short: Every field on the form does one of three jobs. Eligibility fields are pass/fail gates checked before anything is scored. Criteria fields — essays, proposals, budgets, résumés, pitch decks, letters, or closed-ended questions — are read against a rubric, quantified, weighted, and summed into the score. Metadata fields — name, email, location — identify and filter, when used for identification rather than a published scoring criterion. Sorting them before you build makes the purpose of each field easier to explain and check.
Eligibility — the gate. Hard requirements: geography, tax status, organization type, age, program stage, funding request, deadline, or a required document attached. Evaluated pass/fail before scoring, so an ineligible application never competes and never wastes reviewer time. Keep these out of the score — an applicant does not earn a low score for being ineligible; they simply do not enter the ranked pool. Separate confirmed ineligibility from incomplete evidence. Apply the published rule for clarification or rejection, and keep unresolved applications outside the ranked pool.
Criteria — what you score. Anything you score — a qualitative essay, a proposal, a pitch deck, a résumé, a recommendation letter, even a closed-ended question — is read against a rubric that turns it into a number, weighted, and rolled into one score. A fixed rubric, written anchors, controlled instructions and source citations make the reasoning inspectable. Test repeated scoring and reviewer agreement; a fixed prompt alone does not guarantee the same result. A single criterion can draw on several fields — “leadership” or “organizational capacity” might read the essay and the résumé and a reference.
Metadata — what you track. Name, email, location, demographic tags, a contact ID. They identify the applicant, dedupe records, drive filters, and let you disaggregate the pool by geography or discipline. Context, not criteria. The rule that saves you later: anything you will filter or report by must be a clean structured field captured at intake, or your geography cuts break the first time someone free-types their city.
How each field earns its place:
| Field | Role | How it’s used | In the score? |
|---|---|---|---|
| Geography / tax status / org type / deadline | Eligibility | Hard requirement, checked first | No — pass/fail gate |
| Required documents attached | Eligibility | Completeness check | No — pass/fail gate |
| Essay / proposal / pitch deck | Criteria (qualitative) | Rubric 1–5, evidence cited | Yes — weighted |
| Résumé / CV / organizational capacity | Criteria (qualitative) | Rubric 1–5 on track record | Yes — weighted |
| Recommendation / reference letter | Criteria (qualitative) | Rubric 1–5 on strength of endorsement | Yes — weighted |
| Years of experience / program stage | Criteria (closed-ended) | Banded to points (0–4 = 1 … 10+ = 5) | Yes — weighted |
| Name / email / contact ID | Metadata | Identity, dedupe, tracking | No — tracking only |
| Location / region | Metadata | Filters, geographic disaggregation | No — filter only |
Worked example. Say your published weights are motivation 25%, regional ties 20%, leadership 20%, recommendation strength 20%, experience 15%. Each criterion is quantified 1–5 by the rubric — whether it reads an essay, a proposal, or a closed-ended answer — then normalized to its weight and summed to 100. For one applicant:
The criteria are illustrative, not prescriptive. For a grant program the same structure might weight strategic alignment 25%, evidence of need 20%, program feasibility 20%, organizational capacity 20%, and measurement readiness 15% — different criteria, identical mechanism.
Eligibility and metadata both sit outside the 100: an applicant who fails an eligibility rule or never uploaded a required document never reaches the weighted stage, and fields used only for identity or reporting do not move the score — they just let you find the record, filter the pool, and check the pool’s balance afterward.
A field can have different roles in different programs. Location may establish geographic eligibility or support reporting; it should affect a merit score only when the program has a justified, published criterion. Keep each use explicit and avoid counting the same characteristic twice. Do not treat demographic fields as scoring criteria merely because you collect them for monitoring.
For many demanding programs, drop-out or non-delivery is one of the most consequential selection risks — and you cannot screen for readiness against a vague ask. Publish the real load — hours, travel, cost, reporting — and make applicants acknowledge it, so they can assess whether participation is feasible and ask about support. Where relevant, get it in writing: for an individual, an employer release confirming they will be given the time; for an organization, board authorization or fiscal-sponsor documentation. A written commitment can clarify expectations, but it does not establish that someone will complete the program. Discuss practical barriers and available support.
In short: Unnecessary questions can discourage applicants. Justify each one, publish the real completion time, and remove the friction that quietly filters out the people you most want.
Before a field ships, ask whether the decision actually needs it; if not, cut it. Then design for access: a form that works on a phone, in more than one language, with save-and-return so no one loses an hour of work; alternative submission formats and a clear way to request an accommodation; and an honest look at whether the documents you require — audited financials, a formal reference — quietly disadvantage early-stage or less-resourced applicants. Burden is not neutral; it changes who applies.
Decide your weights up front and publish the criteria and weights. Publishing the rules helps applicants understand the evidence needed and gives reviewers a shared reference. Treat it as a stated rule of engagement, not a black box. If an answer misses the requirement, distinguish an access problem or unclear instruction from a substantive gap before judging the applicant.
Here is a fictional teaching example: a community-health grant with a $395,000 award per neighborhood collective. The amount, criteria and scorecards illustrate the method; they are not presented as a verified customer or published funder case. An RFP is really just a series of questions, and every question is already one of the three types:
In the configured illustrative workflow, submissions are checked against the gates before a review score is prepared. Human reviewers verify uncertain evidence. Two Collectives, two outcomes:
Every criterion needs three things: a weight, the evidence that feeds it, and a scoring scale with written anchors describing what a 5 looks like versus a 3. Without written anchors, reviewers may apply different standards. Pilot the rubric before launch and document its version. Do not quietly change scoring rules after seeing applicants. If a correction is necessary, record the reason, communicate it where appropriate, and reassess all affected applications consistently.
Lock the shape early, because it changes both the form and the timeline. Is it application-only, or application → recommendation forms → a shortlisted round of video interviews before final selection? A short interview stage before you commit is common and worth deciding now, not mid-cycle.
In short: Publish a simple end-to-end timeline, and decide up front exactly what applicants hear at each step.
Attach dates to each stage and put them on the page. Then decide the messages: a confirmation the moment they submit, a reminder before the deadline, a prompt if something is missing, and — the one teams skip — a timely, respectful decline for everyone you do not select. How you tell people no is how they remember you.
And the award record doesn’t close at signing. In this fictional example, implementation and evaluation run for two years, followed by a post-project sustainability review — so the same record has to stay audit-ready long after intake, not get rebuilt from scattered files each reporting cycle.
It is tempting to require nominations to hold volume down. A nomination-only requirement can disadvantage qualified applicants who have less access to established networks — often the very ones you most want — and AI does not remove the need for reviewer capacity, support, and appeals. Choose an open or nominated route based on the program purpose, and explain the rationale. Applications missing required eligibility information are flagged before scoring; missing evidence in scored sections is handled according to the published rubric — but completeness alone is not evidence of motivation or future performance.
In short: A rubric only holds if reviewers use it the same way. Decide the governance up front: who reviews, how conflicts are handled, and how disagreements resolve.
Brief reviewers on the anchors so a 4 means the same thing to everyone; require anyone with a personal or professional tie to an applicant to recuse; and consider blind review — names and identifying details hidden — for the first scoring pass. For high-stakes decisions, use at least two reviewers per application; for very large pools, apply dual review to shortlisted, borderline, or randomly sampled applications while monitoring agreement across the whole process. Write down how you break ties, when a score can be overridden, and how that override is recorded. If you allow appeals, say so before you open. We go deeper in How Do You Review Applications Without Reviewer Bias?
The Hult Prize publishes a real example of judges scoring individually, deliberating, and reaching a shared decision. This supports the distinction between a score and a final decision; it does not establish that a particular rubric or AI system is fair.
Put it in writing for your committee and your applicants: AI scores against your rubric and surfaces the evidence; people select. The output is a curated, ranked pool with cited scorecards that the committee reviews and decides from — never an AI verdict. That line is both good practice and good governance.
Test for fairness before launch, too. Compare AI-assisted scores with independent human review across different applicant groups, languages, and submission formats; investigate any material differences and document any change you make to the rubric or scoring instructions. “Humans decide” is necessary but not sufficient — the scoring itself has to be checked.
For a broader review of AI risks, consult the NIST AI Risk Management Framework. It is voluntary guidance for considering trustworthiness during AI design, use and evaluation. It is not a grant-scoring certification. The practical recommendation here is to test the proposed workflow in its own context and document what remains uncertain.
In short: Applications hold résumés, proposals, demographics, references, and other sensitive data. Decide who can see it, how long you keep it, and whether it can be reused — before you collect a single response.
State plainly who on the committee can access which fields, set a retention period and delete on schedule, and be explicit if you intend to keep non-selected applicants on file for future rounds — with their consent. Document the applicable privacy and retention requirements with your organization’s responsible staff. Collect only what the stated decision requires.
Draft the rubric first, with or without an approved AI tool. Start with a small, varied set of consented or de-identified submissions, then expand testing across borderline cases, formats and languages before launch. Real applications can expose issues that a tidy example misses; a pilot can reveal unclear criteria and missing evidence, and the pilot is where you fix it. Calibrate by having your committee score the same few blind and comparing against the AI.
In short: The same loop, in one place — collect clean at the source, analyze each application the moment it lands, then chat with the whole round: rank, compare two applicants side by side, or ask any question and get an evidence-cited answer.
A fixed rubric and source citations support review, but teams still need to test consistency and verify each important interpretation — you can trace any number back to the sentence behind it, the difference between a defensible pool and a black box.
It is not a one-time transaction. Give every applicant a persistent record, run a short baseline survey after selection to match teams or plan support, and invite unsuccessful applicants to opt into future communications, separately from their application. Follow the stated retention policy; a persistent record is not permission to retain sensitive data indefinitely.
Continue the youth-program example from chapter 1. The program wants sustained participation, not only registrations. Before asking for another essay, identify the decision that the answer would change.
| Decision | Question or evidence | Role | Review rule |
|---|---|---|---|
| Is the proposed work eligible? | Which locations will the program serve? | Eligibility | Compare with the published service area. Hold unclear answers for clarification if the rules allow it. |
| Is the participation plan credible? | Describe likely attendance barriers, proposed support, and evidence informing the plan. | Scored criterion | Assess the evidence and feasibility against written anchors; do not reward polished prose by itself. |
| Can the award be followed into reporting? | Applicant ID, program ID and contact details | Record identification | Use for matching, communication and reporting. Do not add merit points. |
| Can reviewers interpret later results? | Proposed participation measure, denominator and collection method | Measurement readiness | Check whether the applicant can define and collect the measure. Agree on the final definition at award. |
Test it: ask two reviewers to score the same sample response independently. If one interprets “participation” as registration and the other as repeated attendance, clarify the definition before opening the round. A narrow score spread does not prove fairness; both reviewers could share the same mistaken assumption.
Before moving on: every scored field should point to a criterion, every criterion should name its evidence, and each missing-information rule should specify whether staff may clarify, hold, or reject. Keep ineligible, incomplete and low-scoring applications as different states.
Once your criteria are set, these run in the Sopact Sense Assistant — or any AI working over your application data:
Read [Collective]’s full submission — the structured roster, the narrative engagement and equity answers, and the uploaded charter — and produce a review packet scored against our 100-point rubric (Collective 20 / residents 15 / engagement + data 30 / priorities 15 / impact + equity 20). Grade it green/amber/red, cite the sentence behind each score, and flag any eligibility gate that isn’t met. Do not infer facts that aren’t in the submission.
Review [Collective]’s submission. If the fiscal-sponsor designation, the evaluator agreement, or the engagement narrative is missing or too vague to score, draft a clarification email requesting exactly what’s missing, and flag it for my review before sending.
Before testing, remove unnecessary personal data from samples, use an approved environment, and document what reviewers will verify. AI output is a draft assessment, not a funding decision.
Ten stages: (1) define the decision and the applicant; (2) set eligibility rules; (3) choose scored questions, tracked fields, and required documents; (4) design for low burden and access; (5) lock the timeline and stages; (6) build the rubric and publish weights; (7) set reviewer roles and conflict rules; (8) pilot on real submissions; (9) communicate with applicants throughout; and (10) select, notify, and retain records responsibly.
Eligibility criteria are pass/fail requirements — geography, tax status, organization type, age, a required document — checked before anything is scored; miss one and the application does not compete. Selection criteria are the weighted evidence — essays, proposals, résumés, closed-ended answers — used to rank the applicants who clear eligibility. Keeping them separate makes the score easier to interpret: no one is scored down for being ineligible; they simply never enter the ranked pool.
Score the fields that carry evidence of fit — essays, proposals, pitch decks, résumés, recommendation letters, and closed-ended questions — by running each through a rubric that turns it into a weighted number. Written anchors and source citations help reviewers inspect the reasoning. Test consistency rather than assuming identical inputs guarantee identical AI scores. Fields like name, email, and location are metadata — they track the application, dedupe records, and drive filters and disaggregation, and do not add merit points when used only for identification or reporting.
Only as long as the decision requires. Unnecessary questions can discourage applicants, so justify each field against a criterion or a filter you will actually use, cut the rest, and publish the real completion time so applicants can plan. Length is a cost, not a signal of rigor.
Drop questions the decision doesn’t need, make the form work on a phone and in the languages your applicants speak, add save-and-return, and offer an accommodation path. Watch for required documents — audited financials, formal references — that quietly disadvantage early-stage or less-resourced applicants.
Publish the criteria and their weights — it helps applicants understand what will be assessed. Whether to publish the detailed scoring anchors is a judgment call: publishing adds transparency for public or high-accountability programs, but it also lets applicants write to the anchors without supplying stronger evidence. Decide based on your transparency requirements and that risk.
For high-stakes decisions, use at least two reviewers per application so you can measure agreement and catch outliers, and brief them on the anchors so a 4 means the same thing to everyone. For very large pools, apply dual review to shortlisted, borderline, or randomly sampled applications while monitoring agreement across the process. Blind review — hiding irrelevant identifying details on the first pass — can address some identity cues, but it does not remove all bias and can conceal context that matters, and anyone with a tie to an applicant should recuse.
Draft the rubric and pilot it on a varied set of consented or de-identified submissions. A small initial pilot is a usability check, not statistical proof of fairness. A pilot can reveal unclear criteria and missing evidence; the pilot is where you fix it. Calibrate by having your committee score the same few blind and comparing against the AI, and check for systematic differences across applicant groups, languages, and formats.
State the real time, travel, cost, and reporting commitment and make applicants acknowledge it, and where relevant require written confirmation — an employer release for an individual, board authorization for an organization. Clear commitments help applicants plan. They do not remove barriers such as care responsibilities, transport, or changes in employment; discuss support and track withdrawals to learn what actually matters.
Use AI to score every application against a fixed, published rubric and to surface the evidence sentence behind each score — then have people make the decision. AI should produce a ranked, cited pool a committee reviews, never a final verdict. Before launch, compare AI-assisted scores with independent human review across applicant groups, languages, and formats, investigate material differences, and document any change to the rubric; a documented human override keeps it accountable.
Bring your application, eligibility rules, rubric and a few sample submissions. Work through the review process with Sopact.
Explore Applications & Grants →
