Prompt Patterns: Create and Edit

An invitation email that doesn't exist yet and a paragraph that needs a more executive tone call for different instructions. In the first case, Copilot is drafting from a source. In the second, it's editing text you already have. Both can introduce a plausible detail that nobody supplied, but the point of failure differs. The create pattern controls what may enter a new draft. The edit pattern protects the meaning of existing content while its wording or structure changes.

Decide whether you're drafting or editing

Drafting produces an initial deliverable from an idea or source, such as a marketing plan, slide deck, invitation email, or meeting agenda. Editing begins with existing content and changes its wording, structure, tone, or format. Writing the invitation is drafting. Shortening it later is editing. A draft may add facts that weren't supplied. An edit can preserve every visible number and still change what a statement means.

Review both before anyone else sees them. A drafting prompt should tell Copilot what to create, why it is needed, who will read it, which facts it may use, and how the finished output should look. Watch for invented venues, budgets, or channels. An editing prompt starts from content you already trust, so your check shifts to meaning. Before writing the instruction, decide whether you're creating something new or reshaping material you have. That answer tells you which failure deserves most attention.

The create pattern: four kinds of "fact"

When you draft from a source, a source boundary alone isn't enough, because a good draft legitimately contains things the source never said. The trick is to keep four categories straight so a reviewer can tell where every statement came from:

Say the source lists a workshop on October 15. "October 15" is a source-backed fact. "Ask people to reply by October 1" is valid only as a supplied decision you authorized, so flag it as one. A promotion channel Copilot dreamed up is a suggestion. A venue nobody stated stays not provided. This lets you add real instructions without pretending they came from the source, and it's what lets a reviewer trust the draft.

A quick audit shows the four categories at work. Suppose Copilot drafts an invitation and writes "Join us for a virtual workshop on October 15." October 15 is a source-backed fact, so keep it. "Virtual" appeared in neither the brief nor your instructions. It's an invention, so it goes, replaced by "Time and location: Details to follow." If you authorized a reply-by date, that line is a supplied decision. Keep it, but don't let it read as if the brief demanded it.

Run that pass sentence by sentence and every statement lands in exactly one bucket: sourced, supplied, suggested, or absent. A draft you can audit that cleanly is one a busy reviewer approves in a single read instead of interrogating line by line.

The edit pattern: preserve, transform, constrain

A strong edit prompt has three layers. Name all three and you can check the result:

• Preserve is what must stay accurate: every date, number, name, and status.
• Transform is the exact change: shorten, restructure, change tone, convert to a table.
• Constrain sets the limits: audience, length, format, order.

Compare "rewrite this" with "rewrite the selected project update for senior sponsors. Preserve every date, number, and named deliverable. Use 60–80 words, a direct tone, and end with the decision required." The second is a spec you can test: count the words, confirm the dates survived, check that the last sentence asks for a decision. Before you submit, list your preservation facts explicitly. That list becomes your verification checklist afterward.

A worked rewrite makes the drift risk concrete. You ask Copilot to condense a project update for a steering committee, preserving three environments, an 18 August validation date, a vendor-certificate blocker, and a Friday decision from Security. The draft nails the facts and the length, but ends "Security must approve or reject the certificate by Friday." Nothing in the source said the decision takes the form of approve-or-reject. That's an invented characterization the sponsors might act on.

The fix is a narrow follow-up: "Revise the final sentence so it identifies Security's decision as needed, without describing it as approval or rejection. Add no new responsibility." Everything else stays. Your preservation list catches this. Check the rewrite against it item by item and the one drifted phrase stands out.

Focused rewrites and broader edits

Match the tool to the size of the change. A focused rewrite targets a bounded passage, a paragraph, a bullet list, where the source is your selection and the output is revised wording. Use it for "shorten this paragraph but keep its dates." A broader Edit with Copilot task reorganizes a whole section, document, or deck: "reorder these headings chronologically, rewrite each opening sentence, and preserve every quoted policy name." Reach for the pattern that fits. A bounded rewrite gives you tighter control and an easier check.

Your selection is part of the prompt. Too wide, and Copilot changes text you were happy with. Too narrow, and it loses the context needed to read a pronoun, a number, or a dependency. Pick the smallest selection that's still complete enough to preserve meaning, and restate the boundary in words: "Use only the selected paragraph."

Transformations reward patience. Turning paragraphs into a table, or detailed statements into presentation bullets, works best one operation at a time, especially in Excel, where formatting, sorting, filtering, and highlighting should each run and be verified separately so you can tell which step introduced a problem.

A couple of practical guards keep transforms safe. In Excel, remember that filtering hides rows, it doesn't delete them: verify the visible rows while the filter is on, then clear it and confirm every original row returns in the sorted order. When a transform touches formulas, keep at least one formula-bearing column inside your selection so you can confirm the math still recomputes. Checking formulas on a table of literal numbers proves nothing. Above all, if a rewrite changes a fact's frame, "cost" becoming "investment," "planned" becoming "confirmed," treat it as a failure even when every digit is right, and send a one-line correction restoring the original word. Small, verifiable steps beat one ambitious prompt you can't fully check.