Save the draft detail first

A writing conference note should start with the student's draft, not the teacher's feeling about the draft. What did the student write, revise, add, remove, explain, or ask? That concrete detail makes the note useful later.

The WWC elementary writing guide emphasizes teaching students to use the writing process and strategies for planning, drafting, revising, and editing. A conference note should preserve where the student is inside that process.

Thin note: "Needs more detail."

Better note: "Added one reason after oral rehearsal, then reread the paragraph and added a second example after I asked what the reader still needed to know."

The better note shows the draft move, support, and next teaching possibility.

Record feedback and response together

A conference is not only what the teacher said. It is what the student did with the feedback. Save both pieces:

  • Feedback given.
  • Student response.
  • Next writing move.

Example:

"I asked Amina to choose the strongest detail from her planning page. She reread three ideas, circled one, and added it to the second paragraph."

Reading Rockets describes informal classroom-based assessment as a way to understand strengths and needs during instruction. A writing conference note is informal assessment when it tells you how the student responds to instruction.

Keep the note objective before polishing it

Writing notes can become vague quickly: strong voice, weak organization, not enough stamina. Those may be useful categories, but the note should show evidence.

Head Start guidance on objective observation notes asks educators to record what they see and hear before adding interpretation. For writing, that means naming the draft behavior.

Instead of "great revision," write:

"Moved the last sentence to the beginning after rereading the draft aloud."

That is a clear revision move. Later, you can describe it in report language.

Add one next conference target

The note should make the next conference easier. Add one next target:

  • Check whether the student rereads without a prompt.
  • Ask for one more example after the claim.
  • Watch whether oral rehearsal helps planning.
  • Review punctuation only after ideas are expanded.

The WWC data-use guide frames evidence as a tool for planning action. The next target turns a conference note into a teaching plan.

In Dodl Notes, save the note to the student history. Before the next writing block, reopen the thread and choose the target you want to watch.

Use notes for report-ready growth

Writing progress often shows up in small moves: a more specific detail, a clearer sequence, a stronger reread, or a student who can explain a revision choice. Save those moves when they happen.

Once a week, review the notes and ask:

  • What changed in the draft?
  • What support helped?
  • What can the student now try independently?
  • Which example would help a family understand growth?

Writing conference notes are useful when they connect draft evidence to the next writing decision.

Watch for transfer to the next draft

A student may revise successfully during a conference and still need support using the strategy later. That is normal. The note should help you check whether the conference move transfers to the next draft.

After the conference, add one follow-up target:

  • Uses oral rehearsal before starting.
  • Adds a second detail without prompting.
  • Rereads the paragraph before asking for help.
  • Moves a sentence for clearer sequence.
  • Uses feedback from the previous conference in a new piece.

This turns the note into a bridge between conferences. Instead of asking, "What should I talk about today?" you can ask, "Did the last strategy show up again?"

Dodl Notes can keep that history visible. The first note records the conference move. The next note records whether the student used it in a new setting. Over time, the student history can show growth in independence, not only growth in final drafts.

Save strengths as carefully as needs

Writing conference notes often focus on what to fix. Save strengths too. A specific strength can support a report comment, a family conversation, or the next writing goal.

Useful strength notes include:

  • Chose a precise verb after rereading.
  • Added dialogue after checking the mentor text.
  • Organized reasons before drafting.
  • Reread aloud and noticed a missing word.
  • Explained why one detail was stronger than another.

Those notes are not fluff. They show the student using writing behaviors that can be taught, named, and repeated. A balanced writing history helps you avoid report comments that only list needs.

Keep the note connected to the artifact

If the draft or work sample lives in a folder, the note should still explain why it matters. Write enough context that you can reopen the student history later and know which writing move the sample shows.

Do not let the checklist replace the note

Writing checklists are useful, but a checked box rarely tells the whole story. "Added detail" could mean the student copied a model, chose a detail independently, revised after peer feedback, or added an unrelated sentence. The note should explain the writing behavior behind the checklist item.

Try pairing the checklist language with one classroom action:

"Checklist: added detail. Note: reread the second paragraph, chose one detail from the planning page, and added it after the topic sentence."

That small addition makes the evidence more meaningful. It also helps when you need to write about growth. The report comment can say the student is beginning to use planning notes during revision because the conference note preserved that specific move.

Sources