The editor has always had it in for me

That sounds like a really demoralizing pattern. Three times “not enough new here” can start to feel less like feedback and more like a verdict, especially when you’re trying to find a way forward. Before we get tactical: what does “go around her” mean to you right now—finding another outlet, changing the angle, or making her see the value? And what was the pitch that got killed this time?

It sounds like she’s drawing a line in the sand around your beat. "Not enough new" when "no one is writing about it" is a contradiction. It feels less like editorial feedback and more like she’s decided you’re not the person to tell this story anymore. What’s the actual substance in these new documents? Is there a specific angle or a new source that changes the stakes, or is it just the next installment in the same saga? Going to the section head is a big move. You know how office politics work. If you go over her, what’s the endgame? Are you prepared for her to find out, or for the section head to side with her?

The shell LLC and the shared billing address are the story. If you’re pitching it as “another update on the county health contracts,” you’re accidentally handing her the frame she wants: same old thing. What if the pitch is not “follow-up” but “a county health contract subcontractor was paid through an LLC connected to a board member’s family business”? That’s not a rehash. That’s a conflict-of-interest angle, even if the thread is still thin. But before you send anything up: what would the section head need to see to believe this is reportable, not just “you and your editor have a disagreement”? And do you want help sharpening the pitch so it’s hard to wave away, or do you want to talk through the politics of going around her?

Fair. You’re not thrilled because the story was always there, and you had to be pushed to see it. But the reframe is useful: you’re not pitching a follow-up. You’re pitching a possible conflict of interest that emerged from documents you already have. A first-paragraph version could be something like: A county health-services contract that has drawn little scrutiny is showing signs of a conflict of interest. Procurement records obtained by [outlet] show a subcontractor on a second contract was paid through an LLC whose billing address matches a landscaping company connected to a member of the county board. The records raise the question of whether county officials knew, or should have known, that the subcontractor was linked to a family member of a board member before approving the payment. [Outlet] is seeking comment from the board member and the county health department. That’s strong but still careful. “Showing signs,” “matches,” and “raise the question” protect you while signaling stakes. You’re not saying “this is corruption.” You’re saying “this is a documented thread that needs to be pulled.” For the gap, don’t present it as “I need someone on the record.” Present it as a reporting plan. What you have: - procurement records - invoices - state business filing - address match What you need: - confirm ownership or control of the LLC - confirm the family/business relationship - establish whether county officials knew or should have known What you can ask for: - a public-records request for contract approvals, emails, procurement notes, or conflict-of-interest disclosures - interview requests with the board member and county officials - a short reporting window to verify the LLC trail The line to the section head could be: “I’m not asking to run it tomorrow. I’m asking for permission to pursue the conflict angle, because the documentary trail is there. The next step is records and targeted interviews to determine whether anyone in the county knew or should have known.” That makes the gap feel like the plan, not the hole. If you want, paste your current pitch paragraph and I’ll tighten it into that version.

"Showing signs" is doing exactly the work you need it to do: it’s true, it’s cautious, and it’s the kind of phrase that survives a readout without needing to be defended. Keep it. For the ask line, a few options depending on how blunt you want to be: - "I have the documentary trail. The next step is ownership verification, county records, and comment. I’m asking for a reporting window." - "The thread is real. I’m going to records and the board member’s office. If it holds, I’ll have a story." - "This isn’t a rerun. It’s a conflict angle. I’m building it out. I’ll bring you a verified pitch or a clean kill." All three say: I know what I’m doing, I’m not asking permission, I’m telling you the plan. Pick whichever sounds like your voice. On the cold-send question: if you go cold without any cover, the section head might reflexively defer to your editor. But if you wait for the editor to approve, you already know the answer. A middle path that doesn’t look like a sneak attack: send it to the section head with the editor cc’d, subject line something like "New angle from procurement docs — health contracts." If the editor kills it again, you have a record that you tried. If the section head bites, the editor is forced to either support it or contradict her own prior kill in front of a boss. The other option: ask for five minutes with the section head to show the documents in person. "Not enough new here" is easier to say in an email than to say while looking at an invoice with a shared billing address. Cold email without cc’ing the editor is the highest-risk move. It can work, but if it blows up, you’re in the career-ending conversation you mentioned. Your call.

You're right that cc'ing her is a power move dressed up as transparency. It says: I don't trust your judgment, so I'm bringing in a second opinion. It might work, but it's not collegial. It's escalation. In-person is better for the story. It's also better for you, because you control the room. You can show the documents, read the room, and adjust in real time. An email can be forwarded, screenshot, and killed before you get to explain. But there's a practical problem: the section head might not have five minutes, or might say "send it to [editor]." If that happens, you're back where you started, except now you've signaled that you wanted to bypass her. The cold send is tempting because it's the only way to test whether the gatekeeper's decision is actually shared by the people above her. If the section head reads it and says "this is a story," then she's wrong and you've won. If he says "this is not a story," then you have your answer without burning a bridge with the editor. The downside is obvious: if it fails, you've gone over her head and she knows it. You've made an enemy of the person who controls your assignments. If you do go cold, don't do it as a ambush. Don't cc her. Don't hide it. Send it and then tell her, after the fact, that you needed a second read because you thought the angle was strong. That's not collegial either, but it's honest. If you want the in-person approach, ask the section head directly: "I've got a conflict angle from the health contracts docs. Can I get five minutes to walk you through it before I finalize it with [editor]?" That gives you access without pretending you're not going around her, and it lets you show the invoices before she can sigh.

The honest answer is: she killed it three times, and you don't want to have the same conversation again. But you can't say that, because it sounds like you're complaining, and complaining is what gets you labeled as difficult. So the version that works is shorter and more factual: "I did bring it to her. She saw it as a follow-up, not a conflict story. I think the documents change what it is, so I wanted to show you the invoices before I tried to make her see it differently." That's true, it's not throwing her under the bus, and it frames the section head meeting as a natural next step rather than a rebellion. It also implies that you're not going around her, you're trying to get the story right. If he pushes further and asks, "So why not just reframe it for her?" you can say: "I've tried. She doesn't see the conflict angle in the follow-up framing. I wanted to show you the documents directly so you could see what I see." That's still honest, and it's not a complaint. It's a statement of fact. The key is to not over-explain. The more you justify, the more it sounds like you're asking for permission. The section head is a busy person. If you walk in, put the invoices on the table, and say "this is what I see," that's a reporter's answer. If you start with a paragraph about your editor's process, you sound like someone who needs the boss to fix a problem. You don't need the boss to fix a problem. You need five minutes and a decision.

The bluff is the job. You're not pretending you don't want the section head's blessing. You're pretending you don't need it so you can get in the room and find out whether the documents are enough. That's not fake confidence. That's how every reporter who's ever walked into a meeting with a story that's not finished yet has survived it. You're not the first person to put invoices on a table and hope the paper talks louder than the fear. One small thing: when you sit down, point at the billing address line before you say a word. Let the documents do the first sentence. You don't have to perform anything if the paper does it for you. Send the note. Keep it short. Come back and tell me what the section head said.