Documentation

PromptPlan Template Run History: Track Inputs, Outputs, and Quality

Learn what PromptPlan stores in run history and how to use it for prompt optimization and auditing.

Updated 2026-03-08

#run history#quality#audit

What is run history

Run history is the record of previous template executions.

Each record captures:

  • input values
  • output text
  • model used
  • run date and time

Why run history is important

Run history helps you:

  • track what worked
  • compare output quality over time
  • audit decisions made from AI output
  • onboard teammates faster

Practical workflow

  1. Open a template's saved runs
  2. Compare strong vs weak outputs
  3. Identify prompt differences
  4. Update template instructions
  5. Re-test with the same inputs

Tip

When improving a template, rerun with a previous input set so quality changes are measurable.

Related reading

PreviousRunning Templates in PromptPlan: Validation, Rendering, and Output
NextHow to Organize PromptPlan Templates with Categories and Tags