Verification is what makes Yura hours trustworthy. Every log goes through a clear lifecycle that protects both volunteers and organizations.
The lifecycle
- 1
Submitted (Pending)
The volunteer creates a log. It appears in the organization's approval queue. The volunteer can still edit or delete it at this stage.
- 2
Reviewed
An Owner, Manager, or Coordinator opens the log, reviews the details (date, hours, description, custom fields), and decides.
- 3
Approved (Verified)
The log becomes Verified — read-only for the volunteer, but editable by the org with every change logged in the audit trail.
- 4
Locked (after export)
Once included in an exported report or end-of-period checkpoint, the log is Locked. Any further edits require a written reason that's captured permanently.
Locking prevents retroactive changes to reports that may have been shared with funders, schools, or grant committees. It's the last layer of accountability.
If you're volunteering through a school, your school admin or assigned teacher is typically your verifier for school-affiliated hours. Hours logged with outside organizations go through the external supervisor email flow.
What happens on rejection
If a verifier rejects your log, the rejection reason appears on the log detail. Fix the issue (wrong date, incorrect hours, missing description) and resubmit the corrected log — don't create a duplicate.
Always write a specific rejection reason. 'Hours don't match event duration — you RSVPed for 2pm-4pm but logged 6 hours' is actionable. 'Rejected' with no reason leads to confused resubmissions.