> ## Documentation Index
> Fetch the complete documentation index at: https://docs.passlet.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Updating passes

> Change pass data, upgrade to new template versions, and read the revision timeline.

Passes in wallets aren't static — Passlet pushes changes to Apple Wallet and Google Wallet automatically when you update a pass. There are two kinds of update:

## Update pass data

Change the **variable values** of an issued pass — a new seat, a bumped tier, tomorrow's date. From the pass detail page choose **Update pass data**, or select multiple passes on the list and use the bulk **Update data** action. The wallet pass refreshes with the new values; holders don't need to do anything.

## Upgrade the template version

Issued passes are **pinned** to the template version they were issued from, so publishing a redesign never silently changes live passes. When a newer published version exists, passes show a **"vN available"** indicator — upgrade them:

* per pass, via **Upgrade template to vN** on the detail page, or
* in bulk, via **Upgrade to vN** on the passes list.

After the upgrade the pass re-renders with the new design, keeping its variable values (you'll be prompted for any newly required variables).

## Revisions

Every update — data change or version upgrade — creates a **revision**: a full snapshot of the pass's variables and template version at that moment. The pass detail page has a revision timeline scrubber so you can see exactly what a holder's wallet showed at any point.

<Note>
  Updates are processed asynchronously, like issuance. Wallet providers usually refresh within
  moments, but delivery timing is ultimately up to Apple/Google push infrastructure.
</Note>