Produce, revise and publish writing with technology, and update it in response to ongoing feedback and new information

Learning goal: Produce clear and coherent writing in which the development, organization and style are appropriate to task, purpose and audience. Develop and strengthen writing as needed by planning, revising, editing, rewriting or trying a new approach, focusing on addressing what is most significant for a specific purpose and audience, and editing for conventions with command of grades 11-12 Language standards 1-3. Use technology, including the Internet, to produce, publish and update individual or shared writing products in response to ongoing feedback, including new arguments or information.

The scenario this unit uses. Castlemere Regional Library is invented, and so is every number attached to it. Its board is deciding whether to stop charging overdue fines. The simulated sources are these. Budget sheet (audited): the system has 9 branches, 62,000 active cardholders and an annual budget of 8,000,000 dollars; fines brought in 48,000 dollars last year, which is 0.6 percent of the budget. Finance office estimate: staff time spent collecting and recording fines cost about 21,000 dollars, an estimate built from average minutes per transaction multiplied by wages, not from a time study. Circulation report: 7,400 of the 62,000 cards, about 12 percent, are blocked because the holder owes 10 dollars or more, and 4,440 of those 7,400 blocked cards, 60 percent, belong to cardholders under 18. Pilot report: two branches went fine-free for 12 months; their on-time return rate was 91 percent in the year before and 89 percent during the pilot, and 310 of their 820 blocked cards, about 38 percent, were reactivated. Staff survey: 54 of 80 staff responded; 36 favor ending fines, 12 oppose and 6 are unsure. Public comments: 212 comments were submitted; 131 favor ending fines and 81 oppose. Dunmore report: another invented library went fine-free and saw circulation rise 6 percent in the same year it added Sunday hours. None of this describes a real library, and the evidence supports more than one reasonable position.

Task, purpose and audience decide development, organization and style. The same evidence becomes different writing depending on the job. A 250-word letter to the editor of a local paper, a 900-word policy memo to the Castlemere board and a 60-second statement at a public meeting share a claim but differ in all three dimensions. Development is how much support each point gets: the memo explains the collection-cost estimate; the letter may simply say "the library estimates". Organization is order and signposting: a memo leads with the recommendation and uses headings; a letter builds to its point in paragraphs. Style is sentence length and word choice: the spoken statement uses shorter sentences and repeats its claim because listeners cannot reread.

Revision is about what is most significant. Revision is not the same as editing. Editing fixes conventions: spelling, punctuation, hyphenation, agreement. Revision changes what a piece says or how it is built. The standard asks writers to focus on "what is most significant for a specific purpose and audience", which means deciding which weakness most damages the piece and fixing that first. If a memo's recommendation is buried on page two, no amount of comma repair helps.

Five moves, chosen as needed. Planning sets claim, audience and structure. Revising reorders, adds or cuts. Editing fixes conventions. Rewriting drafts a section again from scratch when repair is not working. Trying a new approach changes the form: turning a narrative opening into a direct recommendation, or a list of reasons into a comparison table. Mature writers choose among these moves; they do not perform all five mechanically.

Technology for producing, publishing and updating. Shared documents let several writers draft, comment and track changes; version history lets a writer see what changed and restore an earlier version; comments tie feedback to exact sentences. Publishing online means the piece itself can be updated in place; print can only issue a correction, an erratum or a revised edition, because copies already distributed cannot change. That creates a responsibility. When a published piece is changed because of new information, a reader who saw the earlier version deserves to know. Common conventions are a dated update note at the top or bottom ("Updated October 12: this post now includes the pilot's return-rate data") and a correction note when an error is fixed. Silently changing a claim erases the record of what was said.

Ongoing feedback, including new arguments or information. Feedback is ongoing when it keeps arriving after publication: comments, replies, new data. The writer's task is to sort it: which comments offer a new argument (a reason the writer did not consider), which offer new information (a fact that changes the evidence), which point to a problem of clarity (a confusing passage, an unexplained term, a misleading heading), and which simply disagree without any of these. The first two can require a change in what the piece claims or answers, and only after the writer checks them: new information must be credible and must change what the piece claims, and a new argument must be relevant and not already answered. A clarity comment can require a change in how the piece says it. Plain disagreement requires no change. All feedback deserves reading.

