vault backup: 2025-12-08 16:37:36

pre-takeoff-research.md

@@ -11,9 +11,9 @@ title: Pre-Takeoff Research
 ---
 # Pre-Takeoff Research
 
-<!--
+%%
 This note should be arranged chronologically:
--->
+%%
 
 > [!important] Requirement Precedence
 > In case of conflict:
@@ -21,20 +21,24 @@ This note should be arranged chronologically:
 > are superseded by the terms of our proposal,
 > which are superseded by specific direction from the bid team.
 
-<!--
+%%
 Where NEC, IBC, and other applicable codes fall in this hierarchy
 is subject to some debate.
--->
+%%
 
 > [!aside] "Plans & Specs"
 > The oft repeated "per plans and specs" is a gross oversimplification:
-> The RFP documents are more likely than not
-> to have one or more irreconcilable contradictions,
+> The RFP documents will---more likely than not---
+> have one or more irreconcilable contradictions,
 > or some instance of [[gold-plating]] too egregious to accept.
-> When ConEst takes of a project "per plans and specs",
+> When ConEst takes off a project "per plans and specs",
 > we are taking off _Bid's interpretation_ of the RFP documents,
 > which they must be able to articulate.
 
+%%
+The limitations of Bid's authority are currently being questioned
+%%
+
 Seek to use the cheapest method,
 as determined by Senior Construction Estimator
 and Database Administrator,
@@ -114,9 +118,9 @@ _without respect for voltage drop_.
   * Riser Diagram
   * Subfeed schedule (if present)
 
-<!--
+%%
 TODO: Create flow chart for wiring methods.
 Some cases to mention:
 * Deck thickness (minimum 3x conduit outer diameter)
 * Renovations (may not be able to run in slab)
--->
+%%