Help & Documentation
Offline-first guidance for safe gear lists.
Auto Gear Rules
Rules that automatically add or remove gear based on what's in the project
Auto Gear is a rule engine that adds (or removes) items on a project's gear list when its conditions are met — a specific camera is picked, a crew role is on the job, a project requirement enables slow motion. Rules are built in a three-step wizard (Triggers → Logic → Devices) or a quick one-screen editor, and run when you click Generate Auto Gear in the project's Auto Gear tab. Two scopes: global rules (Settings → Workflow → Auto Gear, shared by every project) and a project's own override (project workspace → Auto Gear tab).
How Auto Gear works
Each rule checks its triggers against the project's current state and, when they match, adds or removes gear. Every item a rule adds carries a small ⚡ badge with the rule's name in the gear list, so you always see where it came from.
- A rule has three parts: Triggers (when it fires) → Logic (Add Gear, Remove Gear, Smart Action or Dynamic Logic) → Devices (what changes).
- Triggers come in 5 categories — Project Context, Crew, Device Name, Device Property and Project Requirements.
- Rules run when you click Generate Auto Gear at the bottom of the project's Auto Gear tab. Preview Results shows what would change first, without touching the gear list.
- Multi-camera aware — the engine reads every camera package, including temporary ones. Device triggers are checked per camera package, so per-camera items carry their camera's assignment.
- Items already on the gear list are skipped as duplicates, so running again doesn't double them.
- Delete an auto-added item from the gear list and it goes on the project's Excluded Items list, so later runs don't add it back.
Tips
- Start from the stock rules. They cover the common 'every cable for every body' patterns.
- Combine triggers when one alone would fire too often — 'Camera Body = ALEXA 35 AND Battery Mount Type = V-Mount' is more useful than the body match alone.
- Give a project its own rules with 'Override for this project' — that's how you do a one-off setup without changing what every other project gets.
Trigger types
Pick a trigger type, then the values it should match. Each type has its own match modes that control how the values are compared.
- Project Context
- Always (fires every time), Scenario (Handheld, Steadicam, Crane, Outdoor and so on), Shooting Days, Delivery Resolution, Device in Gear List (a named device is, or is not, on the gear list), Provider and Provider Category, and whether the project Has Sub-rental, Has Owned Gear or Has Rental Gear.
- Crew
- Crew Member (a specific person from your contacts) or Crew Role (DIT, DP, Gaffer and so on), each present or absent.
- Device Name
- The device picked in a camera package: Camera Body, Monitor, Lens Control, Video Distribution, Wireless Video, Mattebox, Camera Handle, Viewfinder, Tripod Head, Tripod Bowl, Tripod Type and Camera Cage.
- Device Property
- A spec of those devices: Battery Mount Type, Power Input Type, Video Output Type and Video Input Type, FIZ Connector Type, Camera Weight (kg), Media Slot Type, Monitor Size Category, and the lens set's length, weight, front diameter, brand, mount and series.
- Project Requirements
- What the project asks for: recording resolution, codec, sensor mode, aspect ratio, frame rates, Slow Motion Enabled, lens, filter, storage media, camera handle, viewfinder extension, camera support, the monitoring settings (clean feeds, frame guides, LUTs, peaking, false color, zebra and more), vehicles, and cart devices and accessories.
Tips
- Match modes: 'If any match' fires when one selected value matches, 'If all match' needs every one. Numeric triggers such as Shooting Days, frame rates or Camera Weight (kg) compare greater than, less than or equal to; Shooting Days can also fire 'Every X Days'.
- On/off requirements such as Slow Motion Enabled match when enabled in the project, or when NOT enabled. Crew and Device in Gear List triggers check 'Is present' or 'Is absent'.
- A trigger with no predefined options takes the exact values you type.
- Device in Gear List: type to search the device library or keep your own name. It matches a gear list item with exactly that name, upper and lower case aside, and it also sees gear another rule adds in the same run.
- Between two triggers you pick AND (both must match), OR (at least one), XOR (exactly one) or NOT (the first must match, the second must not). The conditions are read left to right with no precedence: 'A AND B OR C' means '(A AND B) OR C'.
Creating a rule (three-step wizard)
From Settings → Workflow → Auto Gear (for a global rule) or from a project's workspace → Auto Gear tab. In the project tab 'New Rule' opens a quick one-screen editor; the full wizard opens from there, and whenever you edit an existing rule.
- Click 'New Rule' in a project's Auto Gear tab. The quick editor asks for one 'When' trigger and the gear to 'Then add' — 'Create Rule' saves it. For anything more, click 'Advanced Editor': your draft carries over into the full wizard. (In Settings, 'New Rule' opens the full wizard straight away.)
- Step 1 — Triggers: pick a trigger type and its values (the list has a filter, 'Select All' and 'Clear All'). 'Add another trigger' stacks more, joined by the operator you pick between them.
- Step 2 — Logic: choose Add Gear, Remove Gear, Smart Action (then pick which one) or Dynamic Logic (build custom item counts). Your triggers are summarised above in a 'When …' sentence so you can sanity-check them.
- Step 3 — Devices: search the device catalog or add a custom item name, then set quantity and category and reorder with the move buttons. 'Expand per camera package (color-matched)' adds one copy per camera package, with a minimum count and a name pattern. Smart Action and Dynamic Logic rules skip this step.
- Click 'Test Rule' at any time to see whether the rule matches the current project and what it would add, then 'Create Rule' (or 'Save Rule' when editing). Leave 'Rule name (auto-generated if empty)' blank and the name is built from the first trigger and first item.
Example: multi-camera slow-motion media kit
A compound-trigger rule for high-speed shoots:
- Name the rule 'High-Speed Media Kit'.
- Trigger 1: Camera Body, 'If any match' — ARRI ALEXA 35 and RED V-Raptor.
- Trigger 2: Slow Motion Enabled, matches when enabled in the project.
- Operator between them: AND.
- Logic: Add Gear.
- Devices: CFexpress Type B 512 GB × 4, SSD 2 TB × 2.
- Save.
→ Whenever one of those cameras is in a camera package AND slow motion is enabled, the next Generate Auto Gear adds the high-capacity media kit to the gear list.
Tips
- Give rules clear names that describe both the trigger and the intent — 'ALEXA 35 Base Kit' beats an auto-generated name once the list grows.
- The step indicator at the top of the wizard jumps to any step without losing your work.
- Saving checks the rule first: a missing item name, a trigger with no values or no threshold, or a rule with no condition at all is pointed out, and the wizard jumps to the step that needs fixing.
- Leaving a part-built rule asks first: once you have edited anything, Escape, the × and Cancel all raise a "Discard changes?" confirm. An untouched wizard still closes straight away.
Common Pitfalls
- Overlapping rules that add the same item from two paths. Duplicates are skipped, but reviewing the rule list now and then keeps it readable.
- Forgetting that global rules apply to EVERY project. One niche addition that shows up everywhere is annoying.
- Setting quantities too high in haste. Auto-added items still deserve a look before pickup.
Smart (computed) actions
A Smart Action works out its items when the rule runs, from the devices actually in your project and the device catalog, instead of from a fixed list. Pick one on the Logic step under 'Select Logic:'.
- Smart Charger Selection — picks chargers for the project's battery mount and battery count, preferring quad, then dual, then single chargers.
- Smart Power Cables — connects the camera to its accessories, with a D-Tap fallback and spare cables.
- Smart Monitor Cables — SDI or HDMI cables matched port to port between camera and monitor, plus power cables and rigging.
- Smart Focus Monitor — adds the Default Focus Monitor from the Auto-Gear Hardware Defaults when a lens control is in the package.
- Smart FIZ Cables — motor-to-controller cables, including ARRI LBUS and connector matching.
- Smart Power Plates, Smart Video Village Battery Plates and Smart Monitor Sun Hoods — battery plates matching the preferred monitor batteries, and one sun hood per monitor on the gear list.
- Smart Card Readers — compatible card readers for every recording-media format in the project. Smart Diopter Frame adds the matching frame when an in-tray diopter is requested.
- Video Village presets — ready-made monitor stations for director, DoP, gaffer, sound, DIT loop, iOS viewing and PIX-E recorders.
- Sync actions — mirror the camera package (camera body, cage, FIZ system, batteries, wireless video, monitor, hotswap) and the project's filters, recording media and lenses into the gear list; Transportation Cars does the same for the configured vehicles. Sync Recording Media takes the card count from the media plan when one is saved.
- In multi-camera setups, per-camera items carry the camera's assignment (for example 'A Cam', 'B Cam').
Tips
- Smart rules are marked 'Smart' on their card and skip the Devices step in the wizard — the catalog supplies the items.
- Output depends on what's actually in your project. The same smart rule produces different items for different projects.
- Use 'Test Rule' or Preview Results to see what a smart rule would add before you generate.
Generating, previewing and undoing
The bar at the bottom of a project's Auto Gear tab runs the rules. Nothing changes on the gear list until you click Generate Auto Gear or run a single rule.
- Preview Results — runs every enabled rule without changing anything and opens the summary with 'Would Add'. If nothing matches, a short notice says so instead.
- Generate Auto Gear — adds the matching items to the gear list (temporary camera-package gear included) and opens the Generation Summary: Added, Rules Matched, Duplicates Skipped and Excluded, then Matched Rules with their items and the time each fired.
- 'Rules Not Fired' lists the rules that did nothing, each with its reason — Conditions not met, No matching items, or Error.
- Undo Generation in the summary removes every rule-added item from the gear list and the temporary gear, and reports how many it removed.
- The Last Generation panel in the tab keeps the most recent result for reference.
- Excluded Items — an auto-added item you delete from the gear list is listed here with the rule it came from, and later runs leave it out. 'Restore' lets one back in; 'Clear All' empties the list.
- When the project changes under rules that already ran (another camera, other requirements), their cards show 'Context Changed' and a banner offers 'Rerun Affected Rules'.
Tips
- Preview first on a big project — the summary shows exactly what a run would add before you commit.
- Removing an unwanted auto item from the gear list is enough to keep it off for good; there's no need to edit the rule.
Managing rules
Every rule is a card in the list. The card shows its triggers ('When:'), what it adds or removes, and whether it fits this project ('Matches Project' or 'No Match'). Smart rules carry a 'Smart' tag, remove rules a 'Remove' tag.
- Toggle a rule on or off without deleting it — useful for seasonal or client-specific setups.
- Reorder with Move up / Move down — rules run in list order. The move buttons hide while 'Search rules…' is filtering the list.
- Edit opens the full wizard; Duplicate gives you a starting point for a variant; Delete asks before removing.
- Export Rule saves a single rule as a JSON file. 'Export' saves the whole rule set; 'Import' adds the rules from a file (a rule set, a single exported rule or an exported preset) to your list.
- 'Stock Rules' opens the Factory Rule Catalog, where you can search the stock rules, pick some and click 'Add Selected'.
- On a phone or tablet, Stock Rules, Export, Import and Presets live behind the “… More” button beside New Rule; on a desktop-width screen they stay on the row. Settings → Workflow → Auto Gear folds the same way, with Save as Preset, Presets, Reset Defaults, Export and Import behind its “… More”.
- In a project, 'Run This Rule Now' (▶) on a card runs only that rule against the project and adds its items.
- A rule whose conditions don't match the project, or that is switched off, cannot fire on its own; running it asks 'Run Rule Anyway?' first and runs it on 'Run Anyway'.
- When a rule shows 'Context Changed', the same button becomes 'Rerun This Rule' (↻) — the project moved under a rule that already fired.
Tips
- Disable rules for gear you rarely use rather than deleting them. Faster to re-enable when the job type comes back around.
- Export your rule set before any reset to the stock rules. Rebuilding by hand is the most tedious recovery task in the app.
- Running one rule is the way to pull its kit into a shoot that doesn't technically meet its triggers — no need to loosen the rule or generate everything again.
Global rules vs project rules
Two scopes. The same wizard creates both — what differs is where you open it from.
- Global rules: Settings → Workflow → Auto Gear. Apply to every project. Sync to the cloud.
- A project uses the global rules by default — the Auto Gear tab says 'Using your global rules'. While it does, adding, editing, reordering or deleting a rule in the project tab changes the GLOBAL rules, and so every project that uses them.
- 'Override for this project' copies the current global rules into the project ('Using project-specific rules'). From then on the tab edits only that copy, stored on the project and synced with it; later changes to the global rules no longer reach it.
- 'Revert to global' deletes the project's own rules and goes back to the global set.
- Contact rules: a crew contact can carry its own rules (Contacts → open the contact → Operator preferences → Gear rules). They run in every project where that contact is linked on the Crew tab, on top of the global or project rules. The Auto Gear tab lists them read-only under 'From contacts on this project', with a link to the contact where they are edited. A gear-list line added by one names the rule and the contact. On a shared project, a collaborator who does not have that contact does not run its rules.
- Contact rules per project: each rule under 'From contacts on this project' has a tick. Untick it to leave that rule out of this project only; the contact and your other projects are not changed, and the choice is saved with the project. To give a contact a rule you already have, open the contact and use Gear rules → 'Add from my rules'. In Project Requirements, 'Always add for …' on a recommended device adds it to that contact's 'Preferred devices' rule.
- Shared rules: a connected crew member can share their own gear rules with you (their profile contact → 'Share with my crew'). While your contact for that person is on the Crew tab, their shared rules run with yours on Preview and Generate. They are listed under 'From contacts on this project' with the badge 'Shared' and the same tick to leave a rule out of this project. You cannot edit them; only the person who shares them can. They are read when the project opens and need a connection: offline, or after the person stops sharing, the project runs without them.
Tips
- Override first, then edit, when a change is meant for one project only — editing while on the global rules changes them everywhere.
- Collaboration: global rules sync to the cloud, so collaborators on a shared project see the same defaults.
Factory rules
Pre-built rules that ship with the app as a starting point.
- Factory rules cover smart chargers, cables, batteries, power plates, outdoor gear, and support hardware via the computed actions above.
- Auto-Gear Hardware Defaults — the Small Monitor Preferred Battery, Large Monitor Preferred Battery and default monitors that the smart battery, power-plate and focus-monitor rules use. Set them for every project in Settings → Workflow → Auto Gear, or per project in the Auto Gear tab with 'Override hardware defaults for this project'.
- Legacy parity rules keep older project setups compatible.
- Factory rules can be enabled, disabled, or edited just like your own rules.
- 'Reset Defaults' (Settings) asks 'Reset all rules to factory defaults?' and then REPLACES the whole rule list with the stock rules — your own rules go too. In the Factory Rule Catalog, 'Add Selected' adds stock rules alongside yours, while 'Replace all with factory defaults' swaps the list after a confirmation.
Tips
- Review factory rules before turning everything on. Smart actions depend on your catalog being up to date.
- Save the refined factory set as a Preset before you start modifying — easier to undo a wrong turn.
- Factory rules are also a learning path. Open one, look at the trigger logic, see how smart actions are wired.
Category organization (mapping + order)
Auto-gear places each generated item into a category and inserts new categories in a preferred order. You can make it follow YOUR own category organization instead of its built-in names.
- Category Mapping (a section of Settings → Workflow → Auto Gear): map a built-in auto-gear category (e.g. "Camera Batteries", "Consumables") onto your own category name, so generated items land in your existing categories instead of creating a duplicate.
- Category Order (a section of Settings → Workflow → Auto Gear): drag to set the order in which auto-gear inserts NEW categories. Existing categories in your gear list keep their position.
- Per-project order: a project’s Auto-Gear tab has a "Category Order" section with an "Override the global category order for this project" toggle — turn it on to give that project its own order.
- Temporary camera-package gear follows the same mapping and order as your permanent gear list.
Tips
- Leave a mapping field blank to keep the built-in category name.
- A project that already customized its order keeps it — enabling per-project override never resets your categories.
Collaboration: rule-level lock
Unlike most editors in the app, the Auto-Gear rule editor uses a RULE-level lock rather than a per-field one. The wizard modal stages a local draft and commits only on Save, so the whole rule is claimed on mount and released on close.
- Opening a rule in the wizard claims that rule for your session.
- Other collaborators see the Save button and the rule's Enabled toggle disabled with a 'locked by other' notice.
- Closing the wizard (Save or Cancel) releases the lock for everyone.
- Per-field locks apply elsewhere in the app — Auto-Gear is the exception, and the rule-level scope is intentional because of the staged-draft behaviour.
Tips
- If another session has a rule you need open, ask them to close the wizard. Idling doesn't release the lock.
- See the Collaboration topic → 'Where field locks apply' for the full per-editor matrix.
Auto Gear takes repetitive 'add the same cable every time' work off your plate. Start from the factory defaults, then build compound-trigger rules for the camera packages you actually use.
Related Topics
See also
