{"id":2392,"date":"2026-11-18T01:30:00","date_gmt":"2026-11-18T01:30:00","guid":{"rendered":"https:\/\/freepostfinder.com\/blog\/?p=2392"},"modified":"2026-11-18T01:30:00","modified_gmt":"2026-11-18T01:30:00","slug":"four-ways-to-decline-a-pitch-politely-compared-side-by-side","status":"publish","type":"post","link":"https:\/\/freepostfinder.com\/blog\/four-ways-to-decline-a-pitch-politely-compared-side-by-side\/","title":{"rendered":"Four Ways to Decline a Pitch Politely, Compared Side by Side"},"content":{"rendered":"<p>If you run a blog, a newsletter or any publication that accepts outside writing, your inbox fills with pitches. Some are great, many are not quite right and a few are plainly off-topic. Knowing how to say no politely to a pitch is part of the job, and the style you choose changes how people remember you. Here is a friendly comparison of four common ways to decline, so you can choose whichever suits the message in front of you.<\/p>\n<h2>Option one: the short, plain decline<\/h2>\n<p>This is the one-liner: &#8220;Thanks for sending this. It isn&#8217;t a fit for us, so I&#8217;ll pass.&#8221; It is quick, honest and leaves no room for confusion. The sender knows where they stand within seconds and can move on to the next publication without waiting.<\/p>\n<p>The weakness is tone. Without a touch of warmth it can read as curt, particularly to a newer writer who spent days on the draft. If you favour this style, add one genuine sentence about what you noticed, such as a good opening or a clear structure. That small touch costs five seconds and changes the whole feel of the message.<\/p>\n<h2>Option two: the decline with a reason<\/h2>\n<p>Here you add why: &#8220;We&#8217;re focused on practical how-to pieces, and this one is more opinion.&#8221; People often appreciate a reason, because it tells them how to adjust a future pitch. Used well, it turns a rejection into a bit of guidance.<\/p>\n<p>The risk is that reasons invite debate. A sender may answer your reason with a rebuttal or a rewrite, and now you are in a longer conversation than you wanted. Keep the reason about fit, never about quality, and keep it to one sentence. &#8220;It doesn&#8217;t match our current topics&#8221; is safer than any critique of the writing.<\/p>\n<h2>Option three: the decline with an alternative<\/h2>\n<p>This is the friendliest option. You say no to the pitch as written and offer something else: a related angle you would consider, a later window when you review submissions, or a pointer toward a more suitable outlet. It leaves the sender with a next step instead of a closed door.<\/p>\n<p>It takes more effort, which is the trade-off. You need to know your own editorial gaps well enough to suggest them, and you must be sure you can honour the offer. Do not mention a later window unless you will really look at pitches then. An empty alternative is worse than none.<\/p>\n<h2>Option four: the silence<\/h2>\n<p>Plenty of people simply do not reply. It is understandable when volume is high, but it is the weakest choice, because the sender cannot tell whether the message arrived, got buried or was ignored. Many will follow up, which creates more work for you in the end.<\/p>\n<p>If volume really is overwhelming, a one-line auto-reply stating your policy on unsolicited pitches is better than silence. It sets expectations once and spares both sides a string of nudges.<\/p>\n<h2>Side-by-side: which one when?<\/h2>\n<ul>\n<li><strong>Pitch is off-topic:<\/strong> plain decline, with a kind line.<\/li>\n<li><strong>Pitch is close but not right:<\/strong> decline with a reason about fit.<\/li>\n<li><strong>Writer shows promise:<\/strong> decline with an alternative or a later invitation.<\/li>\n<li><strong>Pitch is spam:<\/strong> a policy auto-reply, or no reply at all.<\/li>\n<\/ul>\n<p>Whatever you choose, respond within a few days. A prompt, gentle refusal is remembered far more kindly than a perfect one that arrives a month late.<\/p>\n<h2>Helping people who hear no<\/h2>\n<p>You can make a decline more useful by pointing people to the places where they can publish more easily. A step-by-step <a href=\"https:\/\/freepostfinder.com\/blog\/how-to-create-and-publish-an-article-on-dev-community\/\">guide to getting a piece live on DEV<\/a>, or a separate <a href=\"https:\/\/freepostfinder.com\/blog\/how-to-create-an-account-and-publish-an-article-on-substack\/\">walkthrough for starting a Substack and sending out a first article<\/a>, gives a rejected writer somewhere to go straight away. That gesture turns your refusal into an act of help.<\/p>\n<h2>What about repeat senders?<\/h2>\n<p>Some people pitch you again and again with ideas that never fit. Being kind does not mean being endlessly available. After a couple of declines, a slightly firmer note is fair: say that their topics have not matched what you publish, and invite them to read a few recent pieces before writing again. That tells them exactly what to change and gives you a clear reason to hold your line the next time a similar message lands.<\/p>\n<h2>Keeping reference habits honest<\/h2>\n<p>One more habit is worth borrowing from careful reference sites. <a href=\"https:\/\/esimglobo.com\/\">An independent directory of connectivity providers<\/a> notes plainly that a listing based on a code assignment is not proof of a consumer product. Editors can apply the same caution: a polished pitch is not proof of a good article, and a plain no is not an insult.<\/p>\n<h2>My pick, and a template to steal<\/h2>\n<p>For most editors most of the time, the decline with an alternative wins, followed closely by the plain decline with warmth. Here is a template you can adapt: &#8220;Thank you for sending this, and for thinking of us. It isn&#8217;t right for our readers at the moment, so I&#8217;ll leave it there. If you&#8217;re open to a shorter piece on a practical topic, I&#8217;d be glad to read a pitch.&#8221;<\/p>\n<p>Keep a few such lines saved and adjust them for each message. The aim is not to sound polished; it is to be clear, quick and kind. Do that consistently and writers will keep sending you their best work, even when your answer on a given day is no.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Plain refusal, refusal with a reason, refusal with an alternative or silence? A friendly comparison of four ways editors can say no to pitches.<\/p>\n","protected":false},"author":2,"featured_media":2393,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[471],"tags":[],"class_list":["post-2392","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-content-marketing"],"_links":{"self":[{"href":"https:\/\/freepostfinder.com\/blog\/wp-json\/wp\/v2\/posts\/2392","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/freepostfinder.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/freepostfinder.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/freepostfinder.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/freepostfinder.com\/blog\/wp-json\/wp\/v2\/comments?post=2392"}],"version-history":[{"count":1,"href":"https:\/\/freepostfinder.com\/blog\/wp-json\/wp\/v2\/posts\/2392\/revisions"}],"predecessor-version":[{"id":2495,"href":"https:\/\/freepostfinder.com\/blog\/wp-json\/wp\/v2\/posts\/2392\/revisions\/2495"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/freepostfinder.com\/blog\/wp-json\/wp\/v2\/media\/2393"}],"wp:attachment":[{"href":"https:\/\/freepostfinder.com\/blog\/wp-json\/wp\/v2\/media?parent=2392"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/freepostfinder.com\/blog\/wp-json\/wp\/v2\/categories?post=2392"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/freepostfinder.com\/blog\/wp-json\/wp\/v2\/tags?post=2392"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}