100 writing, publishing, and querying tips that actually survive revision

A lot of writing advice reads like it was assembled from a stack of vague sticky notes. "Be consistent." "Revise more." "Add stakes." Cool—now what? When your pages are messy, your POV is drifting, and your query underperforms, a philosophy won't fix it. You need concrete moves—revision passes that isolate one problem at a time, POV choices that stay locked, character wants that drive every scene—something that still works when you're tired and the draft still isn't cooperating.

So here are 100 conference-level tips—compressed into the parts that actually matter: revision passes, POV choices, character-first plotting, conflict that escalates, structure that moves, and query clarity built around protagonist wants and obstacles. No fluff. Just the work.

1-20: how to revise your manuscript in stages (so you don't "edit better" by vibes)

1. Give each revision draft one job. If everything is getting fixed at once, nothing gets fixed. 2. Start with story-first passes. Get cause-and-effect working before you polish sentences. 3. Stage two: evaluate idea/structure/characters/narrative thrust. Not "what I like," but "what the book does." 4. Stage three: continuity. Names, timelines, distances, promises—track them like you mean it. 5. Stage four: voice. Ask whether the narration sounds like the same person on every page. 6. Stage five: language. Clarity over cleverness; cut repetition; tighten confusing phrasing. 7. Stage six: grammar/spelling/punctuation. Do this last, or you'll break things you already fixed. 8. Make a revision checklist from your own recurring problems. If you always lose a character's motivation in the middle, that becomes a line item. 9. Use a "scene receipt" pass. Every scene must cash a promise: what changes, and why does the reader care? 10. Fix tense/person consistency early. It's annoying to discover this in the final proofread. 11. Mark unresolved threads. If you "forget" a dangling plot beat, the reader will remember it for you. 12. Resist random reshuffles. If you move a chapter, you must justify what new information it creates. 13. Do continuity before sentence-level edits. Otherwise you'll rewrite around a mistake you haven't corrected yet. 14. Read for "what the protagonist wants right now." If they stop wanting things in the middle, your middle stalls. 15. Trim what repeats the same emotional beat. Two scenes that deliver the same revelation are usually one scene with extra steps. 16. Scan for unclear pronouns. If "she" could refer to two people, the reader's brain spins. 17. Look for overwritten transitions. Replace "meanwhile/then/afterward" clutter with actual information. 18. Check scene goals vs chapter outcomes. The chapter ending should move forward (discovery, decision, revelation). 19. Keep a "known fixes" doc. When you revise again next month, you don't start from zero. 20. Stop when the draft is stable. "Perfect" is a liar. Stable is a publisher.

21-40: how to choose and limit POV in a novel (clarity is a craft decision, not a prayer)

21. Use third-person limited (when it fits). It keeps the narration inside the character's head. 22. One POV per scene. If the camera hops, the reader loses who they're inside. 23. Keep POV range tight across the book. The more you vary it, the more you invite confusion. 24. Align the main protagonist with the main POV character. If the POV isn't tracking your lead, the pitch-to-page translation breaks. 25. Name your POV rules in plain English. "This scene belongs to X; only X's knowledge counts." 26. Avoid "omniscient leakage." If the narration starts explaining what characters "should" feel, it's drifting. 27. Check access to information. Can the POV character realistically know what the narrative claims they know? 28. Watch internal monologue density. If every paragraph is thoughts, the scene becomes static. 29. Let actions contradict thoughts sometimes. That's character. But don't contradict without consequences. 30. Maintain voice consistency with POV. The POV character's worldview colors the prose. 31. Handle multi-POV like a schedule, not a mood. Readers need predictable entry points. 32. Use chapter openings to confirm POV. First lines should "lock in" who we're with. 33. Avoid empty POV swaps. If the alternate POV adds nothing new, it's just noise. 34. Make POV swaps justify plot timing. If the swap slows the engine, cut it or revise the placement. 35. Track cause-and-effect across POV. The reader should still feel the timeline, even if they're in different heads. 36. Use internal conflict in the POV character's head. External conflict happens in the world; internal conflict happens in the brain. 37. Keep a simple POV map for revision. Scenes, POV character, and what they learn. 38. If you're stuck, revise POV before anything else. Blurry POV makes every other edit feel pointless. 39. Don't overstuff your cast. More POVs means more tracking, more continuity risk. 40. Treat POV as part of story clarity, not style. Clarity is pitchable.

41-60: tips for character development and conflict (because engagement needs teeth)

41. Build the plot around character wants. If the protagonist doesn't want something specific, the stakes float. 42. Give the protagonist a concrete desire. Not "freedom." What does freedom look like for them this week? 43. Make obstacles personal. The "why" matters more than the "what." 44. Add conflict between allies. Friendly cooperation is great—right until it isn't. 45. Let characters face tough choices. No clean solutions; decisions should cost something. 46. Escalate believably. Each new problem should be the logical consequence of the last. 47. Avoid "reset" endings inside chapters. If chapter five undoes chapter four, the reader feels cheated. 48. Use external conflict for visible pressure. Threats, deadlines, pursuit, legal danger—whatever your genre uses. 49. Use internal conflict for emotional pressure. Fear, guilt, denial, desire colliding with reality. 50. Show growth through action, not speeches. When they change, what do they do differently? 51. Let competence create new danger. A capable character can still fail—because failure is a consequence, not an error. 52. Track promises characters make. Then pay them off later or break them with intent. 53. Use consequences to keep the engine running. Every victory should create a bigger bill. 54. Make the midpoint hurt. The story can pivot without comfort. 55. Don't rely on coincidence. If events land like "and then," the reader stops believing. 56. Let relationships strain under pressure. Pressure reveals the truth of alliances. 57. Cut emotional repetition. If the character cries about the same thing in five scenes, revise the structure. 58. Write the scene where the character can't avoid choosing. That's where the book becomes alive. 59. Use "what they want" as your internal compass during drafting. If you can't answer it, fix that before you write more. 60. End scenes with movement. Discovery, decision, revelation—anything that pushes forward.

61-80: pace and structure like you mean it (forward movement beats cliffhanger cosplay)

61. Use narrative time deliberately. Multi-POV work needs clear sequencing, not chaotic montage. 62. Confirm what the reader knows at each handoff. Don't spring information without purpose. 63. End chapters with forward motion. A chapter ending should create the next beat, not stall it. 64. Prefer "revelation that changes plans" over empty surprise. 65. Make suspense about believable worsening, not abstract dread. 66. If you rely on cliffhangers, earn them. A cliffhanger that delays resolution becomes a slog. 67. Use internal narrative thrust. Even in quiet scenes, something shifts in the character's plan. 68. Check your escalation curve. Are problems getting smaller in the last third? Fix that. 69. Balance setup and payoff within a few scenes. Long stretches of setup drain momentum. 70. Control viewpoint distance. If the prose becomes distant, the emotional connection weakens. 71. Make chapter goals match character goals. When those diverge, the scene feels off. 72. Trim "we're going there" exposition. Show what changes because the characters changed. 73. Use sensory specifics sparingly but consistently. Too much feels like wallpaper; too little feels like fog. 74. Watch for "time resumes here" traps. If you bounce in time, the reader needs clean signals. 75. In multi-POV, watch for repeated structural beats. Similar scenes across POVs can feel cloned. 76. Let your best scene do the most work. Don't waste it on a plot beat that should've been cut. 77. Don't bury the "why now." Readers need urgency that ties to the protagonist's desire. 78. Audit your middle. The muddy middle is usually "nothing changes" in the protagonist's plan. 79. When pacing drags, fix the turning points. Scenes aren't "slow," your story is waiting for permission to move. 80. Before you revise language, revise timing. When timing clicks, prose editing gets easier.

81-90: what to write in a query letter protagonist wants (and how obstacles drive plot clarity)

81. Open the query with the protagonist's name and what they want. No mystery meat. 82. Make the biggest query-letter problem plot clarity. Specifically: want + what stops them. 83. Write the query like a chain of decisions. Desire leads to choice; choice triggers the next problem. 84. State obstacles as active forces, not background noise. Who/what blocks the protagonist's plan right now? 85. Don't hide the ending. Agents need enough plot to judge outcome and pacing. 86. Align query language with the synopsis logic. If the query says "X solves everything," the synopsis better follow. 87. Keep stakes readable. The reader should immediately understand what's at risk for the protagonist. 88. Use concrete phrasing for motivation. "They need to be brave" is vague; "they can't protect their sibling unless…" is pitchable. 89. If a draft query feels flat, check the protagonist's want. Most "boring queries" are missing desire specificity. 90. Write a clean through-line from page one to last beat. Your query can be short, but it can't be vague.

91-100: how to pitch your work to agents effectively (and keep collaboration from melting your brain)

91. Pitch the book you wrote, not the version you wish you wrote. 92. Emphasize what the protagonist wants and why it matters now. Everything else is support. 93. Keep your "why this genre" explanation tight. Show competence through specifics, not lectures. 94. Match your comps to actual reading experiences. If a comp is only similar by theme, it's weaker than you think. 95. Tailor query details to what the agent requests. That's not begging; it's respecting their time. 96. If you get feedback, separate "taste" from "truth." Taste opinions are debate; structural issues are repair. 97. Plan for multiple rounds of edits. Collaboration is revision, not one miracle pass. 98. Work with reputable objective professionals. You want feedback that's consistent, not random. 99. Communicate shared goals. If you disagree about the target outcome, you'll bleed time. 100. Treat writing as a sustainable life practice. Consistency matters—but permission to stop when you're not productive matters too.

Frequently asked questions

The bottom line

If your draft can't answer "what does the protagonist want, right now?" then the query will suffer and the revision will feel endless. Fix the stages, lock the POV, make the conflict earn its escalation, and let the stakes do the talking.