LidLog
How to document a change before it gets lost in the job notes
Small changes are easy to lose when they live in several messages and someone’s memory. Keep a short record that connects the original scope, the new request and the decision still needed.
Start with the original scope
Reference the estimate, work area or task being changed. Explain what was originally included. A change is easier to review when the reader can compare it with a clear starting point.
Describe the requested difference
Write down what is being added, removed or replaced, with quantities and locations where useful. Identify who requested it and when. Separate confirmed instructions from items that are still being considered.
Record effects and decisions separately
Note possible effects on materials, price and scheduling, and label anything that is still an estimate. Keep the actual approval record in the project file. A daily-report note should not be treated as proof that a customer accepted a revised price.
Carry the decision into the next document
Use LidLog’s Daily Report for the day’s factual record and the Estimate Generator when you need to describe revised proposed work. Cross-reference document numbers in the notes. Before preparing the invoice, check that it reflects the agreed scope and does not count the same work twice.
Review checklist
- Original scope referenced
- Requested change described precisely
- Requester and date recorded
- Unconfirmed effects labeled
- Decision record retained and later documents checked