Compare a request with the current scope first: what changes, who performs it, what resources or access it needs and who approves. Record the agreed start and acceptance evidence so a chat request does not become a different obligation in each person's mind.
An owner may want another property included, another contact channel covered or a different report. None should automatically be assumed part of the existing service. This guide proposes an operating change register; it does not interpret a contract or set a fee.
Establish the baseline
Reference the current scope document and version, then state the difference requested. For example, identify the additional channel, what remains unchanged and whether anything stops. If the baseline is missing, clarify it before agreeing the addition. One party's memory is not sufficient evidence that the other already accepted the work.
Make the request assessable
| Field | Agreement needed |
|---|---|
| Reference and requester | A shared identifier |
| Existing scope | Current document or task list |
| Addition or removal | A defined output, not simply “more support” |
| Impact | People, time, system access, equipment and costs to assess |
| Options | Methods, exclusions and unresolved assumptions |
| Approval | Authorised decision-maker for this case |
| Start | Agreed date after readiness checks |
| Acceptance | Evidence and person checking the new output |
KW Hospitality's quote-preparation guide highlights visible scope and assumptions. This article adapts that clarity principle to an operating change record; purchasing conditions are not being treated as management contract terms.
Assess dependencies before promising delivery
Adding a communication channel can add coordination, checking and information needs as well as a login. Establish whether access exists, who authorises it and how it will be removed when work ends. Keep passwords out of the request record.
Separate assessed items from unknowns. Do not invent an unagreed fee, deadline or outcome. Refer specific contractual questions to an appropriate adviser rather than asserting an addition is covered by a package.
A fictional additional-property report
An owner asks to include another property in an existing report. The team checks the data sources, reporting units, access authority and responsibilities for that property. If access is missing, distinguish preparation from full reporting; do not populate unknown values with zero to make the report look complete.
After agreement, confirm who supplies data, checks it and receives the report. Adding a property's name to a cover page is not evidence that the new scope works. This is a fictional example, not a promise that Kines accepts every such request.
Accept the change and update shared records
Before use, compare the deliverable with the request and preserve unresolved items. A trial needs an agreed boundary, period and end condition. “Let's try it” should not silently become a permanent obligation.
When accepted, update the working scope and responsibility documents used by the team. Retain the earlier version and notify affected people. Updating only the owner's copy leaves on-site staff working from different instructions.
Before the new scope starts
- The existing scope is identifiable.
- Additions, removals and exclusions are clear.
- People and access are ready for the agreed work.
- Pending costs and conditions remain explicit unknowns.
- Approval and the start date are confirmed.
- Acceptance and open-item handling are defined.
- The parties use the same current version.
Frequently asked questions
Does asking in a chat mean work has started?
In this register, a request, an approval and an actual start are distinct. The effect of communications depends on the relevant agreement; staff should not infer authority from ambiguous wording.
Does a minor change need the same process as a large one?
Scale the detail to the impact, but retain evidence of what changed, who accepted it and how completion is checked.
Discuss the actual difference you need
Bring your existing scope and requested additions to LINE OA @kines. Read what a hotel management company does to organise the discussion.
Reference and scope
KW Hospitality: Requesting an accurate hotel supply quote provides context on scope clarity. This register is a Kines editorial operating proposal, not a contract amendment valid in every situation.


