Write Clear Project Change Requests with Voice Dictation

“Could we add one more thing?” sounds small until different people interpret it differently. A project change request needs to explain what would change, why it matters, and what decision is needed before work begins.

Voice dictation can help you capture that explanation while the context is fresh. Speak the reasoning, then edit the text into a request that someone can evaluate. On your Mac, keep the current brief beside your draft so you can distinguish the agreed work from the proposed addition.

1. Start with the current agreement

Before dictating, find the latest agreed scope, deliverable, and deadline. Name the document or version that defines them. Without this starting point, “add a page” could mean expanding the project, replacing an existing page, or correcting an omission.

Write one sentence about what stays the same. For example, the audience and delivery format may be unchanged even though the content would expand. That boundary helps keep a specific request from becoming a broader redesign.

2. Dictate five short sections

Use these prompts, pausing between each one:

• Current plan: What has already been agreed?
• Requested change: What exactly would be added, removed, or replaced?
• Reason: What new information makes the change useful?
• Impact and options: What might change in timing, effort, or other deliverables?
• Decision: Who needs to choose what, and by when?

Separate confirmed facts from estimates. “The writer estimates one additional day” is different from “the delivery date is confirmed.” If the effect on cost or review time is unknown, say what still needs checking rather than inventing a number.

3. Turn the spoken explanation into a request

Here is a fictional spoken draft:

We agreed on a three-page setup guide for October ninth. Support keeps getting questions about connection errors, so I want to add a troubleshooting page. Writing would take about one extra day; design review isn't estimated yet. We could replace the appendix or keep it and aim for October twelfth. Maya needs to decide which option we should plan around.

An edited request could read:

Subject: Decision requested: troubleshooting page for the setup guide

Hi Maya,

The current plan is a three-page setup guide due October 9, 2026. I propose adding a troubleshooting page to address recurring connection questions reported by support. The audience and delivery format would stay the same.

The writing estimate is one additional working day; design review time still needs confirmation. We could replace the appendix and aim to keep October 9, or retain it and target October 12 for a four-page guide. Neither revised schedule is confirmed yet.

Could you choose a preferred option, or keep the original scope, by October 2 at 15:00 UTC? Once you respond, I will confirm the review effort and proposed schedule before updating the project plan.

Thank you.

The message makes the choice visible without presenting an estimate as a promise. Add a link to the current brief and check that the recipient can open it.

4. Reuse a compact change request template

Current plan: [agreed scope and deadline]. Requested change: [specific addition, removal, or replacement]. Reason: [new information or need]. Unchanged: [boundaries]. Expected impact: [estimate and assumptions]. Still to confirm: [unknowns]. Options: [choices and trade-offs]. Decision requested from [person] by [date, time, and time zone if needed]. Next step after the decision: [owner and action].

Replace every placeholder. For a small change, combine these fields into a short paragraph. For a larger one, keep the headings so a reviewer can scan the trade-offs.

5. Review the words that change commitments

Check dates, quantities, names, and phrases such as “replace” versus “add.” Verify that “not confirmed” has not become “confirmed” in transcription. Remove spoken filler, but keep uncertainty that affects the decision.

After a decision, record the agreed scope and schedule in the project brief. A request email alone does not update the plan, and silence does not establish agreement.

For related writing tasks, see creating project briefs and writing project status updates.

TypeFree is a simple way to turn speech into editable text and write faster. Dictate your next change request, refine the trade-offs, and send a clear decision for your reader to consider.