WF01 / Life / Make a file

Turn school notices into an importable calendar

Extract the dates once, resolve uncertainties, and make a calendar file you can inspect before importing.

Make it yoursSee the sample

THE WAY THROUGH

From your material to a useful result.

  1. 01

    Extract an event table first: source line, title, date, start, end, location, and all-day status. Keep uncertain fields visible.

  2. 02

    Confirm the year and time zone. Separate provisional events; compare against the existing calendar before creating anything.

  3. 03

    Generate an .ics file containing confirmed events only. Use stable event IDs and exclusive end dates for all-day events.

  4. 04

    Preview the file in a separate calendar. Check an all-day event and a timed event, then import only once.

A FICTIONAL TASK TO PRACTICE ON

Here’s the job.

Fictional school: Maple School. Year: 2026. Time zone: America/New_York. Notice A: School closed September 21–22, all day. Notice B repeats the September 21–22 closure. Notice C: Parent evening October 7, 18:00–19:00. Notice D: Photo day Friday, date to be confirmed.

What a careful result should contain

Confirmed: one closure, September 21–22; one parent evening, October 7, 18:00–19:00 America/New_York.
Needs confirmation: photo day.
The downloadable reference contains 2 events. The closure ends at the start of September 23 in the calendar file.

This is an authored reference, not a captured Grok Bot, Instinct, or other product run.

BEFORE YOU RELY ON IT

Give the result a proper check.

  • A missing year or time is a question, not permission to guess.
  • A two-day closure occupies exactly two dates.
  • Repeated notices do not create duplicate events; an update needs an explicit replacement plan.

Try to break it

The newsletter repeats a closure and says “Friday” without a date. Pass: 2 confirmed events and 1 question. Fail: a duplicate closure or a guessed photo day.

TAKE IT FOR A SPIN

Bring your own details.

Describe your task and paste the source material you want to use. This page prepares a prompt; your chosen AI tool does the work.

These details stay in this page until you copy them. They are not saved or sent to a model here.

Read the full starting instructions
Read the school material below. First produce a source-linked event table and separate unknowns. Deduplicate repeated notices. Use only an explicit year and time zone; ask if absent. After the table is approved, create an importable .ics file for confirmed events with stable UIDs, correct time zones, and exclusive all-day end dates. Return the file, preview table, and excluded items. Do not import or invite anyone.

Did you get a result you could use?