The first-collab paperwork checklist: every document, in the order you'll actually need it

Somewhere between "we should shoot something together" and the actual shoot day, there's a stack of paperwork that has to get done — and nobody hands new creators the list. Platforms gesture at it with a tick-box. Forums argue about fragments of it. Meanwhile the actual stack is knowable, finite, and has a correct order, and once you've run it a few times it takes less effort than picking the outfit.

This post is the whole list, in shoot-chronological order: what to handle before you even reply to the DM, the agreement, the releases, the records, the day-of sequence, and what happens after. It's the system I built before my first collab and still use for every scene. I didn't invent it from industry experience — I'm about a year into self-producing — I built it from years of reading and writing contracts in a different field, plus running businesses before this one, where "get it in writing before the work starts" was already the house rule.

The disclaimer first, because this post needs it: I'm not a lawyer. Nothing here is legal advice. Requirements vary by where you live and where your collaborator lives, and the records law in particular carries real penalties. Use this as the map of which documents exist and when they happen; have a lawyer in your jurisdiction look at the documents themselves.

Each layer below gets a short version here and a deep dive in its own post. This is the hub. Bookmark this one, branch out as each layer becomes the thing you're staring at.

Before you even DM back: verification

The paperwork process starts before any paperwork exists, because every document downstream depends on knowing who you're actually dealing with. Before I commit to a scene with someone new, three things have to be true:

• Their identity verifies. Live video call, a real professional footprint, references I can actually contact — not just a profile that DM'd me.
• They can produce government-issued ID. Not on shoot day as a surprise — confirmed up front, because the records layer below is built on it.
• They have, or will have, an in-date STI test. Standard panel, recent enough to mean something on the shoot date, and we exchange results before anyone travels.

That's the compressed version. The full vetting checklist — green flags, red flags, the non-negotiables, how I read a cold inquiry — is its own post: how I pick collaborators. Read that one before your first yes. The short rule for this post's purposes: if any of those three can't happen, there is no scene, and therefore no paperwork problem to solve.

The reason verification leads the checklist instead of living beside it: every document below has their legal name and date of birth on it. If you can't verify who they are, you can't fill out a single form truthfully — which tells you the paperwork isn't a formality. It's a forcing function.

Layer one: the agreement

Once you're both in, the first actual document is the agreement — a model agreement, or for an unpaid collab, a content trade agreement. This is the document that answers the questions people otherwise settle by assumption and later by argument:

• Who owns what. Does each of you own the footage from your own cameras? Joint ownership of everything? One owner with a license to the other? Any of these can work. Not writing it down is the only wrong answer.
• Where it can go. Which platforms, paid or free, clips or full scenes, promo use, whether either of you can license it to a third party later.
• What happens if someone leaves. If one of you quits the industry or wants the scene pulled, what's the process? Agree on that while you still like each other.

For a money-changes-hands shoot, that's a model agreement with rates and deliverables in it. For the far more common first-collab shape — no money, both of you shoot, both of you post — it's a content trade agreement, and I wrote a whole post on what a content trade agreement needs to cover, because "we'll both just post it" is the handshake deal that produces the most fights I read about.

One more thing at this layer, and it matters more every month: if the paperwork comes from the other side — a studio, an agency, a third-party producer, anyone with their own boilerplate — read it for the AI clause before you sign. The language that grants someone a perpetual right to your likeness, voice, and "derivatives thereof" hides in otherwise boring sections, and I broke down exactly what it looks like in the AI-clauses post. Between two independent creators using shared templates, this is a quick check. With anyone else's paperwork, it's the first thing I read. (Again: I'm not a lawyer — if a contract someone hands you has language you can't confidently paraphrase, pay a professional to read it before you sign.)

Layer two: the releases

The agreement says what you've both decided. The model release is the document that makes it usable: the person on camera grants the person publishing the right to use their image and likeness in the content.

The part new creators miss: in a collab, releases go both directions. You appear in their footage, so you sign a release for them. They appear in yours, so they sign one for you. Two documents, mirrored, even if the terms are identical. One signed release covering "the content" is ambiguous about whose publication it authorizes — and ambiguity is the thing this entire stack exists to remove.

The other thing new creators miss: the platform tick-box is not a release. When OnlyFans or any other platform makes you add a tagged collaborator and the other person taps "approve," that satisfies the platform's compliance process for that upload, on that platform, for as long as both accounts exist. It does not give you a standing, documented right to the content across platforms, re-edits, promo cuts, or the day one of you deletes an account. I wrote up the full comparison — what the tick-box actually covers versus what a real release covers — in the OnlyFans release form vs. model release post. The short version: do the platform flow because you have to, and sign a real release because the platform flow isn't one.

I'm not a lawyer, so take the framing rather than the law from me — but the operator's logic here is the same one I used in business before this: a right you can't produce a signed document for is a right you don't have when it matters.

Layer three: the records

The third layer is the one with a statute attached: 18 U.S.C. §2257 records. If you produce sexually explicit content in the U.S., you're required to keep records proving every performer was an adult — a copy of the government-issued ID, the legal name, date of birth, the names they perform under, organized and retrievable the way the regulation specifies.

