Your CV says you served on the committee for two years. You remember the work clearly: reading proposals, revising a process, and following up when decisions stalled. The reader sees only the committee's name.
The handbook urges faculty to distinguish meaningful contribution from a bare membership list. An accurate account helps someone assess what the role involved without making the work sound larger than it was.
Describe the responsibilities you actually carried
What were you asked to do, and what did you complete? Explain preparation, analysis, drafting, coordination, or implementation where relevant. Include the dates and scope so the reader can interpret the commitment.
Use the reporting rules that apply. Don't decide that a label automatically makes an activity reportable or unreportable everywhere.
Separate contribution from selection
Being elected, appointed, invited, or volunteering can provide context. It doesn't by itself describe the work that followed. State the selection route accurately where useful, then explain the contribution.
A modest title can involve substantial work, while a prominent appointment may have had limited activity during a particular period.
Report outcomes at the right level
If the group produced a report, recommendation, event, or revised procedure, identify it and explain your role. Don't claim the team's whole achievement as your own.
If the project didn't reach completion, describe what happened and the stage reached. An intended result is different from an implemented change.
Give newer forms of work a clear explanation
Digital resources, professional discussions, or other less familiar activities may need context about purpose, audience, responsibilities, and evidence. Follow the local criteria rather than assuming novelty either guarantees or prevents recognition.
Use a short evidence check
For an important claim, ask what record supports it and whether you may appropriately retain or share that material. Avoid exposing confidential committee information, personnel matters, or private participant details.
Evidence should clarify the contribution without creating a new privacy problem.
Use a specific work product to recover the contribution
Take a completed report or recommendation you're permitted to consult. What part of the process did you support? Perhaps you compared alternatives, drafted a section, coordinated feedback, or helped implement an agreed change. Describe that part rather than claiming everything the committee ultimately produced.
If the output doesn't reveal individual roles, a short factual note can preserve the context while it is fresh. Follow the applicable rules for retaining information. You don't need to collect confidential deliberations to explain that you completed an assigned task.
Check the claim against the stage reached. A recommendation can be completed even if implementation is still pending. A revised process can be in use without evidence yet about its longer-term effects. Those distinctions let you give appropriate credit to the work without turning an unfinished outcome into a completed success. The reader needs an accurate account, not a larger adjective attached to a committee name.
Rewrite one service entry in three parts: role and dates, work completed, and result or current stage. Compare that description with the supporting record. You'll have a stronger entry because it helps a reader understand the work, not because it adds more adjectives.
