> For the complete documentation index, see [llms.txt](https://info.picturesup.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://info.picturesup.app/paperwork.md). # Paperwork and releases Paperwork is a production's documents and its talent releases. Releases are signed with a finger, on a phone on set or from an emailed link, and the signed copy is kept with the production and prints when you need it. ![The Paperwork tab](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FsIqqwiQzDrDP1r0VuIVs%2Fpaperwork.9f6672d5.png?alt=media) *Talent releases, documents and the release forms shared by every production.* ### Talent releases Each person on camera gets a release. The list shows who has signed, who has a link out, and who still needs one, with the date it is needed by. #### Adding someone 1. Choose "Add talent". 2. Enter their name, their email so the link can go to them, their role on this shoot, and the date it is needed by. 3. Pick the release form. The standard talent release is used until the studio makes its own. #### Getting it signed There are two ways. **By email.** "Send link" emails them a page that takes about a minute on a phone. The link works for 30 days. "Remind" sends it again. "Copy signing link" in the "⋯" menu gives you the link to send another way. **On set.** Open the production's [Shoot day](/shoot-day.md), go to Releases, hand over the phone and choose "Sign a release". It works without signal and syncs later. ![Signing on a phone](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FRcu9DnYf5N1QL26oVxgc%2Frelease-signing-phone.05d78123.png?alt=media) *The signing page: name, the release text, and a box to sign in.* The person reads the release, fills in their name and the form's fields, signs in the box, ticks that they agree, and chooses "Sign and save". #### The signed copy ![A signed release](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2Fs8oRkTp1K9ZqrCTP8dAk%2Frelease-signed.0ef6adf6.png?alt=media) *The release as it was signed, ready to print.* "View" opens the signed release: the text exactly as it was when signed, the details, the signature, and an audit footer with the date and time, whether it was signed on set or by link, the device, and a record number. "Print" prints it or saves a PDF. A signed release keeps its form and text for good. Editing the form later changes nothing already signed. Removing a release deletes the signed copy and its signature, so only do that on purpose. Unsigned releases appear on Home under Needs you, with a "Remind" button, and the Paperwork tab shows how many are still unsigned. ### Documents Contracts, permits, insurance and the brief live here, as an uploaded file up to 14 MB or a link. Each has a kind, a name, a status of Draft, Sent or Signed, and notes such as where the paper copy is. The "⋯" menu opens, downloads, changes the status, edits or removes it. Bigger files belong in Media, linked from here. ### Release forms Forms are shared by every production. "New form" or "Edit" opens the editor: * the form's name * the release text, in plain English, with "Insert" buttons for the studio name, the production, the client, the signer's name and the signing date * extra fields, up to 20, each text, email, phone, date or a tick box, required or not. Full name and the signature are always on the form. Forms already used can be edited; signed releases keep the text they were signed on. "Archive" retires a form you no longer use. The studio keeps at least one active form. ### Good to know * Admins and editors change paperwork. Viewers read it. Crew see the release list and its statuses only: no documents, no signed copies. * A signing link stops working when the release is signed or removed, or after 30 days. There is no way to switch a link off on its own before then. * Signatures made on set wait in the phone's browser until they sync. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://info.picturesup.app/paperwork.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.