Like the releases, 2257 runs both directions in a collab. You're a producer of your edit, so you keep a records file on them. They're a producer of theirs, so they keep one on you. Bring a copy of your own ID for their file; expect theirs for yours. A collaborator who hesitates at this exchange is telling you something — this is the least optional document in the stack.

The full mechanics — who counts as a producer, what the file contains, the custodian statement, how long you keep it — are in the 2257-for-solo-creators post. And this is where the disclaimer earns a restate with feeling: I'm not a lawyer, and 2257 is federal law with criminal penalties. My post and this checklist tell you the document exists and where it sits in the sequence. A lawyer tells you whether your records would survive an inspection. Those aren't the same service.

Shoot day: the order of operations

Everything above can — and mostly should — happen before anybody travels. Shoot day has its own sequence, and one rule sits over all of it:

Every signature happens before anyone undresses.

Not "we'll sign after, the light's good right now." Not "we're friends, it's fine." The entire value of consent paperwork is that it's executed while everyone is dressed, comfortable, and free to walk out the door at zero cost. A release signed after the scene is a release signed by someone who already can't unwind their position. Paper first. The light will survive.

So the day-of order looks like this:

1. IDs out, records exchanged. Physically check the ID matches the person, copies into each 2257 file, both directions. Two minutes.
2. Sign anything not already signed. Agreement and both releases — ideally executed in advance, re-confirmed now. Witness each other's signatures.
3. The boundaries conversation, documented. Talk through what's in the scene, what's out, safewords or stop-signals, anything either of you won't do today regardless of what was discussed three weeks ago. Then write the conclusions down — a boundaries page, a scene outline both of you initial. A boundary that lives only in conversation is a memory test. ("Today's no overrides last month's yes" is the whole spirit of it.)
4. If kink is involved, a written consent document. Any impact, restraint, breath play, D/s dynamics, or anything else in that family gets its own signed consent doc — listed activities, listed limits, the agreed signals, the conditions for stopping. The free generators at /tools include a BDSM consent form alongside the release, agreement, and 2257 templates, all browser-only.
5. Then, and only then, the shoot. Which has its own whole anatomy — the prep, the blocking, the unglamorous 95% — that I walked through in what actually goes into a scene.

If the order feels ceremonial, good — ceremony is the point. Running it the same way every time makes it impersonal, and impersonal is what lets you hand a clipboard to someone you're excited to work with without it feeling like an accusation.

After the shoot: closing the loop

The stack isn't done when the cameras stop. Three tasks close it out, and they're easiest within a day or two while everything's still in one bag:

• File the records. Your 2257 file gets their ID copy and documents; signed originals or countersigned PDFs of the agreement and releases go into your records system — backed up, findable in five years, not a camera-roll photo of a page on a hotel bed.
• Exchange copies. They get fully executed copies of everything they signed and everything you signed for them. Both sides hold a complete set. Lopsided paperwork breeds exactly the disputes the paperwork was for.
• Complete the tagged-collaborator flow on every platform, before publishing. Whatever each platform calls it — tagged collaborator, release form, co-author approval — both of you finish it on every platform where the content will appear. It's not a substitute for your release; it is a requirement of the platform's rules, and skipping it is how finished content gets stuck in review or taken down.

Then you're done — actually done, with a documented scene that can survive a platform dispute, a falling-out, or a records inspection. That's the entire reason the stack exists.

The condensed checklist

The copy-paste version. Everything above, one screen:

Before you commit

• [ ] Identity verified (live video + footprint + references)
• [ ] Government-issued ID confirmed available, both sides
• [ ] In-date STI test agreed and results exchanged

The documents (before shoot day if possible)

• [ ] Model agreement or content trade agreement signed — ownership, platforms, exit terms
• [ ] Third-party paperwork checked for AI/likeness clauses before signing
• [ ] Model release signed: them → you
• [ ] Model release signed: you → them

Shoot day, in order

• [ ] IDs physically checked; copies exchanged for both 2257 files
• [ ] All outstanding signatures executed — before anyone undresses
• [ ] Boundaries/limits conversation held and documented
• [ ] Written kink consent doc signed, if applicable
• [ ] Shoot

After

• [ ] 2257 records filed, both directions
• [ ] Fully executed copies of everything exchanged
• [ ] Tagged-collaborator / release flow completed on every platform before publishing
• [ ] Originals backed up somewhere you'll find them in five years

All four core documents — model release, model agreement, 2257 records, and the BDSM consent form — have free, browser-only generators at /tools; nothing you type leaves your device, and the story behind them is in the announcement post.

Last restate, because it's the honest frame for everything here: I'm not a lawyer. This checklist is process, not legal advice — it's the order of operations that running businesses before this one taught me to never skip. The documents themselves deserve a professional read in your jurisdiction at least once, before the first scene. After that, the system mostly runs itself — and the paperwork stops being the scary part of the collab and becomes the boring part, which is exactly what it should be.

— Sly