← Back to docs

Weekly Planner Factory

Weekly Planner Factory

The authenticated Weekly Planner combines school days, transport, appointments and laundry into a Monday-Sunday week view. Each week follows ISO week numbering and the Europe/Stockholm timezone.

Plan your own week

Every Tools account has an independently editable personal planning profile. Open the planner, choose the current, previous or next week, then create an activity with a date, category, title and optional start/end time. All-day events cover study days and other dates without set times.

Types: School, Study day, Bus and travel, Laundry, Appointment and Other. Each may include notes. Travel entries can record a departure place, destination, route number and school-only coach. The repeat field creates the same activity on the same weekday for up to 12 consecutive weeks. Edit an activity to move it to another date or change its details.

School journeys and special school buses

Enter a home stop and school stop under profile settings, then add school hours as a timed School event. The school card links to Transit Planner with that day's first and last lesson times. Transit Planner uses actual Skånetrafiken journey searches for journeys to school and home. No departure time or bus line is invented.

Special school-only/gymnasium buses may not appear in regular searches. Record their confirmed travel times as a Bus and travel event with route/line, origin and destination. Profiles also support a separate school-bus note. Confirm such services with the school or operator.

Add a Study day as an all-day event once the date is confirmed. If School or Bus and travel is still present on that date for the same profile, the planner flags this for checking.

Laundry and booking warnings

Add a Laundry activity on the intended date and time. Leave its status at "Needs booking" until the slot has actually been reserved, then switch to "Booked". The planner surfaces a reminder seven days ahead, including when the target day lies in the coming weeks. It flags overlapping appointments, school and travel in visible profiles. These warnings are not bookings and do not contact the laundry provider.

Family profiles with child-owned planning

A guardian can create additional standalone planning profiles (for example, shared laundry or a person without a Tools login), which they manage. A child with an account independently owns and edits their own plan.

A family group is administered separately at My families. Only accepted members of a guardian-owned group can be invited to share weekly planning. Family membership never automatically grants access. A child receives a separate planner invitation and may accept or decline. Accepted sharing is read-only for the guardian by default. The child may explicitly grant editing, independently permit their connected Google Calendar to be read, modify either permission, or revoke sharing at any time. Leaving the family group immediately ends planner visibility. The child's events stay with their account. Parent-managed standalone profiles do not silently merge into child-owned profiles.

No Score, health, Microsoft To Do or unrelated permission is granted.

Google Calendar overlay

Connect a personal Google Calendar under My MCP connections, then opt into "Show Google Calendar" in the planner view. Only the requested week's events are read and displayed beside local activities. A guardian can see a linked child's Calendar events only after separate planner calendar consent. Google OAuth remains per-account. Tools does not create or modify Google events from this page, and does not automatically call OpenAI. School schedules and bus times are never fabricated.

Session API

Signed-in web clients can use /weekly-planner/data?date=YYYY-MM-DD with optional profile=VISIBLE_PROFILE_ID and calendar=1 query parameters. The JSON response includes authorized profiles, the ISO week, its visible activities, conflict/booking warnings and permitted Calendar overlays. The route enforces the same session and resource authorization as the web UI, returns private no-store data and is not a public bearer-token API. Mutations require the web session and CSRF protection. Routes are unversioned.