QR codes on memorial benches, tree markers and public memorials
The buyer profile changes the job. A council bereavement or parks team commissions benches and tree markers in batches across several sites, holds them as assets, and answers to donors when something stops working. A woodland burial ground wants markers that weather without maintenance visits. A crematorium fits hundreds of near-identical niche plaques and needs the workflow for the hundred, not the one. All three share one property that makes codes genuinely worth doing: the plaque is fixed and public, and the page behind it is the only part that can ever be updated. That is the argument to put in a committee paper, and it is also why the static-or-dynamic decision belongs to the organisation, not to whichever contractor cut the plaque.
| Surface | The fixing reality | What it means for the code |
|---|---|---|
| Hardwood bench slat | Screws and countersunk brass plates; slats curve gently and get sat on, leaned on and rained on | Small rounded-corner plate, engraved and infilled, fixed away from the seat zone; size up for glare and wear |
| Cast bronze bench or ground plaque | Bolted or resin-fixed; ground-level plaques silt over | Deep relief so patina keeps contrast; ground fixing wants a raised frame and an annual clean in the maintenance schedule |
| Stainless steel tree marker | Small, often cable-tied or screw-fixed to a stake | Material is cheap to etch but small: keep the destination short, error correction H, and test on the actual stock |
| Slate or stone tree marker | Engraved like a miniature headstone, driven into soft ground | Same rules as stone, plus frost heave and mower strike: place with the groundskeeper, not just the donor |
| Indoor niche or book of remembrance | Curated, indoor, often regulated by the crematorium | Contrast is easy indoors; the constraint is the crematorium's own design rules, so ask before generating anything |
Consent comes before the code
Churchyards, listed parks and public land all have rules about what may be fixed where, and some authorities restrict plaques to approved suppliers or ban fixings to living trees outright. A QR code does not change any of that: it is one more engraved element on an approved plaque at best, and an unapproved addition at worst. Get the memorial's permission settled with the authority first, then add the code to the artwork. Promising a family a coded bench the council will not approve is the expensive order.
A bench plaque is read by someone sitting down, so the distance is close, but public settings are not kind to small codes: glare after rain, worn surfaces, fingers, and readers whose eyesight or hands make small targets awkward. Treat 40 to 50mm as the floor for a bench plaque and go larger if the plate design allows, with error correction set to H for the same reason as any outdoor memorial. Keep the code on the upper slat or the plaque's own field rather than the seat surface, away from armrest wear, and check the quiet zone survives the plate's border and fixing holes: a countersunk screw hole placed in the code's margin quietly kills it.
The council ordering a season of benches, and the burial ground marking a new lawn, are both better served by a register than by a folder of files. One row per memorial: label, destination, site, plaque type. The bulk generator turns that list into a batch of files named by label, with a manifest mapping every file back to its row, which is what you hand the plaque founder so the right code lands on the right bench. Static codes suit the register-and-forget case and stay free and unlimited. Dynamic codes earn their place where the destination might move, such as a tribute page being built after dedication day, and beyond three of them that is Pro at £9 a month, a line item that belongs in the same budget line as the plaques themselves.
From dedication ceremony to working plaque
Settle consent and siting
Written approval from the authority, and the physical position agreed with whoever maintains the ground.
Decide the destination before ordering
A page that exists today, or a dynamic code while it is still being built. See the tribute page options.
Build the register
One row per memorial with label and destination, even for a batch of three. The register outlives the supplier.
Generate the batch
Bulk generator, error correction H, sized for the plaque, exported as SVG at exact millimetres for the founder's software.
Proof and fix
Scan the first finished plaque on site, in the rain if you can, then record the plate serial against the register row.
For organisations managing many memorials, the scan count on a dynamic code answers a question councils actually get asked: is anyone visiting. Report it plainly, the same discipline as for a family headstone: this is how many visits were scanned, never engagement or conversion language, and no individual visitor is identified anywhere in the data. A quiet bench is not a problem to be managed; it may simply be in a quiet park. What the count genuinely supports is the annual report line to donors that the memorial is being visited, and the decision, years later, about whether a moving tribute page is still worth maintaining.