Pre vs post bidding
When to bid from a script, when to bid from a cut, and how the two relate.
- Every bid pack is PRE or POST — chosen in the New pack dialog.
- PRE unlocks the Script view; the Player is disabled because there's no footage yet.
- POST unlocks the Player, markers, and per-shot bidding.
- Both produce the same shot list shape, so exports and reporting stay consistent.
Why the split exists
Bidding a script and bidding a cut are the same job with different evidence. At script stage you're estimating how many shots of what kind; on a cut you're estimating this shot, right here. Slate keeps one data model and swaps the front end.
PRE — estimating by volume
You don't know the shots, so you bid the work types: fire augmentation, set extension, crowd tiling. Each work type has tiers (typically Wide / Medium / Close, or your own ladder). You set days per tier once, and the breakdown's shot counts multiply out.
This is why the first script bid feels front-loaded and the second one takes minutes — the tier days are already there.
POST — estimating by shot
You have the cut, so you bid each shot on its merits: markers, thumbnails, methodology notes, and days per department. Presets and AI Quick Bid handle the repetitive rows.
Moving between them
Create a new POST pack in the same project when the cut arrives. Your work types, tiers, presets, rates, and tags carry over — they're workspace-level, not pack-level, so the post bid inherits everything you learned at script stage.