Rural Residential Estate: 28 Issues Found

Summary: The 'CHAINLINK FENCE' detail illustrates a 6'-0' high fence and explicitly restricts the brace rail to 8' fences with the note 'BRACE RAIL (FOR 8' HGT FENCE ONLY)'. This directly contradicts the Chain Link Fences and Gates specification, which requires brace rails on 'ALL GATE AND TERMINAL POSTS' without any height restriction.

Why it matters: If the contractor follows the drawing note, they will omit the brace rail on the 6'-0' chain link fence installations. The omission of brace rails on terminal and corner posts compromises the structural integrity of the fence by weakening its ability to maintain fabric tension, violating the specification.

Suggested next step: Please confirm that brace rails are required on all terminal posts for the 6'-0' chain link fence as per specification section 323113, and remove the '(FOR 8' HGT FENCE ONLY)' note from the brace rail callout in Detail K.

RFI draft: Please confirm that brace rails are required on all terminal posts for the 6'-0' chain link fence as per specification section 323113, and remove the '(FOR 8' HGT FENCE ONLY)' note from the brace rail callout in Detail K.

Summary: Drawing Detail K for the chainlink fence labels the brace rail as '1.66' (1 5/8') OD BRACE RAIL (FOR 8' HGT FENCE ONLY)', restricting brace rail installation to 8-foot-high fences. The fence shown has a height of 6'-0'. However, the specification Section 323113 Part 3, Section 3.2.C.4 requires that 'ALL GATE AND TERMINAL POSTS SHALL BE BRACED...

Why it matters: Omitting brace rails from gate and terminal posts on fences shorter than 8 feet compromises the structural stability of those posts. Terminal and gate posts bear the full tension of the stretched fabric and are subject to wind and impact loads. Without diagonal bracing, these posts may lean, deflect, or fail prematurely. This contradicts a...

