# Turn Invites Into a Checked Date Table

> A read-only prompt that turns pasted invite text into a flagged Markdown table of dates, times and places to check by hand.

## Install

Copy the content below into your project:

# Turn Invites Into a Checked Date Table

A read-only prompt that turns pasted invite text into a flagged Markdown table of dates, times and places to check by hand.

## Start here

This is a reusable prompt for an ordinary AI chat that accepts text. It turns pasted event invite text into one Markdown table plus a short notes section, flagging every uncertain detail instead of guessing. It only reads what you paste; it does not open mail, connect to a calendar, or create anything.

**What to paste:** copy the prompt below, then fill its INPUT part. Paste the whole thing (brief plus your input) into the chat. You can reach the prompt text from the reference notes linked below.

**What to fill in:**

| Field | What goes there |
| --- | --- |
| SOURCE_ID | a short label you make up, e.g. `invite-2026-04-a` |
| TIME ZONE CONTEXT | the zone you believe the invite uses, or `unknown` |
| EVENT TEXT | the raw invite text; separate multiple events with a blank line or `---` |

**How to check the output:**

- Every original date, time and place string should appear exactly as written, with any normalized `YYYY-MM-DD` only in parentheses.
- No row may have an empty Flags cell.
- Any row flagged `CONFLICTING_DETAIL` must show both competing values.
- No predicted date for `TBD` or tentative wording, and no time zone the paste never states.
- The reply must not claim it read an inbox, checked a calendar, or scheduled anything.

### Introduction

The prompt defines a careful extractor, not a scheduling planner. It transcribes what the text says and flags ambiguity across these columns: Event, Date, Time, Location, Source snippet, Flags and Confidence. Flags include MISSING_DATE, MISSING_LOCATION, AMBIGUOUS_DATE, AMBIGUOUS_LOCATION, CONFLICTING_DETAIL, TENTATIVE_LANGUAGE and NONE. Output has four sections: the table, "Needs human check", "Ready to add", and "Boundaries observed".

### Prerequisites, permissions and limits

- An ordinary AI chat that accepts pasted text. No terminal, account or API setup is needed.
- The job is read-only: it must not request account access, browse, send messages or create calendar entries.
- You, a human, approve, correct or skip each row and add entries by hand.
- Treat the output as preparation, not booking. If a date or location is missing, it stays flagged rather than filled in.
- Avoid pasting private invite details you would not share with your chat provider.

Source reviewed; runtime not tested.

### FAQ

**What if an invite is missing a date or place?**
The row is still produced, with the field left as written and a MISSING_DATE or MISSING_LOCATION flag. Nothing is invented for you.

**Is the worked example a real result?**
No. It is fictional and shown only to illustrate the table shape.

### Attribution

Original TokRepo prompt, licensed CC BY 4.0. External reference material retains its own rights. Reference: [ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>).

## Complete reusable prompt

You are helping me prepare a verification brief for an assistant that reviews pasted event invite text and returns a calendar-ready extraction sheet. This brief is for a human-audited, read-only job: the assistant only reads text I paste, never opens my mail, never connects to a calendar, and never creates, moves, or sends anything. I will use this brief myself to instruct an assistant, then a human approves each row before any calendar entry is made by hand.

How to use this brief
1. Fill in the INPUT section with the raw invite text (institutions, personal messages, or forwarded notes are all fine).
2. Paste this whole brief plus your filled INPUT into the assistant.
3. The assistant returns a single Markdown table plus a short notes section.
4. A human reads the flags and either approves, corrects, or skips each row before adding it to a calendar.

ROLE
The assistant is a careful extractor, not a scheduling planner. It transcribes what the text says and flags what is ambiguous. It does not infer missing dates, does not guess time zones, and does not invent locations.

INPUT (fill this in)
SOURCE_ID: <short label you create, e.g. invite-2026-04-a>
TIME ZONE CONTEXT: <the time zone you believe the invite uses, or 'unknown'>
EVENT TEXT:
<<<
<paste each invite or note here; separate multiple events with a blank line or '---'>
>>>

TASK
For every event in EVENT TEXT, produce one row with these columns:
- Event: short title from the text (or 'No title given')
- Date: calendar date as written, then a normalized YYYY-MM-DD in parentheses if unambiguous
- Time: as written, with any stated time zone
- Location: venue or address exactly as written
- Source snippet: the shortest phrase from the paste that supports the date and location
- Flags: one or more of MISSING_DATE, MISSING_LOCATION, AMBIGUOUS_DATE, AMBIGUOUS_LOCATION, CONFLICTING_DETAIL, TENTATIVE_LANGUAGE, or NONE
- Confidence: HIGH, MEDIUM, or LOW with a one-line reason

RULES
- Copy dates, times, and place names exactly as written first; your normalization goes in parentheses and never replaces the original text.
- If two different dates or places appear for what looks like the same event, do not choose. Emit both and flag CONFLICTING_DETAIL.
- If wording like 'sometime next week', 'TBD', or 'tentatively' appears, flag TENTATIVE_LANGUAGE and keep the wording rather than converting it to a date.
- If a time zone is not stated and TIME ZONE CONTEXT is 'unknown', do not attach a zone; flag AMBIGUOUS_DATE.
- Never merge two separate events into one row, and never split one event into two rows unless the text clearly describes two.

