Create a register without secrets
Download the QR inventory to complete in your spreadsheet app (CSV).
For each distributed QR code, record the material, location, exact content, expected destination, owner and last check date. Add the location of source files and print approval. This register tells you what to check when a product, team or supplier changes.
Do not store passwords or recovery codes in it. Instead, indicate which access-management location should be consulted. For a Wi-Fi QR code, separate material tracking from access to the network secret so that a widely shared table does not expose the password.
Identify what you actually control
- A URL on your domain: check domain, hosting and page access.
- A shared document: check file ownership and permissions.
- An external redirect: check the account, continued-service conditions and transfer options.
- Direct content such as a vCard: keep the source, but plan a new QR code if details change.
A static QR code keeps its content. It can still depend on an external website when that content is a URL. “Static” alone therefore does not guarantee the page will remain available.
Prepare a supplier handover
Before closing an account, list the printed addresses that depend on it. Request final files and editable sources, then check that company access works independently of the supplier’s personal account. Confirm who receives domain renewal notices.
Test an example from every material family after the handover. If old addresses remain on your domain, preserve their paths or redirects. A better-looking new website should not silently remove the menu, form or product page already in print.
Set up a checking routine
Choose a frequency suited to your materials and also check after significant changes: a new menu, migration, an owner leaving or a campaign ending. Identify closed pages and replace them with useful information where possible.
Archive the register, QR files and approved versions together. Fix an existing item with changing a printed QR code. Understand dependencies with static and dynamic QR codes.