I used to burn my last-minute transfers on rumors, and it cost me more weeks than any bad pitch or unlucky toss combined. The fix was not finding a better news source. It was deciding, before the deadline, what kind of news would actually change my mind. The problem with incomplete team news is not the missing information itself. It is the gap between a rumor and a confirmed lineup. That gap fills with anxiety, and anxiety makes a sideways move feel like progress. A player tweets something vague, a local reporter posts a photo of a player stretching near the dressing room, and suddenly I am convinced I need to act. Most of the time, I did not need to act. I needed to wait. Here is the system I use now. The two-question filter I only make a late swap if I can answer two questions with something I can point to, not something I heard. First, who is the source, and have they been right about this team before? I keep a mental shortlist of three or four accounts that have a track record of getting lineup news correct for specific teams. If the information comes from someone outside that list, I treat it as unverified. If the answer is "some account with 800 followers" or "a forum post that says apparently," I stop. That is not news. That is noise with a clock on it. Second, if this news turns out to be wrong, how much does the swap actually hurt me? I write down the downside before I make the move. If I am dropping a locked-in starter who has played the last four matches to bring in a player who might get fifteen or twenty minutes off the bench, the maths is bad even if the rumor is true. The downside is clear, and the upside is usually a player who might get a single point. I also stop. The thirty-minute cutoff For a standard evening match, I stop checking lineups thirty minutes before the deadline. That sounds backwards, because that is often when the real news drops. But for me, the last thirty minutes are where panic lives. If I have not already decided my team is fine, I will talk myself into a bad move. I would rather miss one late lineup leak than make three rushed changes and undo a week of research. Pre-write your swap conditions The practical habit that changed things for me: I write down my planned swap before the rumor cycle starts. Not a mental note. A line in a notes app: "If Player X is benched, I bring in Player Y." That way, when the noise arrives, I am not making a decision under pressure. I am checking whether my pre-written condition was met. Most rumors will not meet it. Break the refresh cycle One more thing that helped: I stopped refreshing the same three accounts over and over. Repetition feels like research, but it is just anxiety wearing a different hat. I check once, confirm the source, then close the tab. My team does not get better because I watched the same vague tweet get quoted four times by different aggregators. What to skip entirely Do not make a swap based on a single training photo. Do not make a swap based on a journalist's "understands that" phrasing. Do not make a swap because a player posted a flight photo twelve hours before kickoff. These are all things I have fallen for. None of them are reliable lineup indicators. The goal is not to avoid all late news. It is to make sure a late swap is a response to verified information, not to the feeling that you should be doing something. If nothing changed except your heart rate, keep the team you built.