PlenaProof Pilot-in-a-Box

One sector. One workflow. One sample output. One pilot.

Most of PlenaProof is optional. This page is the single front door for an institutional pilot: choose your sector, choose one workflow, see the receipt you would receive, read the 30-day plan and what is included — and exactly what PlenaProof does not claim — then email a pilot request.

Build my pilotSee sample outputsOpen Trust Center
What this page is. A pilot-scoping pathway. It does not imply a production backend, legal certification, official verification, court admissibility, or regulatory compliance. Every sample shown here is illustrative, not a real customer record. A pilot scopes one workflow so your institution can decide whether to go further.

Build your pilot in three choices

Pick a sector, a workflow, and the output family you care about. The panel updates to show the sample output, the 30-day plan, and the truth boundary for that combination.

Sample output

Open full Sample Output Library

Truth boundary

The 30-day pilot plan

Every pilot follows the same shape: one workflow, one department, one receipt type. Nothing here requires a production backend to begin.

Week 1

Scope

Scope one workflow, one department, and one receipt type. Agree the intake fields, the reviewer role, and what "done" looks like.

Week 2

Configure

Configure intake fields, reviewer roles, and the sample packet. Walk the team through the receipt anatomy and the truth boundary.

Week 3

Run

Process a limited set of sample cases or public-safe test cases. Capture missing items, refusals, and escalations as they occur.

Week 4

Report

Export a readiness report, a receipt sample, an issues log, and an adoption recommendation for your decision-makers.

What a Founding Pilot includes

Concrete deliverables, not a vague engagement. Exact scope depends on your data boundaries, reviewer roles, case volume, backend activation, and legal/security review.

You receive

  • 1 suite, 1 workflow scoped to your department.
  • A limited case / sample-case volume agreed up front.
  • A receipt / output prototype in the family you chose.
  • A readiness report at pilot close.
  • A pilot closeout memo with an adoption recommendation.
  • An issues log of gaps, refusals, and unresolved risks.

Pilot success metric categories

Measured against your real workflow — PlenaProof does not invent numbers. Categories only:

  • Cases processed.
  • Receipts generated.
  • Missing items identified.
  • Deadlines tracked.
  • Reviewers trained.
  • Audit exports produced.
  • Public-safe verification links created.
  • Time saved, if measured.
  • Unresolved risks identified.

Three first-pilot starting points

If you are not sure which combination fits, start with one of these.

Pilot 1

University / College

Workflow: applicant credential intake, or research authorship / origin record.

Output: Institutional Proof Packet or Authorship Origin Record.

Not official degree verification unless connected to authorized sources.
Pilot 2

NGO / Church / Human Service

Workflow: beneficiary intake, service encounter, staff/volunteer record, or archive continuity.

Output: Human Service Encounter Receipt or Institutional Continuity Report.

Documents the service / review trail; does not replace safeguarding, legal, medical, or government review.
Pilot 3

AI Accountability / Employer

Workflow: AI-assisted decision review.

Output: Human Review & AI Decision Audit Pack.

Does not certify AI systems or guarantee compliance; documents human review, refusal, appeal, and correction paths.

What a PLENA receipt actually contains

Every output above shares the same plain-language anatomy. A receipt records what happened around a trust event — it does not certify the underlying claim.

PlenaProof Receipt anatomy

Receipt ID
A stable handle the record can be cited by.
What was submitted
The item, document, or request that came in.
Who reviewed or received it
The named human role that handled it.
Accepted / refused / corrected / missing / escalated / preserved
The outcome of each step, including what was not accepted.
Evidence / private binder reference
A pointer to the supporting evidence, kept private.
Public-safe metadata
Only the fields safe to show publicly.
Verification status
What can and cannot be checked right now.
What this receipt does NOT prove
The explicit limit of the record.
Related receipt IDs
Links to connected records.
Export / QR / public-verify link
Where available, a way to check the public-safe view.

PLENA Status Legend

The label beside any feature tells you how far along it is. Used across the Command Center, Registry, Badge, Verify, Pricing, and Roadmap.

Sample / demo onlyPublic information surfaceClient-side previewPilot-ready templateConfigured institutional workflowBackend-requiredPlanned integrationIndependently verifiedPublicly active

Request your pilot

Send the three choices you made above and we will reply with a scoped 30-day plan.

Email hello@joinplena.com with your sector, workflow, and output family.

Email my pilot requestSee pricing