Natural-language dates let you add timing to a task using the words you would say to another person: “call the vet tomorrow at eleven” rather than choosing a day and time from a picker. The useful part is capturing the action and its timing together, then checking the interpreted date.
mmbl recognises dates in task capture. Its capture screen highlights a recognised phrase and shows a date chip, giving you a chance to verify what will be saved before you move on.
Put the action and the date in the same thought
“Tomorrow at four” is timing without a task. “Pick the cat up from the vet tomorrow at four” gives the app both pieces.
Useful wording looks like this:
- “Call the vet tomorrow at 11 am.”
- “Send the proposal on Friday at 10 am.”
- “Pick up the cat tomorrow at 4 pm.”
These are examples of the kind of clear phrasing to aim for. Always check the displayed date rather than assuming every phrase or variation will be interpreted exactly as you intended.
When speaking several tasks together, keep each date close to the action it belongs to. “Call the vet tomorrow at eleven, and buy cat food” is easier to review than a long list followed by several disconnected dates.
Check what relative words resolve to
“Tomorrow” depends on when you capture the task. “Next Friday” can mean different things to different people. Even a simple time such as “at seven” leaves morning or evening unstated.
For something important, be more explicit. Say the date and include am or pm, then inspect the result. If the task matters across time zones, verify the time in the app in the context you will actually use it. Do not rely on an unstated timezone assumption.
A quick review has three parts:
- Is the day correct?
- Is the time correct, including morning or evening?
- Is that date attached to the right action?
The review is especially worthwhile after correcting yourself aloud. “Thursday, sorry, Friday” is natural speech, but your intention is only confirmed when the saved result matches Friday.
Separate a real deadline from a hopeful plan
A deadline means something happens if you miss it: an appointment, a submission cutoff, or an agreed delivery. A hopeful plan is when you would like to do the work. Both can be useful, but treating every hope as a deadline makes the list noisy.
Before adding a date, ask why the task needs that date. Buying cat food before you run out has a practical time constraint. Researching an optional future purchase may be fine without one.
This also prevents an all-too-easy habit: saying “tomorrow” for everything you don’t want to decide about today. A dated backlog still needs a decision; it just returns to you tomorrow.
Keep the task concrete enough to start
A date does not fix vague wording. “Japan on Friday” might refer to booking a hotel, buying currency, or checking a flight. “Book the hotel for Japan on Friday morning” identifies an action.
If the work is bigger than one action, split it. “Prepare the proposal” might require gathering figures, drafting, reviewing, and sending. Capture whichever step you need to do next, and use the real deadline to plan backwards if necessary.
Projects are a separate concern. mmbl can sort captured tasks into predefined projects, so adding a date need not involve choosing a destination every time.
Review upcoming work before the day begins
Natural-language capture saves effort at the moment a thought arrives. A short look at Upcoming helps you notice what needs preparation before its date becomes today.
During a weekly review, check that each date still represents an actual intention. Move a date when plans change, remove one when it was arbitrary, and keep the action itself clear. A task date is most useful when you can trust what it means.
Try saying it with mmbl.
Capture tasks by voice and let mmbl sort them into the projects you’ve already created.
Get mmbl for iPhone