The platform powering Connected Funding

The Connected Journey, in product form.

Everything below is live in the product today — each area one stage of the same journey, working the same shared record. The theme throughout: information that stays connected instead of being re-keyed, and a record either side can verify without taking anyone's word for it.

Programme designApplicationAssessmentAwardDelivery & evidenceReportingImpact

Winning the money

Programmes, applications & assessment

The funder dashboard's programme pipeline: outcomes donut and received-versus-awarded trend
The pipeline at a glance: received, in assessment, awarded, unsuccessful — and how the round moved month by month.
  • Programme designerbudget envelope, award range, windows, machine-readable eligibility, per-stage questions and weighted criteria — with a design review that flags applicant burden and unassessable stages before you publish.
  • Open application linka charity that has never seen GrantOS applies through one URL, creating its account and organisation as it goes — email-code verified, authenticator secured.
  • Eligibility in minutes, not after the deadlinerules checked live against the applicant's passport and answers; unknowns show honestly as needs-review, never a silent pass.
  • Two-stage EOI → fulla short expression of interest sifts the field before anyone writes the full form; invited applicants continue on the same record.
  • Assessment on the recordfrozen, hashed submissions; conflict-of-interest declared before an application unseals (and applicant-org members refused automatically); side-by-side weighted scores; every decision carries its rationale.
  • Award → live grant, one clickconditions register, milestones, reporting calendar and payment schedule minted from the design plus the application. The charity accepts the award by confirming the record.

The agreement

Grant setup & the conditions register

The funding conditions register grouped by category, with live rule checks showing conditions being met or breached
Every string attached to the money: its source clause, its consequence, who owns it — and whether it's being met right now.
  • 10 grant archetypes, 21 overlays, 12 funding regimesrestricted project, capital, multi-year, research, consortium, outcome-based and more — each generating its own compliance shape, proportionate to size and risk.
  • Machine-readable conditionsevery string attached to the money with its source clause, owner, deadline and — crucially — the consequence of non-compliance stated up front.
  • Live rule-linked conditionsconditions tied to the rules engine show being met or being breached right now, from real spend and delivery data.
  • Payment-gating conditionsa condition can block a payment, depend on another, and attach to a specific instalment — surfaced on decisions, never blocking the recording of reality.

The money

Finance without payment rails

The charity home dashboard: portfolio by status, money in versus spend recorded, outstanding actions and upcoming deadlines
Money in vs spend recorded across the whole portfolio — with every exception one click from the record behind it.
  • Payment scheduleexpected instalments with triggers — signing, report acceptance, milestones, retention release — receipts recorded by the charity, shortfalls visible.
  • Deterministic compliance checksout-of-window, over-budget-line, possible duplicate, missing evidence — explainable rules, re-run when the baseline changes.
  • Burn & pacingwindow-elapsed versus spend drift surfaces before it becomes a clawback conversation.
  • Review signals, not accusationsgrant-level patterns — round numbers, supplier concentration, end-loaded spend — framed as prompts for the charity to get ahead of.

The work & the proof

Delivery, outcomes & evidence

The delivery tab: milestone donut and measured outcomes with confidence ratings and attribution notes
Outputs delivered, outcomes measured — each with its method, a confidence rating and an honest attribution note.
  • Activity logdate, venue, headcount, evidence; unapproved venues flagged; late logging marked backdated, honestly.
  • Outcomes with honest attributionoutputs (sessions run) separate from outcomes (what changed); every measurement carries its method, a confidence rating and an attribution note.
  • Write-once evidence, SHA-256 hashedintegrity re-verified on every download; withdrawal and replacement happen on the record.
  • Upload once, evidence manyone attendance register can support a milestone, a condition, a report and an outcome — the single biggest burden-killer for charities.

When reality diverges

Changes, risks & questions

Change requests with pending and approved decisions, above a shared risk register with likelihood and impact ratings
Changes decided on the record, and a risk register both sides can see coming — “we told you in March” becomes a link, not an argument.
  • Variation requestsvenue, budget, timeline, scope — the funder's written decision versions the baseline; agreed tolerances say what may flex without asking.
  • Shared risk registereither side raises risks with probability, impact, mitigation and what to watch for. “We told you in March — here's the record.”
  • Questions on the recordthe in-app replacement for the email chains grant disputes are made of; only the side that asked can close a question.

Telling the funder

Reporting & the audit pack

The reporting calendar showing an accepted report, a submitted report and a due report, with frozen hashed snapshots below
The reporting calendar: accepted, submitted, due — and every report a frozen, hashed snapshot the record can't quietly contradict.
  • Reports assembled, not writtenfrozen snapshots generated from the live record; corrections chain to the original, both stay visible.
  • Acceptance releases paymentsa funder accepting a report is the recorded decision that releases report-triggered instalments.
  • One-click audit packa verifiable ZIP — hashed evidence, ledgers, milestones, outcomes and the event chain — against a published open format anyone can verify independently.

The organisation, held once

The organisation passport

The shared organisation passport: documents with hashes and attestation badges from self-declared through funder approved
Held once, shared on the charity's terms — and every entry shows how far it's corroborated, from self-declared to funder-approved.
  • Registry-verifiedCharity Commission, Companies House and CIC status checked daily against the official registers — an independently confirmed status, not a claim.
  • The evidence status ladderevery policy and document shows how far it's corroborated: self-declared → document supplied → funder approved. Claims and proof are never conflated.
  • Shared on the charity's termsthe charity controls which funders see which categories, revocable any time — and both sides always see the same view.

Trust & access

Security, roles & the audit chain

The grant history: a dated diary of every event, each hash-chained to the one before, with a chain-verified badge
The story of a grant, event by event — each one hash-chained to the last, and the whole chain re-verifiable on demand.
  • Two locks on every accountpassword plus mandatory authenticator app, with lockout and revocable sessions.
  • 17 granular permissionswhat the checkboxes show is exactly what the server enforces; auditors are read-only by design.
  • Hash-chained, append-only audit trailevery change in the same transaction as its audit event; UPDATE and DELETE revoked at the database level; the chain re-verifiable on demand.