Coming back to close a thread you started

You posted a question. People you have never met stopped what they were doing and tried to help. Three suggestions came in, you tried the second one, it worked, and you went back to your life. Perfectly natural. The thread, meanwhile, stays exactly where you left it: a question, three guesses and no ending.

That missing ending costs a few minutes to write, and it is one of the most useful things anyone can post in a community. Here is how we would go about coming back to a thread you started and leaving it finished.

Who the ending is really for

A thread has two audiences. The first is the handful of people who replied while it was fresh. The second is everyone who arrives afterwards, often from a search, with the same problem and no way to ask you anything. Over the life of a useful thread, that second group can easily outnumber the first.

Those later readers skim in a particular way. They read the question to check it matches their situation, then jump to the bottom to see how it turned out. If the bottom says nothing, they have to weigh three suggestions with no idea which one held up. Worse, the most recent reply can look like the answer simply because it came last.

The people who helped want to know too. Someone who spent ten minutes thinking about your problem has no other way of finding out whether they were right. Our piece on asking a question a community can answer warns against ending on “never mind, fixed it”. What follows is the longer version of what to write instead.

Post what worked, with the details that made it work

Start with the result, in the first line, so a skimmer cannot miss it. Then give enough detail that a stranger could repeat it. A closing post usually needs four things:

1. The outcome. Fixed, partly fixed, or decided against.
2. The exact change. The setting, the part, the quantity, the version. “I adjusted it a bit” helps nobody.
3. What did not help. A short list of dead ends can save the next person an evening.
4. Why you think it worked, if you have an idea, labelled as your guess.

Here is an invented example, for someone who asked why their sewing machine kept skipping stitches on stretchy fabric:

Solved, thanks all. It was the needle. I swapped the universal needle for a stretch needle, size 75, and the skipped stitches stopped on the first test seam. Changing the tension and rethreading made no difference for me. I think the universal needle was pushing the fabric aside instead of forming the stitch, but that is my guess, so take it as one.

Five sentences, and the next person with a skipping machine knows what to buy, what to skip and how far to trust the explanation.

Keep the scope honest as well. “This worked on my machine with this fabric” is a more useful claim than “this is the fix”. Someone on a different setup can then judge how far it applies.

Thank people so they can tell what they did

“Thanks everyone!” is friendly, and it is better than silence. But it does not tell anyone what their reply was worth. Specific thanks do, and they double as navigation, because they point later readers towards the replies that mattered.

• Name the person and the part. In our sewing thread, say, “Mara’s point about checking the needle type is what solved it” is worth more than a row of hearts.
• Credit the near misses. A suggestion that failed may still have ruled something out. “Sam’s rethreading idea did not fix it, but it told me the thread path was fine” is both kind and informative.
• Thank the people who asked you questions. A reply that only said “what fabric is it?” may have done the real work.

A warm sentence and a clear pointer will do.

Leave the question better than you found it

By the end of a thread you usually understand your problem better than you did when you wrote the question. Your title may even be wrong. “Machine eating my thread” might have turned out to be a needle problem on stretch fabric, and someone with that exact problem will never recognise it from the title.

Where a community lets you edit your opening post, a few small changes help a great deal:

• Add a line at the very top, such as “Update: solved, see the note below”, and link straight to your closing reply if you can.
• Add the words you know now. If you learned that the thing is called a “stretch needle”, put that term in, so search can find it.
• Correct details that turned out to be wrong, and say that you corrected them. Rewriting the question silently can make the early replies look confused when they were answering what you actually asked.

Keep the original wording readable underneath. Someone may arrive with the same misunderstanding you started with, and your first description is what they will recognise.

If you cannot edit, a closing reply that restates the question in better words does the same job. Guest replies here work that way: they can’t be changed afterwards, as the help page explains, and each one is read by a moderator before it appears. So take a moment to get your closing note right before you send it, and do not worry if it takes a little while to show up.

Closing a thread that did not end neatly

Plenty of threads have no tidy solution, and those deserve an ending too. A few honest versions:

• It never got solved. “I gave up and replaced the part” is still an outcome. So is “still happening, here is everything I ruled out”, which gives the next person a head start.
• It went away by itself. Say so, and mention anything that changed around that time. An unexplained fix is frustrating, but readers would still rather know.
• You chose something else. If you asked for a recommendation and bought a different one, say which and why. The reasons are often the useful part.
• It was your own mistake. The wrong file, the unplugged cable. People are most tempted to skip these, and readers are most glad to find them, because someone else has made the same mistake.

For discussion threads with no single answer, the closing post is more of a “here is what I took from this”. If it ran long, a short recap is a kindness, and our piece on summarising a long thread has a simple way to write one.

It is rarely too late

Perhaps you are reading this and remembering a question you asked last spring. You can still go back. Some places close old threads or discourage replying to them, so check the local habits first (ours are in the guidelines). Otherwise, a late note is usually welcome. Open with the delay so nobody is confused: “Coming back to this months later, in case it helps someone.” Then write the same closing post you would have written at the time, plus anything you learned from living with the fix.

That last part can be the most valuable of all. Very few threads say whether a solution still held up after six months. If yours does, it may be the most useful reply there.

A small habit makes all this easier: when a problem gets solved, go back before you close the tab, while the details are still in your head. Five sentences is plenty, and somebody you will never meet will be very glad of them.