If the three featured templates above match your case, start there. The sections below cover additional families (vendor review, insurance, supply chain) for when the exception is more specialised.
Choose the path, not the template
Start from the job you need done. Let the template path stay light until the bundle earns a deeper path.
Every paid run should feel obvious: choose the job, see what is missing, understand what the reviewer will see, then continue with the smallest path that gets the case moving.
Best for What this path is built to solve first.
Requires The minimum evidence families that make this path useful.
Produces Summary, exhibits, and the reviewer-facing structure you will get.
Reviewer sees The calm outside-review view, not your internal upload mess.
Chargeback / payment dispute
Use when payment, fulfilment, and customer contact need to become one reviewer path.
Best for DNR, SNAD, refund dispute, or payment-review pressure where the reviewer needs chronology and objections handled fast.
Best for: chargebacksRequires: order + payment + delivery or contactProduces: dispute-ready summary
Every family uses the same calm structure, then adds only what that path needs.
Verdict + strongest issue The fast outside-review headline.
Missing evidence + fastest fix What upgrades the path quickest.
Exhibits + timeline The ordered record behind the claims.
Cannot-prove boundary What still remains unknown even after packaging.
The logic that makes this different
Templates here are not forms. They are assembly paths for records.
Most tools give you a form to fill. We start from a different question: what is the minimum structure that makes a reviewer reach a position without needing a call?
LAYER 1
Case framing
What happened. Who are the parties. What the reviewer must decide.
LAYER 2
Facts & timeline
Ordered events. Critical dates. The sequence that matters.
LAYER 3
Evidence map
What supports each claim. What is missing. What is declared vs confirmed.
LAYER 4–5
Reviewer view → Outputs
Summary first. Status. Actions available. PDF + verify link.
Every template follows these five layers. The difference between families and tiers is how deep each layer goes — not whether the layer exists.
🧠
AI EVIDENCE ENGINE v3.0
Not sure which path fits? Let the upload intelligence choose the lane first.
Upload your evidence files → Vraimony builds a claim-to-evidence graph → scores fit by family → shows the best starter path first → then only offers the deeper path if the bundle earns it.
New in v3.0: After finding your template, run Falsification Mode — AI attacks your case before you send it. Finds every overstatement and gap the reviewer will find.
Templates by family — or let AI choose for you
Free starters. $19.99 full cases. AI routes you to the right one.
Every template below is designed around one specific outside-review situation. Starter = organise and prepare. Decision-ready = sealed case the reviewer acts on.
⚖️ DISPUTE / CLAIM AI routes here for F02, F08, F10 · falsify before sending
All decision-ready templates include: sealed case record · reviewer-facing link (no account) · PASS/Declared/Unverified labels · PDF exports · tamper-evident verify URL · structural guarantee.
💡Looking for your workspace? Open the App Shell → — start from your situation, not from the template list.
Three pain paths — same engine
Choose your situation. Then choose free or decision-ready.
Each path leads to free starter templates for organising your case, and decision-ready templates for building a complete record for outside review.
⚖️ Dispute / Claim
Something is contested. The other side needs to review it.
Chargeback, insurance claim, invoice dispute, partner disagreement, commercial claim, demurrage, force majeure. The case exists — it needs to be packaged so the reviewer can reach a position without another email chain.
Minimum evidence to proceed
One timeline (even partial)
One document that establishes the claim
One clear ask for the reviewer
Weak — no timelinePartial — timeline onlyReview-ready — sealed
Something is being transferred. The other side must acknowledge it.
Project delivery. Milestone sign-off. Service acceptance. Change orders. A handover record the receiving side can ACK or MER — without repeated back-and-forth.
Minimum evidence to proceed
What is being handed over
Delivery state (partial / complete)
Who receives and what they must confirm
Weak — no delivery statePartial — no receiver pathReview-ready — ACK path set
Shipment disrupted at a global chokepoint. The adjuster deadline is already running.
General Average notice. War-risk reroute. Vessel waiting offshore. Cargo in floating storage. Active at Hormuz, Bab el-Mandeb, Suez, Black Sea, and any port disruption. When disruption creates a documentation deadline — package the facts before the adjuster, insurer, or counterparty asks for them. The protocol is the same regardless of which chokepoint caused it.
Minimum evidence to proceed
Bill of lading or voyage reference
Notice or event that triggered the deviation
Timeline from original plan to current state
Notice received — undocumentedPartial — timeline onlyReview-ready — adjuster path set
More templates are added as decision patterns are confirmed by real usage. Template IDs are stable once published — they do not change.
Local-first template packs
Templates now work as same-server packs: starter first, deep only when the bundle justifies it.
Vraimony routes to a family in the browser first. The template pack then decides whether you should start in a light starter path or go directly into a decision-ready deep path. No third-party AI providers. No external integrations. Template logic and routing packs are served from the same Vraimony server only.
Starter path
Fast lane for weak or partial bundles. Organise the case, close the biggest gap, then upgrade.
Deep path
Use when uploads already cover the core evidence families and contradictions are contained.
Plugin-first
Best experience is the WordPress/Woo plugin shell: Cases · Upload · Templates · Settings.
Same-server only
Rules, packs, and AI fallbacks come only from your Vraimony server. No third-party calls.
We improve review-readiness. We do not control the reviewer's decision.
Local-First Plugin Shell
Run cases, uploads, and template routing inside WordPress first.
The recommended operator flow is now plugin-first: Cases → Upload → Templates → Settings. Upload triage, bundle verdict, and template recommendation can happen in the browser first, then hand off to your own Vraimony server only when needed.
Choose the paid path that matches how often you use templates.
Starter stays free. Deep is best for one live issue. Repeated use fits Pro. If your team works from Woo every week, treat the plugin path as the operator workflow.
Use One Case when one issue needs a reviewer-ready bundle now, Template Pro when Deep paths repeat, and Plugin Pro when Woo order context is the real entry point.
Best for one live issue
One Case — Deep path
Use this when one chargeback, delivery dispute, vendor review, or handover issue needs a reviewer-ready bundle now.