Bid Package (OSP) Compared to a Takeoff File (OST)
There are several key differences between Bid Packages and Takeoff files:
- A Bid Package (OSP) can include images (some, all, or none)
- A Bid Package (OSP) can be sent through Project Express
- A Bid Package (OSP) overwrites an existing Bid if imported into the same database (if you want to create a copy, import it into a different database)
- A Bid Package (OSP) sent from a secured database will not import into an existing database (it creates its own, secured database)
- A Takeoff file (OST) file creates a new bid each time it is imported (it cannot be used to update an existing bid)
- A Takeoff file (OST) does not include image files
- A Takeoff file (OST) file can be used to create and update a Quick Bid project
- A Takeoff file (OST) sent from a secured database includes no security
Note
Before you export a bid with images (an OSP Bid Package), we recommend you first collate and organize all your drawings including copying them all to a single main folder. If you leave your images as-is, depending on how the recipient has configured his or her On-Screen Takeoff, when they try to import your Bid Package, the folder structure may not be setup correctly and the links to those images may be broken.Example Use
- Use a Bid Package (*.osp file) if the user to whom you're sending the project does not have access to the image files (either they are on a different network or they don't have access to the Planroom or DFS)
- Use a Takeoff file (*.ost file) if you are sending the project to someone who already has a copy of the project (including plans) and you just want to update the takeoff/quantities (this will create a copy of the bid in their database, they can then compare the two bids and copy/paste over whatever is needed)
- Use a Takeoff file (*.ost file) if you are sending the bid to a Quick Bid user so he or she can price the bid
![]() | Sending a Bid Package via eMail or to a File ![]() |
Related Articles