Review works best when everyone understands what the decision means. In HelpHours, acceptance includes the current self-reported revision in one journal total. It does not certify the volunteer, prove attendance, or establish an official record. A short written policy and a calm pending queue are usually enough for a trusted community group.
Define what accepted means before submissions arrive
Write one plain rule for the journal, such as “include time spent on the listed cleanup activities during this date range.” Avoid words like verified, certified, approved service, or official credit unless an external process actually provides that assurance.
Review the pending queue in a predictable cadence
Tell volunteers when review normally happens and keep pending entries visible to the manager. Check the service date, duration, activity label, and optional note against the event context. A pending entry contributes zero until the manager decides.
Accept or reject the current revision, not the person
The decision belongs to one entry revision. Reject an unclear or out-of-scope report without turning it into a judgment about the volunteer. The receipt holder can correct the entry and return it to pending for another review.
Treat possible duplicates as a question, not an identity match
Similar names, dates, and durations may deserve a closer look, but they do not prove duplication. HelpHours allows duplicate names because it has no accounts and does not infer identity from IP addresses, cookies, or browsers. Use the activity context and ordinary group communication when clarification is needed.
Keep notes minimal and avoid sensitive explanations
Store only a recognizable name and the activity detail needed for this journal. Do not put medical, safeguarding, immigration, employment, or disciplinary information into notes. If a rejection requires a sensitive conversation, handle it outside this lightweight journal.