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

# Make the installation earn its keep

> A permanent tag that opens one locked file is doing almost nothing. What else can sit behind it, and why the moment someone scans is the hard part to buy.

Someone scanned a row of tree tags in a park. Each one opened a secure Google Sheet — no branding,
no public access, one destination for one audience. Durable tags, properly installed, on public
infrastructure, and a locked door behind every one of them.

The physical work was done well. Then it stopped.

## The thing being wasted is the scan

Getting somebody to voluntarily point their phone at your equipment is the hardest part of any
channel, and it already happened. They are standing in front of the thing, curious, holding an
unlocked phone.

A tag that meets that with a login screen has spent the money and skipped the return.

## How it works

Add the things the scan is worth to the same [Page](/pages/pages-overview). Nothing comes off the
tag, and nothing is produced twice.

```
Tree 4412 — London Plane
├── Species and planting date      on the Page itself
├── Who maintains this tree        your name, and why it matters
├── Report a problem              open to anyone
└── Works history                 your team's tool, their sign-in
```

The crew still taps through to the tool they use. Everyone else gets something.

## What goes where

|                        | What it does                         | Options                                                              |
| ---------------------- | ------------------------------------ | -------------------------------------------------------------------- |
| **Context**            | What the thing is, in plain words    | Text, an image and Item fields on the Page — no external tool needed |
| **Your name on it**    | A professional did skilled work here | Page [theming](/pages/page-theming) and a logo                       |
| **A way to respond**   | Turn a scan into something useful    | See [Let anyone report a fault](/how/report-a-fault)                 |
| **The internal route** | Unchanged, still protected           | Your inspection app or asset system                                  |

## Context costs nothing to add

The first row is the cheapest and most overlooked. Species, planting date, capacity, serial,
who services it — that data is already on the Item, and putting it on the Page is a section, not
an integration.

If the only thing you do is stop a public tag being a dead end, that is most of the value here.

## What it needs

* One Page rather than a direct redirect — see
  [Direct Mode vs. Page Mode](/pages/direct-mode-vs-page-mode)
* Item fields you almost certainly already have
* One decision: what you are willing to publish

Nothing produced again. An installed tag can be given all of this by editing its Page.

## The tag is the smallest part of the job

An anodised plate is not cheap, and neither is installing five hundred of them. What sits behind
them is a text field and an afternoon, and it is the difference between a tag that identifies
something and a tag that does something.

## Related

* [One tag, your team and the public](/how/team-and-public)
* [Let anyone report a fault](/how/report-a-fault)
* [Pages Overview](/pages/pages-overview)