Reach ConsoleManagement & operations
Board prototype. Counts below mix published historical Reach scale with clearly illustrative operational records. Organisation reviews is a connected workflow for authorised staff; the other sections remain demonstrations.
Service manager workspace · service queues and reporting
Connected service demonstration
Interactive demonstration
Fictional people and organisations. Progress stays in this browser tab. No real applications, payments, messages or automated checks are sent.
Today at Reach
Run the service from exceptions, not spreadsheets.
The normal path is automated and auditable. Staff spend time where judgement, support or risk actually needs a person.
Core workflows healthyIllustrative status · not live monitoring
Human exception queue
Open full queueWhat actually needs somebody today
What needs watching
96.4%example organisation response coverage
4.1 daysmedian example application resolution
89%example opportunity records complete
0automated safeguarding decisions
Today’s handover
- Finance-volunteer demand is above available supply.
- 17 organisation profiles need accessibility details reconfirmed.
- One partner feed has three failed records awaiting retry.
People management
Manage a national member base without opening profiles one by one.
Fast indexed search, saved segments, bulk lifecycle actions and restricted personal-data views.
Saved views:
| Member | Status | Skills / evidence | Current roles | Last active | Trust | ||
|---|---|---|---|---|---|---|---|
| Amelia StoneRV-104982 · London / Remote | Available | UX · WordPress · Accessibility2 verified placements | 2 4–6 hrs/week remaining | This week | Trusted collaborator | Open | |
| Daniel BrooksRV-092113 · Manchester / Remote | Trustee-ready | Finance · Risk · Governance1 verified board role | 1 4 hrs/month | 3 days ago | Board Ready | ||
| Priya MehtaRV-118021 · Remote | Building experience | Writing · Canva · Socialportfolio evidence | 0 | Yesterday | First Step |
Organisation management
Verification, recruitment quality and service history in one record.
Registered charities can clear routine checks automatically; community groups take a proportionate evidence path.
| Organisation | Verification | Response | Live roles | Access info | Reports | Last active | |
|---|---|---|---|---|---|---|---|
| Northside Community Food NetworkGreater Manchester · sample | Verified charity | 96% 2 days typical | 3 | Current | 0 | 2 days ago | View |
| Community Garden CollectiveGrassroots example | Needs review | New | 0 | Partial | 0 | Today | |
| Example Youth TrustNational · sample | Verified charity | 92% 3 days typical | 4 | Current | 1 closed | Yesterday |
Marketplace control
Opportunities, applications and placements as state machines.
Staff manage exceptions and quality. The platform handles normal transitions, reminders, expiries and completion prompts.
1Draftquality checks
2Publishedsearch + matching
3Applications7 / 14 / 21 timers
4Placementagreed scope
5Completeevidence + reference
Before publishing
- Outcome described
- Time commitment present
- Named contact
- Accessibility information reviewed
- No discriminatory eligibility text
- Closing date sensible
Clean records publish without staff touching them.
Applications do not rot
- Day 0 Acknowledge both sides
- Day 7 Friendly reminder
- Day 14 Stronger prompt
- Day 21 Role visibility warning
- Repeat Human exception
Close the loop
- Confirm participation
- Capture agreed outcome
- Verify skills used
- Offer reference prompt
- Update badges / evidence
- Ask both sides for feedback
Support workspace
One inbox for service questions, with context already attached.
Staff should not ask people to repeat their account, application and organisation history when Reach already has it.
Ticket R-20418
SLA healthyApplication hasn’t had a reply
Member: Sam Taylor · Application: Community newsletter review · Organisation: Northside
Applied 8 days agoAutomatic reminder sent yesterdayOrganisation response rate 96% example
Sam
I just wanted to check whether I need to do anything else.
Restricted workspace
Restricted by capabilityTrust, safety and moderation stay human-led.
Automation can route, deduplicate and assemble evidence. It does not decide safeguarding outcomes or serious sanctions.
Open restricted cases
Case TS-1042Safeguarding · assigned lead only
HighCase TS-1041Disputed organisation restriction
AppealCase TS-1037Repeated volunteer no-show reports
PatternControls
- Case access logged
- Original evidence preserved; changes are audited
- Reporter identity restricted
- Appeal route available
- Sanctions require authorised role
- Automation cannot close safeguarding cases
Inkfire platform operators can maintain the case system without default access to case content.
Content management
Open inline editing demo Edit Reach in context, not through a maze of CMS fields.
Content editors can work on the actual page. Structured service data keeps controlled fields separate from editorial copy.
About Reach
Skills, people and organisations creating change together.
Reach connects people who want to use their skills with charities and community organisations that need them.
Inline editable Content editor can change this copy and save a draft.
Impact figure · 5,996 placementsStructured data · requires Impact Manager capability
Deterministic automation · design
Rules, timers and queues. No AI dependency.
The schema and queue storage exist; the production worker, retry executor and lock recovery are not implemented yet. These cards show the intended rule model.
Application response remindersWhen application unresolved → day 7 / 14 / 21 sequence → exception on repeated failure
624 this weekOpportunity expiryClosing date passes → unpublish → notify organisation → preserve reporting record
118 this weekAvailability reconfirmation3 / 6 / 9 month lifecycle → member choice → temporary search hide if not reconfirmed
326 dueReference promptPlacement completed → ask organisation → volunteer reviews wording → optional sharing
60 this weekPartner feed deliverySigned feed batch → retry 3 times → dead-letter queue → platform operator
3 failedIdempotency is a worker requirement
When the worker is implemented, retries must not send duplicate emails, duplicate placements or apply the same restriction twice.
Dead-letter is the intended failure path
The worker should move exhausted jobs into an operator queue with the original payload and error rather than silently dropping them.
Management information
Measure what makes Reach sustainable.
Service quality, volunteer outcomes, supply/demand and staff workload should be visible without spreadsheet archaeology.
96.4%
Example coverage12
from 1,482 routine example actions87 : 22
example roles : peopleBoard dashboard
- Cost per placement
- Active volunteer retention
- Organisation response quality
- Supply shortages by skill
- Support demand per 1,000 members
- Exception volume by workflow
Service manager dashboard
- Queue age and ownership
- Overdue applications
- Verification backlog
- Restricted cases by SLA
- Failed automation jobs
- Accessibility-support requests
Inkfire platform operations
Technology roleOperate the machine without becoming Reach’s service team.
Technology operations are separated from charitable decisions and restricted case content.
Application
- Release health
- PHP errors
- API latency
- Search-index lag
- Cache hit rate
Jobs & integrations
- Email retries
- Regulator lookups
- Partner feeds
- Analytics pipeline
- Dead-letter queue
Continuity
- Backup evidence
- Restore tests
- Incident log
- Security patches
- Rollback readiness
Access boundary
Platform operators can see service health, record IDs and technical errors. Safeguarding narratives, private health information and confidential moderation evidence require an explicit Reach-granted capability.