“Put the library visit on the calendar” sounds complete until someone asks which library, which day, or when you expect to leave. Often, the next useful step is finding one missing detail before sending the request.
Nestie is Nestify’s assistant; our introduction to Nestie explains the names and where to start. This guide helps you prepare one calendar request, with a worksheet you can also use for a paper diary or a message to another adult.
Choose one action and collect the missing facts
Start with the change you actually want: add a new event or change an existing event. Those are different instructions. If the library visit is already on the calendar, adding it again is different from moving its start time.
Nestify’s App Store listing describes speaking to Nestie to add or edit calendar events. On the phone, open Nestie and type your request or use its microphone. The greeting in this article’s title does not activate the phone in the background.
Before sending anything, gather the details from the organizer’s message, booking confirmation, or person making the plan. Keep unresolved questions in a separate note. A calendar request can save a change, so an unfinished worksheet belongs outside the conversation until you know what you want to submit.
For a new event, ask yourself:
- What should this event be called?
- What is the exact date?
- When does it start, and when does it end?
- Where does it happen?
- Is it happening once, or does it repeat?
For an edit, also identify the existing event by its title and current date or time. State the particular detail that should change. “Move the library visit” leaves more open than “Change the start time of the October 3 library visit.”
You do not need to fill every possible field. A home reading hour may need no location beyond its title. An outing to a different branch does. Include the information your family needs to distinguish this plan from another one, without adding private details that serve no purpose.
If the organizer has not announced an end time, ask about it. If your family is still choosing a day, keep the choice in your planning note. A calendar entry should reflect the decision you are ready to make.
Make the date, time and scope explicit
Consider this fictional example. A family has agreed to visit the library on October 3, 2026, from 10:00 to 11:00 a.m. The visit will happen once, at their usual branch.
An initial note might say:
Add the library thing next Saturday at ten.
The family can turn that into:
Add “Family library visit” on October 3, 2026, from 10:00 to 11:00 a.m., at our usual library branch. Make it a one-time event.
This is an example of wording, not a special command format. The second version records the family’s chosen date, duration and repetition. It also avoids relying on what “next Saturday” will mean when someone reads the message later.
Use a real branch name in your own request if “our usual branch” could mean more than one place. For an unfamiliar venue, check the organizer’s location before adding it. A recognizable event title is usually more useful than including a child’s full name or other identifying information.
When travel or a remote event introduces different time zones, name the intended zone alongside the time. For example, a planning note could say “10:00 a.m. in Los Angeles” rather than just “10.” Google Calendar’s time-zone guidance explains that events display in each viewer’s local zone. That is a Google-specific behavior; identify the intended zone when preparing your Nestie request.
Repetition deserves its own sentence. Adding one visit is different from scheduling a visit every Saturday. Changing one date in an existing series is different from moving the whole series. Google documents separate scopes for recurring-event edits; that does not establish which edits another app supports.
If you need to change just one occurrence, identify its exact date and say that only that occurrence should change. Use that scope where the app supports it. If you cannot tell whether the available action matches your intention, leave the request unsent and use the relevant calendar’s supported editing controls.
Use a small request template, then send only what you mean
Copy this worksheet into a private note. You can leave gaps while gathering information; send a completed request separately once the decision is clear.
- Action: Add an event, or change an existing event.
- Event: Title; current date and time if changing it.
- New date: Month, day and year.
- Time: Start and end, with a.m. or p.m.
- Time zone: Include when it matters to the plan.
- Place: Enough detail to identify the intended venue.
- Scope: One-time event, or the intended repetition or occurrence where supported.
- Keep unchanged: Any existing details that should stay as they are.
For the fictional library visit, the completed request above contains everything the family has decided to add. There is no need to paste the field labels or explain how the decision was made. Keep your working notes for yourself.
Read your final wording once before sending. Does the action match your intention? Did an old date survive from an earlier plan? Does a sentence accidentally ask for a second change? Resolve those differences in the wording first.
If another adult maintains your family calendar, the same note can become a message to them. If you use paper, write the agreed details in the diary. Choosing a person to enter the event still leaves attending, transporting or supervising to be agreed separately with the people involved.
Once you have sent a request, follow our guide to checking a calendar change before your family relies on it.