Calendar Time Is Not Work Time

A calendar tells you what was planned. A work record should say what happened, who did it, and how long the work actually took. Those are related facts, but they are not interchangeable.

Treating an event as a clue preserves that distinction. The event can bring a forgotten task back into view. The owner still decides whether any work occurred and what belongs in the final record.

Scheduled length can be misleading

Suppose a calendar contains this block:

HVAC service window, 10:00 a.m. to noon

The two-hour block might represent the vendor’s arrival window. The owner may have spent twelve minutes opening the unit and discussing the repair. The vendor may have worked for seventy minutes. Or the appointment may have been canceled.

Saving two hours for the owner would confuse the schedule with the activity. A useful review should ask for the actual duration and the person who performed the work.

All-day events need even more restraint. “Turnover” or “Property visit” may help the owner remember a task, but an all-day flag says nothing about elapsed work time. When travel is involved, keeping separate rental property travel records ensures that transit time, business tasks, and personal stops are not lumped into an artificial work block. It should arrive without a duration rather than receiving an arbitrary default.

What a calendar clue can contribute

A selected event may offer a starting date, a title, calendar context, and an editable time suggestion when the event is timed. Those values can make review faster. They should remain suggestions until confirmed.

The HostHours review form asks for:

• the property;
• the activity date;
• actual time spent;
• category;
• person;
• factual details.

Each event requires its own confirmation. Selecting several clues can prepare a review queue, but it does not turn the queue into saved activities.

This matters when one event contains several people. A cleaner’s scheduled turnover is not automatically the owner’s work. A meeting with a contractor may produce a record for the owner’s coordination time, while the contractor’s work is recorded under that person only when the owner has reliable facts to preserve.

Use read-only sources deliberately

Calendar Recall reads calendars available through the device’s system store. That can include calendars synchronized from Google and subscribed calendars that the device can see. The user selects the exact sources. Birthday calendars are filtered out.

Source selection deserves the same care as entry review. A personal calendar may mix rental appointments with family plans, while a subscribed booking calendar may show guest stays rather than the owner’s work. Select only a source that is likely to provide useful reminders.

HostHours does not need to edit an event, create a new appointment, or request direct Google Calendar authorization for this job. Read-only access is enough to surface a possible clue.

The Home calendar is also bounded. It reads selected sources for the visible month, within the current property’s tax year, and no later than today. It is not meant to scan an unlimited history in the background.

Previously confirmed calendar records are filtered from the clue list. That reduces repeat prompts, but the user should still watch for two events that describe the same task, such as a personal reminder and a vendor invitation.

A practical review test

Before confirming a clue, ask four questions:

1. Did the activity occur?
2. Who performed the work being recorded?
3. How much actual time did that person spend?
4. Does the note describe the completed activity rather than the appointment title?

If any answer is unknown, leave the field unresolved or skip the clue until better information is available. A message thread, receipt, vendor invoice, or photo may refresh context. None of those sources should be used to manufacture a duration they do not contain.

A good final note often differs from the calendar title. “Plumber” is a weak record. “Met plumber at Pine Avenue unit, reviewed leak under kitchen sink, approved replacement valve, and confirmed follow-up for Friday” preserves what the owner actually did. The duration still needs to come from the owner’s recollection or another reasonable basis, not the service window.

Calendar and activity timelines serve different purposes

HostHours has two calendar-like views. Calendar clues show possible work found in selected sources. The activity tracker in Records → Evidence shows days with saved records. Mixing those views would make planned events look confirmed.

The separation is intentional. Clues belong before review. Saved activities belong after confirmation.

Start with one narrow source rather than every calendar on the device. Review a single week, reject events that did not become work, and correct every suggested duration. The result should be a factual activity history, not a copy of your schedule.

HostHours organizes factual records. It does not decide whether an activity qualifies for a particular tax, accounting, or legal treatment.