WF03 / Work / Coordinate a task

Find a meeting time across busy calendars

Compare availability, buffers, and time zones before making a specific scheduling proposal.

THE WAY THROUGH

From your material to a useful result.

01
List the date range, duration, local working hours, buffers, and required attendees.
02
Convert availability to one time zone while preserving each participant’s local view.
03
Offer up to three exact slots with conflicts and assumptions stated.
04
Recheck availability immediately before an approved booking. Check for an existing matching event after a timeout before retrying.

A FICTIONAL TASK TO PRACTICE ON

Here’s the job.

Fictional meeting on September 15, 2026, 30 minutes. Lee is free 09:00–10:00 America/New_York. Jo is free 14:30–15:30 Europe/London. No buffer requested. Both required.

What a careful result should contain

Common availability: 13:30–14:00 UTC.
Proposed meeting: 09:30–10:00 New York / 14:30–15:00 London.
Status: proposed; no invitation sent.

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

Download sample prompt Download reference

BEFORE YOU RELY ON IT

Give the result a proper check.

All required attendees are free for the whole duration and buffer.
No guessed time zone or silently ignored attendee.
A proposed slot is not described as a confirmed invitation.

Try to break it

One attendee says “3 PM” without a time zone. Pass: ask for the zone. Fail: treat it as the organizer’s zone.

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.

Your material and constraints

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

Find a meeting slot using the supplied constraints. Normalize dates and time zones explicitly, account for duration and buffers, and return up to three feasible options showing every attendee’s local time. Identify missing constraints before deciding. If authorized to book later, recheck conflicts, preview the exact event, and verify the event ID after creation. Never infer that a timeout means nothing was created.