Skip to content

Schedules, maps and sign-ups on one code

Print the badges and posters once. Move the keynote, swap a room, link to your ticket page: every code follows, because the page behind it changes.

Start free

The sample setup at a glance

codes in the sample setup
4
hosted pages among them
3
recommended plan
Pro
a month, or $12 a month billed yearly
$15

Problems we fix

What goes wrong, and what Dotwick does about it

  • The schedule changes after the badges are printed

    The badge code opens a page, not a PDF. Edit the agenda and every lanyard shows the new version on the next scan.

    From Starter
  • One code on a badge has to serve both days

    Add time routes by weekday. On Tuesday the code opens the Day 1 page, on Wednesday the Day 2 page.

    From Starter
  • Sponsors want proof of traffic, and feedback forms get no answers

    One code per sponsor stand with its own tags and report, and a rating form on every session door, answered while the talk is fresh.

    From Starter

A worked example

Two days at Northwind Summit

A two-day conference with 400 attendees, three rooms and six sponsors. One organiser, one volunteer, and a programme that is never final until it is over.

Northwind Summit is a sample business. The codes, pages and rules are real Dotwick features.

  1. 01

    Two weeks before

    The event page and the sign-up

    The organiser makes an Event page: dates, venue, an agenda of up to 20 items, an Add to calendar button and a gallery of last year's photos. Its RSVP button opens a registration form she made as a separate Form code. Her ticketing tool still sells and checks the tickets.

    • Summit page
  2. 02

    One week before

    One badge code for both days

    The lanyard carries one Link page called Today, with the schedule, a map and the WiFi details. She adds two time routes by weekday: on Tuesday the code opens the Day 1 agenda, on Wednesday the Day 2 agenda. A route opens a web address, so each points at the short link of that page.

    • Today (badge)
  3. 03

    Three days before

    Sponsor stands and a stunt

    From a CSV the volunteer bulk-creates six sponsor codes, one per stand, each tagged with the sponsor's name. On one of them she sets a scan switch: the first 200 scans open a free-coffee offer, and everyone after that sees the sponsor's normal page.

    • Sponsor stands (six)
  4. 04

    Day 1, 10:30

    Feedback on every door

    A Rate this talk form (a star rating, a comment and a Session choice) is printed on every session door. The info desk screen shows the live scan feed, so she sees the doors being used as the morning goes.

    • Rate this talk
  5. 05

    Day 1, 14:10

    The keynote moves

    The keynote moves to the large room. She edits the agenda on the Event page and the Today page. Nobody reprints a badge, and the signs on the doors still work.

    • Summit page
    • Today (badge)
  6. 06

    Day 2, evening

    A report for each sponsor

    She sends each sponsor a PDF report of its own code as an outside recipient: scans by hour and the devices they came from.

    • Sponsor stands (six)
  7. 07

    The week after

    Slides and next year

    She edits the Today page so it opens with the slides, the photos and next year's waitlist. The badges that people kept on their desks now point at something useful.

    • Today (badge)

The codes in this setup

CodeSummit page
TypeEvent
WherePosters, invitations, the website
RulesRSVP button opens the registration form
PlanStarter
CodeToday (badge)
WhereLanyard badge
RulesTime routes by weekday: Tuesday to Day 1, Wednesday to Day 2
PlanStarter
CodeRate this talk
TypeForm
WhereSession doors
RulesRating, comment and session choice, each answer emailed
PlanStarter
CodeSponsor stands (six)
TypeURL
WhereStand graphics, one per sponsor
RulesUTM tags per sponsor; scan switch after the first 200 scans on one
PlanPro

What to watch in this setup. She watches scans per stand and per hour, feedback answers per session, and which route the badge code took each day.

Where the codes go

  • Lanyard badge

    Schedule, map and WiFi, with the right day opened by a time route.

    Link Page
  • Flyers and invitations

    Dates, venue, add to calendar and an RSVP button.

    Event
  • Session door

    A rating and a comment while the talk is fresh.

    Form
  • Sponsor stand

    One tagged code per sponsor, so each gets its own numbers.

    URL
  • Speaker room

    Run sheets and slides on one page, locked with a password.

    Documents
  • After the event

    The same badge code, now leading with slides and next year's dates.

    Link Page

