One situation / two attempts

The value is in what happens next.

A new foreman needs a clearer handoff. The first conversation helps, but leaves a gap. The debrief makes the next attempt more specific.

Illustrative example. These people, reports, and coaching excerpts are fictional. This demonstrates the intended experience; it is not a customer testimonial or evidence of measured results.

One useful rep leads to the next
  1. 1. CommitName the person, first move, decision boundary and check-back.
  2. 2. AttemptTry it within your authority. Report what happened, including what stayed unfinished.
  3. 3. DebriefRead the coaching when sent. A queue or review hold can delay delivery.
  4. 4. Revise and repeatChoose a supported next move. Return to it in the next check-in.

Completion is self-reported. A sent debrief does not complete an unfinished assignment or establish mastery. Solo coaching is AI-only for routine delivery; Cohort coaching is reviewed and approved by the founder before delivery.

What stays private, and what a sponsor can see

Private coaching record

Scenarios, commitments, check-in answers, coaching content, private self-assessments, Load Index and safety classifications.

No company-dashboard access to this content.

Used by the coaching system and authorized Varentum reviewers under the privacy policy.

Company operations

Authorized administrators can manage their assigned roster and see access, current week and completion information under existing company permissions.

Roster access is separate from optional reporting consent.

Optional aggregate reports

Participation, reported application and coaching delivery require participant consent. Detailed progress is suppressed below five consenting people in a group.

No private answers or employee ranking.

Supervisor observations and anonymous crew feedback are separate sources, never inferred from self-report. Company pilot summaries retain their own privacy thresholds; crew results need at least five responses. Sharing a de-identified field example requires a separate opt-in.

Week one / set the agreement

Make the next handoff usable.

01 · Commitment

One person. One observable result.

“Before Tuesday's huddle, I'll ask Luis to own the open-items list. Each item needs a location, owner, and next update time. We'll check the list together at 2:30.”

The participant saves the plan once. It appears again at check-in.

02 · Report the attempt

Useful does not mean perfect.

“I explained the list and Luis agreed. At 2:30 he had the locations, but two items still had no owner. He thought I was assigning people. I hadn't explained which decisions he could make.”

A completed conversation can still reveal an unfinished agreement.

03 · Illustrative coaching excerpt

The missing piece was decision authority.

You named the result and kept the check-in. Your report also says, “He thought I was assigning people.” That leaves a specific question: which decisions belong to Luis, and which still need you?

Use the clear-expectations framework to separate ownership of the list from authority to assign work. Check what he understood before assuming he avoided the responsibility.

Next rep: Monday before the huddle, ask Luis to explain how he will handle an item with no owner. Agree which decisions he can make and where he needs your approval.

Week two / return to the commitment

Check the result before changing the target.

04 · Previous commitment returns

“What happened with that move?”

The next check-in shows the Monday commitment. The participant reports whether it was tried, what changed, and what remains open.

“Luis explained the boundary back. He can collect and verify owners, but a crew reassignment needs the superintendent. On Tuesday he flagged a missing decision instead of leaving the line blank.”

05 · Review and repeat

Keep the part that worked.

The next debrief can connect the reported change to the earlier gap and choose one next application. It must not declare a habit mastered from one report.

The record is participant self-report. A supervisor's separately observed handoff is a different source of evidence.

What if the attempt was blocked?

Report it. “The PM had not approved the change” is different from “I knew what to say but avoided the conversation.” Name the missing decision, resource, time, or opportunity. Coaching should distinguish what you control from what requires support. It should never suggest bypassing company procedures.

What you can expect.

Clear coaching boundaries

Solo is AI-coached. Written debriefs use your check-in, that week's framework, and prior coaching context. Routine Solo debriefs do not receive human review. Flagged records may be held for review.

Cohort debriefs are drafted with AI and reviewed and approved by the founder before delivery. Neither path promises live coaching calls.

A paced weekly rhythm

The suggested rhythm is learn Monday, commit Tuesday, report Thursday, and debrief Friday. Week access follows your enrollment start, advancing after full seven-day intervals.

Routine Solo delivery is scheduled for the next business morning at 8 a.m. Mountain time, Monday–Friday. Human review, safety holds, or delivery problems can delay a debrief; the portal shows its status. It is not an instant response or an emergency service.

Your scenario, commitment, and check-in belong to your private coaching record. Company roster access and optional cohort reporting have separate boundaries. See what a sponsor can see.