b2KIT

Weekly Planner

Plan your week with a 7-day grid view, time blocks, and recurring event support with local persistence.

Tested tool guide Tested browser tools Checked August 16, 2026

What Weekly Planner does, with a checked example

Weekly Planner lays Monday through Sunday out as columns against a stack of time slots, so you build a schedule by placing blocks on the grid instead of typing rows into a list. Set a block to repeat and it reappears on the same weekdays each week without re-entering it. Every change saves to the browser you're using as you make it, so the plan is still there next time you open the page. The part people miss: that save is tied to this one browser and device - open the tool on your phone or a different computer and the grid starts empty.

Worked example

A concrete input and expected output from the current implementation.

Input

Add a block labeled 'Team standup' from 9:00 to 9:15, repeating on Mon, Wed, Fri.

Expected output

A 15-minute 'Team standup' block appears at the 9:00 slot on the Monday, Wednesday, and Friday columns of the grid, and continues appearing on those three days in later weeks until you edit or delete it.

Marking a block to repeat applies it to every selected weekday going forward rather than to a single date, so it shows up three times per week, not once.

How the result is produced

1

Grid and time blocks

The week is drawn as seven day-columns against a shared column of time labels, similar to a calendar week view. You create a block by setting a start and end time on a given day, and it renders sized to that duration in the matching slot. The tool's feature description doesn't specify the exact interaction for changing an existing block's time or day afterward - whether that's re-entering the start/end values, dragging, or something else - so confirm the edit method in the tool itself before relying on it.

2

Recurrence and local save

Flagging a block as recurring ties it to one or more weekdays instead of a single date, so it renders on that weekday every week the grid is viewed. Edits autosave to storage inside your browser as you make them - no account, login, or outbound sync - which is what makes the plan reload on return but not follow you to another browser.

Good uses

  • Blocking out recurring work hours - deep-work windows, standups, class times - once and having them show up every week automatically
  • Sketching a single week's plan (errands, workouts, meal prep) visually against time slots instead of a bullet list
  • Comparing how a typical week's time is actually allocated across days before committing to a new recurring commitment

Limits and checks

  • Data lives only in the browser and device you created it on; clearing site data, using a private window, or switching browsers means the plan is gone, since there is no account or sync layer
  • It isn't clear from the feature description whether the grid represents this specific week's dates or a reusable weekday template - confirm which before using it to plan something tied to an actual calendar date
  • Recurring blocks likely repeat on a simple weekday pattern; if you need an exception on one occurrence (skip a single Tuesday without breaking the rest of the series), check whether the tool supports editing a single instance before relying on it for that

Common questions

Will this sync with Google Calendar or Outlook, or show up on my phone too?

No. It saves locally in the browser you're using, with no account or network sync described, so a plan made on one device or browser will not appear on another unless the tool offers an explicit export you can re-import elsewhere.

If I edit one occurrence of a recurring block, does it change the whole series or just that day?

That's not confirmed by the tool's description, and the answer matters if you want a one-off exception. Test it on a throwaway block first - edit a single occurrence and check whether the other repeats changed too - before trusting it with a real schedule.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools