Set allowed hours on the child’s account, not a chart on the fridge

Part of our guide on setting up family link

Enforce screen time limits directly on your child's account, not with a laminated chart.

Why a Printed Schedule Has No Effect Once Signed In

Say you print a schedule and stick it on the fridge. The child signs in and ignores it. A printed schedule lacks enforcement. The OS must control the hours.

A schedule only works if it lives on the child's account. The OS enforces it, not a piece of paper. This ensures the child cannot bypass the limits easily.

A signed-in session runs on a timer, not on the paper. Windows checks the window at sign-in and again when it closes. Cross the end time and the account signs out. The paper does nothing at either moment. Set the end time 15 minutes before you want the screen dark. That leaves room for a save prompt.

The child will find the gaps on their own. A shared login defeats the whole setup, because limits attach to the account, not the machine. Two children on one login share a single window. Give each child their own Microsoft account. Then a bedtime of 20:30 does not force the older one off at the same minute. For the detail, see our notes on setting up Screen Time website filters.

The Account Question First: Local vs Microsoft

Picture setting a schedule on a Windows local account. It won't work. Only a Microsoft account with Family Safety allows time limits. The child must have their own account.

A Windows local account cannot be time-scheduled. Use a Microsoft account instead. This integrates with Family Safety for proper scheduling and content filtering.

A local account stores its settings on the machine alone. Family Safety needs a cloud profile to push the window down. Convert the local account in Settings, under Accounts, then Your info. Select Sign in with a Microsoft account instead. The child's desktop stays as it is. We go through local settings for multiple computers step by step elsewhere on the site.

Family Safety uses the birth date to set the age band. Some settings only appear inside that band. The same birth date later controls when the account leaves family group management. Enter it correctly the first time. Changing it afterwards involves support.

The child needs the password to sign in. If you hold it, the schedule works and the child cannot swap accounts. Write it down somewhere the child cannot reach. Resetting it later takes two minutes from your own account.

Where Allowed-Hours Windows Live in Settings

Say you want to set allowed hours. In Windows, it's under Family Safety. On macOS, it's called Downtime. Same idea, different names. Check the child's account settings.

In Microsoft Family Safety, allowed hours are under Activity Controls. On macOS, it's in Screen Time settings as Downtime. Both limit usage within set windows.

Family Safety splits the week into days. You set a start and an end for each block, and a day can hold more than one block. School nights at 16:00 to 19:00 then 19:30 to 21:00 leaves the dinner gap. The child signs back in when the second block opens.

Screen Time on macOS works in the same shape. Downtime takes a start, an end and a repeat rule for school days against weekends. Weekends usually need a wider window. Set Saturday and Sunday separately, or the weekday cut-off fires on a free morning.

Both systems also decide what happens at the edge. Windows signs the child out when the window closes. macOS can block the whole device or only stop apps. Pick one behaviour and tell the child which it is.

How to schedule computer use for children and test it

Test the schedule on the child’s actual Windows profile. Open the Family Safety app or family.microsoft.com, select the child, then choose Screen time > Device > Schedule. Check the path against the current product before publishing, since Microsoft can rename labels.

Sign in with your own Microsoft account, the adult account linked to the family group. The child’s Microsoft account must already belong to that group. Select the child’s name, not your own, before changing the schedule.

Use a quiet moment for the test. Sign out of the parent profile, then sign in at the child’s Windows login. Check the displayed name before entering the password. Set a short test window only if changing the normal schedule won’t disrupt schoolwork or sleep.

Watch the screen as the allowed period ends. Windows can show a warning, lock the session, or sign the child out, depending on the current setup. A blocked sign-in can appear after the child signs out. The exact message can change with Windows updates.

If it never signs out, the child is on the wrong profile. Check the name on the login screen. Test the opening edge later, too. Sign in while the device should remain blocked, then try again after the window opens. Record what Windows actually does.

1. Open Family Safety or family.microsoft.com and select the child.
2. Confirm the child’s name on the Windows login screen.
3. Test one blocked period and one allowed period.
4. Record the warning, lock, sign-out, or blocked sign-in you observe.

Clock and offline behaviour can change the test result

Keep the device online during your first test. Microsoft says limits are applied server-side where the device is online, so changing the local clock alone should not open the window. Test the schedule before relying on it.

An offline device can behave differently from an online one. The device may rely on previously received settings, and the result can depend on its connection history. Turn Wi-Fi off only after the normal online test works. Record whether Windows still blocks the child.

Daylight-saving changeover is a known edge case. Re-check the actual block time on the changeover day instead of predicting it from the clock change. Open the child’s schedule and confirm the displayed times before the next restricted period.

Protect the parent session as carefully as the schedule. A child using an unlocked parent account can work around restrictions without changing the child’s settings. Lock Windows with Win + L whenever you leave, and keep the parent account password private.

Fast user switching can also leave another session available. Sign out of the parent account before testing the child’s limits. If the child reaches a desktop under the parent’s name, stop the test and secure that account first.

1. Run the first test while the device is online.
2. Repeat the check after a controlled offline test.
3. Re-check the actual block time after daylight-saving changeover.
4. Lock or sign out of every parent session.

Scheduling Content as Well as the Window

Say you want to filter content too. Set app limits in Family Safety. This fits certain activities inside allowed hours. SentryPC offers cloud-based monitoring for this.

SentryPC monitors user activities in real-time. It filters content and applications based on settings. This complements the allowed hours for comprehensive control.

However, SentryPC requires setup. It comes with step-by-step instructions, making it accessible for parents. Consider it if manual filtering feels overwhelming.

App limits run on a separate clock from allowed hours. A game can carry a one-hour daily cap inside a three-hour window. The window decides when, and the cap decides how much. Set both or the child fills the whole evening with one app.

Blocking by category beats blocking by title. Family Safety filters web content into levels, and the strictest level also narrows search. A blocked page shows a request button. You'll get an email when the child asks for access.

SentryPC adds reports on top of the limits. It logs sites, apps and keystrokes, then sorts them by account. Setup takes longer than the built-in tools, so start with Family Safety. Move up only if the built-in reports leave you guessing.

Questions people still ask

As a tech enthusiast, I've seen firsthand how proper scheduling can balance screen time effectively.