Compare document versions with AI: deleted text is not a canceled policy
ChatGPT, Gemini and Claude all found the removed loaner-laptop sentence in our workshop announcement. None assumed the loaner service had ended. The useful difference was what they told us to check next—and whether the result was ready for an English-speaking team.
Our pick: ChatGPT for the pre-send handoff
WekeyLab AI would use ChatGPT’s change table for this announcement. It paired the old wording, new wording and next action, retained the unchanged dietary-request deadline and reminded us to update calendar invitations and the room reservation. Those reminders connect a document edit to the places colleagues actually rely on.
This was not a case where one service found the changes and the others failed. Gemini identified the same changed topics in a compact list and added a useful recording-permission check. Claude also found the changes and emphasized confirming the room booking, but returned its answer in Korean despite the English input. For an English-speaking recipient, that response would need translation before handoff.
What we changed before asking the AIs
We wrote two short versions of a fictional internal workshop announcement. The event stayed on October 16, 2026, with a9 a.m. start,8:30 a.m. check-in,40-person capacity and a bring-your-laptop instruction. The registration and schedule paragraphs switched order. That movement alone did not change the capacity.
The new version moved registration from October9 at5 p.m. to October8 at noon, extended the end time from noon to12:30 p.m., and changed Room204 to402. Dietary requests moved from email to the intranet form while the October12 deadline stayed. Waitlisting changed from automatic enrollment to selecting “Join waitlist.” Recording access changed from all employees for30 days to registered attendees for14 days. Slides for all employees were added. The loaner-laptop sentence simply disappeared.
We fixed ten checks before sending the same English question to three new chats. There was no imposed response length or format. The full input and actual responses are preserved below; this was a text comparison, not an upload or scanned-PDF test.
The removed laptop sentence: all three handled the distinction
The old version promised loaners if requested during registration. The new version only said to bring a laptop. A document comparison can establish that a sentence is missing; it cannot establish whether the organizer canceled the service or accidentally deleted the sentence. All three answers respected that boundary.
ChatGPT asked us to confirm whether loaners were unavailable or accidentally omitted. Gemini asked whether the policy still existed and should be restored. Claude likewise asked whether the removal was intentional. There is no basis here for declaring one service uniquely careful. The shared result is useful: this is the question to resolve before sending, not a reason to invent a new rule.
Loaner laptops: This is the only old detail that disappears without an explicit replacement. Confirm whether loaners are still available.
ChatGPT supplied the most convenient working table
Its four columns made the earlier deadline, later finish and new room easy to compare with the original. It also kept October12 beside both dietary-request channels, so the reader could see that only the submission method changed. Its extra calculation—one day and five hours earlier for registration—matches our independent29-hour check.
The best follow-up was outside the announcement itself: update the calendar invitation, room reservation, registration page and attached schedule. A correct email still leaves confusion if the calendar points to Room204. These were recommendations, not claims that any system had already been updated.
Gemini was concise; Claude was useful in a different language
Gemini’s checklist focused on the intranet form and recording portal. It recommended verifying that access could be limited to registered attendees for14 days. That is a useful operational question because changing a sentence does not configure permissions.
It called “Join waitlist” a checkbox, although the supplied text did not specify a control type. We would keep the neutral verb “select” until inspecting the real form. Gemini and Claude did not restate the unchanged October12 dietary deadline. This was omitted context, not a wrongly reported change.
Claude’s Korean table highlighted the recording restriction and recommended checking the actual room reservation. The English prompt did not explicitly demand an English answer, so we did not count language as a factual error. We preserved it as observed and did not rerun it to improve the comparison. For routine reuse, specify the desired output language.
WekeyLab AI’s corrected announcement
The text below follows the supplied new version. It is a working draft until the organizer resolves the missing loaner policy. We have not added a promise either way. Times remain the fictional event’s local times; a real distributed team should add its actual time zone.
Team workshop — October16,2026 The workshop runs from9:00 a.m. to12:30 p.m. in Room402. Check-in opens at8:30 a.m. Register through the intranet form by October8 at noon. Capacity is40 people. If full, select “Join waitlist” in the form. Bring your laptop. Submit dietary requests through the intranet form by October12. The recording will be available to registered attendees for14 days after the workshop. Slides will be available to all employees afterward. EDITOR CHECK BEFORE SENDING: confirm the loaner-laptop policy, add accurate wording if needed, and remove this editorial note.
Use this comparison prompt next time
The improved prompt below is WekeyLab AI’s template, not another tested response. Its purpose is to expose omissions and preserve the difference between text evidence and an operational assumption. Before sending an announcement, inspect the actual form and calendar as well as the draft.
For a related example, our meeting-notes comparison shows a future sharing promise being labeled complete. The weekend-work reply comparison examines a similar problem: language that quietly adds a commitment. Both are linked below.
Compare OLD and NEW in English. Show changed, added and removed information, with the wording from each version. Separate confirmed textual changes from questions for the owner. Do not infer that a removed sentence proves a policy ended. Identify important unchanged dates or conditions that a reader could otherwise miss. Then list what needs checking before publication.
Sources and actual records
September18,2026,09:02–09:03 KST. Same English synthetic input, one submission per new web chat, no length or format cap. ChatGPT Free, Think off, model name not displayed; Gemini Flash, plan unverified; Claude Free, Sonnet5 Medium. ChatGPT/Gemini replied in English, Claude in Korean; the cause was not established. Saved answer lengths:1730/1491/806 characters including whitespace. UI/status text excluded and file fingerprints matched. Ten checks fixed before collection, manually compared to the supplied versions; an independent text diff and deadline calculation were saved. No real sending, permissions change, PDF parsing or time saving was tested. KR/ZH editions localize this same run, not separate local tests. Related English search results were observed; US keyword volume is unknown.
Related: AI meeting notes comparison / 회의록 비교
Related: weekend work replies / 업무 요청 답장 비교
ChatGPT · 2026-09-18 09:02-09:03 KST
I'm updating our team's internal workshop announcement. Compare the old and new versions and tell me what changed and what I should update before sending it to colleagues. OLD VERSION Team workshop — October 16, 2026 The workshop runs from 9:00 a.m. to noon in Room 204. Check-in opens at 8:30 a.m. Register by October 9 at 5:00 p.m. using the intranet form. Capacity is 40 people. Bring your laptop. Loaner laptops are available if requested when registering. Send dietary requests to [email protected] by October 12. If the workshop is full, you will automatically join the waitlist. The recording will be available to all employees for 30 days after the workshop. NEW VERSION Team workshop — October 16, 2026 Capacity is 40 people. Register by October 8 at noon using the intranet form. The workshop runs from 9:00 a.m. to 12:30 p.m. in Room 402. Check-in opens at 8:30 a.m. Bring your laptop. Send dietary requests through the intranet form by October 12. If the workshop is full, select "Join waitlist" in the intranet form. The recording will be available to registered attendees for 14 days after the workshop. Slides will be available to all employees after the workshop. Here’s the change list I’d use as a pre-send checklist: Item Old New What to update Registration deadline Oct. 9, 5:00 p.m. Oct. 8, noon Update deadline everywhere Workshop end time 12:00 p.m. 12:30 p.m. Update schedule/calendar details Room Room 204 Room 402 Update location Loaner laptops Available if requested during registration Not mentioned Confirm whether loaners are no longer available or were accidentally omitted Dietary requests Email [email protected] by Oct. 12 Intranet form by Oct. 12 Remove the email instruction and direct people to the form Waitlist Automatically joined if full User selects “Join waitlist” Update instructions so people know they must actively opt in Recording access All employees, 30 days Registered attendees, 14 days Update both audience and availability period Slides Not mentioned Available to all employees after workshop Add this to the announcement Things I’d verify before sending Loaner laptops: This is the only old detail that disappears without an explicit replacement. Confirm whether loaners are still available. Intranet form: Make sure the form actually supports dietary requests and has the “Join waitlist” option. Calendar/intranet materials: Because the time and room changed, update any calendar invitation, room reservation, registration page, or attached schedule—not just the announcement. Recording wording: The change from “all employees” to “registered attendees” is substantive, so make sure that access restriction is intentional. Deadline: The new deadline is October 8 at noon, one day and five hours earlier than the old deadline. Everything else in the new version is consistent with the old announcement, with the addition of the slides information.
Gemini · 2026-09-18 09:02-09:03 KST
I'm updating our team's internal workshop announcement. Compare the old and new versions and tell me what changed and what I should update before sending it to colleagues. OLD VERSION Team workshop — October 16, 2026 The workshop runs from 9:00 a.m. to noon in Room 204. Check-in opens at 8:30 a.m. Register by October 9 at 5:00 p.m. using the intranet form. Capacity is 40 people. Bring your laptop. Loaner laptops are available if requested when registering. Send dietary requests to [email protected] by October 12. If the workshop is full, you will automatically join the waitlist. The recording will be available to all employees for 30 days after the workshop. NEW VERSION Team workshop — October 16, 2026 Capacity is 40 people. Register by October 8 at noon using the intranet form. The workshop runs from 9:00 a.m. to 12:30 p.m. in Room 402. Check-in opens at 8:30 a.m. Bring your laptop. Send dietary requests through the intranet form by October 12. If the workshop is full, select "Join waitlist" in the intranet form. The recording will be available to registered attendees for 14 days after the workshop. Slides will be available to all employees after the workshop. Key Changes Between Versions Registration Deadline: Shifted earlier, from October 9 at 5:00 p.m. to October 8 at noon. Workshop Duration: Extended by 30 minutes, now running 9:00 a.m. to 12:30 p.m. Location: Moved to Room 402 (previously Room 204). Dietary Requests Method: Now submitted via the intranet form, removing the [email protected] email route. Waitlist Process: Requires users to manually check "Join waitlist" on the form instead of automatic enrollment. Recording Access: Access is now restricted to registered attendees (down from all employees) and time-limited to 14 days (down from 30 days). New Materials Added: Slides are now explicitly provided to all employees post-workshop. Loaner Laptop Info: Removed entirely from the new text. Action Items to Update Before Sending Clarify Loaner Laptops: Decide if loaner laptops are no longer offered, or if that policy still exists and needs to be re-added to the announcement. Double-Check Intranet Form Fields: Ensure your intranet form has been updated to include the new "Join waitlist" checkbox and a dedicated Dietary Requests field before publishing the link. Highlight Shifted Deadlines: Emphasize the earlier registration cutoff (Oct 8 @ noon) in your email subject line or callout box so returning attendees don't rely on the old date. Confirm Access Restrictions: Verify with your IT or multimedia team that the recording portal can restrict access strictly to registered attendees for the 14-day window.
Claude · 2026-09-18 09:02-09:03 KST
I'm updating our team's internal workshop announcement. Compare the old and new versions and tell me what changed and what I should update before sending it to colleagues. OLD VERSION Team workshop — October 16, 2026 The workshop runs from 9:00 a.m. to noon in Room 204. Check-in opens at 8:30 a.m. Register by October 9 at 5:00 p.m. using the intranet form. Capacity is 40 people. Bring your laptop. Loaner laptops are available if requested when registering. Send dietary requests to [email protected] by October 12. If the workshop is full, you will automatically join the waitlist. The recording will be available to all employees for 30 days after the workshop. NEW VERSION Team workshop — October 16, 2026 Capacity is 40 people. Register by October 8 at noon using the intranet form. The workshop runs from 9:00 a.m. to 12:30 p.m. in Room 402. Check-in opens at 8:30 a.m. Bring your laptop. Send dietary requests through the intranet form by October 12. If the workshop is full, select "Join waitlist" in the intranet form. The recording will be available to registered attendees for 14 days after the workshop. Slides will be available to all employees after the workshop. 변경 사항 비교 항목 기존 변경 비고 시간 9:00~12:00 9:00~12:30 30분 연장 장소 204호 402호 호실 오타 아닌지 확인 필요 등록 마감 10/9 17:00 10/8 12:00 마감이 하루 이상 앞당겨짐 노트북 대여 등록 시 요청하면 대여 가능 문구 삭제됨 의도적 삭제인지 확인 필요 식이 요청 접수 이메일([email protected]) 인트라넷 폼 접수 채널 변경 — 폼에 해당 항목이 실제로 추가됐는지 확인 대기자 등록 정원 초과 시 자동 대기 폼에서 "대기자 등록" 직접 선택 자동→수동으로 절차 변경, 공지에서 강조 필요 녹화본 제공 전 직원 대상, 30일간 등록자 한정, 14일간 접근 범위·기간 모두 축소됨 — 가장 큰 변경점 자료(슬라이드) 언급 없음 워크숍 후 전 직원 공개 신규 추가 항목 발송 전 확인 필요 사항 노트북 대여 안내 누락 — 실수로 빠진 건지, 정책이 없어진 건지 확정 필요. 계속 제공한다면 문구 복원 권장. 호실 변경(204→402) — 실제 예약된 방과 일치하는지 재확인. 녹화본 축소(전 직원 30일 → 등록자 14일) — 정책 변경이 맞다면 공지에서 별도로 눈에 띄게 표시하는 게 좋음. 기존에 "전 직원 열람 가능"으로 알고 있던 동료들이 혼란스러워할 수 있음. 대기자 등록 방식 변경(자동→수동) — "정원 초과 시 폼에서 직접 대기자 등록을 선택하세요"처럼 행동 지침을 명확히 문장에 넣는 게 좋음. 그냥 "선택 가능" 정도로만 쓰면 놓치는 사람이 생길 수 있음. 등록 마감 단축 — 기존 대비 마감이 빨라졌으므로, 공지 발송 시점과 마감일 사이 여유가 충분한지 확인.