Answering Questions Online

For most TAs, the course forum (Piazza, Ed Discussion, Campuswire) and email take as much time as office hours, and reach more students. An answer you post is read by everyone with the same question, and an answer that contradicts another TA's confuses all of them. Online answers also have their own traps: students who post their whole solution, questions at 2 a.m. the night before a deadline, and the temptation to just give the fix. This page covers response times, consistent staff answers, hints that teach, code and privacy, and tone, with example replies.

Defaults that work. If you only take four things from this page:

Read the whole thread before you reply, including other TAs' answers.
One owner per thread, and one staff answer per question.
Reply with the next step, not the fix: ask what they tried, point to the place to look.
Keep solution code private. Make a code post private before you answer it.

Set expectations

Publish a response window and keep to it, for example "within one business day," with no replies late at night. Students get frustrated when nobody says what to expect. There is no research-backed "right" number; agree one as a staff.
Split forum duty by day or by assignment, so someone owns each day and nobody is on call all week.
Tell students where questions go: the forum for course content, private posts for personal matters and code, email only for what can't go on the forum.
Say whether staff will wait a little before answering, to give students a chance to answer each other.

Answering consistently

Read the whole thread first, including follow-ups and other TAs' replies.
Claim a thread before answering, so two TAs don't answer in parallel.
Don't contradict a teammate in public. Raise it in a staff-only comment or the staff channel, agree, then post one corrected answer.
Endorse good student answers instead of rewriting them. Correct a wrong student answer quickly and kindly. Every resolved question should end with an endorsed or staff answer.
Pin one FAQ thread per assignment, link to it from repeat questions, and unpin stale posts.
When a question reveals a bug in the assignment, stop answering it piecemeal. Tell the instructor, post one pinned clarification, and link it from every related thread. Your answer becomes part of the assignment.

Hints, not answers

Online it is tempting to just post the fix: it is faster, and the student is grateful. But the next three students with the same bug will copy it, and nobody learns to debug. Reply the way you would in office hours:

Ask what they expected, what happened, and what they tried.
Point to where to look: the test that fails, the lecture slide, the documentation.
Give the next step, not the last one.
Use question templates (error message, what you tried, which test fails) so posts arrive with enough to work with. Studies of CS forums find that questions showing the student's own problem-solving are the most common kind and go with better grades.

Code, privacy and anonymity

Never post full or partial solutions publicly. If a student posts their code publicly, make the post private before you answer.
Turn a useful private question into a public one, with the student's OK and without their code or name, so everyone benefits.
Anonymity: most forums let students be anonymous to classmates but not to staff. It lowers the cost of asking; in CS1 studies, women posted anonymously much more often than men, so the visible forum can look less diverse than the class really is. Don't treat the named posters as the whole class.
Grades, accommodations and personal matters never go in a public post, even in an answer.

Tone

Students already worry about looking unintelligent in public, and most never post at all. Thank them for asking, assume a good-faith effort, and never write "as stated in the spec." A pointer that sounds kind gets read: "Good question; the answer is in the spec's section 3, which is easy to miss."

Keeping it in its hours

Check the forum at set times rather than all day, and keep to your response window. Look at the forum weekly for patterns, such as a concept many students are missing, and pass them on to the instructor or into office hours. Keeping Your TA Hours in Check has more.

AI and the forum

Students now ask AI tools many questions they once posted. Forum traffic has dropped in some courses, and public Q&A sites saw sharp declines after ChatGPT. The questions that still reach the forum tend to be harder or about the course itself, so they deserve careful answers. If your course uses an AI assistant on the forum, a person should check its answers before students rely on them.

Example replies

A hint: "Good question. What does your function return when the list is empty? Try that case by hand, then look at the example from Tuesday's lecture. Post back what you find."
Endorsing, with a nudge: "Endorsed: this answer is right. One addition: the same issue shows up in part 3, so check there too."
A code post: "Thanks for sharing your code. I've made this post private so nobody else sees solution code. The bug is in how you update count. Trace it by hand for the input [2, 2]. What do you expect, and what do you get?"
Making it public: "This is a great question others will have. OK if I repost a version without your code in the Homework 3 FAQ?"
A spec bug: "You're right, the spec and the starter tests disagree. Follow the tests. There's a pinned clarification here: [link]. Thanks for catching it."