Most operations run on what nobody ever wrote down.

That works until the company grows, until the person who knew leaves, or until a machine starts answering questions people used to answer themselves.

Redesign the work. Write it down. Train the managers who run it.

Including when to trust the AI.

Method

Redesign

Structure · Ownership

Who owns what, where decisions get made, and what happens when the responsible person is out. Most operations problems are structural, and documentation never fixes a structure that was not designed.

Write it down

Procedure · Evidence

Procedures with a named owner and a revision date. A defined source of truth for every number reported. And the rules for AI: which decisions it may touch, and what a person verifies before anyone acts.

Train

Onboarding · Managers

Onboarding with staged ownership gates, so there is a defined moment someone is trusted to work alone. And manager development, because a system nobody was taught to run is a document, not an operation.

Record

500+ page operations SOP library

First-party record

Rebuilt and expanded, with version control and a named owner for every process. Every SOP went through a quarterly review.

12-day onboarding program

First-party record

Knowledge checks and ownership gates: most new coordinators were carrying the full role solo by day 12.

Average caregiver tenure: a few months to over two years

First-party record

Tenure kept rising as the workforce grew to 200+ caregivers, and several changes happened at once, so it is a system result, not the effect of any one intervention.

About 70% of new hires quit within 100 days

Industry benchmark

The figure the tenure result above should be read against.

Manager transition on 30/60/90 gates

First-party record

Restructured the org: designed the roles, wrote the job descriptions and ran hiring.

AI oversight layer, and the standard governing it

First-party record

Scanned for missed follow-ups, payroll variances and coverage gaps. After four wrong findings in one weekend, the evidence standard followed: when its output could be cited, and when it had to be verified against a source record.

Engagements

Operations Diagnostic

Redesign · One week

What is happening versus what is supposed to happen, written up. Where structure is undefined, where ownership is ambiguous, and what each gap costs.

Operating Model Rebuild

Redesign · Three to five weeks

Roles, ownership, escalation and cadence, designed and documented. Including what happens when a seat is empty.

Documentation Sprint

Write it down · Two to four weeks

An audit of what the team knows and never wrote down, then the structure to hold it.

AI Use Policy and Evidence Standard

Write it down · Two to three weeks

What AI may decide, what a person confirms against a source record, how AI-assisted output is marked, and who owns the exception.

Onboarding and Ramp Curriculum

Train · Three to four weeks

Ownership gates, knowledge checks, and a defined point at which a new hire is trusted to work alone.

Manager Development

Train · Six to eight weeks

Coaching conversations, scorecards, accountability that holds without becoming punitive, and a handover with real gates.

Fit

  • Service organizations of roughly 20 to 300 people, where the process lives in a few people's heads
  • Companies that grew faster than anyone could write down how they work
  • Teams that adopted AI quickly and have no rule for when to trust what it returns
  • Regulated or licensure-bound work, where an unverified answer becomes a compliance problem
  • Distributed or frontline workforces with a turnover problem onboarding is supposed to fix and does not

The name

verus
Latin: true, real, genuine. The root of verify, veracity, and of verdict, from vere dictum, truly said.
Astraea
The goddess who held the scales. The last immortal to leave the earth, and she left because people had stopped being able to tell a true account from a convincing one.
-ia
The state, or the place, of a thing. As in academia.

Verastria. The place where truth is weighed.

A verdict is not the answer that sounded best. It is the one that was checked.

Contact

Name the part of your operation that only works because one particular person is still there.

That is usually enough to tell whether you have a structure problem, a documentation problem, or a training problem, and roughly what it takes to fix. No charge for that answer.

hello@verastria.com

Remote engagements