OUTPUT FORMAT
Section 1: the Markdown table described above.
Section 2: 'Needs human check' - a bullet list of every flagged row with the exact question a human should answer (for example, 'Is 3 PM the local venue time or my home time zone?').
Section 3: 'Ready to add' - only rows flagged NONE with HIGH confidence, listed as bare date, time, title, location lines.
Section 4: 'Boundaries observed' - one sentence confirming no external calendar access or actions were taken.

WORKED EXAMPLE (fictional, for shape only)
Input: 'Team offsite, Thu 14 May, 10:00, Room 4B, Riverside Annex. Dinner somewhere nearby - TBD.'
Output row: Event: Team offsite | Date: Thu 14 May (2026-05-14) | Time: 10:00, zone unstated | Location: Room 4B, Riverside Annex | Source snippet: 'Thu 14 May, 10:00, Room 4B, Riverside Annex' | Flags: AMBIGUOUS_DATE, TENTATIVE_LANGUAGE | Confidence: MEDIUM - date is clear but time zone is unstated and the dinner has no set place or time. Needs human check: 'Which time zone is 10:00 in, and is the dinner a separate row?'

CHECKS THE USER SHOULD RUN
- Pass: every original date, time, and place string appears verbatim somewhere in the table, not only as a normalized value.
- Pass: no row has a blank Flag cell. Fail: any row lacking a flag.
- Pass: every CONFLICTING_DETAIL row lists both competing values. Fail: a single chosen value with no alternative shown.
- Fail: a predicted date for TBD or tentative wording, or a time zone the paste never states.
- Fail: the assistant claims it read an inbox, checked a calendar, or scheduled anything.

BOUNDARIES
Only process the pasted text. Do not request account access, do not browse, do not send messages, and do not create calendar events. Producing this sheet is preparation, not booking. If an invite is missing a date or location, leave it flagged rather than filling the gap yourself.

## References and reuse

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes)

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 把邀请整理成可人工核对的日期表

一条只读提示词，把粘贴的邀请文本整理成带标记的 Markdown 表格，列出日期、时间、地点与存疑处，供你人工核对。

## 开始使用

这是一条可复用的提示词，适用于任何接受文本的普通 AI 对话。它把粘贴的活动邀请文本整理成一张 Markdown 表格和一小段说明，把所有不确定的细节标出来而不是替你猜。它只读取你粘贴的内容，不会打开邮件、不会连接日历，也不会创建任何东西。

**粘贴什么：**复制下方提示词，填写其中的 INPUT 部分，然后把整段（提示词加你的输入）粘贴进对话。提示词原文见下方参考链接。

**要填写的内容：**

| 字段 | 填什么 |
| --- | --- |
| SOURCE_ID | 你自己起的短标签，例如 `invite-2026-04-a` |
| TIME ZONE CONTEXT | 你认为邀请使用的时区，或填 `unknown` |
| EVENT TEXT | 原始邀请文本；多个活动之间用空行或 `---` 分隔 |

**如何检查输出：**

- 每一个原始日期、时间和地点字符串都应原样出现，规范化的 `YYYY-MM-DD` 只能放在括号里。
- 任何一行的 Flags 单元格都不能为空。
- 被标为 `CONFLICTING_DETAIL` 的行必须同时列出两个相互冲突的取值。
- 对 `TBD` 或含糊措辞不得给出推测日期，也不得添加原文未声明的时区。
- 回答不得声称自己读过收件箱、查看过日历或安排过任何事情。

### 简介

这条提示词把助手定义为谨慎的提取员，而不是排期规划者。它只转录文本内容并标出歧义，列包括：Event、Date、Time、Location、Source snippet、Flags 和 Confidence。标记包括 MISSING_DATE、MISSING_LOCATION、AMBIGUOUS_DATE、AMBIGUOUS_LOCATION、CONFLICTING_DETAIL、TENTATIVE_LANGUAGE 和 NONE。输出分四部分：表格、“Needs human check”、“Ready to add”、“Boundaries observed”。

### 前提、权限与限制

- 一个能接受粘贴文本的普通 AI 对话即可，无需终端、账号或 API 配置。
- 任务是只读的：不得索取账号权限、不得联网浏览、不得发送消息、不得创建日历事件。
- 由你本人逐行确认、修改或跳过，再手动录入日历。
- 输出只是准备工作，不是预订。缺少日期或地点时保持标记，不会被自动补齐。
- 不要把不愿提供给所用 AI 服务的私密邀请信息粘贴进去。

来源已审阅；未做运行测试。

### 常见问题

**邀请缺少日期或地点怎么办？**
该行仍会生成，字段按原文保留，并带 MISSING_DATE 或 MISSING_LOCATION 标记，不会替你想出一个值。

**文中的示例是真实结果吗？**
不是。它是虚构示例，仅用于说明表格的结构。

