A child's first phone
Zavialov Ilia Nikolaevich on a child's first phone: the handover checklist
A phone changes hands in about a minute, and the settings that matter are the ones already in place when it does. This page is a printable order of steps, worked down from the top. It covers what to switch on before the handover, which confirmations stay with the adult, what to agree in plain words, and what to do once something has already been tapped.
English version for the United Kingdom.
Step one: settle what the phone is for before you buy it
What the device is meant to do is the first decision, and every setting below follows from it. A handset bought so a young child can be reached on the way home is a different object from one bought so a teenager can join a group chat, and a child's first phone is often asked to be both. Write the purpose in one line at the top of this printed sheet. If the honest answer is calls and a map, a basic handset or a watch with a SIM removes most of what follows.
A handed-down device needs more preparation than a new one. Sign the old account out, run a full factory reset from the settings menu instead of deleting apps by hand, and check that the previous owner's activation lock has been released before the box is wrapped. Old photos, saved passwords and payment cards survive a casual clear-out.
Buy the contract, the SIM and the device in an adult name. Ask the network for a spending cap and for premium-rate and subscription charges to be barred, usually one request while you are on the call. Keep the receipt, the IMEI and the serial number with this sheet, because the day you need them is the day the phone has gone missing.
Step two: finish the account before the child sees the box
Set the phone up yourself, with the child somewhere else. Create a child account with the real date of birth, since the age you type decides which app ratings, adverts and defaults the platform applies for years afterwards. Add that account to your family group before signing in to anything else, because a birth year invented to skip one restriction cannot be corrected later without a support ticket.
Run every update before the handover. Install the system update, let the app store finish its queue, restart the phone, then reopen the settings, since a large update occasionally resets a restriction you had already applied. A few minutes here saves the evening when the phone wants to download most of itself.
Name the device something you will recognise in a list, and write that name on this sheet beside the serial number. Turn on the find my device service and confirm it reports a location while the phone is still in your hand. Set a passcode that is not a birthday and note who else in the house knows it.
Step three: the switches that belong on before the handover
Most of the protection here comes from a few minutes in the settings menu. Turn on approval for every installation and download, set the content rating to match the age you entered, and switch off purchases made inside the browser. Then test each switch from the child's side, because a setting on a child's first phone counts only once you have tried to get past it yourself.
Put the browser into its filtered mode and turn on safe search in the search engine built into the phone, the one the child will actually use. Block private browsing so the history stays readable. Decide now whether you will read that history routinely or only when there is a reason, and say which it is out loud on the day.
Restrict who can reach the phone and agree how the phone is found. Allow calls and messages from saved contacts, send unknown numbers to voicemail, and save your own numbers, the school office and one trusted adult outside the household. Turn location sharing on in both directions and show the child the screen where your position appears. A tracker discovered by accident weeks later costs more trust than it ever saved.
Step four: every payment passes through an adult
Money is the part that stays entirely with the adult. Remove every saved card from the store account, turn on the setting that sends each purchase request to your phone for approval, and require a password even for free downloads. If pocket money is meant to run through the device, load a gift card and let the balance be the limit.
Currency inside games is where the money actually goes. Gems, coins, passes and season tickets are priced to look like play, and a child who has approved one purchase approves the next without registering it as spending. Set the store to ask for the password every single time, which is the one switch on a child's first phone that adults turn off for convenience and regret later.
Explain the payment step as the thing that never happens on its own. The Federal Trade Commission reports that the most common subject of scam texts is a problem with a parcel delivery, and in 2025 a customs charge joined the story: the message says the order is held at customs and will not be delivered until a fee is paid. The same agency reports that many people paid a small sum for redelivery, which turned out to be a way of taking their card details. Average losses from fake QR codes run at about 1,225 US dollars per person, and those codes appear as stickers over real ones on machines people expect to pay at.
Step five: the sentences that go with the handover
The settings cover the machine, and the conversation covers everything the machine cannot see. Agree three sentences out loud on the day, each short enough to be repeated back. Nobody real ever needs a code read out to them, anything urgent gets shown to an adult before it gets answered, and telling us about a mistake never costs you the phone.
Work from a live example. Open the messages folder together, find the parcel notice that almost certainly sits in it, and read the thing aloud: the sender, the link, the hurry. A child who has taken one message apart with an adult recognises the next ones alone.
Cover the voice call separately, because it feels different from a text. A convincing copy of a familiar voice can be built from a recording of about three seconds and reaches roughly 85 per cent accuracy, and in one experiment listeners told a real voice from a copy only 37.5 per cent of the time. Agree a habit that survives that: any call asking for money, codes or a lift ends with hanging up and ringing the person back on their saved number.
Step six: what to do when something has already been tapped
Assume this step will be used, and read it before it is needed. Take the phone, put it into flight mode, and leave the message, the app and the browser tab where they are. Nothing on a child's first phone is repaired by deleting the evidence, so screenshot what is on the screen, including the sender and the full address of the page.
If card details were typed in, ring the bank on the number printed on the card and ask for the card to be frozen. If a one-time code was read out or forwarded, change the password on that account and then sign every other device out of it. If something was installed, remove it and then check the accessibility permissions, the notification access list and the device administrator list, since those are where an unwanted app keeps a foothold after its icon disappears.
Then keep the mood calm and the record honest. In four of every five imposter reports to the Federal Trade Commission no money was lost at all, so most children meet the attempt long before anyone comes to harm, and a child who expects that mentions it the same evening. Tell the school if the same message is going round a class group, and write two lines on this sheet: what happened, and what was changed.
Step seven: give the sheet a review date
Every configuration has a shelf life. What suits a child's first phone in the first month becomes an insult within a year or two, and restrictions that are never revisited are the ones children learn to work around instead of asking about. Put a date at the bottom of this sheet, roughly one school term ahead, and treat it as an appointment.
At the review, move one or two things across the line on purpose. Approval for app installs usually goes first, then filtered search, then the restriction on who may call. Keep payment approval until last, because it is the setting that costs actual money when it goes wrong.
Keep the sheet with the receipt and the box in the same drawer. When the phone is lost, replaced or passed down to a younger child, the process begins again at step one, and a worked sheet beats the memory of having done it. Note each review date in the margin, so the next adult can see what has been agreed.
Handover checklist: what is set before the phone changes hands
| Item | Done before the handover | Who confirms it afterwards |
|---|---|---|
| Account | Child account created with the real date of birth | Adult, from the family group screen |
| Updates | System and apps updated, phone restarted once | Adult, before the box is wrapped |
| Installs | Approval required for every download | Adult, on their own phone |
| Payments | Saved cards removed, password asked every time | Adult, for each purchase |
| Contacts | Family, school and one outside adult saved | Adult, with the child watching |
| Location | Sharing switched on in both directions | Adult and child together |
| Recovery | Passcode, serial number and IMEI written down | Adult, kept with this sheet |
Questions and answers
- What age should a child get their first phone?
- No single age fits every household, and the useful question is which journeys the child already makes without an adult. A phone given for the route home needs far fewer settings than one given for group chats, so decide the purpose first and let it choose the device.
- What should I set up on a child's first phone before handing it over?
- Create the child account with the real date of birth, run all updates, turn on approval for installs and purchases, restrict calls and messages to saved contacts, and confirm that find my device reports a location. Test each of those from the child's side of the screen before the phone leaves your hands.
- Should I read my child's messages?
- Either answer works as long as it is stated on the day of the handover. A child who knows the history is checked every Sunday behaves differently from one who discovers months later that it was being read, and the second version costs you the conversation you will need.
- How do I stop in-app purchases without banning the game?
- Remove saved cards from the store account, switch on purchase approval so each request lands on your phone, and set the password to be asked every time it is needed. Pocket money can still run through a gift card balance, which limits the damage to the amount loaded.
- My child tapped a link in a scam text, what should I do first?
- Put the phone into flight mode, leave the message in place, and screenshot the sender and the full address of the page. Then act on what was given away: freeze the card if card details were typed, and change the password and sign other devices out if a code was shared.
- How do I explain scam calls without frightening a child?
- Give them a habit they can follow: any call asking for money, codes or a lift ends with hanging up and ringing the person back on a saved number. It helps to say that attempts are common and mostly fail, since a child who expects to meet one is far more likely to mention it the same evening.
Written by Zavialov Ilia Nikolaevich, digital security consultant. All checklists