Suggested next step: Request clarification on whether brace rails are required at all gate and terminal posts regardless of fence height, as stated in the specification (Section 323113, 3.2.C.4), or if the drawing's restriction to 8-foot fences only is the intended design. If the spec requirement governs, request that Detail K be revised to remove the '(FOR 8' HGT...

RFI draft: Request clarification on whether brace rails are required at all gate and terminal posts regardless of fence height, as stated in the specification (Section 323113, 3.2.C.4), or if the drawing's restriction to 8-foot fences only is the intended design. If the spec requirement governs, request...

Summary: Detail B (Trapped Outlet Control Structure) indicates a 12' outlet pipe with an invert elevation of 'INV:183'. This is a clear typographical error (missing the decimal point) and is physically impossible, as the structure's stated top Rim Elevation is '7.52' and the matching 12' inlet elevation is '1.83'.

Why it matters: If the control structure is constructed or fabricated with an outlet invert elevation of 183 feet, it will be entirely incorrect and fail to function. The outlet invert must logically be at or slightly below the lowest inlet to allow proper gravity drainage without causing unintended storm water backup.

Suggested next step: Please confirm that the 12' outlet invert elevation on the Trapped Outlet Control Structure should be '1.83' instead of '183', and update the detail accordingly.

RFI draft: Please confirm that the 12' outlet invert elevation on the Trapped Outlet Control Structure should be '1.83' instead of '183', and update the detail accordingly.

Summary: The Utility Plan (C300) specifies that the 12' West (outlet) invert for STORM OCS 4.0 is 1.83. However, Detail B on C402 for the Trapped Outlet Control Structure (which corresponds to STORM OCS 4.0) shows the 12' outlet invert as 183.

Why it matters: The missing decimal point on the detail creates a massive elevation error (183 feet instead of 1.83 feet). While clearly a drafting typo, it must be formally documented and corrected to prevent any potential confusion or errors during the fabrication of the pre-cast structure.

Suggested next step: Please confirm that the 12' outlet invert elevation on Detail B/C402 should be 1.83 to match the 12' W INV for STORM OCS 4.0 on the Utility Plan (C300), and revise the detail accordingly.

RFI draft: Please confirm that the 12' outlet invert elevation on Detail B/C402 should be 1.83 to match the 12' W INV for STORM OCS 4.0 on the Utility Plan (C300), and revise the detail accordingly.

Summary: The Segmental Retaining Wall Specifications (C501) contain contradictory requirements for the thickness of the leveling pad if lean concrete is used. Note 13 permits the use of lean concrete but limits it to '3 INCHES THICK MAXIMUM'. However, Note 29 dictates that the leveling pad must have a 'MINIMUM THICKNESS OF 6 INCHES', without any...

Why it matters: If the contractor elects to use a lean concrete leveling pad as permitted by Note 13, it is physically impossible to satisfy both the 3-inch maximum requirement and the 6-inch minimum requirement simultaneously. This ambiguity could result in an improperly sized foundation that either wastes material or compromises the structural stability of...

Suggested next step: Please clarify the required thickness for the retaining wall leveling pad when lean concrete is used. Should the 3-inch maximum dimension in Note 13 govern, or the 6-inch minimum dimension in Note 29? Please coordinate the specification notes with Detail C on C402.

RFI draft: Please clarify the required thickness for the retaining wall leveling pad when lean concrete is used. Should the 3-inch maximum dimension in Note 13 govern, or the 6-inch minimum dimension in Note 29? Please coordinate the specification notes with Detail C on C402.

Summary: Drawing C300 General Note 5 mandates that 'SLURRY BACKFILL IS REQUIRED FOR ALL WORK IN PUBLIC RIGHT OF WAY.' In direct contradiction, the project specifications for both Earth Moving (Note 12) and Storm Drainage (Note 13) explicitly require 'GRANULAR BACKFILL' for utility trenches beneath and within five feet of pavement areas, and permit...

Why it matters: Conflicting backfill material requirements create confusion during the bidding and construction phases, as slurry backfill (flowable fill) has vastly different material costs, procurement considerations, and placement methods compared to granular or spoil backfill. If the municipality indeed requires slurry backfill in the public right of way,...

Suggested next step: Please clarify the required trench backfill material for utility work located within the public right of way. If slurry backfill is required by the local municipality as stated on C300, please update the Earth Moving and Storm Drainage specifications to permit its use in lieu of the specified granular backfill and Class B compacted trench sections.

RFI draft: Please clarify the required trench backfill material for utility work located within the public right of way. If slurry backfill is required by the local municipality as stated on C300, please update the Earth Moving and Storm Drainage specifications to permit its use in lieu of the specified...

Summary: Drawing sheet C003 General Note 10 strictly prohibits the reuse of excavated subgrade material, stating that 'ON-SITE REUSE IS NOT PERMITTED' because the entire site contains environmentally impacted soil. However, the specifications for EARTH MOVING (Note 12) and STORM DRAINAGE (Note 13) on sheet C500 explicitly permit the use of 'COMPACTED...

Why it matters: If contractors follow the standard specification notes allowing the reuse of excavated compacted spoil backfill, they will violate the project's Soil Management Plan and environmental regulations by reusing contaminated soils on-site instead of transporting them to a licensed landfill.

Suggested next step: Please clarify if the Soil Management Plan's prohibition on reusing excavated soil on-site (Drawing C003, General Note 10) supersedes the standard specification allowances in Earth Moving Note 12 and Storm Drainage Note 13 that permit compacted spoil backfill to be used in landscape areas.

RFI draft: Please clarify if the Soil Management Plan's prohibition on reusing excavated soil on-site (Drawing C003, General Note 10) supersedes the standard specification allowances in Earth Moving Note 12 and Storm Drainage Note 13 that permit compacted spoil backfill to be used in landscape areas.

Summary: The drawing details for the asphalt pavement sections specify the surface and binder courses using obsolete designations 'SURFACE NO. 4' and 'BINDER NO. 4' or 'BINDER NO. 3'. However, the Asphaltic Paving specification explicitly mandates that both the asphaltic binder course and surface course shall be 'MIXTURE LT' for regular and heavy-duty...

Why it matters: Using contradictory or outdated mix type designations on the construction details will cause confusion during the material submittal process and may result in the contractor ordering an asphalt mix that does not comply with the intended 'MIXTURE LT' performance criteria required by the specification.

Suggested next step: Please confirm if the asphalt surface and binder courses should be 'MIXTURE LT' as required by the Asphaltic Paving specifications, and update the Asphalt Pavement Section details on sheet C401 to remove the 'NO. 4' and 'NO. 3' designations.

RFI draft: Please confirm if the asphalt surface and binder courses should be 'MIXTURE LT' as required by the Asphaltic Paving specifications, and update the Asphalt Pavement Section details on sheet C401 to remove the 'NO. 4' and 'NO. 3' designations.

Summary: The drawing specifies that the aggregate storage reservoir base must have 'NO GREATER THAN 5% PASSING THE NO. 200 SIEVE'. However, the specification states it should have 'NO GREATER THAN 50% PASSING THE NO. 200 SIEVE'. This creates a direct contradiction regarding the acceptable material gradation.

Why it matters: An open-graded base for porous pavement requires very low fines to allow water to drain efficiently. The specification's allowance of up to 50% passing the No. 200 sieve (which represents silt/clay particles) is likely a typographical error, as that amount of fines would clog the reservoir and prevent drainage, leading to system failure. The...

Suggested next step: Please clarify the maximum allowable percentage passing the No. 200 sieve for the porous pavement aggregate storage reservoir. Should the specification be revised to match the 5% limit shown on the drawings to ensure proper drainage?

RFI draft: Please clarify the maximum allowable percentage passing the No. 200 sieve for the porous pavement aggregate storage reservoir. Should the specification be revised to match the 5% limit shown on the drawings to ensure proper drainage?

Summary: The grading plan details multiple incorrect spot elevations for the 'PROPOSED RETAINING WALL' that violate standard grading practices and acceptable engineering principles. For example, one section indicates '8.22 TW' (Top of Wall) and '8.18 BW' (Bottom of Wall), yielding a wall height of just 0.04 feet and placing the top of the wall...

Why it matters: If constructed with these elevations, the retaining wall will fail to retain the proposed surrounding earth, leading to immediate overtopping and localized slope failures. This requires a complete redesign of the wall profile and adjacent grading to ensure the wall successfully retains the soil mass.

Suggested next step: Please review and revise the Top of Wall (TW) and Bottom of Wall (BW) spot elevations for the proposed retaining wall to ensure adequate wall height and that the TW is set appropriately above the retained earth grades.

RFI draft: Please review and revise the Top of Wall (TW) and Bottom of Wall (BW) spot elevations for the proposed retaining wall to ensure adequate wall height and that the TW is set appropriately above the retained earth grades.

Summary: Sheet C200 (Grading) references a detail on sheet C400 for the 'PROPOSED RETAINING WALL' (shown as '#/C400'). However, sheet C400 (Details) contains only erosion control and paving details: Detail A (Inlet Protection - WDNR TS-1060), Detail B (Silt Fence - WDNR TS-1056), Detail C (Construction Entrance - WDNR TS-1057), Detail D (Joining Two...

Why it matters: The retaining wall shown on C200 includes significant wall elevations (e.g., TW and BW grades ranging from approximately 8.18 BW to 10.34 TW), indicating a wall with substantial height variation. Without a corresponding construction detail, the contractor lacks critical information on wall type, materials, reinforcement, footing requirements,...

Suggested next step: Please clarify where the retaining wall construction detail referenced as #/C400 on sheet C200 is located. Sheet C400 does not contain a retaining wall detail. Please provide the correct sheet reference or issue the missing retaining wall detail, including wall type, materials, reinforcement, footing design, drainage, and backfill requirements.

RFI draft: Please clarify where the retaining wall construction detail referenced as #/C400 on sheet C200 is located. Sheet C400 does not contain a retaining wall detail. Please provide the correct sheet reference or issue the missing retaining wall detail, including wall type, materials, reinforcement,...

Summary: Detail K on C401 explicitly restricts the brace rail to 8-foot high fences only, stating it is 'FOR 8' HGT FENCE ONLY.' However, the chain link fence specification on C502 Section 3.2.C.4 requires brace rails at all gate and terminal posts regardless of fence height, stating 'ALL GATE AND TERMINAL POSTS SHALL BE BRACED MIDWAY BETWEEN THE TOP...

Why it matters: This conflict creates ambiguity for the contractor regarding whether to install brace rails at gate posts and terminal (end/corner) posts for the 6' high fence. Omitting brace rails at gate and terminal posts, particularly at the 24' wide sliding gate, could compromise fence stability under lateral and operational loads. Conversely, installing...

Suggested next step: Please clarify whether brace rails are required at gate and terminal posts for the 6' high chain link fence on this project. Detail K on C401 limits brace rails to 8' high fences only, while Specification Section 3.2.C.4 on C502 requires all gate and terminal posts to be braced regardless of height. Please confirm which requirement governs and...

RFI draft: Please clarify whether brace rails are required at gate and terminal posts for the 6' high chain link fence on this project. Detail K on C401 limits brace rails to 8' high fences only, while Specification Section 3.2.C.4 on C502 requires all gate and terminal posts to be braced regardless of...

Summary: Sheet C100 (Site Dimension) includes a detail callout '#/C400' for 'REPLACE EXISTING GRAVEL IN-KIND', directing the contractor to sheet C400 for construction specifications. However, sheet C400 (Details) contains only details A (Inlet Protection - WDNR TS-1060), B (Silt Fence - WDNR TS-1056), C (Construction Entrance - WDNR TS-1057), D (Joining...

Why it matters: Without a corresponding detail on C400, the contractor has no specification for how to perform the gravel replacement, including material type, gradation, thickness, compaction requirements, or extent of removal and replacement. This unresolved cross-reference could lead to inconsistent field interpretation, RFI delays during construction, or...

Suggested next step: Request the engineer to either add the missing detail '#' to sheet C400 for 'REPLACE EXISTING GRAVEL IN-KIND' specifying material, gradation, thickness, and compaction requirements, or clarify whether this callout should reference a different detail or sheet.

RFI draft: Request the engineer to either add the missing detail '#' to sheet C400 for 'REPLACE EXISTING GRAVEL IN-KIND' specifying material, gradation, thickness, and compaction requirements, or clarify whether this callout should reference a different detail or sheet.

Summary: Sheet C100 includes a callout pointing to '# C400' for instructions to 'REPLACE EXISTING GRAVEL IN-KIND'. The '#' symbol indicates an unresolved or broken detail reference tag, meaning the intended detail cannot be identified on the referenced 'C400 DETAILS' sheet.

Why it matters: Without a valid detail reference, the contractor will lack the necessary section, material, or subgrade preparation specifications for the gravel replacement. This missing information could lead to improper installation or RFI delays during construction.

Suggested next step: Please provide the intended detail for the 'REPLACE EXISTING GRAVEL IN-KIND' scope on Sheet C400, and update the unresolved '# C400' callout on Sheet C100 with the correct detail identifier.

RFI draft: Please provide the intended detail for the 'REPLACE EXISTING GRAVEL IN-KIND' scope on Sheet C400, and update the unresolved '# C400' callout on Sheet C100 with the correct detail identifier.

Summary: Sheet C402, Detail C (MODULAR BLOCK MSE WALL) Note 1 lists only two approved retaining wall systems: 'KEYSTONE, ROCKWOOD, OR APPROVED EQUAL.' However, Sheet C501 (SPECIFICATIONS) Item 4 lists four approved systems: 'REDI-ROCK RETAINING WALL UNITS, VERSA-LOK STANDARD RETAINING WALL UNITS, KEYSTONE RETAINING WALL UNITS, ROCKWOOD RETAINING WALL...

Why it matters: This inconsistency can create confusion during bidding and construction. A contractor reviewing the detail on C402 may exclude Redi-Rock and Versa-Lok from their material submittals, believing only Keystone and Rockwood are acceptable. Conversely, the specification on C501 names all four. The specific call for Versa-Lok adhesive in Item 49...

Suggested next step: Please clarify which retaining wall manufacturers are approved for this project. Sheet C402 Detail C Note 1 lists only Keystone and Rockwood, while Sheet C501 Specification Item 4 also includes Redi-Rock and Versa-Lok. Additionally, C501 Item 49 specifies Versa-Lok adhesive by name. Please confirm whether Redi-Rock and Versa-Lok are acceptable,...

RFI draft: Please clarify which retaining wall manufacturers are approved for this project. Sheet C402 Detail C Note 1 lists only Keystone and Rockwood, while Sheet C501 Specification Item 4 also includes Redi-Rock and Versa-Lok. Additionally, C501 Item 49 specifies Versa-Lok adhesive by name. Please...