We are thinking to create a Manual Area, Manual Linear, etc.
If this option is chosen, you could just manually enter inputs as numbers:
Area
Linear / Perimeter
Point Count
etc.
Then when you apply items to the takeoff it will reference your manually entered numbers instead of based on point data on the plans.
For manual Volume calculation, I'm curious if you think we should prompt for Wall Height, and compute the volume by Area * Wall Height, or just have an input that you can directly enter your desired Volume to be used in any child item formulas?
EDIT: The point count is probably the takeoff that will be most used for manual entry, but the other takeoff types will be useful as well.
Hello Heber!
I want to share this post with the aim of helping, not confusing. My goal is to provide useful insights and clear guidance, so I hope it brings value and understanding rather than uncertainty.
When considering how to implement volume calculations for takeoff items, both options you mentioned have their own advantages and potential drawbacks.
Here's my breakdown:
Advantages:
Disadvantages:
Advantages:
Disadvantages:
A combined approach might be beneficial. You could implement an option to prompt for wall height and compute volume while also providing an input field for users who wish to directly input a volume.
Proposed Implementation:
This way, you cater to both types of users—those who prefer automation as well as those who want manual control—and enhance the overall usability of the takeoff tool.
This is fascinating. What’s clicking for me is how this ties into how we actually estimate today. In our estimating software, we’re constantly typing in the things we know we’ll need but can’t measure, predictive quantities based on early NAPKIN sketches or experience.
Up until now, the takeoff tool was just “where we measure.” Measurements flowed into the estimate, end of story. But this idea of manual inputs inside the takeoff tool changes that. It means I can start capturing those assumed or placeholder quantities in the same environment, so the estimator’s intent, the “I know I’m going to need this” stuff, becomes visible and connected once the API syncs up.
And yeah, if I’m entering a manual quantity, I’m doing it intentionally, I don’t need the software to compute wall height or volume for me. It’s about being able to log what we know just as easily as what we can measure. Love where this is headed.
Also please let me do a manual unit of measure on the takeoff item would be one thought...like 1 lumpsum for example. Or 50 days for layout. But perhaps I can learn to use the item for that.