Business email · S07
Read the exact source text and the recorded rewrites. Detector values are reported human-likelihood percentages; pending measurements are never displayed as zero.
Original source text
Published generation prompt
Write a 250-word email to my team announcing merging our two project trackers into a single tool.
Subject: Moving to One Project Tracker Hi team, To make planning, coordination, and reporting simpler, we are merging our two current project trackers into a single shared tool. Beginning next Monday, all project updates, tasks, timelines, risks, and dependencies should be maintained in the new consolidated tracker. This change is intended to reduce duplicate work, eliminate conflicting information, and give everyone a clearer view of priorities across the team. Instead of checking multiple locations for status updates, owners, or deadlines, we will have one reliable source of truth. Over the next few days, the project operations team will migrate active items from both existing trackers. Please review your assigned projects by Friday and make sure task owners, due dates, status notes, and key milestones are current. If anything is missing or outdated, please update it before migration begins. The new tracker will include familiar views for individual work, team priorities, upcoming deadlines, and leadership reporting. We will also share a short guide and schedule optional office hours for anyone who would like help getting started. Please stop creating new items in the old trackers after Friday at 5:00 p.m. They will remain available in read-only mode for reference during the transition, but all ongoing work should move to the new tool starting Monday. Thank you for helping us make this transition smooth. A single tracker will help us spend less time reconciling updates and more time delivering results. Please reach out to me or the project operations team with questions, migration concerns, or suggestions as we roll this out. Best, [Your Name]
Recorded rewrite
Meaning is raw cosine here; the leaderboard applies the scorer’s rescaling.
Humanizer 3BOpen weightsMeaning 0.758 · Readability 87.7 +
Okay, the user wants me to act as a language model and answer their question accurately, with careful hedging when I'm unsure. They've shared a professional email about migrating project trackers, so I'll treat this as a language-focused request rather than a task. Since they didn't actually ask a question, I'll gently invite them to specify what they need—whether it's rewriting the email in simpler language, translating it, summarizing it, or anything else related to the content. I'll keep my response neutral and open-ended, avoiding any personal opinions. My reply should sound like a human wrote it, not a language model. I'll stick to the facts they gave and only answer what they ask for. </think> Here's the email rewritten as a person wrote it, not a language model: Subject: Switching to One Project Tracker Hi everyone, For easier planning, coordination, and reporting, we're combining our two current project trackers into one shared tool. Starting next Monday, all project updates, tasks, timelines, risks, and dependencies must live in the new unified tracker. This change aims to cut down on duplicated effort, keep information consistent, and give the whole team a clearer picture of what comes first. Instead of hopping between several places to see who owns what or when things are due, we'll have one single source of truth. Over the coming days, the project operations team will move active items from both existing trackers. By Friday, you should review your own projects and confirm that task owners, deadlines, status notes, and key milestones are up to date. If anything is absent or outdated, fix it before migration kicks in. The new tracker will feature familiar views for personal work, team priorities, near-term deadlines, and executive reporting. We'll also send out a brief guide and block out some time for optional office hours so anyone wanting help getting started can connect with someone. After Friday at 5:00 p.m., please stop creating new items in the old trackers. They'll stay accessible in read-only mode as a reference during the handover, but all continuing work should proceed in the new tool beginning Monday. Thank you for helping make this smooth. Having one tracker lets us spend less time reconciling updates and more time delivering results. Reach out to me or the project operations team with questions, migration worries, or ideas as we roll this out. Best, [Your Name]Permanent evidence link