Do they want to lead?
Choose people who want people-leadership responsibilities and have a real opportunity to practice. A strong craft professional may prefer a technical advancement path. Do not use a coaching record as a promotion test.
Company pilot / working agreement
Give the practice somewhere to happen.
Start with 5–8 newly promoted foremen or early superintendents, one executive sponsor, and a few behaviors worth observing over 12 weeks.
This guide prepares a pilot discussion. Scope, start dates, service expectations, and price are agreed before enrollment. It is not a promise of business results.
Agree on these six things first.
Make participation possible.
Agree when the short lesson, planning, and check-in fit the working week. No travel does not mean no effort. Record actual time during the pilot rather than promising an unmeasured time saving.
Choose ordinary work.
A shift handoff, a private correction, a delegated responsibility, or a request for a PM decision is enough. Identify a backup opportunity if the project changes.
Say what they can decide.
Name decisions they can make, approvals they need, and who will resolve resource or workload barriers. A missing approval is not automatically a motivation problem.
Use what you already teach.
Bring a short, approved example of a good handoff or delegation agreement. Participants can reference its standard in their weekly plan. Varentum can reinforce an existing academy or supervisor program; custom integrations and curriculum are not included by default.
Decide what you will observe.
For example: “The receiving lead can name the owner and next update time.” Agree who can observe that ordinary work, when, and with what consent. Do not ask for copies of private debriefs.
Protect the space to be honest.
| Record | Boundary |
|---|---|
| Company roster | Authorized company administrators can see assigned participants, access, current week, and completion information. |
| Individual coaching | Scenario answers, commitments, check-ins, debrief content, Load Index answers, and help/safety classifications are not exposed in the company dashboard. |
| Optional cohort reporting | Requires participant consent. Reports are suppressed below five consenting participants in a reportable group. A five-person enrollment does not guarantee a report if fewer than five consent. |
| Field examples | Sharing a de-identified example requires a separate participant opt-in. Do not infer someone's private record from a small group's activity. |
| Independent observation | A sponsor can record behavior they actually observe at work under an agreed process. Keep that separate from participant self-report and never substitute private coaching content for an observation. |
Participation in a company program does not silently turn on reporting consent. Participants control the optional permissions in their portal. Read the privacy notice.
Measure the pilot honestly.
- Before the first practice: choose one or two behaviors and capture the participant's private baseline. Use an agreed example of what “not yet,” “sometimes,” and “consistently” look like.
- Every week: count planned opportunities, attempted applications, submitted check-ins, and delivered debriefs separately. Record blocked opportunities and missing reports instead of treating every blank as failure.
- At week 12: repeat the same behavior checkpoint. Compare only matched baseline/endline records, and report how many were missing.
- After the program: arrange a 30-day follow-up. Ask what persisted, what support mattered, and whether the sponsor wants to continue.
A self-reported change is not verified mastery. Attendance is not behavior change. Changes in rework, retention, safety, or profit cannot be attributed to Varentum from a small uncontrolled pilot.
Agree on success criteria before launch. Include whether participants found the coaching useful, whether delivery was reliable, and whether the sponsor would fund another group. The first pilot is for learning as well as evaluation.
Know what is being delivered.
Cohort: weekly debriefs drafted with AI, then founder-reviewed and approved before delivery. Solo: AI-coached debriefs without routine human review. Both use the participant's field record; neither promises live coaching calls.
Agree a shared Monday start for a company group if you want the Monday–Friday rhythm. Access advances on seven-day intervals from enrollment start; this is paced development, not a library to binge. Routine Solo debriefs are scheduled for the next business morning at 8 a.m. Mountain time, Monday–Friday. Cohort review or safety holds can delay delivery.
The full participant program is currently delivered in English. A Spanish inquiry page is available; a complete Spanish coaching experience is not yet offered. If your team needs Spanish, tell us about the need before making a purchase decision.