PLENA Sample Output Library

See the artifacts, not just the claims.

A serious buyer wants to see what comes out, not only what is promised. Below are illustrative previews of the artifacts a PLENA pilot produces. They are not generated from real cases.

Build a pilot around one of theseOpen Trust Center
Every item on this page is a sample. Sample only. Not a real verification. Not a real customer record. Not legal, regulatory, or institutional certification. Real outputs are produced only inside a scoped pilot, against your own data and reviewer roles.
01

Sample Institutional Proof Packet

Sample only

What an institution exports to show a board, accreditor, or funder that a workflow was handled with named human review.

PLENA Institutional Proof Packet — SAMPLE Packet ID: SAMPLE-IPP-0001 Institution: Example University (sample) Workflow: International applicant credential intake Cases in packet: 12 (sample) Human reviewer: Registrar intake officer Accepted: 9 · Missing items flagged: 3 · Refused: 0 Evidence: private binder ref BINDER-SAMPLE-12 Public-safe fields: packet ID, status, date Does NOT prove: that any credential is genuine or accredited
02

Sample Human Review & AI Decision Audit Pack

Sample only

Documents that a human reviewed an AI-assisted decision, what was corrected, refused, or escalated.

PLENA AI Decision Audit Pack — SAMPLE Pack ID: SAMPLE-AI-0001 Decision: AI-assisted eligibility recommendation Human reviewer: Named officer (sample) AI role: Drafted recommendation from inputs Human action: Upheld with 1 correction Refused: Auto-decision without review (blocked) Escalated: Appeal path recorded Does NOT prove: that the AI system is safe, fair, or compliant
03

Sample Refusal Receipt

Sample only

The record an individual keeps when they are told no — capturing who refused and what was missing.

PLENA Refusal Receipt — SAMPLE Receipt ID: SAMPLE-RR-0001 Submitted: Service / benefit request (sample) Decision: Refused Refused by: Named officer / desk Stated reason: Document X missing Missing: Official translation of exhibit Preserved: Yes (on this device) Does NOT prove: that the refusal was wrong or unlawful
04

Sample Human Service Encounter Receipt

Sample only

Records that a service encounter happened, who was present, and what was agreed — for NGOs, churches, and human services.

PLENA Service Encounter Receipt — SAMPLE Receipt ID: SAMPLE-SE-0001 Encounter: Beneficiary intake session (sample) Present: Intake officer + beneficiary Outcome: Eligibility documented Escalated: Safeguarding flag routed Preserved: Yes Does NOT prove: legal status, medical findings, or safeguarding determination
05

Sample Public Service Journey Receipt

Sample only

Tracks a citizen's administrative journey through a public-service workflow with human oversight.

PLENA Public Service Journey Receipt — SAMPLE Receipt ID: SAMPLE-GOV-0001 Request: Citizen service request (sample) Steps: Logged → routed → reviewed Reviewed by: Public-service officer Public-safe view: status + receipt ID only Does NOT prove: an official eligibility decision
06

Sample Counterparty Due Diligence Record

Sample only

The defensible review trail a bank or fintech builds when screening a counterparty.

PLENA Counterparty Due Diligence Record — SAMPLE Record ID: SAMPLE-FIN-0001 Counterparty: Example Vendor Ltd (sample) Reviewed by: Due-diligence analyst Documented: profile, source-of-funds notes Risk flags: 2 open Missing: beneficial-owner confirmation Does NOT prove: identity, sanctions status, or AML compliance — PlenaProof runs no identity/sanctions checks
07

Sample Public Verify Result

Sample only

What a third party sees when they check a public-safe receipt — including what it cannot confirm.

PLENA Public Verify — SAMPLE RESULT Looked up: SAMPLE-RR-0001 Found: A public record exists for this ID Status: Sample / demo only Confirms: a public record exists Does NOT yet confirm: tamper-proof signature, genuine issuer status, cancellation status, or court acceptance
08

Sample Registry Profile

Sample only

An organization's public-safe profile in the PLENA registry.

PLENA Registry Profile — SAMPLE Profile: Example Organization (sample) Status: Pilot-ready template Public-safe fields: name, sector, receipt families Verified records: 0 (sample) Does NOT prove: accreditation, licensing, or endorsement by PLENA
09

Sample Board / Funder Audit Export

Sample only

The summary an institution hands to a board or funder at the end of a reporting cycle.

PLENA Board / Funder Audit Export — SAMPLE Export ID: SAMPLE-AUD-0001 Period: Q1 (sample) Cases handled: 142 · Receipts: 138 · Gaps: 6 Deadlines met: 31/34 Reviewers: 4 named roles Does NOT prove: program impact or financial accuracy
10

Sample Data Flow Diagram

Sample only

Where data lives and moves in a pilot — for procurement and security reviewers.

PLENA Data Flow — SAMPLE [User device] --submits--> [Client-side workflow] | (stays on device unless deliberately exported) [Reviewer] --records decision--> [Private evidence binder] [Institution] --chooses--> [Public-safe receipt fields] | [Public Verify] Backend custody / API: backend-required (not active in pilot)
11

Sample Pilot Scope Memo

Sample only

The one-page scope a pilot starts from: one workflow, one department, one receipt type.

PlenaProof Pilot Scope Memo — SAMPLE Pilot: Example Institution (sample) Suite: 1 · Workflow: 1 · Department: 1 Receipt family: Institutional Proof Packet Sample-case volume: up to 20 Deliverables: readiness report, receipt sample, issues log, adoption recommendation Truth boundary: pilot-scoping only; no production backend, certification, or official verification

Ready to see one of these against your own workflow?

A pilot produces these for real, scoped to one department, in 30 days.

Build my Pilot-in-a-BoxEmail hello@joinplena.com