Gemini
Pending safe baseline
Score only if a no-login or project-safe route returns a complete answer that is separable from prompt echo/UI text.
This evidence log tests a safe first workflow: paste fictional transcript-style voice notes into a general AI assistant and ask for a summary, task register, uncertainty list, draft replies, and safety checklist. No real recording, phone contact, calendar, meeting bot, CRM, email, note-app connector, task system, customer contact, shipment booking, file send, spend approval, or inventory update was used.
In the synthetic Northstar Candle Co. work-capture fixture, ChatGPT scored 4.59/5 and Duck.ai scored 4.56/5. Both produced useful review drafts without login, uploads, connectors, real audio, or live actions. The practical lesson is not “let AI run your workday”; it is “use AI to draft a reviewable task register, then verify the facts and commitments yourself.”
Scores cover the assistant text only. They do not test call recording, transcription accuracy from audio, mobile apps, contact/calendar access, meeting bots, task creation, reminders, CRM/email connectors, or workplace automation.
Prompt echo, setup friction, history/sidebar contamination, and pending routes are tracked separately in the evidence CSVs.
| Tool | Score | Last tested | What worked | What to review |
|---|---|---|---|---|
| ChatGPT | 4.59/5 | 2026-06-21 | Best current result by a narrow margin. It produced a strong summary and task register, preserved the Lakeview and Cedar Room uncertainty boundaries, drafted useful review-only replies, and avoided claims that it sent files, booked shipment, approved spend, or updated live systems. | It did not explicitly calculate the $1,060 pre-shipping Cedar Room total, left some owners vague, and slightly blurred the old-label-photo follow-up owner in the teammate note. |
| Duck.ai | 4.56/5 | 2026-06-22 | Very close to ChatGPT. It captured names, dates, price components, Lakeview inventory/request details, explicit uncertainty labels, review-only customer/team drafts, and no-live-action safety boundaries through a no-login Duck.ai route. | It also did not explicitly calculate the $1,060 pre-shipping Cedar Room total, kept approval authority vague, omitted the Maya/Sam old-label-photo follow-up from the team-note draft, and required cleaned-output separation because raw page text included prompt/history/UI chrome. |
A pending row is not a recommendation or a quality failure. It means a safe route has not yet produced a full, distinct answer that can be scored.
Pending safe baseline
Score only if a no-login or project-safe route returns a complete answer that is separable from prompt echo/UI text.
Pending safe baseline
Use the same transcript packet and keep public answer-page prompt echo separate from assistant output before scoring.
Pending safe baseline
Prior no-login Copilot checks can echo prompts or gate output. Keep scores blank unless a distinct assistant answer appears.
The fixture uses Northstar Candle Co., a fictional small business. Maya dictates three short notes after a packaging vendor call, a teammate hallway conversation, and a Lakeview Market store-manager check-in. A strong answer must preserve the Cedar Room artwork deadline, label burn-time correction, uncertain shipping estimate, Lakeview dock/address blocker, inventory counts, and no-approval/no-booked-shipment boundaries.
The trap is that a polished AI summary can sound like work already happened. We score down any output that implies files were sent, spend was approved, freight was booked, a customer was contacted, inventory was updated, or a task/calendar system changed.
The prompt deliberately separates transcript cleanup from call recording, contact/calendar access, customer communication, approvals, and live task automation.
content/fixtures/voice-notes-work-capture/synthetic-voice-note-transcripts.md
Three fictional Northstar Candle Co. transcript-style voice notes: Cedar Room packaging, Jules artwork/label follow-up, and Lakeview Market sample/order notes.
content/fixtures/voice-notes-work-capture/voice-notes-paste-prompt.md
The exact prompt asking for a clean summary, task register, decisions/approvals, uncertainties, customer reply, teammate note, and safety checklist.
content/fixtures/voice-notes-work-capture/expected-voice-notes-output.md
Manual answer key with required facts, uncertainty labels, task highlights, draft-reply constraints, and must-not-invent checks.
content/fixtures/voice-notes-work-capture/voice-notes-test-protocol.md
The no-connector protocol: sanity prompt, prompt/output separation, screenshots, raw text, cleaned assistant output, metadata, and no-score blockers.
The current test starts from synthetic pasted transcript text. It is not a shortcut around consent, recording laws, workplace data rules, or customer privacy.
The current scores cover two public web prompt-only runs using a synthetic transcript packet. They do not test transcription accuracy from audio, mobile voice-note capture, paid plans, account memory, exports, team sharing, real customer or employee data, meeting-bot consent, phone contacts, calendars, reminders, CRM/email/note-app/task connectors, browser extensions, automations, shipment booking, file sends, spend approvals, inventory edits, or customer contact. New rows will be added only when raw output or setup-friction evidence is saved and scored with the same rubric discipline.