“AI task management tools” or “task app” searches
Use the beginner support guide to decide when paste-only triage is enough and when a real task app needs sandbox permission, audit-log, and undo testing.
This evidence log tests a safe first workflow: paste synthetic project notes into a general AI assistant and ask for a reviewable priority list, task table, dependency map, risk register, and draft updates. No Jira, Asana, Trello, Notion, Slack, Gmail, Outlook, calendar, reminder, ecommerce, shipping, CRM, task-system connector, workflow automation, browser agent, real project data, or live action was used.
In the synthetic Northstar Candle Co. launch-triage fixture, Duck.ai scored 4.60/5 and Perplexity scored 4.36/5. Both produced useful review drafts without touching real project systems. Duck.ai had the cleaner overall balance; Perplexity gave a detailed table and dependency map but needed more human checking for priority order and one due-date detail.
These scores cover assistant text only. They do not test Jira, Asana, Trello, Notion, Slack, Gmail, Outlook, calendars, ecommerce, shipping, support tools, project-management connectors, workflow automation, browser agents, real workplace data, or task creation.
Early task-management and workflow-agent searches overlap. This route map keeps readers on the safest relevant page before they connect Jira, Asana, Trello, Notion, Slack, email, calendars, ecommerce, or browser agents.
Use the beginner support guide to decide when paste-only triage is enough and when a real task app needs sandbox permission, audit-log, and undo testing.
Use the to-do-list guide when the reader only needs a priority list, owners, due dates, and dependencies from pasted notes — not a full project-management platform.
Route automation-curious readers to the workflow-boundary evidence before they let an agent touch live apps, customer systems, prices, calendars, or messages.
Use the admin-professional route map for readers comparing task triage with email, calendar, spreadsheet, form, PDF, and meeting-note workflows.
Setup friction, prompt echo, public answer-page cleanup, and pending rows are tracked separately in the evidence CSVs.
| Tool | Score | Last tested | What worked | What to review |
|---|---|---|---|---|
| Duck.ai | 4.60/5 | 2026-06-24 | Best current result. It produced a practical task-triage draft with strong no-live-action boundaries, useful leadership and team-message drafts, solid stale-claim detection, and mostly accurate owners, dates, and dependencies. | Priority order slightly over-weighted support macro/return-policy work before Alex’s Thursday 11:00 input gate, and it had minor fuzziness around Jules/final-count and social timing details. |
| Perplexity | 4.36/5 | 2026-06-24 | Produced a separable public answer-page draft with a detailed task table, dependency map, risk register, draft leadership update, person-by-person draft asks, human-review checklist, and strong connector/live-action boundaries. | Priority order put inventory first while stale-claim cleanup was lower than the answer-key top order. One table row shifted Alex’s landing-page draft from Wednesday EOD to Thursday EOD, and the public answer page required Show more expansion plus prompt-echo cleanup. |
A pending or setup-friction row is not an output-quality score. It means no distinct project-triage answer has been captured through a safe route yet.
Pending safe baseline
Score only if a no-login or project-safe route returns a distinct assistant output, not sign-in UI, prompt echo, or marketing copy.
Pending safe baseline
Run only after a visible composer and separable output can be verified; keep project connectors and real workplace data out of scope.
Pending safe baseline
Prior no-login Copilot runs sometimes echo prompts only; keep the full fixture unscored unless a distinct answer appears.
The fixture uses Northstar Candle Co., a fictional candle business preparing a small Cedar Room summer bundle launch. The notes mix Monday planning-call fragments, Tuesday support-thread snippets, Wednesday vendor/warehouse constraints, stale marketing copy, and task fragments. That mirrors a normal worker’s problem: the facts exist, but they are scattered across messages, notes, and partial plans.
A strong answer must preserve owner limits, deadlines, tentative price/inventory status, stale copy risks, return-policy ambiguity, and draft-only boundaries while turning the packet into something a human can review before updating any project system.
The prompt deliberately separates planning/status drafting from connected tools, customer messaging, ecommerce, approvals, and action-taking.
content/fixtures/ai-project-management-task-triage/synthetic-project-packet.md
Fictional Northstar Candle Co. launch notes from planning, support, vendor, warehouse, and marketing fragments.
content/fixtures/ai-project-management-task-triage/project-triage-paste-prompt.md
The exact prompt requiring an ordered 48-hour priority list, task table, dependency map, risk register, leadership draft, draft asks, human-review checklist, and connector boundary.
content/fixtures/ai-project-management-task-triage/expected-project-triage-output.md
Manual answer key for must-preserve facts, priority logic, task rows, risks, draft communications, must-not claims, and scoring criteria.
content/fixtures/ai-project-management-task-triage/project-triage-test-protocol.md
No-connector protocol: use only synthetic project data, preserve prompt/raw/clean output separately, and never score login gates or prompt echoes as model output.
A polished task table can still carry a wrong date, implied approval, stale customer promise, or unsafe automation step.
The current scores cover two public web prompt-only runs using a synthetic project packet. They do not test paid plans, project-management apps, task creation, Slack/Teams/email/calendar connectors, ecommerce or warehouse systems, support tools, CRM records, real project data, privacy retention settings, automated reminders, live publishing, pricing updates, inventory reservations, shipment booking, customer contact, approvals, or production workflow automation. New rows will be added only when raw output or setup-friction evidence is saved and scored with the same rubric discipline.