How it works
The network is deliberately modular: organisations own their listings; the regional hub aggregates; volunteers interact through a single phone-friendly join flow.
Three layers
The system stacks cleanly:
- Organisation hub — /join/{your-slug} lists your projects and days.
- Regional aggregator — /join/bop shows participating hubs filtered by rohe and locality.
- Join flow — /join/{slug}/{code} captures name, mobile and optional email; project days add roster RSVP.
Publish workflow
Coordinators use workspace admin at Community → Volunteers. Publish a year-round project or schedule a volunteer day, optionally link the day to a project roster, then share the short URL or QR poster. Subscribers receive push notification when new listings go live.
Notifications
Volunteers can subscribe per hub or to the regional BoP channel. Web push alerts fire when new opportunities are published. Roster days can use copy-ready SMS text for groups not yet on push.
Governance
Platform admins maintain a hub registry (suspend/restore), refresh the regional directory, and ensure regional quality. Organisations retain editorial control of their own listings.
Common questions
- What is OSVector's role?
- Infrastructure: auth for coordinators, data storage, notifications, publish flows and regional aggregation.
- Can one day belong to a project?
- Yes — linked days prompt roster members to respond yes or no instead of open public sign-up.
- Where is data stored?
- In the organisation's OSVector workspace database with standard access controls.
Volunteer view: For volunteers
Ready to volunteer?
Browse live opportunities across the Bay — filter by district or town, join year-round projects, or sign up for a community day.
Browse opportunities