Start by defining the incident
Treat a parental controls incident as a mismatch between the household's intended rule and the device's observed behavior. Examples include a child account using an app outside the expected schedule, an approval request going to the wrong adult, or a restriction changing unexpectedly. Record what was observed, the device, the child account, the date and time, and the rule that was supposed to apply. Avoid guessing about who changed a setting until the account and device history have been checked.
Preserve a small evidence set
Capture screenshots of the relevant setting, the unexpected screen, and any approval or notification. Note the operating-system version and whether the device was online. Save these items in a household-controlled location with a short incident identifier. Do not collect unrelated messages, browsing activity, or other private material merely because it is accessible. The goal is to preserve enough evidence to reproduce the mismatch while minimizing unnecessary surveillance.
Check the account structure first
Confirm that the device is signed in to the intended child account and that the expected adult is the family organizer or supervising parent. Apple's guidance places child Screen Time management within Family Sharing. Google's Family Link guidance likewise ties supervision to the child's Google Account and supported devices. A rule attached to a different account can look like a bypass even when the platform is behaving as configured.
Verify the control at its source
Open the authoritative parental-control settings instead of relying on a remembered rule. For Apple, review Screen Time for the child from the parent's device. For Google, review the child's controls in Family Link. Compare downtime, app limits, content restrictions, and approval settings with the household's written expectation. If a password or parent access code is required, use the platform's normal verification path. Never record the code in the incident note.
Make one change at a time
Choose the smallest reversible correction. Examples include assigning the right account, restoring one schedule, or correcting an approval recipient. Record the old value, the new value, who authorized the change, and why it was made. Do not reset every control at once, because a broad reset destroys the evidence needed to understand which setting caused the problem.
Test from both sides
After the change, test the exact scenario on the child's device and verify the result on the parent's device. Google's instructions explicitly recommend checking the child's device after a parent changes account controls. Test both an allowed action and a blocked action so the result is not based on a single screen. Record the time, the device state, and the observed result.
Close the incident with an owner
Mark the incident resolved only when the intended rule is written down, the device behavior matches it, and an adult owner is responsible for the next review. If the mismatch returns, reopen the same record and add the new observation rather than creating disconnected notes. Escalate to platform support when the expected setting is present but repeated controlled tests still produce inconsistent behavior.
Keep the family conversation separate
The technical record should describe settings and observations, not assign motives. Discuss expectations with the child in age-appropriate language, including what is limited and why. This separation makes the record useful for troubleshooting while reducing the chance that an uncertain technical event becomes an accusation.
Sources
- Use Screen Time to manage your child's iPhone or iPad — Apple Support
- Manage your child's account with Family Link — Google for Families Help
- Unlock your child's device with a parent access code — Google Families Help