Dots morning briefing workflow
Start the day with decisions, deadlines and the next three actions.
Set up the inputs
Replace the bracketed fields with actual sources, destinations and timing. Connect the relevant plugins or provide the files directly. Keep the first run focused on one project so feedback is easy to apply.
What a useful result looks like
An account review tomorrow appears in both email and Calendar. A good brief lists it once, links to the event and the customer thread, and asks you to choose the proposal version.
Run it once, then repeat
Paste the task brief below and request one complete result. Open the source links, check the dates and owners, and revise the format. For recurring work, have the dot confirm the schedule and destination after the first result meets your needs.
Improve the brief over time
When you edit an output, state the reusable preference behind the edit. Keep project facts in the named source documents. Update the brief when the responsibility changes, and review its end date when the project closes.
Copy this task brief
Responsibility: prepare my weekday morning brief. Sources: [mail labels], [calendar names], [project documents]. Scope: changes since the previous completed brief; on the first run, use the last 48 hours. Schedule: [time] [IANA time zone], Monday–Friday, until [end date]. Confirm the schedule. Output: 1. Today’s meetings, with preparation needed. 2. Deadlines in the next seven days, with owner and source link. 3. Unanswered questions that need my input. 4. My next three actions, ordered by impact and urgency. Keep the brief under 500 words. Deduplicate the same event across sources. Label missing dates as unknown. Put the finished brief in [destination]. If nothing material changed, say so in one sentence. Start by producing one brief now, then incorporate my feedback.Download Markdown ↓