sfwa.org

For game writers, a non-disclosure agreement (NDA) is typically the confidentiality layer wrapped around a work-for-hire contract: it keeps unreleased project details, scripts, and studio information private, while the work-for-hire terms determine who ends up owning the writing itself. The two documents do different jobs, and problems usually arise when writers treat the NDA as a formality and don't check how it interacts with ownership, portfolio rights, and the scope of what must stay secret. The SFWA (Science Fiction & Fantasy Writers Association) site addresses both sides of this in its "Writing for Hire" series, including John Dale Beety's article on NDAs for game writers and Josh Heath's piece on who owns the rights to the work.

What the NDA does in a work-for-hire deal

In a work-for-hire arrangement, the hiring company commissions writing and, under the contract, is treated as the author and owner of the delivered work. The NDA sits alongside that and covers information rather than authorship. In practice it usually asks the writer to:

• Keep unreleased game content, story bibles, character details, and internal studio communications confidential.
• Avoid disclosing the existence or nature of the project before the company's own announcement.
• Return or destroy confidential materials when the engagement ends.

The practical consequence for writers is that confidentiality can outlast the contract. Even after the work-for-hire relationship ends and the company owns the text, the NDA may still restrict what the writer can say about the project, which directly affects portfolio use and public credit.

Where the NDA and rights ownership collide

The ownership question and the confidentiality question are separate, and the SFWA coverage treats them that way. Ownership terms answer "who owns the words"; the NDA answers "what can I say about them." A writer can sign a clean work-for-hire agreement that assigns copyright to the studio and still be blocked from showing the work publicly by a broad NDA.

That is why the two documents should be read together. If the contract gives the company full rights but says nothing about credit or portfolio use, the NDA's confidentiality clause may effectively decide whether the writer can ever reference the project. Writers who want to list game credits or show samples should look for language in either document that permits disclosure of the writer's involvement after the game is announced, or that carves out portfolio use of published material.

Warning signs in an NDA

Beety's article flags NDAs that writers should hesitate to sign. The useful test is scope: a confidentiality agreement should protect the company's unreleased information, not restrict the writer's general ability to work or speak. Conditions worth questioning include:

• Open-ended secrecy with no end date. Confidentiality that never expires, or that covers information that becomes public through the company's own marketing, is broader than needed.
• Restrictions on future employment or work. An NDA is not a non-compete; language that limits where or for whom the writer can work afterward belongs in a different negotiation.
• Confidentiality that swallows the writer's own pre-existing material. If the writer brings in original concepts or prior work, the NDA should not be read to hand those over or lock them up.
• No carve-out for publicly available information. Once the game ships and details are public, the writer should not still be bound to silence about them.
• Vague definitions of "confidential information." Broad definitions can capture ordinary industry knowledge or the writer's own general skills.

A practical way to review the pair

Read the work-for-hire agreement first and note what it says about ownership, credit, and portfolio rights. Then read the NDA and check whether it undercuts any of those points. If the contract is silent on credit and the NDA forbids mentioning the project, the writer has effectively no public record of the work.

For writers weighing a specific offer, the SFWA articles on NDAs and on rights ownership are the place to start, since they describe the agreement types, rights, and limitations writers can expect when contracting with games companies. The decision rule is straightforward: sign when the NDA protects genuinely unreleased company information and leaves your ability to work, your pre-existing material, and your post-release credit intact; push back or ask for changes when it reaches beyond that.

SFWA is the Science Fiction & Fantasy Writers Association, a professional organization for authors working in science fiction, fantasy, and related genres. The domain sfwa.org is its official website, and the site serves as a public-facing hub for the organization's identity, its members' professional interests, and craft- and business-focused writing guidance. If you are a writer in these genres looking for a professional body, or a reader trying to understand what the site represents, the short answer is: sfwa.org is the home of a genre-writers' association, not a publisher, retailer, or literary agency.

What the Organization Is

