Planning a CoachingOS implementation

Describe one complete cycle

Write a short account of the current process: a coach visits, records evidence, meets with an educator, agrees on an action, and follows up. Identify where information is lost or where the next person does not know what to do. That gives the implementation discussion a concrete purpose.

Decisions to make before setup

• Model: the instructional framework and language the team already uses.
• Participants: coaches, educators, leaders, and the implementation owner.
• Evidence: what gets recorded and what belongs outside the coaching record.
• Actions: how the team writes a specific, observable next step.
• Access: who needs to see or change each type of information.
• Follow-up: when and how previous work is revisited.

Bring these requirements to NovaPath so platform fit, configuration, access expectations, and implementation scope can be confirmed. This checklist does not promise a particular integration or permission feature.

Pilot a representative workflow

Select a small group that reflects the work you need to support. Use an illustrative record to walk through observation, focus, action, and follow-up before entering real information. Agree on where questions and corrections will go.

Then review actual use against the intended routine. Did people find the prior observation? Was the next step clear? Did the follow-up conversation refer to it? These questions reveal more than whether people opened the software.

Prepare an implementation brief

Include the participant groups, current templates, desired workflow, expected observation volume, access requirements, and decision dates. Identify which existing records need to be retained and whether any migration or integration is requested; confirm those items explicitly in scope.

Define success before expansion

Agree on a few practical measures such as completed coaching cycles, follow-through, and time spent finding records. Set a review date and name who decides whether to expand. A successful pilot needs a usable routine and clear ownership, not only a completed setup.