> 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/productions/gear.md). # Gear Gear has two levels. The studio library under Gear in the sidebar is everything the studio owns, in packages and cases, with a QR label on each. A production's Gear tab is what goes on this shoot: company gear from the library, the kit crew bring, and rentals, with a dock that tracks the list from draft to returned. ### The studio library ![The Gear library](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2F6GUTc44nTZOKmnGjuShu%2Fgear-library.33d6f286.png?alt=media) *Gear by category, in a grid. List and Packages are the other views.* Items sit in categories: Camera, Lenses, Lighting, Grip, Sound, Power, Media and Support to start with, plus any you add with "+ Category". Each shows its status: Available, In repair, Retired, or Out with the production that has it. #### Adding gear 1. Choose "Add gear". A photo helps; a phone shot is fine. Catalogue photos come later. 2. Enter the name. As you type, the sheet suggests matching items already in your library and fills in the category and specs from them. 3. Fill in the specs, quantity, serial number and asset tag. The tag is suggested from the studio's initials, the category and the next number, such as `OF-CAM-01`, and it is what prints on the QR label. 4. Choose where it packs: a package, a case in a package, or a case on its own. 5. Admins can add a day rate and a replacement value. Only admins see these. #### Packages and cases The Packages view groups gear the way it travels: a package such as "A-cam package" holds cases such as "A-cam case", and cases hold items. "New package" and "New case" make them, and each case gets a label for its own QR code. Loose items sit under "Not packed". #### Labels "Print label" on any item, "Print case label" on a case, or "Print labels" on a package opens a sheet of QR codes that fits 30-up address labels on Letter paper. Print it at 100% scale. Scanning a label on set, or typing the code printed under it, finds the item in [Shoot day](/shoot-day.md). ### A production's gear ![A production's Gear tab](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FdYAnFoUlYoertm60QhZK%2Fgear-production.8a07fc8b.png?alt=media) *Company gear, crew kit and rentals for the whole shoot, with the dock at the bottom.* Pick "Whole shoot" or a single day at the top. Each day has its own list; gear added to the whole shoot goes on every day, and gear added to a day joins the whole-shoot list too. #### Company gear "Add gear" then "From the gear library" opens the library as a tree. Tick packages, cases or single items, then "Add N items". Retired gear cannot be picked, and gear that is out with another production says so. Each row shows In, Checked out or Returned as the list moves along, or Missing and Set aside once the crew have checked it on set. The "⋯" menu changes the quantity, prints a label, or takes it off the list, with Undo. #### Crew kit Kit is the gear a crew member brings. It follows the person onto the days they are booked, and the daily kit fee is set on their deal memo in [Crew](/productions/crew.md). "Add gear" then "Crew kit" opens someone's kit to add to it. The same list is on their page in [People](/people.md). #### Rentals ![A rental](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FPyviLeTWIHAlUb2qbtmC%2Fgear-rental.6e02cdad.png?alt=media) *A rental from one house, with its lines and subtotal.* "Add gear" then "Rental" opens a rental: the rental house, picked from Companies or added new, pickup and return times, a quote number, the lines with quantity, rate per day and days, and notes. Rentals are grouped by house and move through Quoted, Confirmed, Picked up and Returned. A rental's lines appear on every day inside its pickup-to-return window. Rates, line totals and the subtotal are for admins. Editors see the items, quantities and days. #### Importing a quote Admins can bring in a rental house's quote instead of typing it. 1. Choose "Import quote" and drop the PDF, Excel or CSV file, or paste the lines. Files up to 10 MB; PDFs are read to 20 pages. 2. Map the quote's columns to Item name, Quantity, Rate per day, Days and Line total. The mapping is remembered for the next quote from the same house. 3. Review the rows. Totals and tax lines are left out. Rows where the quantity is unclear, the rate is missing or the total does not match start unticked, and anything you add anyway is marked "Check" until someone edits it. 4. Add the rows as a new rental or into an existing one. A new rental starts as Quoted. Scanned PDFs with no text cannot be read; paste the lines instead. #### The dock The dock at the bottom tracks the list: Draft, Confirmed, Checked out, Returned. It says what is still Quoted, when to check out, what is missing, and when the rental is due back. One button moves it along: "Confirm list", then "Check out", then "Mark returned", each with Undo. Checking out marks the library items as out and confirmed rentals as picked up. Marking returned brings items back to available and rentals to returned. Moving the whole shoot forward brings every day with it. ### Good to know * Only admins see money: day rates, replacement values, kit fees, rental rates and totals, and the Import quote button. "View as Crew" hides them. * Items in repair or retired never change status on their own. * Viewers and crew can browse the library, open items and print labels, and see a production's lists without the edit controls. * Gear checks on set happen in Shoot day under Gear, and show here as Verified, Missing or Set aside. --- # 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/productions/gear.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.