When should a child get their first phone? A readiness checklist

The short answer: there is no evidence-backed correct age, and the numbers people quote — surveys putting the average first phone somewhere around ages ten to twelve — describe what families are doing, not what works. Readiness is a better test than birthdays, and the most useful question isn't phone or no phone but which device solves the actual problem, since a watch or a basic phone covers "I need to reach them" without handing over the internet.

Key takeaways

• Age is a weak predictor; readiness isn't. Two eleven-year-olds can be years apart on impulse control, honesty about mistakes, and looking after their belongings.
• Separate the need from the device. Most first phones are bought to solve contactability. That problem has smaller solutions.
• Set it up before you hand it over. Restrictions added to a phone a child already owns feel like confiscation; the same restrictions present on day one are simply how the phone works.
• Plan for the social pressure, because it's real. "Everyone else has one" is often close enough to true that dismissing it costs you credibility.

Isn't a locked-down phone just going to be worked around? Some of it, eventually — which is why the agreement matters more than the settings. Controls buy time and reduce accidents; they don't substitute for trust.

Does waiting longer actually help? It reduces the years of exposure during the period when self-regulation is weakest. It isn't protective on its own, and a child who gets a phone at fourteen with no preparation is not better placed than one who got a supervised phone at eleven.

---

Why "what age" is the wrong question

The research here is genuinely unsettled. Studies linking adolescent phone ownership to wellbeing tend to find small effects that vary enormously by how the device is used, and the honest summary is that the content and the context matter more than the hardware or the birthday.

What that leaves you with is a judgment call about a specific child. Which is unsatisfying, but it's the real state of the evidence, and any article that gives you a confident number is inventing certainty that doesn't exist.

The readiness checklist

Not a scorecard, and not all-or-nothing. Look for a pattern rather than a perfect run:

• They look after their things. A child who loses a water bottle a week will lose the phone. That's not disqualifying, but it should shape how much you spend.
• They tell you when something goes wrong. This is the single most important one. The value of a phone your child will come to you about is enormous; the risk of one they'll hide is the whole risk.
• They can stop an enjoyable activity when asked. Not cheerfully — just without it becoming a two-hour event every time.
• They understand that messages are permanent. Screenshots exist; "delete it" isn't a remedy.
• They can be alone with boredom. A child who cannot tolerate an unstructured ten minutes will reach for the phone every single time.
• There's a real reason. Walking home alone, changing schools, a second household, an after-school activity that ends at unpredictable times.

If most of these are shaky, that's information about what to work on rather than a verdict — and several of them improve fastest with a smaller device first.

The ladder between nothing and a smartphone

Most families jump from row one to row five in a single step, usually under pressure, and then spend two years trying to add rules retroactively. The middle rows exist precisely to avoid that.

Set it up before you hand it over

The difference between "this is how the phone works" and "I'm taking things away from your phone" is enormous, and it's determined entirely by sequence. Before the phone is unwrapped:

1. Create it as a child account in Family Sharing, not as an adult account you later downgrade — the downgrade path is far more painful.
2. Turn on content restrictions and purchase approval, and set an app age rating. Our step-by-step iPhone Screen Time setup covers the specific toggles.
3. Decide which apps exist on day one. Social media can arrive later; it's much easier to add an app than to remove one. If a specific service is the concern, blocking it properly is more durable than deleting the app and hoping.
4. Set downtime overnight and agree where the phone sleeps. Outside the bedroom is the version that holds.
5. Know what a determined child can undo. Being realistic about where Apple's controls have gaps is what stops you relying on a setting that isn't as solid as it looks.

The agreement is the actual control

Write it down, keep it to one page, and have both of you sign it. The point isn't legalism — it's that a written agreement makes consequences predictable rather than improvised at the moment you're angriest.

Worth covering: where the phone charges overnight, what happens if it's lost or broken, that you can look at it and under what circumstances, which apps need asking about first, and — the one most families forget — what happens when they make a mistake. A stated policy that coming to you about a problem always goes better than hiding it is the clause that earns its keep.

Daily limits should sit inside whatever your household already does about screens generally; the age-by-age guidance is the ceiling, and a phone shouldn't quietly raise it just because the screen is smaller.

When everyone else has one

Sometimes this is exaggerated and sometimes it's simply accurate, and it's worth finding out which before responding. If your child genuinely is the only one without a phone, the social cost is real — group plans do get made in group chats, and being outside them isn't nothing.

Two things help. Talk to other parents in the year group, because the family that waits alone has a much harder time than four families that wait together. And if you're going to wait, give the child something to say — an agreed reason and an agreed date beats an open-ended no, which reads to a twelve-year-old as never.

Frequently asked questions

What's the average age for a first phone?

Surveys in the US and UK generally put it somewhere around ten to twelve, and it has drifted younger over the last decade. Treat that as social context rather than a recommendation — it tells you what other families decided, not what suited their children.

Is a smartwatch a good first step?

For contactability, it's often the best value on the list: calls and messages with the people you approve, location if you want it, and no browser, no app store, no feed. The main limitation is social — it doesn't get a child into the group chat, so it solves a parent's problem more completely than a child's.

Should I be able to read my child's messages?

Whatever you decide, say it in advance. Announced monitoring that decreases as trust is demonstrated works reasonably well; secret monitoring discovered later damages the relationship more than most of what it detects. Younger children generally expect oversight; by mid-teens, blanket message-reading tends to push conversations to apps you don't know about.

What about a hand-me-down phone?

Fine, and cheaper, but wipe it fully and set it up from scratch as a child account. An old phone that keeps your Apple ID, your app history and your saved logins is the most common way a child ends up with adult-level access nobody intended.

My child already has a phone and no rules. Is it too late?

No, but change it gradually and explain the reasoning rather than announcing it. Start with the overnight rule, since sleep is the easiest change to justify and the one with the clearest benefit, and add from there once that has settled.

<p class="note-disclaimer">General guidance for parents, not medical or psychological advice. If you're worried about your child's mood, sleep or online safety, speak to your pediatrician, GP or a qualified professional.</p>