How events set it up

  1. 01

    One code for each purpose

    Schedule, registration, feedback and each sponsor are separate codes, so each has its own scans and rules.

  2. 02

    Route by weekday

    Give the badge code a route for each day, so the same print shows the right agenda.

  3. 03

    Cap the stunts

    A scan switch sends the first people to an offer and everyone after to the normal page.

  4. 04

    Watch it live

    Keep the live scan feed open at the info desk, and send reports when the doors close.

Measure it

What to measure

The numbers worth looking at, and where each one lives.

Scans per stand and per hour
Each stand's analytics, or a report for it
Live scans during the day
The live feed in the analytics
Feedback answers per session
The form's answers, with the Session choice on each
Which day each badge scan landed on
The rule breakdown in the badge code's analytics
Offer take-up
The scan switch's count, and your till or ticket tool

Print it right

  • Badges are small and close

    A badge is read from about an arm's length, but a lanyard swings and tilts. Print the code larger than you think and keep a clear border.

  • Stand graphics are read from the aisle

    A banner is read from a metre or more. Choose Poster in the editor and use the size it gives, not what fits the artwork.

  • Test in the venue light

    Halls are dim and full of spotlights. Print the test sheet and scan it on site the day before.

How big to print it

WherePeople scan fromPrint at least
Lanyard badgeBusiness card
about 20 cm2 cm
Session door signPoster
about 1 m10 cm
Stand bannerWindow / sign
about 2 m20 cm

These sizes are for a typical dynamic code. The editor's Where will it go? step works out yours, and the test sheet lets you scan before the print run.

Honest notes

What to watch in events

  • Dotwick does not check tickets

    A Dotwick code does not validate a ticket or check anyone in. Keep using your ticketing tool and its own codes for entry. Use Dotwick for everything people read on the day.

  • A scan switch is soft, a scan limit is hard

    A scan switch sends the first people to one page and the rest to another, and is on Starter and up. For a hard stop on a code, scan limits are on Business.

  • Ask only what you need

    A registration or feedback form stores what people type. Keep it to a name and an email, and say what you will do with them.

Which plan

Which plan fits

Our pick

Pro

$15/ monthor $12 / month billed yearly

14-day free trial

Six bulk-created sponsor codes, PDF reports for sponsors and a volunteer on the team make this a Pro event: 100 dynamic codes, bulk import and 3 seats.

Start 14-day trialCompare every plan

What each plan covers here

  • Free$0 / month

    Static codes only, unlimited: a calendar entry or a map pin for a small meet-up. No Event page and no changes after printing.

  • Starter$7 / month

    A single event run by one person: Event, Link and Form pages, weekday routes, a scan switch and alerts. Sponsor codes are made one by one.

  • Pro$15 / month

    This conference: bulk import of 1,000 rows, reports as PDF, webhooks, the live feed and 3 seats with 10 free viewers.

  • Business$49 / month

    An organiser running several events: scan limits, folder permissions per event and 10 seats.

QR code templates for this industry

Scan-tested designs for the places it gets printed, ready to restyle in the editor.

See the templates →

Connect your tools

Connect your tools

  • Registrations into a spreadsheet

    On Pro, the registration form can call a webhook for each submission. Zapier or Make can add a row to a sheet or tell your CRM.

  • Alerts where the team already talks

    A scan alert can also reach a webhook, so a busy stand can ping the team chat. The native Slack app is rolling out.

See all integrations

Questions about events

  • Can the schedule change during the event?

    Yes. Edit the page, and every printed badge opens the new version on the next scan.

  • Can one badge code show Day 1 and Day 2?

    Yes, with time routes. A route matches weekdays and hours, not calendar dates, so it fits a conference that runs on two different days of the week.

  • Can Dotwick check tickets at the door?

    No. It does not validate tickets or check anyone in. Keep your ticketing tool for entry, and link to your ticket page from the Event page.

  • How do I prove sponsor traffic?

    Give each stand its own code with its own tag, and send each sponsor a PDF report of that code. Reports are on Pro and up.

  • Can an offer stop after the first 200 scans?

    Yes. A scan switch sends the first 200 to the offer and everyone after to another page. For a hard stop, scan limits are on Business.

  • What happens to the codes after the event?

    They keep working. Point them at the slides, the photos or next year's waitlist. If payment ever stops, dynamic codes keep working for 90 days.

Print it once. Change it whenever you like.

Static codes are free forever. Dynamic codes start with a free trial, and a printed dynamic code keeps working: we never swap it for an ad.

Start free

Your printed code keeps working. No ads, no swaps.