Document parental controls with a short register that answers seven questions: who is authorized, which child account is supervised, which devices are enrolled, what each rule is meant to do, how it was tested, what exceptions exist, and when it will be reviewed. Keep passwords, temporary access codes, precise location history, and private message content out of the document.
Record people by role, not by device nickname
List the family organizer, other authorized parent or guardian, child account, and the adult responsible for routine review. Note the platform role each person holds and the date it was verified. Avoid labels such as "parent phone" because devices change while account authority persists.
Microsoft's Family Safety roles guide distinguishes organizers from members: organizers manage membership, limits, permissions, and enabled activity reporting, while member devices must be added for several controls. Apple's Family Sharing overview similarly assigns child-account and Screen Time management to organizers or parents and guardians. Use the provider's actual role names in the register.
Make one row per child-device relationship
A useful device row contains child account, platform, device model, device name, operating-system version, enrollment date, last seen date, and enrollment state. Note whether the child uses another school or work account on the device and which controls do not apply to that account. Do not record the device serial number unless there is a genuine inventory need and the document is protected.
Microsoft says in its device connection guidance that devices must be connected to the family group for screen-time controls and that a child's Windows account should be a standard user. Google says in Family Link setup guidance that supported device types differ and that daily limits may apply separately to each Android device or Chromebook. Document scope per device rather than assuming one account setting behaves identically everywhere.
Write the purpose before the setting
For each control, record the family decision, technical setting, scope, owner, and test. Example: "School nights: device unavailable from 9 p.m. to 7 a.m.; applies to phone and Chromebook; emergency calling remains available; reviewed by guardian; last tested September 12." This is more useful than a screenshot of a toggle because it preserves intent when the interface changes.
Cover time limits, downtime, app installation and purchase approval, content ratings, browser filtering, communication, location, privacy or activity reporting, and any always-available apps. Google summarizes these supervision categories in its parental controls guide. Mark features the household intentionally does not use so a future reviewer does not treat a blank as an oversight.
Separate routine exceptions from emergency access
Document who can approve more time, a new app, travel access, schoolwork, medical needs, or a temporary communication exception. Record the reason and expiration, not the child's private content. Temporary changes should have a return-to-normal date and a test that the original policy resumed.
For recovery, record only where to obtain official help. Google's parent access-code guidance says the code is obtained through Family Link or the web and is not delivered by email or SMS. The register should link to that process, not store a code or screenshot.
Protect the document itself
Store the register where authorized adults can reach it after losing a phone, but where children, guests, and unrelated accounts cannot edit it. Use revision history or dated exports. Do not include passwords, backup codes, full birth certificates, exact location history, browsing history, or message transcripts. If evidence is needed, record "filter test passed" with the date and device rather than the blocked content.
Give each change an entry: date, decision owner, setting changed, reason, devices affected, observed test, and next review. After a password reset or account-role change, repeat the affected tests. Google warns in its child account management guidance that a password change signs the child out and supervision does not work until the child signs in again.
Review the register with the family
Review after device replacement, major updates, school transitions, travel, age changes, or changes in guardianship. Explain rules in age-appropriate language and make the request path visible. Retire obsolete device rows instead of deleting their history.
Good documentation is not surveillance. It is a minimal operational record that preserves the family's decisions, makes responsibilities clear, and lets an authorized adult verify that the controls work as intended.
Sources
- Roles, Permissions and Data Sharing in Family Safety — Microsoft Support
- How Family Sharing Works — Apple Support
- How to Connect a Device to a Microsoft Account — Microsoft Support
- Get Started With Family Link — Google For Families Help
- Manage parental controls and settings — Google For Families Help
- Unlock Your Child's Device — Google For Families Help
- Manage Your Child's Google Account With Family Link — Google Account Help