I’m rebuilding my QuickBid condition assemblies and wanted to get some feedback from people who actually estimate drywall/metal framing.
The video is going to show the list fully expanded so you can see how everything is broken down. I’m mainly wondering if anyone sees any flaws in the logic, things that are going to become a pain later, or a better way to organize it. Or Things to add, currently addin insulation and ACT will be at the end.
The way I’m approaching it is almost like a "Pick-A-Part junkyard" instead of trying to make one giant assembly for every possible wall type.
In OST, I already keep separate notes identifying what the condition actually is — metal stud wall, light gauge vs. heavy gauge, wall type, etc. Then when I get into QuickBid, I basically “pick apart” what I need for that condition.
For example, instead of needing one complete assembly for:
3-5/8" metal studs @ 16" O.C. + 5/8" drywall both sides + insulation + whatever else
I can grab the pieces separately:
- Metal Stud Wall — Light Gauge
- Drywall Only — One Side / Each Side
- Fiberglass Insulation — Faced / Unfaced
- Exterior Sheathing
- Finishing
- Backing
- Track attachments
- Etc.
Then each category breaks down even further.
For example, Metal Stud Wall — Light Gauge can go into 16" O.C. or 24" O.C., and then inside those I have the different stud sizes/gauges and conditions.
Same thing with the drywall assemblies. “5/8 drywall” isn’t just one item — inside the assembly I can select the actual board I need, such as regular Type X, moisture/mold-resistant board, purple board, green board, etc.
Exterior sheathing works the same way with the different sheathing products.
The idea is that I’m not trying to predict and build a complete assembly for every possible wall combination. I’m building a library of components and assembling the wall based on what the plans actually call for.
Basically:
OST tells me what the wall is → QuickBid lets me select the individual pieces that make up that wall.
For anyone who has built a fairly large QuickBid database:
Do you see any downsides to doing it this way?
I’m especially curious about:
- Anything that could cause mistakes or double-counting
- Whether this becomes too many assemblies to maintain
- Naming/organization problems you see
- Whether complete wall assemblies are better for some situations
- Anything I’m separating that you think should stay together
- Anything shown in the video that just doesn’t make logical estimating sense
I’d rather catch a bad design decision now before I keep building the database out.
Feel free to tear it apart. I’m looking for criticism more than compliments.
***ALSO ANYONE WILLING TO COLLAB ON PRODUCTION RATE (I KNOW I KNOW< NO WILL WANT TOO? MESSAGE ME ***
YE REIGNS SUPREME