Worked case: rewrite without drift

A program manager needs a short decision note for department leaders. The source material says:

• A six-week scheduling pilot involved 24 volunteers from one office.
• Nineteen completed the closing survey.
• Fourteen of those nineteen said scheduling took less time.
• Three participants reported missed notifications.
• The support team logged two duplicate bookings.
• No accessibility review or security review has been completed.
• The pilot budget covered only the test.
• Leaders may approve a second, broader pilot; they are not being asked to approve organization-wide rollout.

The rough draft is:

Our new scheduling system was a huge success. Most employees loved it and it saved everyone time. There were only a few tiny glitches, which IT can easily fix. We should roll it out across the organization next month before people lose momentum. The pilot proved that the tool improves productivity, and the cost should be minimal because we have already implemented it.

The draft is concise and confident. It is also misleading.

Map each problem instead of merely requesting a “more professional” tone.

Scope drift: Twenty-four volunteers in one office became “everyone” and “most employees.” The participants may not represent the organization.

Denominator hiding: Fourteen favorable responses are meaningful only with the nineteen survey responses and twenty-four participants visible.

Unsupported causality: Reports that scheduling took less time do not prove broad productivity improvement.

Minimization: Missed notifications and duplicate bookings become “tiny glitches.” That label dismisses evidence and consequences.

Invented ownership and certainty: The source does not say IT owns the fixes or that fixes are easy.

Authority drift: The requested decision is a broader pilot, not organization-wide rollout.

Invented timing and cost: “Next month” and “minimal” are unsupported. The existing budget did not fund expansion.

The central problem is not style. The text changes facts and the decision.

Create a compact rewrite brief:

PURPOSE
Help department leaders decide whether to approve a broader second pilot.

AUDIENCE
Leaders who know the scheduling problem but not the pilot details.

CORE MESSAGE
Early feedback supports more testing, while reliability, accessibility,
security, budget, and representativeness remain unresolved.

PRESERVE
Duration, participant counts, survey denominator, reported benefits,
notification and booking issues, missing reviews, budget boundary,
and leaders' actual authority.

DO NOT
Claim causality, broad employee preference, easy fixes, rollout approval,
an expansion date, or a known cost.

The outline can now follow the decision: recommendation, evidence, limitations, proposed next step, and information needed.

A responsible version might read:

Decision requested: approve planning for a broader scheduling pilot

A six-week pilot with 24 volunteers in one office produced enough positive feedback to justify considering a broader test, but it does not support organization-wide rollout. Nineteen participants completed the closing survey; 14 of those 19 reported spending less time on scheduling.

The pilot also revealed issues requiring investigation. Three participants reported missed notifications, and the support team recorded two duplicate bookings. The tool has not completed accessibility or security review, and the pilot budget does not cover expansion.

We recommend developing a proposal for a second pilot with more representative participants, defined reliability measures, required reviews, support ownership, and a separate budget. Leaders are being asked to authorize that planning step, not a rollout. The proposal should return with scope, cost, timeline, stop criteria, and accountable owners before a second pilot begins.

This rewrite is slightly longer because the decision requires denominators, limitations, and boundaries. Clarity is not the same as brevity.

Create a preservation table in your working notes, even if the final document does not show it.

For participant evidence, the rewrite retains 24 volunteers, one office, 19 responses, and 14 favorable responses. It does not translate the result into “most employees.”

For failures, it preserves three missed-notification reports and two duplicate bookings. It avoids deciding severity or cause without evidence.

For governance, it retains missing accessibility and security reviews and the budget limitation. It does not imply that existing implementation makes expansion cheap.

For authority, it asks leaders to authorize planning for a second pilot. It explicitly says they are not approving rollout.

One detail is worth examining: “enough positive feedback to justify considering” is a recommendation, not an objective fact. The author should own that judgment and confirm it fits the purpose. A model should not quietly present it as organizational consensus.

Suppose the organization’s voice card says: lead with the action, prefer concrete verbs, acknowledge uncertainty directly, and avoid hype. The rewrite follows those choices. A second style pass might shorten “produced enough positive feedback to justify considering” to “supports considering,” but only if the reduced wording does not overstate evidence.

Do not add a dramatic story from a participant unless a verified, permitted example exists. Do not make the note “warmer” by claiming people were excited. Style requests cannot authorize new facts.

The author should inspect the survey results, support log, review status, budget record, and decision authority. Check whether “volunteers” and “one office” are accurate descriptions. Confirm that the recommendation’s proposed outputs—scope, cost, timeline, stop criteria, and owners—are appropriate.

Then test reader understanding:

• What decision are leaders making now?
• What evidence favors another pilot?
• What problems remain?
• What is explicitly not approved?
• What information must return before action?

If readers answer “approve rollout next month,” the rewrite failed regardless of grammar.