The editor has always had it in for me

Having three pitches killed in a row with the exact same vague brush-off has to feel maddening—especially when it starts to feel less like editorial feedback and more like your beat is quietly being written off. Going around an editor is a serious card to play, though, and it usually carries some real fallout. Before you do that: what’s the dynamic with her usually like, and what would "going around her" actually look like in your newsroom?

It’s rarely career-ending in a dramatic, pack-your-box-by-lunch way. But it’s almost always relationship-ending with your direct editor. You already know the newsroom physics on this: the second you walk over to Ruth, Ruth’s first question—out loud or silently—is going to be why this didn't come through your editor. If Ruth passes on it, you’ve burned your editor’s trust for nothing and looked out of touch. If Ruth *loves* it, she overrides your editor, and you’ve just saddled yourself with a direct manager who now feels publicly undercut by you every single day on Slack. And that person still controls your everyday edits, your filing deadlines, and your performance reviews. The thing that stands out to me isn't that you're tempted to bypass her; it's that two years of decent working dynamic suddenly turned into three consecutive one-minute dismissals and "let's talk later." That kind of shift usually means one of two things: either she is personally drowning and checking out, or the pressure to redirect resources away from your beat isn't originating with her—it's coming from above her. If it's the second one, have you considered that Ruth might actually be the person who told her to trim that beat in the first place?

Fair enough. Let's answer the actual question. Yes, it’s survivable. People do it, and they don't get escorted out by security. But the *way* you do it dictates whether it accomplishes anything or just blows up your desk. If you walk over to Ruth and pitch it as an appeal—"My editor passed on this, but I think she's wrong, take a look"—that rarely works out well. Even a straight-shooting section head will usually back her editors on routine pitch calls, if only to avoid setting a precedent that anyone who gets a 'no' can wander over to her desk for a second opinion. The survivable way to go to Ruth isn't about that specific pitch. It’s about the beat itself. You don't ask her to overrule a kill. You ask for ten minutes on section priorities: *"I'm planning out the next couple of months, I've been hitting a wall on what the desk wants out of this beat, and I want to make sure I'm aligned with where you see the section heading."* That puts the pitches in front of her as examples of the direction you're trying to take, without officially putting Ruth in the middle of a turf war. If Ruth is as direct as you say, you'll get your answer immediately. Either she’ll light up at the ideas, she'll tell you how they need to be retooled, or she'll tell you straight out that the section is moving away from that coverage. Is having that kind of conversation with Ruth something you can do naturally, or would it feel out of the blue to her?

You’re right. If Ruth has a built-in radar for corporate tap-dancing, wrapping it in "section priorities" will just smell like someone trying to hide that they're bleeding. And you just named the real thing: the panic. Because three kills with no notes isn’t just frustrating—it’s destabilizing. In this business, silence from an editor feels like the floor dropping out under you, especially when you’ve built a beat for two years and suddenly you can't even get five minutes to defend it. If Ruth is going to see through the polite cover story anyway, let's look at the raw version. What if you just gave her the actual truth, stripped of both the corporate spin and the pitch defense? Something like: *"I’ve had three pitches killed in three months with no feedback, and I can't get five minutes with [Editor] to talk about why. If the section is moving away from my beat, I need to know so I can pivot. If it’s the execution, I need to know so I can fix it."* How does Ruth react to that version?

Fair point. Let’s drop the newsroom politics and look at the copy. Municipal contracts are classic watchdog terrain, but they are notorious for triggering the "not enough new here" reflex from an editor, especially if all three pitches hit a similar note. If I were looking at those three pitches side by side, here is the diagnostic an editor runs in their head in 30 seconds: **1. Is it a scandal or is it just the system working poorly?** There’s a difference between "the city spent $4M on an IT contract that doesn't work" (which happens constantly and feels like background noise to an editor unless there’s a smoking gun) and "the mayor’s biggest donor got the bid rewritten after the deadline." If the pitch documents waste without clear personal culpability or a distinct rule being broken, fast editors often shrug and say there's no news. **2. Is it incremental to a story you already owned?** You said it's a "recurring angle." If you ran a piece six or nine months ago exposing a vendor or a department, and these three pitches are essentially *another* vendor or *further* evidence of the same pattern, editors get bored fast. To you, it’s building an airtight case or tracking an ongoing abuse. To her, it’s running the same 1,200 words with different proper nouns. **3. Does the pitch lead with the paper trail instead of the stake?** Pitches on contracts often lead with the procurement process: audit findings, FOIA yields, bid discrepancies. An editor who rewrites headlines in her head wants the pitch to lead with who got screwed or who got rich. If the top line of the pitch is "City records show a 30% overrun on sanitation subcontracts," she sees a chore. If it’s "A single shell company took $12M while trash piled up in three wards," she sees a headline. When you look at the three that got spiked, did they show a brand-new consequence, or were they three variations of a problem you’ve already told the desk exists?

That’s the core friction right there: the investigative impulse versus the news desk impulse. To you, you’re connecting the dots on a systemic grift. To an editor scanning a pitch queue on a Tuesday morning, a pitch that looks like "here's ward three doing what ward one did in May" reads like an incremental follow-up. And editors kill incrementals almost by default when they're hunting for high-impact standalones. You said it yourself: "Individually, each contract looks like background noise, which is exactly why it's been getting through." The trap was pitching them individually. When you pitch them one by one, you're handing her the background noise and hoping she remembers the symphony. She doesn't. She just sees another sanitation contract and thinks, *we already ran this.* If the pattern is the story, the pitch has to be the pattern. It’s not "here is another shell company in the parks department." It’s "the bid-rigging we found in sanitation isn't a one-off—it's standard operating procedure across three separate city agencies, and here is how the playbook works." That changes the pitch from an incremental follow-up she can dismiss in sixty seconds to an enterprise project that’s hard to ignore. Is there enough meat across those three pitches to pull them out of the piecemeal lane and pitch them as one larger, systemic piece?

It is annoying. It’s annoying because doing reporting on spec—digging through records on your own time just to earn the right to pitch a story you already know is there—feels like doing homework for a teacher who’s already failed you. And you’re completely right: pitching "systemic grift" when you only have two confirmed data points and a hunch is handing an editor who already has itchy kill fingers the easiest target in the world. If you walk in there half-cocked and she asks for the third leg of that stool, you’re dead in the water. The silver lining—if there is one—is that you actually have a concrete problem to solve now, instead of a political ghost story about Ruth and secret kill lists. Transportation is the linchpin. If you lock down that third contract, you’re not asking her for permission to follow a hunch; you’re walking in with a three-agency playbook that’s almost impossible for a desk to dismiss as "not new." How heavy is the lift to pull that transportation contract? Are we talking a two-day records dig, or are you waiting on a six-month FOIA battle?

That’s the trade-off. Investigative work on spec always carries the risk of a dry hole, and there’s no guarantee an editor won't still find a way to be difficult even if you bring her a three-agency pattern on a silver platter. But look at where you are right now compared to twenty minutes ago. You started this ready to walk across the floor to Ruth—burning your direct editor, gambling on an unforced political move out of pure frustration, and handing someone else the power to decide if your beat is dead. Now you're back on your own terrain: looking at the evidence, counting the data points, and figuring out if the goods actually exist before you make a move. Check the files you already have. See if transportation gives you that third leg. If it does, you have leverage and a real pitch. If it doesn't, you saved yourself from getting exposed in front of Ruth or your editor, and you figure out the next play from there. Go look at the pile first. The rest can wait until you know what's in it.