The award amount is easy to spot on a CV. The work behind it is harder to see. A reader may know you received funding without knowing what you were responsible for, what the project produced, or whether the promised outcomes have been examined yet.
The book's mid-tenure example describes a funded professional development initiative and includes the grant application and approval as supporting records. That gives you a starting point. A useful review account goes further by separating the award, the work completed, and the evidence of any effects.
Identify the project and your actual role.
Use the official project title, funder, relevant dates, and your documented role. Distinguish a principal investigator role from a co-investigator, collaborator, evaluator, or other responsibility. If an amount is reported, make clear what it represents under your institution's reporting rules.
Don't imply that a total team award is your personal funding share or that the amount measures your individual contribution. For a multi-person project, a concise explanation of your responsibilities helps readers understand what you actually did.
The status matters too. An application, an approved award, and an active project aren't interchangeable. Use the stage supported by the record as of the review period.
Explain the problem the project addresses.
What need motivated the work? What was the intended contribution? Keep this explanation focused enough that someone outside the project can follow it. You don't need to paste the entire grant abstract into the narrative.
For a hypothetical teacher development project, the need might concern a specific classroom practice. Describe that need and the project's planned response. Don't jump straight from “we offered workshops” to “we improved student outcomes.” Several steps sit between those statements.
Show the work completed during the period.
Identify the relevant activities and deliverables. Perhaps you developed materials, coordinated partner meetings, implemented a training series, or completed a planned evaluation report. Use records that support the account and are appropriate to share.
Give collaborators and community partners credit. If your contribution was to design an assessment or analyze project data, make that clear rather than describing all project activities as if you personally led them.
When work is delayed or still underway, say what stage it reached and what comes next. A transparent account of progress gives reviewers more useful information than an inflated statement that the project has already fulfilled its entire purpose.
Keep outputs and impact distinct.
A completed resource is an output. Participation records can show who took part. Evidence of a change in practice or learning requires an appropriate assessment of that change. Funding alone doesn't establish any of those results.
If you report feedback or outcome information, explain its source and limits. A participant's positive comment can illustrate an experience without demonstrating a broad or lasting effect. Don't claim the grant caused an improvement unless the evidence supports that conclusion.
Before drafting the grant section, make three short lists: what was awarded, what you contributed during the review period, and what evidence exists about the results. Add a fourth line for unfinished work. That structure will help you write a clear account of the project without asking the award amount to explain everything.
Adapted from The New Faculty Handbook by Zafer Unal, chapter 16, pp. 286–288.
