Word Processing for Composition¶
Strategy · All strategies
Evidence · 1 claim (1 for) · 2 studies (2 quant-synthesis),q4· 2 of 2 report an effect size
Description¶
Word processing for composition integrates software-based writing tools (e.g., Google Docs, Microsoft Word) into writing instruction so that drafting, revising, and editing become fluid rather than laborious. Because text can be inserted, deleted, and reordered without recopying, students revise more and treat writing as a recursive process rather than a single-pass transcription task. The teacher's role shifts toward frequent, embedded feedback — often via comments and revision history — rather than feedback delivered only at the end of a polished draft.
Design Implications¶
Word processing lowers the mechanical cost of revision, which increases both the amount and quality of student writing, with the strongest effects for weaker writers [~M]. Its benefits depend on pairing the tool with process-oriented instruction — planning, drafting, revising cycles and substantive feedback — rather than simply substituting typing for handwriting [~M]. Feedback delivered as inline comments during drafting aligns with evidence that feedback is most effective when it addresses the task and the process rather than the person Feedback is most effective at task and process levels. [+S].
Context¶
Requirements¶
- Reliable access to devices and (for cloud tools) connectivity; a plan for students who lack home access
- Instruction in the tool itself — keyboarding fluency and basic formatting — so tool operation does not consume working memory needed for composing
- A revision-oriented writing routine (Practice with multiple drafts, teacher and peer feedback cycles, and authentic application tasks)
Constraints¶
- Keyboarding speed below roughly handwriting fluency can suppress composing quality; transcription skill must be taught first or the tool becomes a bottleneck [-M]
- Access to built-in spelling/grammar aids can encourage uncritical acceptance of suggestions and shallow editing if editing is not explicitly taught [-W]
- Auto-suggest and autocomplete features may reduce engagement with word choice and spelling for beginning spellers [~W]
- Distraction from notifications and open browser tabs degrades on-task writing time unless managed [-W]
Implementation Variability¶
- Cloud collaborative documents (Google Docs) enable real-time peer review and teacher conferencing within the draft
- Accessibility configurations — text-to-speech readback, dictation, adjustable fonts and spacing — support learners with dyslexia, dysgraphia, or low vision
- Scaffolded templates (graphic-organizer outlines embedded in the document) fade as students internalize text structures
- Version-history reflection — students annotate what they changed between drafts, making revision visible and assessable
Target Learners¶
- Struggling and low-achieving writers, who show the largest gains in length and quality when using word processing [~M]
- Students with dysgraphia or fine-motor difficulty, for whom transcription burden is the primary barrier
- Beginning writers whose keyboarding is not yet fluent may benefit less; handwriting may better support early letter formation and spelling [~W]
Target Learning Goals¶
- Composition quality: organization, elaboration, and coherence across drafts
- Revision and editing as recursive processes rather than one-time correction
- Writing fluency and volume
- Peer collaboration and response in the writing workshop
Instructions¶
- Verify keyboarding fluency; provide targeted typing practice before expecting compositional gains.
- Model planning and drafting in the tool itself, thinking aloud as you compose and revise.
- Have students draft, then exchange documents for structured peer comments tied to a rubric.
- Deliver teacher feedback as inline comments during drafting, focused on task and process levels Feedback is most effective at task and process levels. [+S].
- Require a revision pass that responds to feedback, using version history to document changes.
- Publish or present final texts for an authentic audience to complete the application cycle.
Related Strategies¶
- Process writing workshop — word processing is the natural medium for workshop's draft–conference–revise cycle
- Peer feedback protocols — shared documents make structured peer response actionable
Examples¶
- Google Docs in a writing workshop — a seventh-grade teacher comments on drafts in progress, holds sidebar conferences during writing time, and uses version history to grade revision effort rather than first-draft polish (Google Workspace for Education).
- Microsoft Word with Learning Tools — text-to-speech readback lets students hear their own drafts, catching omissions and awkward phrasing that silent rereading misses (Microsoft Learning Tools).
- WriteToLearn — automated formative feedback on student essays supports multiple revision cycles with immediate scoring (Pearson WriteToLearn).
Key Sources¶
- Morphy, P., & Graham, S. (2012). Word processing programs and weaker writers/readers: A meta-analysis of research findings. Reading and Writing, 25(3), 641-678. doi:10.1007/s11145-010-9292-5
- Graham, S., & Perin, D. (2007). Writing next: Effective strategies to improve writing of adolescents in middle and high schools. Alliance for Excellent Education.
- Bangert-Drowns, R. L. (1993). The word processor as an instructional tool: A meta-analysis of word processing in writing instruction. Review of Educational Research, 63(1), 69–93. doi:10.3102/00346543063001069
- Graham, S., & Sandmel, K. (2011). The process writing approach: A meta-analysis. The Journal of Educational Research, 104(6), 396–407. doi:10.1080/00220671.2010.488703
- Hattie, J., & Timperley, H. (2007). The power of feedback. Review of Educational Research, 77(1), 81–112. doi:10.3102/003465430298487
Page metadata
| Field | Value |
|---|---|
type |
strategy |
id |
word_processing_for_composition |
title |
Word Processing for Composition |
description |
Using word processing software to support drafting, revising, and feedback in writing instruction. |
status |
review |
generated |
by claude/unspecified on 2026-08-29 |
trust |
unverified — no one has confirmed this page's content |
Frontmatter is the page's machine-readable record — see the Schema & Guide.