Start with the contribution, not the badge
Say what you can actually do: review a source, translate a bounded page, test accessibility, document a local need, contribute code, write learning material, support an approved project, provide a verified opportunity, or help organise a defined activity. Do not begin by assuming a formal role.
Define scope and commitment
Specify the deliverable, time window, owner/reviewer, dependencies and what success would look like. Small commitments that can be reviewed are safer than indefinite promises.
Bring evidence, not a self-awarded title
If relevant, provide examples of prior work, qualifications, portfolio evidence, references or source expertise. Evidence supports the contribution; it does not automatically create authority beyond its scope.
Permission before public recognition
A contribution may remain private. Public name, photo, contact, role wording, biography, quote, organization, location or recognition should require separate permission and evidence.
Evidence after contribution
Record what was agreed, what was delivered, evidence, review outcome, corrections and recognition/publication status. Recognition should reflect verified contribution rather than planned contribution.
Reflection
Questions to sit with
- What can I deliver in one bounded contribution?
- Who would need to review or accept it?
- What should remain private even if the contribution is accepted?