Five Common Mistakes When Asking Editors for Help, and How to Avoid Them

1. Sending the draft before knowing what you want from it

The most frequent mistake is also the quietest. A reader sends a finished piece, or half of one, with a note that says only "please have a look." An editor can look at a great many things: structure, opening lines, accuracy, tone, length, whether the idea suits a particular kind of magazine. Without a question, the review drifts toward whatever the reader happens to notice first, and the answer may not match the worry that prompted the request.

Before you write to us, spend ten minutes on a single sentence that begins, "What I most want to know is." It might be whether the idea is strong enough to pursue, whether the middle drags, or whether a walking route is realistic for a Saturday afternoon. That sentence shapes the whole exchange, and it costs nothing. I have watched reviews become twice as useful simply because the reader named one honest concern at the start.

• Write one sentence stating what you want to learn
• Name the audience you imagine for the piece or route
• Say what you have already tried and set aside

2. Treating a pitch as a finished article

A story pitch is a short argument for why a particular piece deserves space: the subject, the angle, why now, who it serves. Many readers send three thousand words and call it a pitch. The review then has to sort through prose to find an idea, and the idea is usually buried in the fourth paragraph.

Keep the pitch to a page. Say what the story is about in two sentences, then why a reader in Guelph or Moncton would care, then what you would need to gather to write it. If the idea cannot be stated that briefly, that is itself valuable to learn early. Our editors would rather help you sharpen a clear page than untangle a long draft that has not yet decided what it is.

3. Planning a local walking guide without walking it

A walking-guide plan built from a map and good intentions tends to fail on the ground. Distances that look short turn out to include a steep lane, a path closed for repairs, or a stretch with no bench and no shade. Readers over fifty, who make up much of our audience, notice these gaps first, and a guide that ignores them loses trust quickly.

Walk the route at least once at the pace a reader would, and note where you paused. Record surfaces, slopes, places to sit, and the nearest washroom. Then bring those notes to the plan, not just the stops you find charming. A plan grounded in what you actually experienced is easier to shape, and the editors can spend their time on order and wording rather than correcting basic facts.

• Walk it once at a relaxed pace before planning
• Note surfaces, slopes, seating and washrooms
• Check seasonal access, especially in mid autumn

4. Expecting a workshop to supply the habit

A writing workshop gives you structure, feedback and an hour of shared attention. It does not write the pages for you in between. Some readers arrive hoping the session itself will produce the discipline they have been missing, and leave mildly disappointed when the real work turns out to be what happens at the kitchen table afterward.

Treat the workshop as a push, not a cure. Decide beforehand how many minutes a day you can truly spare, and bring something to work on, even a messy page. People who arrive with a small, imperfect piece get far more from the discussion than those who come with only an ambition. Be honest about your time, and the workshop will fit around it instead of competing with it.

5. Skipping the practical details of ordering

Reader Services are arranged through the contact page, not bought on the site. You write to us, we reply in writing with a confirmation, and then an invoice follows, paid by bank transfer. Readers sometimes expect something instant and are surprised that a person answers first. That small pause is deliberate: it lets an editor confirm that the service suits what you described before any money moves.

Read the price list and the payment and refund policy before you write, so nothing in the exchange comes as a surprise. Include your name, the service you are interested in, and a few lines about your project. If you are unsure which service fits, say so and describe the problem instead. We would rather guide you toward the right one than receive an order that does not match your need.

• Write through the contact form with a short description
• Wait for the written confirmation before paying
• Pay the invoice by bank transfer, as the policy explains

6. Hoping for a verdict instead of a conversation

The last mistake is expecting a review to deliver a final judgment, a yes or no on your idea. Editors do not hold that power, and a thoughtful one will not pretend to. What a review offers is an informed reading: where the idea is clear, where it wobbles, and what you might try next.

Go in ready to disagree with some of it. Often the most useful comment is the one that annoys you slightly, because it points at something you half knew. Keep the notes, set them aside for a couple of days, and then return. Readers who treat feedback as the start of a conversation tend to make steady progress, while those who wait for approval often stall, no matter how kind the response was.

None of these mistakes is a failing of talent. They come from not knowing how the process works, which is easy to fix. Ask one clear question, keep a pitch short, walk the route, expect to do the work, read the ordering steps, and treat feedback as a conversation. Do that, and an editor's time goes much further. If you are unsure where to begin, write to us through the contact page and describe what you have.