When the conversation changes, check the project record.
A client email can move a delivery date or describe an approval differently from the working plan. TaskFieldAI is being built to help the person managing that conversation inspect the earlier records and clarify the change.
Opens an email to founder@taskfieldai.com. Please don't email private client records.
A new date, an older plan
The client's project lead confirmed a first version by 16 August. Two weeks later a new email targets 19 August. Your delivery plan — outside TaskFieldAI — still says 16 August, and the design review is booked for the 17th.
Illustrative scenario — not customer data
TaskFieldAI can put the two emails side by side and draft a clarifying question. Updating the plan, and moving the review, stays with you.
The latest email gives a different delivery date.
We'll deliver the first version by 16 August.
We're targeting 19 August for the first version.
The new target is three days later than the earlier commitment.
Needs confirmation: These messages don't show whether the new date was accepted.
Read both messages
Thanks for confirming the scope. We'll deliver the first version by 16 August, and we'll send the review link the same day.
Quick update on timing: we're targeting 19 August for the first version. I'll share the review link as soon as it's ready.
See a clarification draft
Thanks for the update. Your earlier email gave 16 August for the first version; this one says 19 August. Is that a proposed change to the delivery date?
A draft for you to edit. Nothing on this page sends email.
Keep the approval trail visible
A change moves through stages, and each needs a different response:
- Proposed — someone has asked. The earlier agreement still stands.
- Accepted — both sides agreed in writing. The plan should change.
- Unresolved — a message treats something as agreed that the record does not show. Ask before acting.
Findings about changed dates and scope are part of Changes and risks Limited test
Work with your existing process
If your team already runs a SOW and change-request process, that process may be enough most of the time. The gap TaskFieldAI is aimed at is narrower: the email that quietly describes the plan differently before anyone raises a change request, and the reconstruction work when someone later asks what was agreed.
It does not replace your delivery system. TaskFieldAI does not update shared project plans, enforce payment or decide what is in scope. It shows the records and helps you ask the right question.
Know the coverage
What TaskFieldAI can see in a typical client project today.
| Source | Can TaskFieldAI see it? |
|---|---|
| Client emails | Yes — Gmail beta, from the mailbox you connect. |
| A SOW or proposal | Only if you upload it yourself (paid plans). Email attachments are not read automatically — only their names are seen. |
| Figma comments or approvals | No. Not visible unless someone confirms the approval by email. |
| Call or meeting transcripts | No. Only what is written up afterwards in email. |
| Your project plan (Asana, Jira, a spreadsheet…) | No. TaskFieldAI does not read or update project plans. |
| Slack or Teams | Not yet — in development. |
It works on one person's mailbox. If a colleague handles part of the client relationship from their own inbox, their messages are not included unless they connect their own account.
Bring a project where the plan and the emails disagreed.
We'll walk through how the current product would lay it out, using an example rather than your client's records.