Back to the concept hub
Build Experience · proposed new pathway

Use a real project to build credible, recent evidence of what you can do.

Reach already connects experienced people with charities that need their skills. Build Experience adds a second route for people who have capability but need recent evidence, confidence, a reference or a supported way back into work.

Concept pathway: this is not a live Reach service and does not imply a current DWP, council or employment-provider partnership.

Where it fits

Build Experience adds a new doorway. It does not replace skilled volunteering.

The clearest model is two routes into the same Reach marketplace, with different eligibility and outcomes.

Existing Reach strength

Skilled Volunteering

For experienced professionals and trustees who already meet Reach's established skills-based volunteering criteria.

  • Professional experience already evidenced
  • Volunteer roles, projects and trustee opportunities
  • Use expertise to strengthen charities
  • Existing Reach proposition remains intact
NEW

Build Experience

For people who can contribute but need a current opportunity to demonstrate capability and create evidence.

  • No three-year professional threshold
  • Well-scoped supported projects
  • Working-style preferences built into matching
  • Verified experience and references on completion
End-to-end workflow

One simple journey from capability to credible evidence.

The new pieces only make sense if they connect. This is the full proposed journey from joining Reach to whatever comes next.

  1. 01
    New entry route

    Create a capability-first profile

    Start with skills, interests, availability and the kind of environment that helps the person do good work. Employment history can add context, but it is not the gatekeeper.

    SkillsGoalsAvailability
  2. 02
    Better matching

    Match on how the person works best

    Practical preferences become searchable without requiring a diagnosis or medical disclosure.

    RemoteAsyncFlexible hoursLow meetingsClear written briefsVariable capacity
  3. 03
    Real charity need

    Choose a genuinely useful project

    The organisation defines a clear outcome, realistic hours, named contact and practical support. It is real work for a social-purpose organisation, not manufactured training.

    Clear scopeNamed contactDefined duration
  4. 04
    Supported delivery

    Complete the project with sensible support

    Reach can make expectations explicit before the project starts, while the organisation provides feedback and a realistic communication rhythm.

    Mentor optionalCheck-insAccessible communication
  5. 05
    New outcome step

    Verify what was actually completed

    At the end, both sides confirm participation. The organisation records the outcome, duration and skills demonstrated instead of the placement simply disappearing into history.

    Outcome verifiedSkills confirmedHours / duration
  6. 06
    Durable evidence

    Add a Verified Reach Experience record

    The person's profile gains a persistent project record, verified skills, an optional portfolio link and a reference where the organisation provides one.

    Verified recordReferencePortfolio evidence
  7. 07
    Optional progression

    Use the evidence for the next step

    That next step might simply be another volunteering project. For people who want employment progression, it could also lead to mentoring, an interview, training, a supported placement or paid work when appropriate.

    Volunteer againMentoringInterviewPaid work when ready
What changes around the platform

The pathway adds useful capabilities for every side of Reach.

These are the additions that make the workflow work rather than leaving Build Experience as a standalone landing page.

For the participant

Capability-first profile, working-style preferences, saved searches, verified experience and references.

For organisations

A project format with clear scope, support expectations, completion confirmation and reference prompts.

For Reach

Placement outcomes become structured data, enabling better matching, evidence and reporting without manual chasing.

For future partners

Universities, councils, disability organisations and employment-support providers could refer people into a measurable pathway.

How the wider Reach redesign fits together

Keep what people recognise. Improve the journeys around it.

Build Experience is only one part of the successor concept. The wider redesign preserves Reach's familiar brand, skilled-volunteering and trustee strengths, then makes the marketplace, profiles and signed-in journeys easier to discover and use.

Keep

Recognisably Reach

The Reach name, purple-led palette, yellow/green/magenta accents, illustration language, volunteer/organisation split, skilled volunteering and trustee recruitment remain the foundation.

Reach identitySkills volunteeringTrusteesHuman stories
Improve

Less hunting. Better matching.

Search becomes more prominent, signed-in areas become task-led, organisations are accountable for responses, and people can match on practical working conditions rather than diagnosis.

Faster searchWork styleResponse dataBetter profiles
Add

New routes without changing the mission

Build Experience, verified evidence, accessibility support, grassroots verification, membership, partner distribution and lean automation extend Reach without turning it into a generic jobs platform.

Build ExperienceAccessibilityVerified evidenceAutomation
Walk the new design

Open the journeys and see the changes in context.

Each prototype page starts from something Reach already does, then shows the additional information, accessibility, accountability or workflow the successor could add.

01Opportunity marketplace

Search with more useful context

Honours: Reach's skills, causes, location and opportunity search.
Improves: work-style, accessibility, verification and response information before somebody applies.

Open opportunity search
02Opportunity detail

Know what the role is really like

Honours: Reach's detailed role and organisation information.
Improves: working style, access information, response history, explainable matching and clearer expectations.

