FEED Scope of Work (SoW) Definition

A structured SoW that defines what FEED must produce, how it will be reviewed, and how interfaces and assumptions are controlled—so RFQs are comparable and change is reduced.

What it is

A FEED SoW converts objectives into a deliverable-based scope with clear boundaries, review gates, and acceptance criteria— enabling consistent EPCM bids and stronger control of change.

Typical triggers

  • Preparing a FEED RFQ and needing comparable bids
  • Misalignment between operator, EPCM, stakeholders
  • Past projects suffered from change orders and unclear deliverables
  • Need for strong interfaces / battery limits definition

Scope (what we do)

  • Define FEED objectives, boundaries, and battery limits
  • Establish a deliverables list (documents, registers, datasheets, models)
  • Define review gates, close-out workflow, and acceptance criteria
  • Set assumptions management and change control expectations
  • Draft bid evaluation criteria and clarification framework (optional)

Deliverables

  • FEED SoW document (RFQ-ready)
  • Deliverables register (owner, format, review points)
  • Interface and battery limit definitions
  • Milestone plan + review gates (schedule-level)
  • Bid evaluation checklist (optional)

References (high level)

Client FEED practices and disciplined document-control / review workflows.

Engagement options

  • SoW sprint (1–2 weeks) for rapid RFQ readiness
  • Workshop + package for multi-stakeholder alignment
  • Bid support (clarifications, technical evaluation)