Document a vendor change during a lodging project

A lodging project may change vendors after planning has begun or after some work has been completed. The new proposal can make it tempting to replace the old project file entirely. A more useful transition record shows what has already happened, what the new vendor is proposing and which responsibilities still need clarification. It keeps the request description aligned with the current project without erasing its history.

Establish the transition point

Write down the event that prompted the review and the current confirmed status. Is the business considering a different supplier, obtaining another proposal or proceeding with a documented change? Those stages should not be blended. Keep any decision about agreements or obligations with the business's appropriate review process rather than making that decision in the request summary.

Identify the part of the project affected by the possible change. A new vendor for one task does not necessarily replace every supplier or alter every phase.

Separate completed work from proposed remaining work

Use a private transition sheet with distinct sections for work supported as completed, work still in progress or unresolved, and work newly proposed. Match each statement to the relevant source. If the record does not establish whether an item is complete, leave that question visible. Do not use a new estimate as proof that an earlier task was never performed.

Record physical items or documents that may need to be handed over, such as current specifications or a project drawing. Identify the person responsible for confirming the handover. The sheet should describe business coordination, not technical acceptance of work the coordinator is not qualified to assess.

Compare the new proposal to the remaining need

Read the new proposal against the current project brief, not against the original idea alone. Which tasks remain necessary? Does the new description include something already completed, omit a remaining item or introduce a different approach? Mark each difference for review. Avoid simply combining the old and new descriptions into a longer list that contains duplicates.

Keep optional additions separate from the remaining scope. A new vendor's suggestion should not become part of the business request without a clear decision and a current explanation.

Resolve interfaces before presenting a settled plan

A vendor transition can create questions about who supplies information, who coordinates access and which party should answer a query about earlier work. Name those questions and the role responsible for obtaining an answer. Do not imply that a new vendor has accepted responsibility for earlier work unless that is supported by the appropriate records.

If the project details have already been shared through a request process, explain the change using the existing private reference. Ask what revised information is needed. Keep a record of the response and do not assume that a revised proposal has been accepted by a funding partner merely because it was sent.

Illustrative example: one part of a property project changes hands

A fictional lodging operation considers a new vendor for the remaining part of a common-area project. The coordinator lists the work already supported by completion records, the unresolved items and the new vendor's proposed scope. The comparison reveals an item appearing in both the earlier records and the new proposal, so the business asks for clarification. The transition note does not decide liability, certify workmanship or claim a financing outcome.

Produce a current-scope cover note

Summarize what changed, what remains the same and which questions are still open. Point to the transition sheet and current source documents. Have the internal project owner check the note before it is used in a request update. The next-step guidance can help the business keep the proposed revision, the update sent and any actual acknowledgment distinct while the project record is brought into line.

The FrontDesk Funds operating-request service is unavailable in CT, FL, GA, MO, TX and VA. Equipment requests are unavailable in CA, VT, ND, MO, FL and GA. Other programs may have different restrictions; check the current request page.