> ## Documentation Index > Fetch the complete documentation index at: https://support.tuckthis.app/llms.txt > Use this file to discover all available pages before exploring further. # Keep track of what you're waiting on > Hand something off, choose when to check on it, and keep it off your todo list. An **Await** is something you're waiting on from someone else: a reply, a contract, a callback. It isn't yours to do yet, so Tuck keeps it apart from your todos. Awaits have their own page and never show up in todo lists or counts. An Await can wait on people, a calendar event, or a thing you describe. A **parked** Await waits on no one. Use it for something you want to set aside and look at again later. Each Await can have a **check-on date**, the day Tuck brings it back to you. > [!NOTE] > > Awaits are made and managed in the web app for now. On iPhone and Mac, an `await:`, `waiting:`, or `park:` line stays as plain text in the thought. ## Start an Await ### From the composer 1. Switch the composer to **Await**. 2. Type what you're waiting on and `@mention` the people you're waiting on. With no one mentioned, the Await is parked. 3. Add a day if you want one, such as `fri`, `next tue`, `in 3 days`, or `!2026-11-20`. Without one, Tuck uses your default check-on date. 4. Press Enter. For example, `contract from @sam fri` becomes "contract from sam", waiting on Sam, with a check on Friday. Chips under the field show who it's waiting on, or **Parked**, and when you'll check on it. ### With a line in any thought Start a line with: * `await:` or `waiting:` to wait on the people that line mentions. * `park:` to park it. People it mentions still link to the thought, but it waits on no one. As with todo lines, each of these lines becomes its own Await and leaves the thought's text. In Thought mode, a chip such as **+1 Await inside** shows before you tuck. These don't start an Await: `wait:`, a line starting with "Waiting on", and `/wait`, which files the thought into a brain named wait. Lines inside code stay as written. In email, text messages, and the ingest API, only the first line can start an Await. A later line, such as a quoted "Waiting: customer reply", stays in the thought as text. ### From a todo Open an open, one-off todo's card and choose: * **Waiting on…** to pick people, an event, a thing, or any mix, plus a check-on date. Waiting on an event sets the check-on to when the event ends. * **Park** to set it aside. The todo becomes an Await, and its due reminder pauses while it waits. ## Check on your Awaits Open **Awaits** in the sidebar. The tile's count is the check-ons due today or overdue. Active Awaits are grouped into **Check on now**, **Coming up**, and **No check date**. **History** shows Awaits that ended and how. You can filter the page by brain. Awaits that are due also appear in the **Check on** panel on Today. On the check-on date, Tuck sends a reminder such as "Still waiting on Sam: call the vet". When you're ready, choose: * **Got it** when the thing arrived. * **Check again** to look again tomorrow, in 3 days, next week, or on a date you pick. * **Make it a todo** when the next step is yours again. If its due date is still ahead, its due reminder comes back. The todo then says how long you waited, such as "Back from Sam after 6 days". * **Drop it** when you no longer need it. Choose **Edit** to change what an Await waits on or when to check on it. To clear the date, choose **No check date** in its date pill. ## Awaits around your meetings With a connected calendar, Awaits show up around your meetings. **Before you meet.** Today's Schedule lists active Awaits waiting on people invited to an upcoming event, longest wait first. For example: "Still waiting on Sam: the contract (9 days)". Tuck matches invitees by email. Up to 3 show per event, then **and N more** opens Awaits. Each Await shows next to its first upcoming event only. **After the event.** An Await waiting on an event moves into **Check on** once the event ends, with a line such as "Board meeting is over. Time to follow up." An earlier check-on date still comes first. It asks once: after you choose **Check again** or set a new date, its check-on date takes over again. Events from a calendar set to **For reference** don't bring up Awaits. See [Calendar and mail context](https://support.tuckthis.app/use/calendar-mail.md). ## Choose your defaults Open **Settings → Awaits**. * **Default check-on date.** Choose 3 days (where it starts), 1 week, or no check date. New Awaits from the composer, **Waiting on…**, and **Park** use it. * **Weekly sweep.** On the day you pick (Monday unless you change it), Today lists Awaits with no check date, such as "2 Awaits have no check date". Give each one **Tomorrow**, **In 3 days**, **Next week**, or **Drop it**. **Not now** hides the sweep for the rest of the day on all your devices. Awaits you started that day are left out. You can turn the sweep off. These settings sync with your vault. ## Good to know * Archiving a thought drops its active Awaits and cancels their reminders. * A person's page lists the Awaits waiting on them. * Awaits don't sync to Todoist. * With [hosted MCP](https://support.tuckthis.app/use/hosted-mcp.md#work-with-awaits), your AI assistant can start, list, re-date, and resolve Awaits for you. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.