WP:BRD sounds like an error code until someone explains it: be bold, get reverted, then talk. It names the cycle that governs most disputed edits on Wikipedia, and it starts the moment somebody undoes a change you were confident was an improvement.
The instinct that follows is to put the edit straight back. Do that, and the page has entered an edit war: two accounts trading the same two versions of a sentence, each revert erasing the other's case instead of answering it. Wikipedia's bright line sits at three reverts on one page within twenty-four hours — cross it and a block is close to automatic, under a rule everyone calls WP:3RR. Long before that line, the second revert has already said something to everyone watching: neither side plans to explain, only to persist.
The next move is the part the acronym saves for last. Open the article's talk page, start a new section, and make the case in writing — the specific source, the sentence it supports, the guideline in play if one applies. A revert with no explanation attached carries little weight beyond the moment it happens. An editor who has never read the source can still restore it later, simply because the talk page shows one side arguing a position and the other side silent.
When nobody answers, or both sides keep arguing past each other, Wikipedia has a ladder built for exactly this. A third opinion brings in one previously uninvolved editor to read the dispute cold. A request for comment posts a neutral summary to a wider noticeboard and pulls in editors who have never touched the article before. Neither process asks who filed the original edit or who has the stronger claim to the subject; both exist to produce an answer that holds regardless of who argues longest.
Reverting past the point of discussion turns a content dispute into a behavioral one. The edit-warring noticeboard, WP:AN3, exists to end exactly that pattern, and its remedies land on conduct rather than on who was right. An administrator can block an account, restrict the page to established editors through semi-protection, or freeze it on whichever version happened to be live when someone finally intervened — an accident of timing, no more.
For anyone managing a page on someone else's behalf, this ladder matters more than the underlying disagreement usually suggests. A second revert reads to other editors as advocacy rather than correction, and advocacy invites the kind of scrutiny a subject's page can least afford: a protection log entry, a noticeboard thread carrying a client's name in its title, a version frozen mid-dispute that nobody has finished checking. Filing a sourced case on the talk page and waiting is slower. It is also the only version of this process that tends to leave the page in better shape than before the dispute started.
The cycle exists because no editor on Wikipedia outranks another enough to simply rule, and it treats persistence as evidence of nothing at all. A case made once, in writing, with a source attached, outlasts a dozen reverts nobody bothered to explain.
