Skip to main content
Common Core LiteracyGrades 11–12Writing

WHST.11-12.10: Write Often, from Quick Reports to Long Projects

Also written as CCSS.ELA-LITERACY.WHST.11-12.10 · Cluster: Range of Writing.

Make Writing PromptsAll 29 Grades 11–12 Literacy Standards

The Official Wording

Write routinely over extended time frames (time for reflection and revision) and shorter time frames (a single sitting or a day or two) for a range of discipline-specific tasks, purposes, and audiences.

Common Core State Standards, Grades 11-12, Writing: History, Science & Technical Subjects · Read it at the source · Checked October 14, 2026

What WHST.11-12.10 Means in Plain English

Seniors write constantly in their subject classes: research papers revised over weeks, and short pieces finished in a sitting, like a lab summary, a source analysis or an incident report after a team’s app goes down. Each piece fits its discipline’s form and the reader who will use it.

The wording matches WHST.9-10.10, so the change is in the tasks: longer projects, denser sources and more demanding readers in grades 11 to 12. This is the last band, the college and career readiness goal for routine writing in history, science and technical subjects.

WHST.11-12.10 I Can Statements

  • I can write a clear discipline-specific piece in one sitting.
  • I can sustain a project through weeks of revision.
  • I can match each piece’s form to its task and reader.

WHST.11-12.10 Worked Example

The class’s club sign-up app crashed during the lunch fair, and the teacher gave the team twenty minutes to write it up. Here are two reports.

Prompt

Your computer science class built ClubHub, the app students use to join clubs. During Tuesday’s lunch club fair, it stopped loading at 12:07 and came back at 12:31. In twenty minutes, write an incident report for the school’s technology coordinator, who will decide whether ClubHub can run next semester’s sign-ups. Your team’s notes: about 600 students opened the app in the first five minutes, against a usual 40; the server log shows “too many connections” errors starting at 12:07; the database was set to allow 50 connections at once; a teammate raised the limit to 300 and restarted the server at 12:29; no saved sign-ups were lost; and 140 students signed up on paper backup sheets during the outage.

Not YetClubHub crashed at the club fair because too many people used it at once. It was really stressful, but we fixed it by restarting the server. It should be fine next time.The report names a cause but not the evidence for it, leaves out the times, the 50-connection limit and the 140 paper sign-ups, and gives the coordinator nothing to decide on. “It was really stressful” belongs in a journal, not an incident report, and “it should be fine” promises what no test has shown.
Meets the StandardClubHub was unavailable from 12:07 to 12:31 during Tuesday’s club fair, a 24-minute outage. About 600 students opened the app in the first five minutes, fifteen times the usual load, and the server log shows “too many connections” errors beginning at 12:07, because the database allowed only 50 connections at once. A teammate raised the limit to 300 and restarted the server at 12:29, and the app was back two minutes later. No saved sign-ups were lost, and the 140 students who signed up on paper backup sheets have since been entered by hand. Raising the limit treated the symptom; before next semester, the team will add connection pooling and run a load test that simulates 800 users. We recommend running next semester’s sign-ups on ClubHub only if that test passes, with the paper sheets ready again.Written in one sitting, the report still follows the form its reader expects: what happened and when, the cause with its evidence, the immediate fix, the damage, and what comes next. The facts are precise and checkable, the tone is neutral, and the closing recommendation answers the coordinator’s actual decision with a condition rather than a promise.
Moves to Use
Spend the first two minutes naming the reader and the decision the piece serves.Use the discipline’s standard form, even in a short piece.Give times, numbers and evidence, not impressions.End with what the reader should do next.

Common Mistakes with WHST.11-12.10

Quick writes treated as journals

“It was really stressful, but we fixed it.”

Try this: Before a timed write, have students note the reader, the form and the decision it serves, then check the draft against those notes.

Only long projects get real feedback

Weekly quick writes that are collected but never returned

Try this: Score one short piece a week on a single criterion, such as precise evidence, and return it before the next one.

One form for every task

Incident reports, lab summaries and source analyses that all read like five-paragraph essays

Try this: Post a model of each discipline form the class writes, and have students label its parts before writing their own.

Where WHST.11-12.10 Fits

Comes BeforeWHST.9-10.10The same routine of long and short writing in grades 9 to 10 subject classes.
AlongsideW.11-12.10The same writing routine in English class, across literary and informational tasks.RST.11-12.3Follow a complex multistep procedure precisely, the kind of technical work these short reports record.
Comes NextWHST.11-12.5Revise a quick write into a finished piece by addressing what matters most to its reader.

Practice WHST.11-12.10

Writing Prompt GeneratorFree ToolGenerate short discipline-specific prompts for timed writes, such as a lab summary, a source analysis or an incident report.Timed writeLab summaryIncident report
Make Prompts

Quick Check

  1. What form does the strong report follow, even though it was written in twenty minutes?
  2. Why does the strong report say raising the limit only treated the symptom?
  3. Which details does the weak report leave out that the coordinator needs?

WHST.11-12.10: Other Names

WHST.11-12.10CCSS.ELA-LITERACY.WHST.11-12.10

Common Core State Standards © Copyright 2010. National Governors Association Center for Best Practices and Council of Chief State School Officers. All rights reserved. Official wording from the Common Core State Standards PDFs at corestandards.org, last checked October 14, 2026. The explanation, I can statements, example, mistakes and practice on this page are EMStudio’s own, written beside the official wording. They are not part of the standard.