The feature guide is the engine, not the dashboard
Most people treat the Words Their Way Feature Guide like a quick-reference chart. It isn't. It's a diagnostic engine that maps kids' misspellings onto phonological and orthographic patterns, and if you just skim it instead of actually using it, you're wasting the whole system. I've been running spelling inventories and feature analyses for years, and the difference between a decent spelling lesson and one that actually moves a kid forward usually comes down to whether you read the feature guide right or just guess from memory. At its core, the feature guide lists spelling patterns organized by stage — typically From Syllables and Affixes through Derivational Relations — and under each pattern it shows the expected sound-spelling correspondences. You take a child's spelling inventory results, sort each misspelling into the closest pattern category, and the pattern tells you what instruction to give next. It's basically pattern-based formative assessment, except most teachers treat it like a coloring sheet. Here's how I actually do it without losing my mind. First, I give the spelling inventory and keep the original misspellings exactly as written. No correcting them. Then I go through each word and ask: what pattern does this misspelling reveal? Not what pattern does the correct spelling have. The misspelling is the data point. A kid who spells "rain" as "rane" isn't failing at vowel teams — they're demonstrating they haven't yet mapped the long A sound to the "ai" pattern, but they do understand that a silent e can mark a vowel as long because they used it correctly elsewhere. That distinction matters when you're planning instruction.
The feature guide itself is organized so that each pattern column shows the phonetic pattern, common orthographic representations, and example words. Some versions include a column for common errors at each stage, which is useful but not comprehensive. I've found the printed version limiting because the error column is abbreviated. When I need something more thorough, I download the digital companion guides from the Words Their Way publisher site, though those change URL structures periodically and sometimes go offline for months at a time. The current download page is typically accessible through the main Words Their Way resources portal, but I'd recommend searching for the specific guide by ISBN rather than relying on bookmarked links since they get deprecated without notice. One thing that trips everyone up is the transition between stages. A kid might be solid at the Syllable Junctions stage but still make errors that look like Rhyme and Shape stage mistakes when you're not careful. I had a third grader last year who could spell "basket" and "winter" perfectly but would write "photo" as "foto" every single time. On paper, that looked like a simple vowel shortening error. But when I ran the feature analysis across his full inventory, I saw the pattern — he was applying a regular consonant substitution rule (f for ph) consistently across all his attempts, which meant he was actually operating at the within word pattern stage for digraphs but hadn't yet internalized the Greek-derived spelling convention for "ph." The feature guide column for "soft f / ph" showed the correct representation, but what I needed was the meta-linguistic note about Greek origins, which only appears in the Derivational Relations material. So I shifted my instruction from drilling the spelling to teaching him the word origin story, which is a completely different intervention than what the basic feature guide would have suggested. Another counter-intuitive thing about the feature guide: high-frequency words don't always fall where you expect. "Wednesday," " Colonel," "February" — these show up in inventories and kids will miss them in ways that look random, but they're not random. They're often indicator words for the syllable stress and morphology stages, not the phonics stage. A kid who spells "February" as "Febuary" is making a morphological error (breaking the root + suffix boundary wrong), not a phonological one. The feature guide will file that under the wrong category if you're not tracking the error type carefully. I keep a separate error log alongside the feature guide sort because the official categories don't always capture the nuance, especially with irregular high-frequency words that don't follow any recognizable pattern at the elementary level.
The biggest limitation of the feature guide is that it assumes you have a complete inventory to work from. If you're only looking at a few words or doing informal spelling checks, the pattern data is too thin to be reliable. I've seen teachers try to use the feature guide with just five or six words and end up prescribing the wrong instructional level because the sample size didn't capture the kid's actual developmental stage. Give at least twelve to fifteen inventory words across the full difficulty range before you start sorting into the guide. Anything less and you're mostly guessing. A second limitation is that the feature guide is stage-based, which works well for most kids but falls apart for bilingual learners or kids with specific phonological processing differences. I had a Spanish-speaking second grader whose misspellings looked like they placed him firmly in the letter name stage, but when I asked him to read his own writing, he was operating at least two stages ahead. His inventory scores were depressed because he was transferring Spanish phonological rules to English spelling — things like writing "desert" for "dessert" or substituting single consonants where English requires doubles. The feature guide had no column for L1 transfer errors, so I ended up cross-referencing with the bilingual edition's error pattern notes and building my own supplemental sorting sheet. If you're working with multilingual students, the standard feature guide alone will mislead you about their actual spelling development. For implementation, the workflow I use takes about twenty minutes per student for a full inventory-to-analysis cycle. Inventory takes eight to ten minutes, the sorting takes another ten, and writing up the instructional implications takes maybe three minutes if you're efficient. The bottleneck is always the sorting step, and the trick to speeding it up is memorizing the stage transition markers — specific error patterns that reliably indicate which stage a kid is in. Once you've done maybe thirty or forty inventories, you stop needing to look up every single pattern and you can sort most words by eye. That's when the feature guide stops being a reference document and starts being a thinking tool.
Get the Full Details
The digital version of the feature guide includes some interactive sorting tools that auto-categorize misspellings, which saves time but introduces a different risk: the algorithm can misclassify borderline cases that a human would catch on reflection. I've used the digital tool for the initial sort and then manually reviewed every word the system flagged as ambiguous. That hybrid approach cuts the sorting time roughly in half while preserving accuracy. The tradeoff is that you need to actually understand the patterns well enough to spot when the tool is wrong, which means the manual method isn't optional — it's the foundation the digital tool builds on top of. Bottom line: the feature guide is only as good as your inventory quality and your ability to distinguish between pattern errors and other types of errors. It won't diagnose dyslexia, it won't account for language background, and it won't replace actual phonics instruction. But used correctly with a solid inventory, it reliably points you toward the next teaching target without the guesswork that usually goes into spelling remediation. The kids who make the most progress are the ones where the teacher has actually done the feature analysis, not the ones who got extra worksheets.
