Checklist: every task with a box, an owner and a date

Tasks grouped by deadline, each with a box to tick, for a crew, a couple or a family.

2 live examples

The example: Planning a 150-person company offsite

Seven deadlines, four owners, counts that update

Planning a 150-person company offsite

Open the exampleThe names and numbers are made up.

What to notice

  • It opens at 9 of 35 done. Those nine ticks are in the page itself, as the organizer left them on Monday, March 1.
  • Tap Jun and the list narrows to Jun's six tasks, and the counts are redone for those six.
  • "Three months before" reads 4 of 5: the facilitator isn't booked, and a line under that task says a decision is due Friday, March 5.

The prompt that starts one like it

Make a planning checklist for [event, date and headcount] as a single HTML page for the people helping me. Group the tasks by deadline, each group with its due date. Every task gets a checkbox and one owner: [paste tasks and names]. Show a done count per group and overall, add buttons to show one person's tasks, and start with these ticked: [list]. Say on the page that ticks aren't saved or shared. It must work on a phone. Then publish it on sharable.link with a password.

The example: Iris and Ben's wedding, ten months out

Month by month, helpers named, prints on one sheet

Iris and Ben's wedding, ten months out

Open the exampleThe names and numbers are made up.

What to notice

  • Each group is headed by the time left and when that is, from "Ten months before" in November 2026 to "Afterwards", by mid-November.
  • Three lines end in a boxed "open" where a helper's name would be. Those are the jobs the couple hopes family will claim.
  • Printed, all 43 lines fit one letter-size sheet in two columns, and every box comes out empty even if it was ticked on screen.

The prompt that starts one like it

Make our wedding planning checklist as a single HTML page to share with family. The wedding is on [date] at [venue], with [number] guests. Group the tasks by months before the day and name each month: [paste tasks]. After a task, put the name of whoever has taken it, and mark the ones still open. Make it elegant, with boxes that tick on screen and a print stylesheet that fits one sheet and prints every box empty. Then publish it on sharable.link with a password.

A checklist on a page has one limit worth knowing first: the ticks aren't saved. Tick a box in either of these and it stays ticked until you reload, and nobody else ever sees it. So a page is a good place to publish a list and a poor place to keep score. The offsite example carries its organizer's ticks inside the page, and the wedding one is meant for a printer.

Who it's for

Anyone who has worked out the steps and needs other people to follow them: an office manager with a crew of four, a couple with willing parents, a family about to move house. Send it once the tasks have owners and dates.

If several people need to tick the same list and watch each other's progress, keep the working copy in a shared spreadsheet or a task board. The page is for everyone who doesn't live in that tool.

What a good one contains

  • Tasks that start with a verb and can be finished. "Book three 56-seat coaches" gets ticked. "Transport" never does.
  • Groups by deadline, with a real date. "Six weeks before, by Thu, Apr 8" shows the crew what's due now. The wedding list names the month instead, for relatives who don't count in weeks.
  • One owner per task. The offsite list has a first name on every line. Put two names on a task and each waits for the other.
  • The number inside the task. 110 singles and 20 twins, $27,000 for the second payment, 7:30 am at the front doors. Nobody should have to open another document to do the job.
  • A count per group and overall. "4 of 5" on a group that was due in February says one thing is late without a meeting.
  • Open jobs marked as open. A small, named job is easier to say yes to than "tell us if you can help".
  • A paper version. One sheet on the fridge gets read more often than a link in a family chat.

When five people need the same ticks

Pick one keeper of the list. On the offsite page that's Imani. The crew messages her when something is done, she updates the list in her Claude conversation and publishes it again over the same link. Everyone who opens it then sees 10 of 35 where it said 9. The page says so in a note, so nobody assumes their ticks are shared.

That holds up while the list moves a few times a week. Date the keeper's ticks, as the offsite page does with "as of Monday, March 1". Without a date, a week-old count looks current.

How to send it

With a password. A planning list names budgets, suppliers and where people will be on a given day. A password keeps it to the crew or the family, and nobody has to sign in.

Every page you publish gets one link that opens in any browser. You choose who can open it: anyone with the link, anyone with the password, or only the people and company domains you name, who sign in with Google or Microsoft. Change the page later and the link stays the same.

Make yours in Claude

Add the connector once, then publish from any Claude conversation and get a link to send.

Add Claude Connector

Already have the file? Upload it here.

More in team and operations

  • Meeting minutes: What a meeting decided and who does what by when, for the people who were there and the ones who weren't.
  • Standard operating procedure: One task written out step by step, with who does what, the tools, and how to tell each step is done.
  • Employee handbook: A short guide to hours, time off, expenses and equipment that every employee and new hire can open.
  • Performance review: A manager's written review for one person, sent before they talk: goals, evidence, strengths, next steps.
  • 30-60-90 day plan: A new hire's first three months in three phases, each with a test both sides can check.
  • Employee onboarding: The page a new hire gets before day one: the week's schedule, a checklist, the people and the tools.
  • All use cases

Keep reading