Projects

Minor Works & Technical Projects

Small capital or fit-out works delivered through the FM function rather than a separate projects team.

A — Hard / technicalOperationalTacticalStatutory exposure

"Minor" describes the budget, not the governance risk — a small project delivered without proper sign-off can create liabilities entirely disproportionate to its size.

Why this service exists

Not every capital-adjacent piece of work justifies the overhead of a full project-governance structure, but leaving small works genuinely ungoverned (no sign-off, no compliance check, no handover documentation) is a recurring, real source of downstream problems — statutory non-compliance introduced by an "quick" alteration being the classic case.

What the service covers

  • Small fit-out and alteration works.
  • Minor capital improvements.
  • Scope definition and governance-threshold setting (what counts as "minor" versus requiring full project governance).

Assets and objects

  • Varies by project — this service is defined by scale and governance route rather than a fixed asset category.

Who takes part

  • FM projects coordinatorRequired

    Mandatory.

  • Specialist contractors per projectRequired

    Deliver the work.

  • Demand-side stakeholder requesting the workSituational

    Requests the work.

  • Compliance sign-offRequired

    Where the work touches statutory systems.

What the service needs

  • Work request and scope definition.
  • Budget authorisation.
  • Compliance implications assessment (critical — many "minor" works touch fire compartmentation, electrical systems or accessibility routes and need proper sign-off regardless of budget size).

How delivery runs

  1. 01Define and apply a clear governance threshold: what qualifies as "minor" and can proceed through this lighter-weight route versus what requires full project governance.
  2. 02Assess compliance implications before work begins, not after — this step is the one most often skipped under time pressure.
  3. 03Execute the work through appropriately qualified contractors.
  4. 04Update asset records and compliance documentation on completion — the same handover-data-loss risk named under Asset Lifecycle Management applies here at smaller scale, and is arguably worse because minor works are less likely to have formal handover processes at all.

What is delivered

  • Completed works.
  • Updated asset/compliance records.
  • Sign-off documentation.

From output to outcome

Output

Completed minor works with documentation.

Outcome

Incremental facility improvement delivered without introducing hidden compliance or asset-data gaps.

Organisational effect

The outcome this service protects against is specifically the "it was only a small job" rationalisation that lets proper governance lapse.

Where it gets tense

  • Minor works that touch fire, electrical or accessibility systems proceeding without the same sign-off rigor a major project would require, purely because of budget size.
  • Asset records not updated after minor works, creating a silent, accumulating gap between documented and actual building condition.

Strategic, tactical, operational

Strategic

The minor/major governance threshold itself is a policy decision worth periodic review, not a fixed, forgotten rule.

Tactical

Batching related minor works can reduce disruption and cost relative to addressing them as they arise individually.

Operational

Occupied-space works need genuine coordination with the affected teams, disproportionately to their budget size relative to disruption caused.

Performance indicators

  • Governance-threshold compliance rate

    Percentage of minor works with proper sign-off.

  • Asset-record update rate post-completion

    Prevents silent data degradation.

  • Occupant disruption complaints per project

    Operational quality indicator.

Risks

  • The core risk is statutory non-compliance introduced through inadequately governed small works — this service's entire risk profile is about scope creep past proper sign-off, not about the technical work itself.

Statutory context

Minor works inherit the statutory requirements of whatever system they touch (fire, electrical, accessibility), regardless of budget size. The duty to secure sign-off rests with the organisation.

Sourcing options

  • Single service

    Typically delivered through a panel of pre-qualified contractors rather than individually tendered, given the scale and frequency of individual jobs.

  • Bundled

    Sometimes bundled into a wider hard-services contract.

Technology and data

  • CAFM-integrated work request and approval workflows.

Competencies required

  • Project coordination.
  • Compliance-implication assessment literacy across multiple statutory domains.

Common mistakes

  • Letting "minor" become a synonym for "ungoverned".
  • Failing to update asset and compliance records after completion, silently degrading the accuracy of the wider Asset Lifecycle Management function.

Connections

Knowledge domains
  • Project/Programme Management
To index
Standards and guidance
  • Inherits the statutory requirements of whatever system the work touches (fire, electrical, accessibility)
To index

Adjacent services

Last reviewed: 2026-08-23

Classified using market terminology (hard / soft / enabling), nuanced against EN 15221-8:2025 and ISO 41011:2024.

Services Atlas