Short links for events: badges, banners and the schedule that changes

Event links are printed at the worst possible moment: early enough that the schedule is still moving, late enough that reprinting is not an option. The room numbers change. A speaker drops out. The feedback form does not exist until the week before.

The whole trick is to print something that does not need to be right yet.

Print the pointer, not the answer

A QR code encodes whatever string you give it. Encode the destination and you have laminated a decision. Encode a short link and you have laminated a pointer, and the decision stays editable until the morning of the event.

We build every event this way, and the destinations are usually still empty when the banners go to print. gc.mw/sched exists on day one pointing at a holding page; by the time anyone scans it, it points at the real schedule.

One link per thing, not one link per event

The instinct is a single gc.mw/event on everything. Resist it — it forces a menu page between the scan and the answer, and it collapses every placement into one number.

Link	Points at	Printed on
gc.mw/sched	The live schedule	Badge, lanyard, hallway banner
gc.mw/map	Venue map and room list	Badge back, entrance signage
gc.mw/wifi	Network name and password page	Table tents, registration desk
gc.mw/ask	Question or feedback form	Session slides, closing slide
gc.mw/deck	Slides, later the recordings	Speaker's last slide

Five links, five sets of numbers, and each one tells you something. A map link with heavy scanning in the first hour means your signage is unclear. A feedback link with nothing means the closing slide was up for eleven seconds.

Making the codes

1. 1

   Create the links first, with holding destinations

   Custom aliases on Pro, four to sixty-four characters. Short words scan better than long ones because a shorter string means fewer modules and therefore larger squares at the same printed size.

2. 2

   Download the vector, not the image

   Add .svg to the link for print. The .qr suffix gives you a PNG for screens and slides. A PNG scaled up to banner size is a blurry code that fails in bad light.

3. 3

   Give it a quiet zone and contrast

   Keep clear space around the code and keep the contrast strong — dark code on light background reads far more reliably than the reverse, and reversed codes are the most common failure we see in event print.

4. 4

   Test on a cheap phone, in bad light

   Print at final size, tape it to a wall, and scan it from the actual distance with the oldest phone in the office. Do this before the print run, not at the venue.

What the numbers tell you afterwards

Scans arriving through a QR are marked and counted separately from ordinary clicks, so a link that lives on both a banner and a tweet still splits cleanly. Alongside that you get clicks and unique visitors by day, the hour breakdown, country, city, device and referrer.

The hour breakdown is the one people underuse at events. A schedule link scanned in a tight band before each session and nothing between them is a schedule people trust. A flat line all day is a schedule people are checking constantly because the signage is failing them.

The one thing to decide before printing

Whether the link can expire. An event link that will be reused next year should not; a link tied to one day's logistics probably should, with an expiry date set so it stops cleanly rather than pointing at something confusing.

Both are per-link settings, and both are far easier to change than a banner. That, in one sentence, is why the pointer goes on the print and the answer stays in the dashboard — see QR codes for the formats and sizing detail.