Skip to content

Compare Versions

RAMP provides a powerful version comparison tool that highlights exactly what changed between any two versions of a template. This is essential for reviewing changes before approval, understanding the evolution of a procedure, and auditing modifications.

There are two ways to open the comparison view:

  1. Navigate to the template detail page.
  2. Click the Compare button on any version.
  3. Select the two versions you want to compare using the version dropdowns.
  1. Open a version in the version editor.
  2. Click the Compare icon in the toolbar.
  3. The current version is pre-selected. Choose a second version from the dropdown.

The comparison page shows two dropdowns at the top:

  • From version — The baseline version (typically the older one).
  • To version — The changed version (typically the newer one).

A Swap button lets you quickly reverse the comparison direction. You can also select versions from URL parameters, making comparison links shareable.

The comparison tool offers two view modes:

Steps are displayed in a single column with changes highlighted:

  • Added steps are highlighted in green.
  • Removed steps are highlighted in red.
  • Modified steps show the content changes inline.
  • Unchanged steps appear without highlighting.

Steps are displayed in two columns:

  • Left column — Steps from the “From” version.
  • Right column — Steps from the “To” version.
  • Lines connecting matched steps help visualize the mapping.

Toggle between views using the view mode selector at the top of the comparison.

The comparison analyzes multiple aspects of each step:

RAMP uses Step Identifiers (stable IDs that persist across versions) to match steps between versions. This allows accurate tracking even when steps are reordered, renamed, or modified.

Change typeIconDescription
AddedGreen plusStep exists in the “To” version but not in “From”
RemovedRed minusStep exists in the “From” version but not in “To”
ModifiedYellow pencilStep exists in both but content or settings changed
ReorderedBlue arrowsStep position changed but content is the same
UnchangedGray circleStep is identical in both versions

For modified steps, the comparison shows:

  • Title changes — Differences in step titles.
  • Rich text content changes — Added, removed, or modified text in the step instructions.
  • Setting changes — Changes to properties like skippable, requires evidence, execution type, and estimated duration.
  • Responsibility changes — Changes to who is responsible for executing the step.

The comparison also identifies variable changes:

  • Variables added in the newer version.
  • Variables removed from the older version.
  • Variables with changed properties (type, default value, required status, etc.).

For complex changes involving step reordering and nesting modifications, RAMP provides a Tanglegram view — a visual tree diagram that draws connecting lines between matched steps across the two version trees. This makes it easy to see how the step hierarchy has been restructured.

The comparison view supports URL parameters for both version IDs and the view mode. You can:

  1. Copy the URL from your browser address bar.
  2. Share it with a colleague.
  3. They will see the exact same comparison with the same view mode.

Click the Share button in the comparison toolbar to copy a pre-formatted link.

Before approving a published version, use the comparison to see exactly what changed from the previously approved version:

  1. Open the comparison view.
  2. Set “From” to the last approved version.
  3. Set “To” to the version pending approval.
  4. Review all changes step by step.
  5. Approve or request modifications based on the diff.

Use comparison to understand changes made over time:

  • Compare any two versions in the template’s history.
  • See who modified what and when (via step audit entries).
  • Track the evolution of critical procedures.

When an instance execution reveals a problem:

  • Compare the instance’s template version against a known-good older version.
  • Identify what changed that might have caused the issue.