Open example opportunity
03Volunteer onboarding

Quick signup, richer profile later

Honours: Reach's simple volunteer account route.
Improves: progressive profile building, skills evidence, CV/LinkedIn-assisted setup, privacy and accessibility preferences.

Open volunteer profile builder
04Volunteer profile

Let experience travel with the person

Honours: Reach profiles and placements.
Improves: verified skills, references, profile status, working preferences, privacy controls and stories linked to real experience.

Open volunteer profile
05Organisation profile

Turn trust into something visible

Honours: Reach's organisation records and verification.
Improves: responsiveness, accessibility culture, live opportunities, stories, named adjustment support and public trust signals.

Open organisation profile
06Find people

Preserve Reach's two-sided marketplace

Honours: organisations proactively searching Reach volunteers.
Improves: evidence, availability, profile status and neutral work-style compatibility without exposing medical information.

Open organisation people search
07Accessible volunteering

Make inclusion usable, not decorative

Honours: Reach's public-benefit mission.
Improves: physical, sensory and communication information, private preferences and a clear Right to Try support pathway.

Open accessible volunteering
08Organisation workspace

Keep the familiar dashboard, strengthen the engine

Honours: Reach's existing signed-in dashboard pattern.
Improves: recruitment workflow, messaging, placements, references, membership, impact reporting and automated housekeeping.

Open organisation dashboard
Design continuity

Evolution, not a rebrand for the sake of it.

The concept deliberately reuses Reach's visual DNA and familiar user mental models. Inkfire's contribution is primarily product structure, accessibility, automation and interaction design, while Reach remains visibly and culturally Reach.

See the wider Reach + Inkfire concept
The wider proposal

A reduced-capacity rescue model that protects Reach's legacy.

Reach's Board has said the closure is about long-term financial sustainability, not a lack of demand or impact. This proposal asks a different question: can the core marketplace, trustee expertise, community, stories and learning survive in a leaner operating model rather than disappear with the current organisation?

01

Preserve what is valuable

Keep Reach's brand, skilled-volunteering proposition, trustee recruitment, marketplace logic, guidance, stories and sector relationships wherever transfer, consent and governance allow.

02

Operate at a smaller cost base

Move the application to a stack Inkfire can maintain directly, automate predictable lifecycle work and run a reduced service where paid staff focus on people, risk and relationships rather than repetitive administration.

03

Earn the right to grow again

Once the core service is stable, add organisation membership, employer programmes, partner distribution, Build Experience and public-benefit funding only where they strengthen the mission and economics.

The human touch stays

People handle the work that needs judgement and trust.

  • Safeguarding and complaints
  • Complex verification and grassroots exceptions
  • Volunteer and organisation support when something goes wrong
  • Trustee recruitment expertise and managed support
  • Funders, partners, communities and sector relationships
  • Governance, ethics and mission decisions
The platform handles the routine

Rules-based work should happen before it reaches a staff queue.

  • Regulator, domain and basic verification checks
  • Profile and opportunity expiry / re-confirmation
  • 7 / 14 / 21-day applicant-response reminders
  • Saved searches, alerts and recommendation refreshes
  • Placement completion and reference prompts
  • Routine reporting and exception routing
Governance model

Reach remains the mission. Inkfire becomes the technology steward.

Under the concept, Reach's trustees and leadership would retain mission, safeguarding, eligibility, partnerships and public-benefit decisions. Inkfire would be paid transparently for application development, hosting, security, accessibility, maintenance and platform operations. The technology partner should never control marketplace ranking, safeguarding decisions or charitable policy.

Why the economics could change

Reduce the fixed cost before asking fundraising to carry it.

The figures below are an illustrative board scenario, not a promise. They show the order of magnitude worth testing against Reach's actual invoices, payroll, support volumes and TUPE advice.

Published handover baseline:platform-related hosting/services of about £771/month, or £9,252/year. Reach's own handover material also describes staff salaries as the larger cost.
Published current example£771/mo£9,252 / year

Upsun, supporting AWS storage and Loqate in the published handover example.

Lean-stack scenario A£250/mo£3,000 / year

Illustrative engineering ceiling for core hosting/services, not a supplier quote.

Potential saving: £6,252 / year · about 68%
Lean-stack scenario B£150/mo£1,800 / year

A more optimised infrastructure scenario once real load and service requirements are known.

Potential saving: £7,452 / year · about 81%
Staffing sensitivity

Automation should reduce routine service work, not erase the service team.

The handover model describes a service / quality function of roughly 3.5 FTE plus three volunteers. That is not the charity's entire workforce. A reduced-capacity rescue could test whether routine automation lets Reach retain approximately 2.0–2.5 FTE of human service capacity while removing the equivalent of 1.0–1.5 FTE of repetitive administration.

Illustrative loaded employment cost£30k–£40kper FTE / year
Routine workload reduced1.0–1.5 FTEscenario, not a staffing decision
Potential staff-cost reduction£30k–£60kper year under those assumptions
Illustrative sensitivity only
£36k–£67k / year

Potential direct reduction from the platform scenarios above plus 1.0–1.5 FTE of routine service workload. This excludes any new membership, employer, partner or grant income.

Before this is used as a board forecast, replace the staffing assumption with Reach's actual payroll, pensions, NI, contractor costs, TUPE advice and measured support volumes. The point of the prototype is to show a credible cost-down mechanism, not to manufacture certainty.

The proposal in product form

Don't just describe the rescue. Show what people would actually use.

These are live previews of the current prototype. The board can open each journey and see how the proposal preserves Reach's core service while making it easier to operate, more accessible and more useful to volunteers and organisations.

Opportunity marketplace
Marketplace

Search is still Reach, but with better context.

Skills, causes and location remain. The redesign adds response quality, accessibility, working style and clearer verification before a volunteer commits time.

Open the marketplace
Opportunity detail
Before somebody applies

Make the real conditions of a role visible.

Hours, work style, accessibility, organisation responsiveness and matching reasons help people decide whether an opportunity genuinely fits.

Open the opportunity
Volunteer profile
Retain the value created

Placements become evidence instead of disappearing.

Verified experience, skills, references, profile states and privacy-controlled work preferences make the account more useful over time.

Open the volunteer profile
Accessible volunteering
Broaden who Reach can support

Turn accessibility into practical information.

Physical, sensory and communication conditions become visible, while private health information stays private and the human support route remains available.

Open accessible volunteering
A rapid rescue sequence

Cut the legacy cost base in weeks, not months.

The rescue target is a safe core-platform cutover within roughly 4–6 weeks once the Drupal code, database, files and decision-makers are available. The first release does not need every future feature. It needs the essential Reach marketplace to survive.

First 48 hours

Secure & freeze the knowledge

  • Take a complete Drupal code, database and private-files copy
  • Run an isolated reference copy with outbound email/integrations disabled
  • Identify the services creating the largest ongoing cost
  • Confirm data-controller, transfer and governance authority
  • Lock the must-survive journeys for cutover
Week 1

Map only what must survive

  • Document volunteer, organisation, opportunity, application, message and placement relationships
  • Map permissions, privacy rules and critical staff actions
  • Create the migration ledger and cutover acceptance tests
  • Separate essential behaviour from legacy complexity
  • Start repeatable import tooling immediately
Weeks 2–3

Build & rehearse the core

  • Implement accounts, profiles, organisations, opportunities and search
  • Implement applications, messages and placements at minimum viable depth
  • Run full migration rehearsals against copied Drupal data
  • Test ownership, private access and real user journeys
  • Keep enhancements out unless they are required for safe launch
Weeks 4–6

Cut over & switch costs off

  • Parallel-check the old and new systems against agreed scenarios
  • Run the final delta migration and account transition
  • Train the reduced human support team on exception handling
  • Go live with rollback and monitoring in place
  • Retire avoidable legacy infrastructure as soon as evidence allows
After the rescue:Build Experience, advanced accessibility, membership, partner distribution, employer programmes and deeper automation can then be released incrementally without keeping the old platform alive while we perfect them.
The goal

Reach may need to become smaller. It does not need to become invisible.

The first success criterion is not feature parity. It is preserving a safe, usable marketplace quickly enough to stop unnecessary legacy costs while keeping the human judgement, relationships and community trust that made Reach valuable. Once the core is safe, the successor can improve in public rather than rebuild behind closed doors for a year.

What the person leaves with

An evidence record, not just a completed placement.

This is the biggest product difference. The value of the project stays attached to the person's Reach profile and can strengthen future volunteering or employment applications.

Open the demo volunteer profile
Verified Reach ExperienceWebsite accessibility reviewExample Youth Trust · 8 weeks
WordPressWCAGContent audit
Outcome verified Reference available Skills confirmed
Important boundaries

Progression should never become disguised free labour.

Build Experience is a charity/community project pathway. Where a commercial employer has a real role, the destination should move toward paid work rather than keeping somebody indefinitely unpaid.

  • Volunteering remains voluntary and valuable in its own right
  • Commercial employers do not receive an indefinite source of unpaid labour
  • Health or disability disclosure is not required for practical working preferences
  • Future employment-support reporting must distinguish volunteering from paid-work outcomes
Example Build Experience project

Digital content sprint

6 weeks · flexible

A small environmental charity needs help turning technical reports into six clear public-facing stories. Most work can be completed asynchronously, a mentor checks in weekly, and the organisation verifies the project and provides a reference at the end.

WritingContent designRemoteAsync-friendlyReference included

Start smaller with Micro Experience

Two hours to one week. Clear scope, flexible pacing and a reviewed outcome.

Explore Micro Experience