TASKLITMUS / CHECK 001

A polished draft can make a promise you never approved.

Consider this constructed example:

Source note: “We expect to send the proposal next week. The date is not confirmed.”

Draft: “We will deliver your proposal by Friday.”

The draft turns an estimate into a commitment and adds a deadline. The source does not support either change. This is an illustration, not a result from a product test.

Before sending an AI-written email, check three things:

1. Trace every promise. Check dates, prices and deliverables against the source. Flag unsupported details instead of guessing.
2. Keep uncertainty visible. “Expect”, “estimate” and “pending approval” carry meaning. A rewrite should not turn them into guarantees.
3. Confirm who can commit. An accurate detail is not automatically an authorized promise. Get the responsible person’s approval before committing the team.

A revision supported by the source:

“We expect to send the proposal next week, but the date is not yet confirmed.”

Try it today: underline every sentence in one draft that commits someone to a date, amount or action. Compare each with the original notes.

​Download the free Task Check Scorecard​

One page to check accuracy, missing facts and cleanup time.

Tasklitmus — Practical AI for small teams.