Receipts over vibes
A public claim should be able to survive the source file.
This page explains how The Open Table separates vision from current operations, documents completion, reviews public language, and avoids turning aspiration into an accidental misrepresentation.
Public-trust standard
Concept visualization The doctrine
Important work must be documented, attributable, and reviewable.
Undocumented work is not treated as complete. Dashboards do not replace source documents. Memory is not a control system. Forms, logs, contracts, approvals, sign-offs, and verification notes are part of the work itself.
Public confidence is not built by sounding certain. It is built by stating the status accurately, naming the source, correcting errors, and refusing to publish what the evidence cannot support.
Public status labels
Words that prevent vision from masquerading as operation.
Currently delivered
The function has an owner, approved workflow, staffing, controls, source records, and current evidence of delivery.
Limited test
A defined, time-limited test is active with a named cohort, buyer, site, partner, or service scope and a review date.
Infrastructure underway
The program has substantive design work but is not yet fully launched or should not be represented as generally available.
Future phase
The concept is authorized as a direction but does not yet have the complete approvals, resources, or evidence required to operate.
Claims review workflow
How public language is cleared.
Draft the claim
State exactly what the organization wants the public to understand.
Classify the claim
Identity, program status, outcome, partnership, accreditation, finance, testimonial, legal, safety, or other high-risk category.
Locate the source
Executed agreement, current register, board action, approved policy, issued determination, signed consent, invoice, log, or validated dashboard.
Check date and authority
Confirm the evidence is current and the person approving the language has authority to do so.
Add limits and status
Use operating, pilot, building, or planned; identify who the service is for and what is not guaranteed.
Approve and publish
Record the owner, approval date, source, review date, and page or campaign where the claim appears.
Monitor and correct
Update or remove language when operations, partnerships, evidence, law, or status changes.
High-risk language
Disciplined language protects the mission.
Use when supported
- Peer-run recovery clubhouse
- Non-clinical community hub
- Work-Ordered Day
- Closed-loop referrals and no-drop re-engagement
- Readiness before placement
- CARF- and OhioMHAS-aligned quality expectations
- A phased or planned program, when labeled clearly
Do not publish without formal proof
- Accredited or certified
- Approved continuing-education provider
- Guaranteed housing, jobs, sobriety, treatment, or outcomes
- A partnership that has not been executed or approved for public naming
- Clinical services operated by The Open Table without proper authority
- Outcome numbers that do not tie to validated source records
- Testimonials, photos, or stories without current informed consent
Source hierarchy
Not all documents carry the same authority.
1. Law and issued records
Applicable law, regulator records, tax determinations, licenses, certifications, and other issued external authority.
2. Executed authority
Signed agreements, board action, approved budgets, issued insurance, contracts, and adopted policies.
3. Controlled operations
Current manuals, charters, workflows, forms, logs, dashboards, and operating packets with approval and version control.
4. Strategic drafts
Workbooks, concept papers, future plans, proposals, and design documents that guide but do not themselves authorize operations.
5. Legacy or archive
Superseded, deprecated, historic, duplicate, or context-only material that cannot be treated as current authority.
6. Memory and conversation
Useful for finding the source; never sufficient as the sole proof of a material public claim.
Correction rule
A correction should not erase the original record. The organization documents what was wrong, what changed, who approved the correction, when it became effective, and where the inaccurate version was removed or superseded.