10 Sep Design Change Log
A capsule house design change log should connect every proposed change to a clear reason, affected scope, current documents, responsible reviewers, commercial and schedule review, decision, and final configuration. It prevents an informal message or marked-up image from becoming an uncontrolled instruction.
The contract defines who may request, price, design, approve and instruct a change. This log records decisions; it does not transfer authority or confirm that a change is technically acceptable.
Identify the Baseline Before Recording a Change
Record the order, unit, model, configuration, drawing revision and specification that form the current baseline. A request such as “move the window” is incomplete unless the team can identify the exact unit and accepted arrangement it would replace.
The capsule house RFQ checklist helps establish initial requirements. After agreement, preserve the accepted baseline and number later changes separately.
Describe the Request Without Assuming the Solution
State the buyer need, location, reason and required decision date. Attach a sketch or reference where useful, but distinguish the requested outcome from a proposed technical solution. The supplier and responsible project professionals may need to develop or reject alternatives.
Design Change Log Fields
| Control | Record | Decision question |
|---|---|---|
| Identity | Change number, unit, baseline and requester | What exactly may change? |
| Need | Reason, required outcome and decision date | Is the buyer need clear? |
| Review | Affected design, interfaces, approvals, cost and schedule | Have responsible parties reviewed it? |
| Decision | Accepted, rejected, revised or withdrawn; authority and date | Is instruction authority valid? |
| Closure | Updated documents and final configuration | Did every affected record change? |
Review Every Affected Interface
Ask responsible parties whether the proposal affects structure, envelope, utilities, interior layout, equipment, transport condition, lifting, foundations, permits, operation, maintenance or other contracts. Do not infer “no impact” because the visible change appears small.
Link technical documents through the supplier submittal register. Keep review comments and assumptions traceable until the decision is closed.
Separate Review From Instruction
A quotation, feasibility comment or revised drawing may support a decision but may not itself authorize work. Record commercial terms, schedule consequences and required approvals in the form established by the contract. Mark rejected and withdrawn options so they cannot be reused accidentally.
Reconcile the Final Configuration
After an accepted change, update every affected drawing, schedule, order item and site interface. At handover, compare the log with the final document package and identify unresolved items.
Keep a Clear Audit Trail
Preserve the original request, review responses, revised proposal and final instruction under the same change number. Record dates and named roles rather than relying on an inbox search. If several options were considered, identify which option was accepted and mark the others as not for use.
Review open changes at regular project coordination points. A change should remain open until affected documents and commercial records are updated, not merely until a verbal decision is reached. This helps purchasing, production, logistics and the site team work from the same configuration.
To request product-side review of a proposed configuration change, contact Rovellc with the order reference, affected unit, current revision and requested outcome. Final impacts remain subject to the agreement and project-specific review.