Saving Options
These are the three ways to commit your work. New users often mix them up — understanding when to reach for each is one of the most useful things to learn about this tab. Update, Save, and Save As also apply to bids that arrived by imports or other routes; in a typical editing session you would reach them after making the edits described in the Unit-level Editing and Regional and Site-level Editing tabs.
Update
Click Update after you have finished editing a unit but before you save
the file. Update runs a quick internal check — it makes sure the unit's
prices still go from cheapest to most expensive down the bid stack, and it
flags any row that broke the order. Update does not write anything to
disk; the file on disk is unchanged. If the check passes, the tab reports
Validated ✓ — prices strictly ascending. and clears the unit's
unsaved-changes marker (the edits themselves are still only in memory until
you Save). If the check fails, the offending rows are listed inline so you
can fix them before saving. Equivalent to Edit → Validate Bid Stack in the
menu bar.
Save
Click Save to write your edits into the file you have open, overwriting the previous version. Save covers every unit you have edited in this session, not just the one currently on screen. If you have unsaved edits or unresolved validation issues at the moment you click Save, a confirmation dialog opens listing what you are about to commit and asks you to confirm — the file itself is not touched until you confirm.
Use Save when you are happy with your edits and want them in the same file
you started from. On success the tab shows Saved ✓.
Save As
Click Save As when you want to keep your edits but leave the original file alone. A file picker opens; choose a new name and location and the tab writes a fresh bid file at that path and then makes that new file the one you are working on. Save As does not show the confirmation dialog Save shows — you are writing to a fresh file, so nothing existing is being overwritten. Any earlier undo entries stay linked to the original file, so if you undo across the Save As you may see a message about the earlier file rather than the new one.
Use Save As when you want a safety copy before running a destructive transform (see the Regional and Site-level Editing tab for the transforms that need this), when you are producing a variant of the original for comparison, or any other time you want the original file to stay untouched.