A dynamic date variable is resolved when the snippet is inserted. Use {date} for today, {date:+7d} for seven calendar days ahead, and a natural-language expression such as {date:next Monday} when that rule is what you mean. Use a guided field such as {ask:Date} when the correct date depends on a person, policy, carrier, bank, or external event.
Key takeaways
- The token stays in the saved template; the resulting date is calculated at insertion time.
- Relative days are calendar days unless the product explicitly supports business-day rules.
- Natural-language dates are useful only when the phrase unambiguously matches the intended rule.
- Prompt for dates that represent a promise or external dependency.
The saved token and the inserted result are different
A dynamic snippet stores an instruction such as {date}, not a fixed date. When you insert the snippet, ExpandCaptain evaluates the instruction using the current date and places the result into the finished text. Tomorrow, the same snippet produces tomorrow's date.
This distinction prevents a common copy-paste error: an old template that still says last Tuesday. It also means a screenshot can show an example result without guaranteeing that exact date for every future insertion.
Four date patterns cover most workflows
Use the simplest rule that accurately represents the situation. Current date and direct relative math are predictable. Natural-language expressions are readable but should be tested around weekends, month boundaries, leap years, and locale settings. Guided fields are safest when the date is not algorithmic.
- {date}: the date at the moment of insertion.
- {date:+7d}: seven calendar days after the insertion date.
- {date:next Monday}: the next Monday according to the parser's rule.
- {ask:Date}: a field the user fills before insertion.
;meetingMeeting notes
Date: {date} at {time}
Attendees: {ask:Attendees}
Next step: {cursor}Calendar days are not business days
Adding seven days is not the same as adding five business days. Holidays, regional calendars, cutoff times, and company policy can all change a business deadline. Unless the product explicitly models those rules, do not describe simple date math as business-day calculation.
For shipping, refunds, legal notices, medical instructions, financial transfers, or regulated commitments, use the date supplied by the authoritative system or ask the user to enter it. The snippet can structure the sentence without inventing the promise.
Test the edge cases before trusting a date template
Create a small test sheet with end-of-month, end-of-year, leap-day, daylight-saving, and weekend scenarios. Check the product's locale and time-zone behavior. If the template is used by more than one person, document the intended rule in plain language beside the token.
A good template might say internally: ‘Use {date:+7d} only for a seven-calendar-day follow-up. Replace with {ask:Date} when the external system provides the deadline.’ That explanation prevents a compact token from hiding an important business assumption.
- 01
Write the intended rule in a sentence.
- 02
Choose the token that exactly matches that rule.
- 03
Test boundary dates and time zones.
- 04
Preview the result before using it in a commitment.
Useful and safe date-aware snippets
Meeting headers, daily logs, follow-up reminders, and internal review notes are strong candidates for dynamic dates. Customer promises and deadlines controlled by an outside service are stronger candidates for prompted fields.
The design rule is simple: calculate facts the computer truly knows; ask for facts that depend on the world.
Common questions
01What does {date:+7d} mean?+
It means seven calendar days after the date when the snippet is inserted. It should not be described as five business days or as a guaranteed external deadline.
02What happens to {date} tomorrow?+
The saved snippet still contains {date}. When inserted tomorrow, it resolves using tomorrow's date.
03When should I use {ask:Date}?+
Use a prompted date when the answer comes from a customer, calendar, policy, carrier, bank, provider, or another external source rather than a deterministic rule.
Sources
Product features and prices were checked on July 16, 2026. They can change. Comparisons describe published scope and are not claims of complete feature parity.
- ExpandCaptain product guide Current documented examples for {date}, {date:+7d}, {date:next Monday}, {ask:Date}, and insertion-time calculation.
- Raycast Dynamic Placeholders Official example of date and time placeholders in another current expansion system.
