1.5 KiB
title, tags, up
| title | tags | up |
|---|---|---|
| Takeoff Scripts | conest-processes |
Takeoff Scripts
I often refer to "ConEst takeoff scripts" as justification for certain of decisions, but they do not really exist in writing.1
Scripts should be directed, limiting extraneous information.
Systems
The structure and names of scripts
were originally intended to match how the terms
are generally understood in ConEst,
such that a new estimator could be told "Do electrical,"
find electrical-takeoff.md, complete all its instructions,
and in doing so satisfy the expectations of the estimator making the request.
I've since come to the conclusion
that the names of systems are ambiguously understood.
A request that an estimator "do electrical"
may or may not come with the expectation
that any of lightning protection, slab deck budgets,
or temporary power be completed as well.
Because I feel I lose nothing in doing so,
Citations
For the purpose of accountability, it is crucial that all direction has a documented origin.
Use footnotes to reference timestamped notes.
Do this:
Even when drawings show 2 separate duplex receptacles,
use `DW & DISPOSAL DUAL CIR - ...`,
which includes only one receptacle.[^1]
[^1]: [[2026-01-12_10-42-30#Unit Dishwasher/Disposal]]
not this:
> [!quote] [[joel-jansen]] 2026-01-12 in reference to [[woodbrook]] (pp.)
> Even when drawings show 2 separate duplex receptacles,
> use `DW & DISPOSAL DUAL CIR - ...`,
> which includes only one receptacle.