By EdCaptain editorial desk · Published
Your child points a phone at a square on a poster. A link appears, and their thumb is already moving. The code looks official because the poster does. But the important decision is still ahead: where will that link take them, and is that where they meant to go?
For families with children aged 10–18, make the pause the skill. A QR code can be a convenient route to information. It is not a certificate saying the destination is trustworthy.
Notice the step between recognising and opening
On supported devices, the camera can recognise a code and display a link before the person opens it. Apple’s iPhone and iPad instructions describe pointing the camera at the code and tapping the link to open the content. Google’s Pixel Camera instructions similarly describe a link or bubble that the user taps.
That is a useful place to stop. Other scanners and versions can behave differently, so an adult should check the device’s actual workflow first. Do not promise that every scanner will wait in the same way. You do not need an unfamiliar scanner app simply because a poster recommends one.
Try: “Before we open it, let’s see what it says it will open.” If the preview is too short, hard to read or unclear, uncertainty is a reason to use another route.
Check who put the code there
The physical setting matters. A code supplied directly through a school’s established communication channel has a different context from an unlabelled sticker found on a wall. Neither context removes the need to check an unexpected request.
The US Federal Trade Commission’s QR-code warning describes reports of genuine parking codes being covered by fraudulent ones. Its advice includes inspecting the destination link for spelling changes before opening it.
If a sticker looks added, damaged or out of place, do not ask the child to peel it off or investigate. An adult can ask the responsible venue or organisation. Standing in a public place is not an obligation to keep using the code, particularly near roads, parking areas or queues.
Read the destination, then ask whether it makes sense
Use three questions:
- Who is the source? Do we know which organisation supplied this code?
- Where is it leading? Does the visible address match information we have checked independently?
- What is it asking us to do? Does that action fit the reason we came?
A menu that suddenly needs a card payment, or a homework resource that unexpectedly asks for a new account, deserves a pause. It may need clarification; the child does not have to decide alone whether it is a scam.
Spelling checks can reveal a problem, but a tidy address or familiar logo cannot prove safety. Avoid teaching a child to judge a destination from one reassuring detail. When the address is shortened or the preview does not make the destination clear, go through a known official website, app or contact instead.
You can say to school staff: “Could you send the resource through the usual school channel or provide an accessible web address?” For a venue, ask whether there is another way to see the information. An alternative is especially useful when a child cannot comfortably aim a camera or read a small preview.
Practise without scanning anything
Materials: three scraps of paper and a pencil, or spoken descriptions. No phone, live link or working QR code is needed. Describe three invented situations: a class worksheet, an unlabelled sticker and a menu asking for payment.
- Choose the purpose. Say what the fictional child wanted: read a worksheet, find information or look at a menu.
- Pause at the preview. Pretend the phone has shown a link. Ask what the child would want to know before opening it. Do not invent a real-looking malicious address.
- Add an unexpected request. The page wants a password or payment. Ask whether that matches the original purpose.
- Choose a different route. The child can ask the teacher through the usual channel, ask the accompanying adult or use an independently known official site.
- Reflect. Ask, “What made us stop? Which question could we ask next time?” There is no reward for being the fastest to open something.
Ages 10–12: the adult handles the phone and any sign-in or payment decision. The child’s complete role is to name the purpose, notice a mismatch and ask for help. Read the scenario aloud or let them point to one of the three questions.
Ages 13–18: invite your teen to lead the source-and-destination check and explain an independent route. Agree that unexpected payment, installation, credential or permission requests still mean stopping for support. Technical confidence does not require them to certify an unfamiliar website.
For a variation, imagine the same code arriving in a message rather than on paper. Our suspicious-text routine helps with that separate delivery route. Practise verbally rather than forwarding a real suspicious message.
If your child already opened it
Start with thanks for telling you. Ask what happened next: did they only open a page, enter information, authorise a payment or install something? Close the suspicious page and do not use its supposed support contact.
The FTC advises changing exposed or reused passwords and checking transactions after a suspected QR scam. Use the genuine service independently from a trusted device; adults should contact the real payment provider promptly about suspicious transactions. If something was downloaded or installed, get trusted device support rather than another “fix” offered by the page.
Our account-security guide covers passwords, additional authentication and recovery. Do not claim that merely closing a page reverses information already submitted, or that every scan means an account was compromised.
Keep the phone and apps updated through their normal trusted settings. The FTC warning also includes a US reporting route; use the appropriate official service where you live.
The aim is not to make every QR code frightening. It is to give the child a useful choice at the moment of uncertainty: “I can stop here and find another way.”
Sources and further reading
- FTC: check QR-code destinations and respond to suspected scams
- Apple Support: scanning QR codes on iPhone and iPad
- Google Pixel Camera Help: QR-code scanning
Read our editorial policy and review methodology.










































































