A model of updating. A student, Theo, published a post on the school news site arguing that Castlemere should end fines. Its first version, written before the pilot report, said: "Ending fines costs the library almost nothing, and there is no evidence it causes people to return books late." Two days later the pilot report was published, showing on-time returns fell from 91 to 89 percent at the pilot branches. A commenter also raised a new argument: shared property creates shared responsibility, and fines are one way a community enforces it.

Theo's options were to ignore both, to delete the post, or to update. He updated. He replaced the sentence with: "Ending fines gives up revenue equal to about 0.6 percent of the library's budget. The two-branch pilot found on-time returns fell from 91 to 89 percent, a two-point decline whose practical effect a system-wide trial should measure." He added a paragraph answering the responsibility argument (replacement charges would keep a cost for lost items), and placed a dated note at the top: "Updated October 12, after publication, to include the pilot report and to respond to a reader's argument about responsibility. The original version stated that there was no evidence of late returns; the pilot shows a two-point decline in on-time returns."

Why this matters. The first claim, "no evidence", was a blanket statement: Theo had not seen the pilot report, and not finding evidence is not the same as there being none. A bounded version would have been accurate when written ("the sources I reviewed, the budget sheet and the circulation report, say nothing about return rates"), and the report then contradicted the blanket claim. Updating keeps the writing honest; the note keeps the writer accountable. Both depend on technology used deliberately.

Editing for conventions. Final editing applies the grades 11-12 Language standards: observe hyphenation conventions (a well-run pilot, but the pilot was well run; compounds ending in -free, such as fine-free, keep the hyphen in both positions in Chicago style), spell correctly, and make usage choices you could defend if challenged, consulting a usage reference where usage is contested.

Worked adaptation to task, purpose and audience: Evidence: fines raise 48,000 dollars (0.6 percent of the budget) and 7,400 cards are blocked. For the board memo: a heading "Recommendation" and one sentence stating it; then "Evidence" with both numbers and the collection-cost method. For a 250-word letter to the editor: open with a reader-level image ("A 15-year-old with a 10-dollar fine cannot borrow a book"), then the two numbers, then the claim. For a 60-second spoken statement: state the claim in the first sentence and again in the last, and use one number, not four, because listeners retain fewer figures.

Worked choice of revision move: A draft memo spends its first 300 words on the history of public libraries and states the recommendation in the last paragraph. The most significant problem for a board that reads memos quickly is that the recommendation is buried. Editing cannot fix it and revising sentence by sentence is slow, so the right move is a new approach: rewrite the memo in recommendation-first order and cut the history to one sentence.

Worked sorting of feedback: Comment A: "The pilot showed on-time returns fell to 89 percent." New information; once checked against the pilot report, it changes the evidence, so update. Comment B: "People should be responsible for what they borrow." New argument; it names a value the post did not address, and it is relevant and not yet answered, so add a response. Comment C: "This is a terrible idea." Disagreement with neither argument nor information; read it, but no update is required. Comment D: "'Almost nothing' compared with what?" Clarity feedback; the phrase is vague, not wrong, so give the figure and what it is measured against.

Worked update note: Weak: silently changing "no evidence" to "a two-point decline." Strong: "Updated October 12 to include the pilot report; the original version said there was no evidence of late returns." The strong note tells readers what changed and why, so the published record stays trustworthy.

Record of revision: Take a piece of your own writing longer than 500 words. In a shared document with version history turned on, make a planning note stating task, purpose and audience; then identify the single most significant weakness and name which move (revise, edit, rewrite or new approach) you will use for it. After revising, write a 3-row change log: what changed, why, and which feedback or new information caused it.

Independent performance: Publish a 400-600-word post in a class space that allows comments. Collect at least three pieces of feedback over several days and bring one piece of new information yourself. Update the post. Success criteria: development, organization and style appropriate to the stated task, purpose and audience; a revision that addresses the most significant weakness, not only surface errors; conventions edited to grades 11-12 standards; the update responds to at least one new argument or new piece of information; a dated update note says what changed and why; a 150-word reflection sorts the feedback into new argument, new information, clarity feedback and disagreement, and explains which items led to changes.