Team Calendar

Team Calendar defines a unified event index rather than a second scheduling system. Keep the shared calendar in the tool the team already uses and retain key event references in a thin database. The business workflow creates an event, adds its calendar entry, records attendance or RSVP and supplies reminders through the relevant integration. The field model supports event type, date, start and end times, time zone, department, attendees, organizer, source module and location or link. Its purpose is a consistent record that complements the active calendar.

The default deliverable is a short recommendation. An explicit setup, build or conversion request produces artifacts after essential missing facts are resolved. Advice receives a direct answer, while a review works from the material provided. This keeps the size of the proposed setup tied to the requested outcome.

Use it for shared-event registers and team availability references alongside an existing calendar. It does not create Google calendar events, resolve scheduling conflicts, synchronize calendars or send reminders. The proposed RSVP and reminder steps require a separate implementation.

This is an empty-template workflow, not processing of real employee or customer records. Automation, reminders and synchronization require the separate integration layer. Sensitive decisions and adjustments require qualified human review before anything is acted on.

Establish included events, holidays and exclusion of personal events; audiences, department views and private items; existing Google synchronization, two-way requirements and ownership; the current calendar and gaps; and whether an index, feed design or conflict rules are requested. Questions are asked one at a time, excluding anything already answered in earlier messages. Unknown facts stay unknown. Intent, confirmed facts, open questions and requested formats remain internal unless the user asks to inspect them; no missing answer is invented.

The field model includes Event (text); Event Type (select); Date (date); Start Time (text); End Time (text); Time Zone (text); Department (text); Attendees (text); Organizer (text); Source Module (text); Location or Link (url); Notes (long_text); Event ID (id).

Event Type starts with Meeting, Deadline, Leave, Training, Travel, Review.

Start Time and End Time remain text fields in the supplied model; Date is a date and Location or Link maps to a URL property.

Requested CSV, SQL DDL, JSON Schema and Notion mappings derive from one field list. Display names remain identical across CSV and JSON, and normalized SQL identifiers are documented. Relation fields keep their relational meaning, dates remain dates and money remains currency. Machine-readable data is separated from explanation, with validation failures and limitations reported separately.

One supplied SQL example is:

CREATE TABLE team_calendar (
  event VARCHAR(255),
  event_type VARCHAR(100) NOT NULL,
  date DATE NOT NULL,
  start_time VARCHAR(255),
  end_time VARCHAR(255),
  time_zone VARCHAR(255),
  department VARCHAR(255),
  attendees VARCHAR(255),
  organizer VARCHAR(255),
  source_module VARCHAR(255),
  location_or_link TEXT,
  notes TEXT,
  event_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

Excel-compatible CSV uses UTF-8 with a byte order mark. Because CSV has no column types, numeric, date and currency formatting is identified after the data. A CSV is not an .xlsx workbook; the latter is generated only when requested. Example rows require an explicit request and must be clearly synthetic. Sensitive identifiers are not unnecessarily repeated in a review, and generated templates remain empty.

Notion output goes to notion-manual-import for the CSV, property mapping, import steps and verification checklist. Manual mappings require no connection. Requested workspace changes require verified tool access, the actual target and authorization; a claimed connection is insufficient evidence. Notion relation columns resolve only after both databases have been imported. Select options are an initial vocabulary that can be renamed to match the business. people-directory supplies the related employee master record; notification-reminder-hub is the separate due-date reminder module. Personal identifiers and sensitive financial details stay out of generated templates.