### 来源致谢

原创 TokRepo 提示词，采用 CC BY 4.0 许可。外部参考材料保留其自身权利。参考：[ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>)。

## 完整可复制提示词

你正在帮我为一位助手准备一份验证简报，该助手会审阅粘贴的活动邀请文本，并返回一份可用于日历的提取表。这份简报用于一项人工审核的只读任务：助手只读取我粘贴的文本，绝不打开我的邮件，绝不连接日历，也绝不创建、移动或发送任何东西。我会自己用这份简报来指导助手，随后由人工在手动录入任何日历之前逐行批准。

如何使用这份简报
1. 在 INPUT 部分填入原始邀请文本（机构通知、个人消息或转发备注都可以）。
2. 把这份完整简报连同填好的 INPUT 一起粘贴给助手。
3. 助手返回一张 Markdown 表格和一小段说明。
4. 人工阅读标记，并在把每一行加入日历之前批准、修正或跳过该行。

角色
助手是谨慎的提取员，而不是排期规划者。它转录文本内容并标出歧义，不推断缺失的日期，不猜测时区，也不编造地点。

INPUT（填写此项）
SOURCE_ID: <你自己起的短标签，例如 invite-2026-04-a>
TIME ZONE CONTEXT: <你认为邀请使用的时区，或 'unknown'>
EVENT TEXT:
<<<
<在此粘贴每份邀请或备注；多个活动之间用空行或 '---' 分隔>
>>>

任务
对 EVENT TEXT 中的每一个活动，生成一行，包含以下列：
- Event：文本中的简短标题（或 'No title given'）
- Date：按原文写出的日历日期，若明确无歧义，则在括号中附上规范化的 YYYY-MM-DD
- Time：按原文写出，并带上任何已声明的时区
- Location：按原文写出的场地或地址
- Source snippet：粘贴文本中支持该日期和地点的最短短语
- Flags：MISSING_DATE、MISSING_LOCATION、AMBIGUOUS_DATE、AMBIGUOUS_LOCATION、CONFLICTING_DETAIL、TENTATIVE_LANGUAGE 或 NONE 中的一项或多项
- Confidence：HIGH、MEDIUM 或 LOW，并附一行理由

规则
- 先按原文逐字复制日期、时间和地点名称；你的规范化放在括号里，绝不替换原始文本。
- 如果同一个活动看起来出现了两个不同的日期或地点，不要做选择。两者都列出，并标记 CONFLICTING_DETAIL。
- 如果出现 'sometime next week'、'TBD' 或 'tentatively' 之类的措辞，标记 TENTATIVE_LANGUAGE 并保留该措辞，而不是把它转换成日期。
- 如果未声明时区且 TIME ZONE CONTEXT 为 'unknown'，不要附加时区；标记 AMBIGUOUS_DATE。
- 绝不把两个独立活动合并为一行，也绝不把一个活动拆成两行，除非文本明确描述了两个活动。

输出格式
第 1 部分：上述 Markdown 表格。
第 2 部分：'Needs human check'——一个项目符号列表，列出每一个被标记的行，并写明人工应回答的确切问题（例如，'Is 3 PM the local venue time or my home time zone?'）。
第 3 部分：'Ready to add'——只列出标记为 NONE 且置信度为 HIGH 的行，以简洁的日期、时间、标题、地点行的形式呈现。
第 4 部分：'Boundaries observed'——用一句话确认未进行任何外部日历访问或操作。

示例（虚构，仅示意结构）
输入：'Team offsite, Thu 14 May, 10:00, Room 4B, Riverside Annex. Dinner somewhere nearby - TBD.'
输出行：Event: Team offsite | Date: Thu 14 May (2026-05-14) | Time: 10:00, zone unstated | Location: Room 4B, Riverside Annex | Source snippet: 'Thu 14 May, 10:00, Room 4B, Riverside Annex' | Flags: AMBIGUOUS_DATE, TENTATIVE_LANGUAGE | Confidence: MEDIUM - date is clear but time zone is unstated and the dinner has no set place or time. Needs human check: 'Which time zone is 10:00 in, and is the dinner a separate row?'

用户应当执行的检查
- 通过：每一个原始日期、时间和地点字符串都应原样出现在表格中的某处，而不仅以规范化值的形式出现。
- 通过：任何一行的 Flag 单元格都不能为空。失败：任何一行缺少标记。
- 通过：每一行 CONFLICTING_DETAIL 都必须列出两个相互冲突的取值。失败：只给出一个选定的值而不展示另一选项。
- 失败：对 TBD 或含糊措辞给出推测日期，或添加原文未声明的时区。
- 失败：助手声称它读过收件箱、查看过日历或安排过任何事情。

边界
只处理粘贴的文本。不要索取账号权限，不要联网浏览，不要发送消息，不要创建日历事件。生成这张表格是准备工作，不是预订。如果邀请缺少日期或地点，保持标记，而不是自己填补空缺。

## 参考资料与复用

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes)

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/turn-invites-into-checked-date-table-2dd99d9d
Author: Prompt Lab