Fixing a wrong delivery date without losing the old answer

Someone entered the invoice date as the delivery date. It happens all the time. The fix is easy, you type the right date in. The problem shows up later, when the next person sees a deadline that doesn't match the reminder that went out last week and has no idea why.

First, keep two things separate. A correction fixes the record of something that already happened. A new event is additional furnishing, a termination, something that actually occurred on the job. Swapping in the real delivery date doesn't create new furnishing on the day you edit it. Florida's §713.01(12), for one, excludes correction of prior deficiencies from final furnishing.

Then keep one row per correction: the project and field, the before value and its source, the after value (or "unknown" if the evidence doesn't settle it), the evidence, the reason, who reviewed it, the fresh calculation, and which reminders and tasks need reconciling.

A fictional example. A job used October 7 as final furnishing because that's when the invoice went out. Dispatch finds the delivery ticket, dated October 3. The ledger says "October 7 → October 3," lists both references, names the reviewer, and stores the old result next to the new one. Don't overwrite the source ticket to match.

The full workflow is here: how to correct a project date and keep the calculation history.