Skip to main content

AI-Scripting for Evaluations, Observations, and Coaching

This article is to help KickUp administrators set up Scripting in KickUp Growth or Foundations instances. AI scripting notes let observers and coaches capture timestamped observations, get AI summaries, assisted form response, and historical context.

This article is for KickUp administrators. If you're an observer or coach looking to use scripting notes during a session, see Using AI scripting notes.

AI scripting notes let observers and coaches capture timestamped observations in real time — and get AI-generated summaries, assisted form response, and historical context without leaving the form.

Jump to:


What scripting notes include

When scripting notes are enabled on a step or instance, the observer or coach gets support across three phases of their session:

  • Before the session — A "Before you walk in" panel in the Insights Side Bar, showing an AI-generated summary of the observer's prior sessions with this educator: past notes, scores, and any patterns or commitments from previous visits. Requires Show past submissions to be on, and only appears when prior session data exists for this educator.

  • During the session — A timestamped note-taking workspace with teacher/student labels auto-applied to each note. If a framework is enabled, AI suggests which framework components each note aligns to — observers can accept or reject suggestions. Tag counts build in real time as notes are added.

  • After the session — Two things happen when the session ends:

    • The Insights Side Bar updates with an AI-generated summary organized by theme, not a raw dump of notes. It also surfaces the observer's connection history with this educator and patterns over time.

    • On the form, every question has assisted form response: click into a question and see a summary of the scripted evidence relevant to that specific question, plus a Suggest button that generates a draft written response based on your notes. Insert it, edit it, or ignore it.

For a full walkthrough of the observer experience, see Using AI scripting notes.


KickUp Growth: enabling scripting on an evaluation step

In KickUp Growth, scripting notes are configured at the evaluation step level. Anyone who can edit evaluation forms can turn this on.

Scripting 1.gif
  1. Open the evaluation edit menu.

  2. Navigate to the step where you want to turn scripting notes on.

  3. Check Enable scripting notes.

  4. Optionally check Show historical submissions — this surfaces the observer’s prior observations and scores for this educator during the session.

  5. Optionally check Show framework — this turns on AI tag suggestions and lets observers manually align notes to a framework.

    • If enabled, select a default framework from the dropdown to pre-populate the selector for observers.


KickUp Foundations: enabling scripting in walkthroughs

In walkthroughs within KickUp Foundations, scripting notes are configured at the instance level.

CleanShot 2026-05-29 at 08.43.35.gif
  1. Navigate to the walkthrough instance and open the edit menu.

  2. Click the Form tab.

  3. Toggle Enable scripting notes on.

  4. Optionally toggle Show past submissions — this surfaces prior walkthroughs for this educator during the session.

  5. Optionally toggle Show framework — this turns on AI framework alignment.

    • If enabled, select a default framework from the dropdown.


KickUp Foundations: enabling scripting in coaching

In coaching within KickUp Foundations, scripting notes can be configured in two places depending on the coaching format — at the form level for coaching logs, or at the step level for coaching cycles.

Coaching logs (form level)

  1. Navigate to the coaching instance and open the edit menu.

  2. Click the Form tab.

  3. Toggle Enable scripting notes on.

  4. Optionally toggle Show past submissions — this surfaces prior coaching logs for this educator during the session.

  5. Optionally toggle Show framework — this turns on AI framework alignment.

    • If enabled, select a default framework from the dropdown.

Coaching cycles (step level)

  1. Navigate to the coaching cycle and open the edit menu.

  2. Navigate to the step where you want to turn scripting notes on.

  3. Check Enable scripting notes.

  4. Optionally check Show past submissions.

  5. Optionally check Show framework — this turns on AI framework alignment.

    • If enabled, select a default framework from the dropdown.


Good to know

Walks defaults. Scripting notes are on by default for Walks. Framework alignment is off by default — most walk leads use notes without tagging to a rubric, and the AI post-session summary generates from notes regardless of whether a framework is enabled.

Coaching defaults. Scripting notes are off by default for Coaching. Framework alignment is also off by default. Scripting notes are currently available for one-to-one coaching only. Group coaching logs don’t support scripting at this time.

Pre-session historical context. When Show past submissions is on and prior session data exists for an educator, observers see an AI-generated “Before you walk in” panel when they open the form.

Assisted form response works with or without a framework. After scripting, every form question surfaces relevant evidence from the observer's notes and offers to generate a draft written response. This works whether or not a framework is enabled — it pulls from whatever was scripted.

Turning off AI. There is no step-level or instance-level toggle to disable AI. If scripting notes are on, AI runs. The options per step or instance are: scripting with AI, or no scripting at all.

Two scenarios admins ask about:

  • "I want scripting notes, but I don't want AI suggestions." Not currently supported at the step or instance level. Scripting notes and AI come as a unit — you can't enable one without the other.

  • "I want to disable AI for a specific step or form." Also not supported at that level. The only way to suppress AI output across your district is the site-wide AI kill switch in district settings, which turns off AI everywhere.

Hiding AI suggestions is not the same as disabling AI. Observers can hide framework tags and teacher/student highlights during a session using the gear icon in the scripting workspace — but this is a visual preference, not an on/off switch. AI calls still run in the background when suggestions are hidden.

Scripting admin 3.png
Did this answer your question?