---
title: LFCS Standard Exclusions — Boilerplate
created: 2026-05-06
created_by: cowork-lfcs
status: live
source_fixture: "[[letter-of-offer-template]] — Hammond Canal Bridge LFCS submission, May 2026, $434,462 ex GST"
related:
  - "[[letter-of-offer-structure]]"
  - "[[../folder-spec]]"
  - "[[../pricing-checklist]]"
---

# LFCS Standard Exclusions — Boilerplate

Pulled verbatim from Liam's Letter of Offer for Hammond Canal Bridge (P424-HCB) and codified as the canonical Standard Exclusions list for every LFCS bid.

These are the **non-negotiable, every-bid-carries-them** exclusions. They go in the `Standard Exclusions` section of every Letter of Offer and Inclusions/Exclusions doc, ahead of any project-specific exclusions.

Project-specific exclusions belong in the `Detailed Exclusions` section — not here.

---

## The list

- All surface water and groundwater management, dewatering, and disposal.
- Disposal of any waste off-site.
- Supply of any site amenities, including skip bins.
- All latent conditions.
- All asbestos-related items.
- D&C responsibility.
- Permits of any kind.
- Allowances for delays caused by other trades or the Head Contractor.
- Service locating, protection, relocation.
- Slip testing.

---

## Standard Preliminaries Assumptions

These sit just under Standard Exclusions in the Letter of Offer — what LFCS assumes the Head Contractor will provide. Same boilerplate-status as the exclusions above.

- Assumes Head Contractor will provide all site facilities and compounds.
- Assumes Head Contractor will provide all traffic management and safety barriers.
- Assumes Head Contractor will provide adequate access to the construction area.
- Assumes Head Contractor will provide all surveys and survey setting out, including reports.
- No allowances have been made for managing environmental permits and approvals.
- Assumes that the Head Contractor will provide all geotechnical testing for the works.

---

## Maintenance rules

- **Append-only with backlinks.** Never delete an item from this list — if a clause becomes inappropriate for a job, that's a project-specific carve-out belonging in the Detailed Exclusions section, not a removal from boilerplate.
- **Changes require a real-world trigger.** A new boilerplate item should only land here after appearing in two or more LFCS submissions and surviving a QS counter-review unchallenged. Track the trigger in `_Log.md`.
- **Wording matches Liam's voice.** First-person plural ("we"), short declarative sentences, no hedging. Don't soften.
- **No project-specifics.** If a clause names a job, a head contractor, a drawing, or a specific spec — it belongs in the Detailed Exclusions of that job's incl-excl doc, not here.