professional

IT Scope of Work (SOW)

Clearly scoped IT project engagements — deliverables, exclusions, timelines, and acceptance criteria in writing.

Scope creep, unclear responsibilities, and disputed deliverables are the most common causes of IT project failure. Brocent's Scope of Work process defines every project engagement with surgical precision — clear deliverables, explicit exclusions, phased timelines, client and Brocent responsibilities, and measurable acceptance criteria — protecting both parties and giving the project the best possible chance of success.

Why Brocent

No scope creep — every deliverable is precisely defined
Explicit exclusions prevent post-project disputes
Client and Brocent responsibilities clearly documented
Measurable acceptance tests for every deliverable
Formal change request process for all scope additions

What's included

Deliverable Definition with Specifications

Every deliverable is described in precise, unambiguous terms: what will be built or deployed, to what specification, verified by what test, and accepted by what date. No vague language — everything is measurable.

Explicit Exclusions & Assumptions

Brocent explicitly documents what is NOT included in scope and what assumptions have been made (e.g., 'client provides third-party licences', 'existing cabling meets Cat6 standard'). This eliminates scope creep disputes before they start.

Phased Timeline with Client Dependencies

A milestone-based project plan identifies each phase, the responsible party, the dependency chain, and the expected completion date — including client actions that Brocent requires to stay on schedule.

Resource Plan & Rate Card

The SOW specifies which engineer types, certifications, and quantities are required for each project phase — along with the applicable rates for additional scope requests or extensions.

Acceptance Test Criteria

Defined acceptance tests must be passed before each project phase is signed off and invoiced. Tests are objective and measurable — ping tests, throughput benchmarks, user acceptance confirmations — not subjective opinions.

Change Request Process

Changes to scope are handled through a documented Change Request (CR) process — specifying the change, cost impact, timeline impact, and requiring written approval from both parties before any additional work begins.