Prompt Versioning

Track prompt changes across versions with author, model, evaluation score, deployment status, diff context, and rollback points. This example brings Versions and Diff together so AI product teams can find the next task without losing context.

It includes representative records such as v24 · concise output format and v23 · added policy examples. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Prompt Versioning
Use this template in Figr

Template facts

Screen

Table

Primary action

New version

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to new version while keeping versions, deployed and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Versions gives users an obvious place to start.
  • Supporting view: Diff keeps the related context close.
  • Primary action: New version stays visible when people need it.
  • First signal: Versions shows a useful value (24).
  • Second signal: Deployed gives additional context (v18).
  • Sample record: v24 · concise output format.
  • Next record: v23 · added policy examples.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Versions → Diff → New version → Review outcome

Patterns used

Table, Versions, Diff, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to versions and diff. People need to distinguish v24 · concise output format from v23 · added policy examples. Keep versions visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “New version”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Retrieval Playground, Evaluation Dataset, Knowledge Source Manager.

Start from this in Figr

Design a prompt versioning screen inside our existing product. Use our current components, tokens and content language. Include Versions and Diff views, credible records like v24 · concise output format, and a clear “New version” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr