Writing teachers often discover that a five-minute conference with a student produces more improvement than a page of written comments on the same essay. The student explains their thinking, the teacher asks a question, and suddenly the student understands what they need to revise. The immediacy and dialogue of a conference make feedback actionable in a way that written comments on a returned paper do not. The question every writing teacher asks next is: can I just do conferences and skip the written feedback?

The answer is that it depends on the students, the context, and the type of feedback. Some teachers have successfully replaced most written feedback with conferences. Others have tried and found that written feedback was still necessary. The research on this is limited, but teacher experience is clear: conferences work best when combined with strategic written feedback rather than as a complete replacement. The optimal system pairs brief written feedback with focused conferences, each doing the work it does best.

Written feedback is better for some purposes. If you need to communicate specific, detailed feedback about multiple issues, writing gives you space to do that and the student something to reference later. If you need to document feedback for grading purposes or to communicate with parents, written feedback creates a record. If you need to provide feedback on mechanical issues like comma placement or verb tense, writing allows you to show the exact location of the error. Conferences are better for other purposes. If you need to understand why a student made a particular writing choice, a conference lets you ask. If you need to help a student see the implications of their argument, talking through it together is faster than written suggestions.

Building an Efficient Conference System

• Use written feedback to point to specific locations of problems and to explain what needs to change; use conferences to understand why and to brainstorm how.
• Conduct conferences during class writing time or workshop periods rather than after school, which makes them accessible to all students regardless of transportation constraints.
• Keep conferences brief (three to five minutes per student) and focused on one or two major issues rather than trying to cover everything.
• Have the student talk first: ask them to explain their argument or their revision plan before you provide feedback, which reveals what they understand and do not understand.
• Take brief notes during conferences about what you discussed so you remember what feedback you gave and can follow up later.

Scaling Conferences With Large Classes

The biggest barrier to using conferences as primary feedback is class size. If you have 150 students and want to conference with each one for five minutes, that is 12.5 hours of conferencing per assignment. Not every teacher has that time. The solution is strategic selection: conference with students who need it most (those whose writing would benefit from dialogue) and use written feedback for students who can revise effectively from comments alone.

Another scaling strategy is peer conferences: train students to conference with each other about their writing. A peer conference is not as rich as a teacher conference, but it is better than no feedback, and it teaches students to think about writing critically by discussing it with others. A writing workshop where students spend 20 minutes conferencing with peers about their drafts gives every student feedback from multiple readers and frees the teacher to concentrate on a smaller number of one-on-one teacher-student conferences with students who need them most.

The goal is not to maximize conference time but to use feedback time efficiently. For some students and some writing, a quick written comment is sufficient. For others, a three-minute conference is transformative. The best systems use both, strategically deployed based on what each student needs to improve.