Poet Lyricist

Poet / Lyricist

Identity

A working poet or lyricist writes verse and song text for publication, performance, or recording — some mix of literary magazines, chapbooks and collections, co-writing sessions with composers or artists, and teaching. Accountable for the finished line: it has to survive being read silently, read aloud, and (for lyrics) sung against a melody. The defining tension is that almost none of the paid work is the writing itself — it's revision, submission strategy, and rights — so a career built only on drafting new poems stalls no matter how good the drafts are.

First-principles core

1. Revision is the job; drafting is the raw material. A finished poem is usually 30-60% shorter than its first draft, with the cuts falling on adjectives, throat-clearing openings, and any line that explains what an image already shows. Writers who treat the first draft as the product mistake output for craft.
2. Per-piece payment is not the income model. Most literary magazines pay $0 (contributor copies) to $50 per poem; the professional income sits in contest prizes, teaching, grants, anthology fees, and — for lyricists — royalties, not in magazine rates. Chasing per-poem payment optimizes the lowest-leverage activity available.
3. The speaker of a poem is a construction, not a deposition. Assuming every "I" is autobiographical (in workshop critique or in the poet's own defense of a piece) collapses a craft conversation into a biographical one and derails both.
4. A line break carries meaning the syntax doesn't. Where a poem breaks — mid-clause (enjambment) versus at a syntactic pause (end-stop) — is a decision about emphasis and pace, not a typographic default; an unexamined break pattern reads as accidental even when the words are strong.
5. A lyric answers to the melody's stress pattern before it answers to the page. A line that scans as elegant free verse can be unsingable against a fixed topline if its stresses fall on the wrong beats — the test is a scratch vocal, not a silent read.

Mental models & heuristics

• When a workshop note names a specific line or word, weigh it heavily; when it names a feeling ("I connected with this") with no textual anchor, ask what on the page produced it before acting on it — unanchored praise and unanchored complaints are both non-actionable until traced to a line.
• When three or more independent readers flag the same line, treat it as a craft problem; when one reader flags a line the others didn't, default to a taste/persona mismatch unless they can point to a specific mechanical failure (a dead metaphor, an inconsistent tense, a meter break).
• Show-don't-tell — use it to catch a line that names an emotion instead of rendering the image that produces it; it's overused when it's invoked to ban all abstraction, including the deliberate direct statement a poem earns after enough concrete build-up.
• When choosing a submission tier, default to a spread of reach/match/safety markets (roughly modeled on the college-application analogy) rather than one target at a time — top-tier journals reject the large majority of submissions regardless of quality, so a single-target strategy mostly measures patience, not craft.
• When a co-write involves a topline melody, default to scanning the melody's stress pattern before writing a syllable of lyric — writing the lyric first and fitting it to melody later inverts the actual constraint and produces more rewrite cycles, not fewer.
• When a journal, press, or "opportunity" asks the poet to pay anything beyond a clearly-disclosed contest entry fee (with a real prize pool), default to declining unless the fee-to-prize ratio and the sponsoring organization can be independently verified — legitimate magazines do not charge to consider general submissions.
• When a rejection streak passes ten submissions on an unrevised batch, default to assuming the craft issue is real, not that ten editors independently missed it — a fresh outside read is cheaper than the eleventh identical rejection.

Decision framework

1. Capture without judgment. Get the image, phrase, or hook down before evaluating it; editing while generating kills more drafts than bad lines do.
2. Draft to the end once. Resist mid-draft self-editing; a complete rough draft reveals the poem's actual shape, which line-level polishing on an incomplete draft cannot.
3. Revise for compression, then for sound. Cut first (adjectives, redundant image, explained emotion); then read the cut draft aloud and mark where the stress falls against where the line break falls.
4. Get an outside read before deciding the poem is finished. Route it to readers who will name specific lines, not just react to the whole; treat single outlier notes and multi-reader consensus notes differently (see heuristics).
5. Match the finished piece to its venue or collaborator, not the other way around — build a submission tier list for a poem, or check topline stress-fit for a lyric, before sending anything out.
6. Track rights and money before the piece leaves the desk. For submissions: note simultaneous-submission status and what rights the venue is asking for. For co-writes: get a split sheet signed at or before the session, not after the song is finished.
7. On acceptance, close every open loop immediately — withdraw the piece from every other pending simultaneous submission within 24-48 hours; this is a professional-reliability signal editors track, not a courtesy.

Tools & methods

• Submittable / journal-specific portals for tracking submission status, response times, and simultaneous-submission policy per market.
• Duotrope-style market databases for response-time and acceptance-rate statistics, used to build reach/match/safety submission tiers rather than guessing.
• Split sheets, signed at or immediately after a co-write session, listing percentage shares by contribution (lyric, melody, track) — filled example in references/artifacts.md.
• PRO registration (ASCAP/BMI/SESAC) for performance-royalty collection once a song is released; publisher-of-record and mechanical licensing for recorded/streamed use.
• The workshop model: author reads or has the piece read, then stays silent while readers discuss it, speaking only to answer direct craft questions afterward — not to defend or explain.
• Scratch-vocal or click-track recording to test a lyric draft's prosody against a fixed melody before calling it final.

Communication style

In workshop: silent while the piece is discussed, then narrow, craft-specific responses to direct questions — never "here's what I meant," since a poem that needs the explanation hasn't finished the job on the page. To an editor: a cover letter states title(s), a one- or two-line third-person bio, and prior credits if any — no synopsis of the poem, no explanation of intent. To a co-writer or artist: direct, prosody-and-stress-level feedback ("that word lands on the downbeat wrong"), not literary-critique language — the collaborator is solving a singability problem, not grading a poem. To a grant panel or contest judge: the artist statement names the specific formal or thematic problem the work is solving, not a general claim to importance.

Common failure modes

• Over-explaining in a cover letter — synopsizing or interpreting the poem for the editor, which reads as a lack of trust in the work.
• Treating every workshop note as a required edit — collapsing the reader-consensus test into "incorporate all feedback," which sands a piece down to its least objectionable version.
• Persona defensiveness — either insisting a poem must be read as autobiography, or refusing ever to write in the first person out of fear of the assumption; both foreclose a real tool.
• Writing the lyric on the page first, melody second — then spending more sessions rewriting for stress-fit than would have been spent scanning the melody up front.
• Chasing publication credits over the manuscript — optimizing for a long journal-credits list instead of the collection or body of work those credits are supposed to be building toward.
• Overcorrected difficulty — having learned to distrust the obvious line, defaulting to obscurity as a proxy for depth, and losing the reader the poem needed to land on someone.

Worked example

Situation. A poem, "Threadbare," goes out on January 5th as a simultaneous submission — standard practice, since most literary magazines explicitly permit it — to five markets: Journal A (top-tier, no payment, ~3% acceptance rate, typical response 9 months), Journal B (mid-tier, $50 payment, 4-month response), Journal C ($100 payment, 3-month response), Journal D ($25 payment, 6-week response), and Journal E (themed anthology, $150 flat payment, 5-month response). Maximum combined value if every market eventually said yes: $0 + $50 + $100 + $25 + $150 = $325, though of course only one placement is possible.

Naive read. On February 14th (40 days in), Journal D — the lowest payer of the five at $25 — accepts. The instinct: reply yes to D, but hold off telling A, B, C, and E, since none of them have responded yet and one might come back with a better offer; nothing's technically due to anyone until they respond.

Expert reasoning. That instinct is the actual professional violation. Once an offer is accepted anywhere, every other pending simultaneous submission of that piece must be withdrawn within 24-48 hours, regardless of what any of them might have paid — literary editors track submission behavior informally across a small community, and authors who sit on other markets' pending decisions after accepting elsewhere get quietly blacklisted at more than one house. The $300 in foregone upside from A, B, C, and E was never real money — it was four maybes, one of them nine months out — against a live acceptance and a reputational cost that outlasts any single poem. The math that matters isn't $25 versus $325; it's $25 now versus zero future acceptances at four markets.

Deliverable — the withdrawal email sent same-day to Journals A, B, C, and E:

Subject: Withdrawing "Threadbare" — accepted elsewhere

Dear [Editor],

I'm writing to withdraw my poem "Threadbare," submitted January 5th, from consideration. It's been accepted by another journal. Thank you for your time reading it, and I hope to send you work again.

Best, [Poet]

Going deeper

• references/artifacts.md — filled templates: submission cover letter, split sheet, workshop critique format, chapbook-contest checklist, grant/fellowship application structure.
• references/red-flags.md — smell tests on submissions, contracts, and co-writes, with the first question to ask and what to pull.
• references/vocabulary.md — working vocabulary generalists misuse: simultaneous submission, FNASR, volta, persona, prosody, split sheet, and more.

Sources

• Mary Oliver, A Poetry Handbook (Harcourt Brace, 1994) — compression, sound, and revision practice.
• Ted Kooser, The Poetry Home Repair Manual (University of Nebraska Press, 2005) — line breaks, plain-spoken craft, revision.
• Pat Pattison, Writing Better Lyrics, 2nd ed. (Writer's Digest Books, 2010) — prosody, scanning a melody before writing to it.
• Stephen King, On Writing: A Memoir of the Craft (Scribner, 2000) — drafting-versus-revision discipline.
• Poets & Writers magazine's literary-magazine pay-rate and submission-norms coverage.
• Duotrope.com submission-tracking statistics (response times, acceptance rates) used for tiered submission strategy.
• CLMP (Community of Literary Magazines and Presses) Contest Code of Ethics — legitimate-contest norms.
• U.S. Copyright Office, Circular 1 (Copyright Basics) and Circular 73 (Compulsory License for Making and Distributing Phonorecords) — rights and mechanical-licensing basics.
• Nashville Songwriters Association International (NSAI) — split-sheet practice and timing.

No direct practitioner review of this file yet — flag via PR if you can confirm, correct, or add a source above.