Voice Calendar Commands for Recurring Family Schedules

Start with the smallest complete structure:

Add [activity] on [date] at [time] for [family member].

For example, a parent could fill the slots as “Add violin lesson on September 8 at 4 PM for Mia.” The wording is a template. Check the resulting title, date, time, and assignment rather than assuming the sentence always produces the same output.

A strong request answers these questions:

1. What is happening?
2. On which date?
3. At what start time?
4. Does it repeat?
5. Who is involved?
6. Is a reminder or related to-do needed?

Do not add every field merely to make the sentence longer. Location, duration, privacy, and an end date are useful when they matter. A short complete request is easier to review than a dense paragraph containing several unrelated plans.

Use one-time commands for an appointment, school meeting, pickup, performance, or other commitment that does not follow a stable pattern.

Prefer an explicit date when “Friday” could be ambiguous. Prefer “4 PM” to “later.” Names and places are common transcription errors, so inspect them closely.

If a plan affects the household but belongs in an external work, school, Google, Apple, or Outlook calendar, remember that KIN does not currently import or sync those sources. Decide whether to copy the family-relevant commitment into KIN manually or keep it only in the outside system.

Recurring events are useful for a stable weekly pattern. Start with a simple rule:

Add [activity] every [weekday] at [time] for [family member].

Current test: “Add soccer practice every Tuesday at 4 PM.” created a recurring series in the isolated August 26 test family. The database contained successive series events, the visible card read “Soccer practice at 4 pm,” and KIN showed “Recurring event added.” Treat that as evidence for this simple request, not a guarantee for every phrase or exception rule.

Templates for common family schedules:

• “Add [sports practice] every Tuesday at 4 PM for [child].”
• “Add [school pickup] every weekday at 3:15 PM for [parent and child].”
• “Add [music lesson] every other Saturday at 10 AM for [child].”
• “Add [family review] every Sunday at 6 PM for [family members].”

KIN's published proof and the August 26 rerun include soccer practice at 4 PM on successive Tuesdays. That supports the simple weekly workflow; it does not guarantee that arbitrary exceptions such as “except school holidays” or a rotating custody pattern will be interpreted correctly in one sentence.

After creating a series:

• inspect at least three occurrences;
• confirm the weekday and time;
• confirm the first date;
• check the end date if one was intended;
• verify the assigned members; and
• add real exceptions when the schedule changes.

A recurring event is a rule, not a promise that the real world will keep repeating. School terms end, sports practices move, and pickup responsibilities change.

The family scheduling routines guide explains how to review those exceptions weekly.

An event says when something happens. A reminder prompts someone at a useful moment. A to-do represents work that must be completed.

Use a reminder template when timing is the main need:

Remind [family member] to [action] at [time].

Use a to-do template when responsibility and a deadline matter:

Add a to-do for [family member] to [action] by [date or time].

Examples might include packing sports equipment, signing a school form, calling a clinic, or bringing an item to an event. KIN supports reminders and to-dos, and its published proof includes a “Pack soccer bag” item assigned to John for 3 PM. Because the full spoken transcript was not retained publicly, treat the sentence structures above as reusable templates, not exact tested commands.

Review whether the result became the object you intended. “Remind Sam to bring cleats” should not silently become a timed calendar event if what you needed was a reminder or task.

When one field is wrong, name the existing event and the desired change:

Move [existing event] from [old time] to [new time].

Current test: “I have a dentist on December 18th at 3 PM” created a visible 3 PM event. “Move the dentist to 5 PM” updated the same event ID and changed the visible card to 5 PM. “Cancel the dentist” then removed that same event from the database and timeline. This simple sequence passed on August 26; similar names or ambiguous dates may still require more context.

Other correction templates include:

• “Change [event] on [date] to [new date and time].”
• “Assign [existing event] to [correct members].”
• “Change [series name] to every [new weekday] at [new time].”
• “Cancel [existing event] on [date].”

KIN's published verification moved the same violin event from 3 PM to 5 PM while preserving its event ID. That demonstrates a correction workflow, not perfect matching for every similarly named event.

If two plans have the same name, include the date, current time, or family member to disambiguate. After a series change, confirm whether the app changed one occurrence or the repeating rule you intended.

Voice input has two interpretation stages: speech must become text, and the calendar system must map that text into fields and actions. Either stage can fail.

Use this recovery loop:

1. Read the transcript and the interpreted result.
2. Identify the smallest wrong or missing field.
3. Restate that field explicitly with enough event context.
4. Review the result again.
5. Switch to typed input if speech remains unreliable.

For example, if a request produces the right event on the wrong day, restate the event name and full calendar date. If it creates the right date but the wrong person, name the event and correct member. Avoid repeating the same ambiguous wording louder.

KIN does not guarantee perfect interpretation. A quiet room, clear names, and explicit dates can help, but every important family plan still needs review.

Do not rely on one dense utterance to handle a long sequence of unrelated events. Split the work when a request contains:

• several different activities;
• a complicated recurrence with many exceptions;
• similar event names on nearby dates;
• sensitive details that should not be spoken aloud;
• unclear phrases such as “later” or “usual time”; or
• a change where one occurrence and the full series could both be reasonable.

For a complex school term, create the stable weekly rule first, inspect it, and then handle exceptions. For several siblings, create or verify one schedule at a time when the assignments differ.

KIN's privacy policy says voice audio and relevant family-schedule details may be sent—with in-app permission—to named service providers for speech recognition and AI interpretation. Voice processing should not be described as on-device-only or end-to-end encrypted. Use typed input when a detail is sensitive or speaking would expose it to people nearby.

Do not operate the app while driving. NHTSA identifies distracted driving as any activity that diverts attention from driving. Wait until safely parked or ask a passenger to capture the plan. A user-initiated hold-to-talk control is not a reason to divide attention on the road.

Before closing the result, check:

• event, reminder, or to-do type;
• title and names;
• calendar date and time zone;
• start and end time;
• repeat rule and several occurrences;
• assigned family members;
• reminder timing;
• privacy audience; and
• whether a change affected one event or the series.

The shared family calendar setup guide adds ownership, privacy, and maintenance rules around the capture step.

The best voice calendar command is a clear template followed by a deliberate review. Name what, when, recurrence, and who. Correct one field at a time. Use typed input when the environment or the detail makes speech a poor choice.

KIN has published current iPhone evidence for one-time creation, simple weekly recurrence, an assigned reminder, and a time correction. Those workflows make useful starting points, but they do not guarantee every sentence, name, or complex schedule will parse perfectly.

See the complete KIN voice calendar for families to review the tested screenshots, product limits, and current mobile workflow.