The site identifies SFWA as "a professional organization for authors of science fiction, fantasy and related genres." Two things follow from that description:

• It is author-facing. The organization exists around the professional lives of writers, not around selling books or representing individual clients.
• Its scope is genre-based. Science fiction and fantasy are named explicitly, with "related genres" left open — a phrasing that keeps the organization's remit broader than two narrow categories.

The name and the domain line up directly: SFWA is the acronym, and sfwa.org is the site. That correspondence matters if you are checking whether a page you landed on is the organization's own site rather than a fan wiki, a convention page, or a third-party news outlet.

What the Website Covers

The homepage surfaces articles that show the kind of material the site publishes. The visible examples cluster around the working conditions of professional writers:

These are labeled under sections such as "Planetside | Writing for Hire" and "Planetside | Writing from Science," which suggests the site organizes content by the writer's situation — writing for hire versus writing informed by science — rather than by genre label alone. The practical takeaway is that sfwa.org publishes professional-development material about contracts, rights, and craft, not just announcements about the organization itself.

Who the Site Is For

Based on the organization's stated purpose and the content on the homepage, the site is relevant to:

• Genre writers — authors of science fiction, fantasy, and adjacent genres who want information on professional practice, including contract terms and rights.
• Writers considering work-for-hire — the game-writing articles address NDA terms and ownership of work, which are the questions that come up when contracting with companies.
• Readers and researchers — anyone verifying what SFWA is and what it publishes.

What the available material does not establish is membership pricing, eligibility rules, or login requirements. Those details are not described on the homepage excerpt, so treat any assumption that access is free or that membership is open as unverified until you check the site's own membership pages.

How to Use the Site

If you arrive at sfwa.org with a specific question, a workable approach is:

1. Identify your situation first. Are you researching a contract issue (NDAs, rights, work-for-hire) or looking for craft material? The section labels — "Writing for Hire" versus "Writing from Science" — map to those two needs.
2. Read the article that matches the situation. For contract questions, the NDA and rights-ownership pieces are the direct starting points; the NDA article explicitly covers warning signs for agreements you may not want to sign.
3. Verify organizational details on the site itself. For membership terms, dues, or access conditions, go to the organization's own pages rather than inferring from article content, since the homepage material does not state them.

The expected result of step 1 and 2 is a clearer picture of what a given contract term or craft problem involves; step 3 is where you confirm anything about the organization's structure or requirements.

Common Points of Confusion

• SFWA is not a publisher or agency. Nothing in the site's description indicates it sells books or represents authors; it is described as a professional organization.
• "Related genres" is deliberately broad. Do not assume the organization covers only hard science fiction or epic fantasy.
• Homepage articles are dated and rotating. The visible pieces carry 2026 dates, so the front page reflects current publishing activity rather than a fixed archive; older guidance may sit elsewhere on the site.
• Domain check is worth doing. Because the acronym is short, confirming you are on sfwa.org avoids confusing the organization's site with unrelated pages that discuss the same genres.

Fiction can give readers hope about climate change by showing believable people taking plausible action inside a changed world, rather than by denying the danger or ending on a rescue. The approach is explained in “Taking the Catastrophe Out of Climate Change: Using Fiction to Give Readers Hope” by Eowyn Scott, published on sfwa.org (Science Fiction & Fantasy Writers Association) on September 22, 2026. It suits writers of science fiction, fantasy, and related genres who want to address climate without leaving readers despairing — and readers who want to understand why some climate stories land as motivating rather than numbing.

The core mechanism: hope comes from agency, not from good news

Climate fiction often fails at hope for a structural reason. If the story's only possible outcomes are catastrophe or a technological rescue, the reader is a spectator to a verdict. Hope, by contrast, comes from watching a character make a choice that matters within limits that are not erased.

That means the writer keeps the physical reality of climate change intact — heat, displacement, loss — while giving characters something to decide. The hopeful note is not “it will be fine.” It is “this is what people did here, and it was worth doing.”

A concrete example of the distinction: a story about a coastal town facing sea-level rise can end with the town saved by an invented technology (rescue), with the town lost and the tone bleak (catastrophe), or with the town relocating and a character choosing what to carry and what to leave (agency). Only the third leaves the reader with a usable feeling.

Techniques for writing hope without softening the science

1. Scale the problem to the character's reach

Global climate is not a scene. Put the character inside one decision — a household, a neighborhood, a job — and let the larger system be visible at the edges. The reader feels the scale through implication rather than exposition.

2. Make the future specific and inhabited

Vague dystopia reads as warning; specific daily life reads as a place. Details of work, food, transport, and ritual in a changed climate do more for hope than any speech about resilience, because they imply people are still living.

3. Let solutions be partial and contested

A fix that solves everything removes the reader's role. A fix that works for some people and costs others something keeps the reader thinking — and thinking is where hope survives.

4. Avoid the two dead ends

• The rescue ending: an invention or authority arrives and removes the problem.
• The pure catastrophe: the point is that nothing could be done.

Both tell the reader their choices are irrelevant. The middle path — real loss plus real agency — is the one that leaves something behind.

5. Use hope as a craft decision, not a message

If characters exist to deliver a moral about climate, readers disengage. If they want things, fail at some of them, and keep going, the hope is carried by the story rather than announced by it.

What this kind of writing can do for readers

The practical takeaway: hope in climate fiction is a structural property of who gets to act and what their action costs. Write the changed world honestly, give one character a decision that matters, and let the ending show what was carried forward rather than what was cancelled.

Under a work-for-hire arrangement, the hiring game company—not the writer—typically owns the rights to the work produced. The SFWA article "Who Owns the Rights to the Work?" by Josh Heath (published September 29, 2026) explains that writing in the games industry often means work for hire, and that writers should understand the kinds of agreements, rights, and limitations they can expect when contracting with games companies. The practical takeaway: unless your contract says otherwise, assume the company holds the copyright and you retain no ownership stake in the delivered work.

What "Work-for-Hire" Means for Ownership

In a work-for-hire arrangement, the writer is commissioned to produce content, and the commissioning company is treated as the author for ownership purposes. That means:

• The company controls how the work is used, revised, published, and licensed.
• The writer generally cannot reuse, resell, or republish the delivered material.
• Credit and attribution terms depend entirely on what the contract specifies—ownership and credit are separate issues.

Because the SFWA source frames work-for-hire as the common model in games writing, the default assumption for a game writer should be that the company owns the output.

Rights and Limitations Writers May Encounter

The SFWA article notes that writers can expect a range of agreements, rights, and limitations when contracting with games companies. When reviewing a contract, look for clauses that address:

The SFWA piece is a general explainer of expected agreement types and limitations rather than a clause-by-clause checklist, so treat the table above as the set of questions to raise with the contract in hand.

What to Confirm Before Signing

The SFWA guidance points to confirming the agreement type and its limits before you commit. In practice:

1. Identify whether the contract is explicitly work-for-hire or a license. A license leaves ownership with you; work-for-hire transfers it.
2. Confirm what rights you are giving up and whether any reversion applies if the work is never used.
3. Check whether portfolio or sample use is permitted, since a full assignment can otherwise bar you from showing the work.
4. Get unclear terms clarified in writing before signing.

Related SFWA Resources

SFWA's Planetside "Writing for Hire" series covers adjacent contract topics. "NDAs for Game Writers" by John Dale Beety (October 13, 2026) explains how non-disclosure agreements apply to work-for-hire agreements for game writers and flags warning signs for NDAs you should not sign. If you are evaluating a games contract, the rights question and the NDA question usually arrive together, so review both.

For background on the organization itself, SFWA (sfwa.org) is a professional organization for authors of science fiction, fantasy, and related genres.