# Set checklists

Source: https://holofolder.com/app/docs/set-checklist-drafts



Open the binder's **Storage** menu, choose **New binder**, then **A set**. Under **Which set?**, find the catalog set by name or code and pick a checklist language. Every card in the set gets a pocket, including Trainers, Energy, repeated Pokémon, secret rares and subsets.

The next step covers versions, promos and cards to leave out. **Which versions?** defaults to **One of each card**, where any version fills the pocket. Choosing a finish such as Reverse holo or Jumbo adds one pocket per card that the catalog explicitly marks with that finish. Missing, false or unknown finish flags are not offered. **Add promos** loads a promo set by code (for example `svp`) so you can tap cards to include, and **Leave cards out** excludes cards you don't want. No checklist claims universal master-set completeness.

Name the binder, choose its pages, check the **Preview**, then **Create binder**. Creating needs a connection with your latest changes saved; offline you can preview but not create. The binder opens as soon as it's saved to your account, and selecting targets never adds owned cards, wants or grades.

## After creation

On the binder's collection view, **What this set binder covers** shows the saved language, versions, promos and exclusions. It is also visible from cached read-only startup.

Your checklist is an independent copy, so catalog updates never change it. Add free pockets for extras, change or remove targets, or append new goals. Completion follows the current targets rather than the original set list. Normal never satisfies Reverse holo, and one owned copy can't fill two pockets.

## API

`create_storage_collection` (`POST /app/api/v1/storage/collections`) accepts an optional `manifest.setScope`, and `list_storage_collections` returns it inside `presetManifest`. Keep the reviewed scope and the same operation, collection and pocket IDs across retries. Normal owner/partner access, permissions and plan limits apply. `preview_storage_preset` does not generate set or master-set checklists, so build the manifest from catalog reads as the app does. Collections without a set scope keep working unchanged.