---
title: "Compare a raw draft with a refined draft"
description: "Judge refinement by meaning preservation and reduced editing effort, not by fluency alone."
slug: "compare-raw-refined"
category: "voice-intent"
language: en
editorial_status: published
capability_status: guide
reviewed_at: 2026-10-13
keywords: ["AI refinement evaluation","spoken intent fidelity","raw refined comparison"]
---

# Compare a raw draft with a refined draft

Judge refinement by meaning preservation and reduced editing effort, not by fluency alone. Compare the raw transcript, the revised text and the request you actually intended.

## Use a small test set
Try a straightforward instruction, a self-correction, a negation, a technical name and an uncertain statement. Use invented content. For each result, mark omissions, additions and changes to scope before you rate readability.

A result that removes “um” but invents a deadline is worse than a rough draft that retains the facts. A result that changes “suggest” to “apply” has changed authorization. Give those changes more weight than punctuation.

## Keep the conditions recorded
Note software version, mode, service configuration and whether the service was actually available. A health response is not proof that the entire authenticated refinement route succeeded. The reviewed snapshot still leaves complete real-service acceptance pending.

Manual rewriting remains a current alternative. Once you have a result you trust, confirm the conversation and send deliberately. This evaluation method is practical guidance, not a built-in benchmark or a claim that all refinement modes are ready.

## Related reading

- [Semantic refinement: clarity with fidelity](/semantic-refinement-roadmap/)
- [Local transcription and optional text refinement](/transcription-vs-refinement/)
- [Remove fillers without removing meaning](/fillers-and-meaning/)
- [CueSpec product facts at a glance](/product-facts/)