Turn rough notes into an email draft without adding new facts

Sort the notes before asking for a draft

Start by collecting only the information the email needs. Mark the exact action you want from the recipient, the facts they need to understand it, and any deadline or date that is actually in your notes. Keep uncertainty visible: write “date not confirmed” rather than letting a blank space look like an invitation to guess.

You can also identify details that must stay unchanged, such as a project name, amount, spelling, or quoted wording. If a detail is irrelevant to the request, leave it out instead of giving the AI extra material to interpret. Avoid entering passwords or one-time passcodes into an assistant.

• Ask: What do I want the recipient to do?
• Mark which names, dates, amounts, and commitments are confirmed.
• Label missing information instead of filling it in from memory.

Set a boundary, not just a tone

A request such as “make this professional” describes style, but not factual limits. Add an instruction that the draft must use only the notes, retain the original ask, and leave gaps unresolved. Ask for a concise draft and tell the assistant to flag missing information rather than inventing a likely answer.

If AI assistance is available for your BITTU Mail account, it can help shape a draft; availability may depend on plan and provisioning. Treat the result as a proposal, not a verified account of events. Keep the source notes beside the draft so you can compare them directly.

Use only the notes below. Keep the request and all confirmed details unchanged. Do not infer dates, reasons, promises, or outcomes. If information is missing, mark it [NEEDS CONFIRMATION]. Turn the notes into a clear, courteous email and do not add a subject unless the notes support one.

Notes:
- ask Jordan to review the attached schedule
- feedback by [date not provided]
- send comments by email

Build around the original ask

A readable email usually makes its purpose easy to find. Check that the opening gives enough context without adding a new story, and that the request remains specific. If your note says “review the schedule,” the draft should not quietly turn that into “approve the schedule” or “confirm the launch.” Those are different actions.

Likewise, preserve the level of certainty in your notes. “We may need to move the meeting” should not become “We will move the meeting.” A polished sentence can sound confident even when its source was tentative. Keep uncertainty where it matters, or ask the relevant person to confirm it before sending.

Compare each sentence with its source

Read the draft one sentence at a time. For each sentence, point to the note that supports it. If you cannot, decide whether the sentence is harmless connective wording or a new factual claim. Remove unsupported claims about why something happened, what another person agreed to, what will happen next, or when it will happen.

Pay particular attention to greetings and sign-offs that imply a relationship, apologies that imply responsibility, and phrases such as “as discussed” or “as promised.” They may be appropriate, but only if your notes support them. Review names, dates, recipients, promises, and any financial information against the original source.

• Supported: “Please review the schedule.”
• Unsupported unless noted: “As agreed, please approve the final schedule by Friday.”

A quick example: request without an invented deadline

Suppose your fragments say to ask Jordan to review an attached schedule, with no deadline recorded. A draft can be clear without pretending a date exists. Keep the missing deadline marked for yourself, or ask for it before sending. Do not replace it with a customary turnaround time.

To: [Jordan's email]@example.com
Subject: Review of the schedule

Hi Jordan,

Could you please review the attached schedule and send your comments by email? I don’t have a deadline recorded, so I’ll confirm the timing separately if needed.

Thanks,
[Your name]

Confirm the draft before it leaves your mailbox

The example’s sentence about the missing deadline is useful only if it accurately describes what you want to tell Jordan. If it does not, remove it; the notes do not establish that you will confirm timing separately. This is the same discipline to apply throughout: a draft may contain plausible wording that still adds a commitment.

Before sending, verify the recipient, subject, attachment, and every specific detail against your notes and the original message or document where appropriate. If a fact is unclear, resolve it or leave it out. You can confirm the process worked when the email reads smoothly, preserves the exact ask, and every factual statement can be traced to information you supplied.