The Request System: Turning Screen Time Requests into Life Lessons

Short answer: when your child hits a block, they tap Request Access instead of arguing. You get a notification and grant 15 minutes to 2 hours, or decline, in one tap.

Denials carry a 4-hour cooldown, so the asking can't turn into badgering.

Try it with your family →

The argument you're actually trying to end

The screen time fight is rarely about screen time. It runs like this: your child wants something, they ask at the worst possible moment, you say no while doing something else, and the next twenty minutes go on the tone of voice rather than the request.

Do that daily and you become the obstacle in your child's day. That's the cost most parental control tools ignore — they're very good at saying no and give you nothing to say yes with.

How the request system works

For your child: they hit a blocked app or run out of time, and the block screen offers a Request Access button. They tap it, and they wait.

For you: a notification arrives with what they want, how much they've used today, and what they've asked for recently. You grant 15 minutes, 30 minutes, an hour or two hours — or decline, with a message if you want.

The cooldowns do the unglamorous work:

That's the bit that makes it survivable. Without a cooldown, a request button is just a nag button.

Why this is better than a wall

A block teaches your child that the phone said no. A request teaches them how to ask an actual person for something, and how to hear no without it becoming a scene.

Those are the skills that outlast the phone. And the practical effect is immediate: the negotiation moves off your evening and into a notification you handle in four seconds while the kettle boils.

Making it teach something

Don't reflexively tap approve. Three questions cover almost every case: is this reasonable right now, how have they been this week, and does saying yes here cost anything?

Then reply like a person. "What do you need it for?" or "Is homework done?" turns an approval into thirty seconds of contact, which is the actual point.

Say yes readily when they've been solid, when the reason makes sense, when it's a decent hour. Say no when they hit the limit five minutes ago, when it's late, when responsibilities are outstanding — and say why, briefly, without a speech. "Too late tonight, ask tomorrow and you'll get it" is complete.

Answer promptly, even if the answer is no. A request that sits unread for three hours reads as being ignored, and after a few of those they stop asking and start looking for a way around.

The trust ladder

• First month: approve most reasonable requests. Watch what they do with it.
• Second month: if requests are sensible, raise the base limits so fewer are needed.
• After that: consider dropping the limit on apps that have stopped being a problem.

They're ready for more when requests are well-timed and a no doesn't cause a scene. They need less when the requests come at 2am, when denial produces anger, or when you find them testing the system instead of asking it.

If this isn't your family, turn it off

Some parents don't want a negotiation layer, and that's a legitimate choice. Constant approvals are an interruption, and for some children an openable door is an invitation to lean on it.

Settings → Notifications → Allow Access Requests, toggled off. Blocked apps then just say restricted, with no button. Turn it back on whenever you like — plenty of families start with it off and enable it once things have settled.

Frequently asked questions

They request ten times a day.
The base limit is too low. Raise the daily allowance for whatever they keep asking about by 30-60 minutes. Requests should be occasional; if they're routine, the rule is wrong.

Do I have to explain every denial?
No. Brief reasons help with 12 and 13-year-olds who are still learning where the lines are. With an older teen who's heard it before, "not tonight" is enough.

Can they request during bedtime?
They can ask; you decide. Most parents never approve after lights out, and the 4-hour cooldown means one refusal covers the rest of the night. The requests stop within a couple of weeks.

My partner and I answer differently.
Agree two or three ground rules — nothing after 10pm, always yes for school work — rather than trying to agree case by case. Consistency between you matters more than any single call.

Does my child know the requests come to me?
Yes. There's no hidden mode in ParentalEdge, which is exactly why the request button works — they know who they're asking.

Turn blocks into conversations →

The rest of the pre-teen series: Age-Appropriate Web Access and Time Limits Pre-Teens Accept. For 16-17s, the partnership approach is a different strategy.