Ir para o conteúdo

OPTYTECH BLOG

Fit out change requests: a practical decision record

Two people in high-visibility clothing working among construction materials

OpTyTech editorial guide · Construction & Fit Out. Prepared with AI assistance and checked against the linked primary sources. The template and example are illustrative; the cover photograph does not identify an OpTyTech project.

Before changing an agreed fit out scope, prepare a short record of what is requested, why it is needed, which information it affects and who will review it. Keep the request, the assessment and the decision distinguishable. The practical template below is for organising that conversation, with technical and commercial decisions left to the responsible project team.

The Association for Project Management describes change control as capturing and assessing requests to alter an approved project baseline, followed by a decision to accept, reject or defer. Its guidance includes reviewing effects on scope, programme, resources, cost and risk. Read APM’s change control guidance.

First identify exactly what would change

Consider starting with the current drawing, brief or schedule reference. Describe the proposed difference in ordinary language, and attach the relevant marked-up information where available. Separate an observed problem from a proposed solution: a room that needs to support more meetings is a requirement to assess, rather than approval of a particular layout.

Name the person gathering the missing information and the person responsible for the next review. Mark unknown effects as questions. Avoid inserting a cost, completion date or technical conclusion simply to make the form look complete.

A practical change request record

The Scottish Government’s 2019 construction-client guidance discusses recording a request, its reason, dependencies and decision history. It is a Scottish public-sector reference, not a statement of Irish project requirements. See its change control and document management sections.

The following is an illustrative planning record to adapt with your project team. Use the project’s agreed contract administration process for formal instructions and commercial approvals.

FieldWhat to capture
Reference and versionGive the request a clear identifier, date and revision.
Current positionLink the drawing, scope or schedule being discussed.
Requested differenceDescribe what would change and why it is being proposed.
Affected interfacesList packages, occupants or activities needing review.
Open questionsIdentify missing cost, programme or technical information.
Review ownerName who gathers information and the required decision date.
Decision recordRecord the outcome, decision-maker, date and any conditions.
Follow-up referencesIdentify revised records and who needs the agreed information.

Keep the original request identifiable when further information arrives. A later drawing revision should be traceable to the recorded decision. The Scottish guidance emphasises maintaining consistent project information and an audit trail.

Hypothetical example: a meeting-room layout request

Imagine an office team asking to move a proposed meeting-room partition after reviewing the furniture arrangement. This is a hypothetical planning example, not a completed OpTyTech project.

The first entry could describe the requested position and the reason for it, with the current layout attached. It could flag that the project team needs to review the relationship with power, data outlets, access and the planned occupation date. It would leave the design answer and price open until the relevant people have assessed them.

The useful next step is a coordinated review, with someone responsible for obtaining the information. If the decision is deferred, record which answer is missing and when it will be reconsidered. If it is approved through the agreed process, identify which drawings or schedules need updating and who should receive them. The example does not establish a safe construction method or permission to carry out work.

Keep a request separate from an approved change

APM’s process distinguishes assessment and recommendation from approval, followed by updating the plan and monitoring implementation. A submitted form is therefore a record for review; it should not be labelled as an approved change merely because it has been received. APM explains the process stages.

  • Proposed: the request has been logged and needs review.
  • Under review: named questions or assessments are still outstanding.
  • Decision recorded: show the actual outcome and any conditions.
  • Follow-up: identify updated information and outstanding actions.

What if the request is urgent?

Raise the timing constraint with the responsible project lead. Explain what decision is needed, by when, and what information is still missing. Ask how the project’s agreed process handles that situation. An urgent label should make the next action clearer; it should not be used to present an unreviewed proposal as an instruction.

Discuss the requirement with OpTyTech

For a fit out enquiry, share the current brief, the proposed change and the questions your team needs to resolve. Explore Construction & Fit Out or contact OpTyTech to discuss the requirement. This guide concerns project information and coordination, rather than technical design or interpretation of a construction contract.

← Back to the blog