Parental controls often span an adult account, a child account, a family group, one or more devices, individual apps, and platform-level restrictions. A change log prevents a fix on one device from being mistaken for a family-wide fix.
Define the failing behavior precisely
Record the child account, supervising adult account, device model, operating-system version, app or service, network state, control being tested, and the time of the test. State the symptom in observable terms: an app remains available after it was blocked, a permission is still granted, a schedule applies on one device but not another, a purchase request goes to the wrong adult, or a setting cannot be changed. Do not record passwords, private messages, browsing contents, or a child's location in the change log.
Google's Family Link app-permission guidance says settings may need to be repeated for each device and that disabling some permissions can keep an app from working correctly. It also distinguishes between permissions controlled only by parents and permissions a child may also grant. Log both the device and the permission authority before changing a rule.
Confirm the control plane
Verify that the expected adult and child accounts are in the same family arrangement and that the device is signed into the intended child account. Then open the setting from the official management path rather than from a saved shortcut. Google's parental-control overview describes Family Link controls for account settings, app and screen-time limits, supervised-device location, and content restrictions. Those controls do not all have the same scope, so record which category you changed.
On Apple devices, confirm whether Screen Time is managed through Family Sharing or directly on the child's device. Apple's Screen Time guidance explains that a parent or guardian in the family group can manage app, content, communication, schedule, and privacy restrictions, and that settings can vary by software version and region. Do not translate an Android menu path into an iPhone procedure or assume that identically named controls have identical effects.
Use a controlled test sequence
Start with a non-urgent rule and one device. Capture the before state, make one approved change, note whether the device was online, allow the platform's normal sync opportunity, and then test from the child's device. If it fails, check account identity, family role, device enrollment, software version, app-specific permission, and conflicting schedule before changing another rule. Record rollback instructions beside every change.
Separate policy from enforcement. A screenshot of the parent setting shows configuration, while the child's device test shows whether the rule is enforced. Preserve both without exposing personal content. When testing a block or limit, verify normal access is restored after rollback. For safety-critical communication or access needs, use a direct family plan rather than relying on an unverified control during troubleshooting.
Close only after scope is clear
Repeat the test on each device expected to receive the rule. Record which platforms passed, which remain unresolved, and who owns the next action. If a change affects only new apps or only one device, say so plainly. Keep the log short enough to use: timestamp, operator, account roles, device, setting path, before value, after value, expected result, actual result, evidence, and rollback.
Sources
- Manage your child's app permissions — Google
- Manage parental controls and settings — Google For Families Help
- Set up parental controls to manage your child's iPhone or iPad — Apple