Keep Vehicle Software Update Records

Record every vehicle software update as its own dated event, separate from oil changes, inspections and other maintenance entries. Each entry should capture the vehicle's identity, the date the update was reported, who reported it, any version or campaign identifier you actually have, the exact outcome as stated, and a reference to the notice or service paperwork that supports it. This applies whether you drive a Mercedes-Benz, a Ford F-150 or another vehicle. The brand changes where the evidence comes from and which identifiers appear on it. It does not change the structure of the record.

Key terms

• Software update: a change to the programming of one or more of the vehicle's electronic control modules, such as infotainment, driver assistance, powertrain or body electronics.
• Over-the-air (OTA) update: an update delivered wirelessly to the vehicle instead of being installed by a technician. Ford brands its OTA updates as Power-Up, and Mercedes-Benz also offers wireless updates on many connected models. Which modules can be updated this way depends on the model, model year, market and equipment.
• Campaign: a manufacturer-organized action covering a defined group of vehicles. It may be a safety recall, a non-safety service action or a customer satisfaction program, and it usually carries its own identifier.
• Repair order: the shop's document for a service visit. A dealer-installed update often appears as one line on a repair order that also lists unrelated work.
• VIN: the 17-character vehicle identification number. It is the most reliable way to tie an update record to one specific vehicle.

Why updates need their own record

Software updates and maintenance follow different logic. Maintenance is interval-based work such as fluids, filters and brakes. An update is an event with its own source, identifiers and completion evidence. When an update is buried inside a general service entry, three problems follow. Its identifiers get lost. You can no longer tell an offered update from a completed one. And it becomes tempting to connect unrelated changes.

That last risk matters. Owners sometimes notice that a maintenance history shown in an app, the instrument cluster or an online account looks different, or appears to be missing, around the time of an update. A record should log that observation as a separate dated note. It should not state that the update erased, changed or restored the history unless the manufacturer or the shop says so in writing. If the history display matters to you, for example before selling the vehicle, ask the dealer or manufacturer directly. Keep your own records regardless of what any app shows.

What to record for each update

Field	What to enter	Notes
Event ID	A short unique label, such as U-01, U-02	Lets you cross-reference paperwork and later notes
Vehicle identity	VIN, make, model, model year	Copy the VIN from the registration or paperwork, not from memory
Reported update date	The date the update is said to have happened	Use the date printed on the document if there is one
Date recorded	The date you made the entry	Shows how fresh the information was
Reported by	The owner, the vehicle's on-screen notice, the app, or a named dealer or shop	Distinguishes your own observation from a business's statement
Version or build	Software version exactly as shown	Write "not supplied" if absent; never guess
Campaign identifier	Recall, service action or program number exactly as printed	Write "not supplied" if absent
Module or system	Infotainment, driver assistance, powertrain and so on, if stated	Only what the source names
Reported outcome	The exact wording, such as "completed", "failed", "pending" or "offered"	Quote rather than paraphrase
Supporting evidence	Repair order number, notice, screenshot, letter	Attach or file a copy and note where it is stored
Linked service visit	Repair order or maintenance entry from the same visit	Link by reference; keep the update as its own event
Open questions	Anything to clarify with the shop or manufacturer	Add the answer and its date when you receive it

Offered, reported and documented are different outcomes

The most useful habit is to record exactly how far the evidence goes. There are three distinct levels:

• Offered: a notice, letter, app message or on-screen prompt says an update is available or required. This does not show that anything was installed.
• Reported installed: someone states that the update was done. This could be a dealer advisor on the phone, a vehicle message saying the update succeeded, or your own observation. Note who made the statement.
• Documented complete: a document explicitly records completion, such as a repair order line that names the campaign or update and shows it as performed, or a written confirmation from the dealer or manufacturer.

Do not upgrade an entry beyond what its evidence shows. A screenshot of a "software update available" message stays at "offered" until something shows otherwise. A repair order that mentions a software update without naming a version supports "dealer reports completed" but leaves the version field blank.

Step-by-step: documenting an update

• 1. Create a new event ID before you write anything else, even if the update happened during a larger service visit.
• 2. Enter the VIN and the vehicle description from an official document.
• 3. Record the reported update date and, separately, today's date as the date recorded.
• 4. Note who reported the update and how: dealer paperwork, a phone call with a named advisor, a vehicle notification or an app message.
• 5. Transcribe any version, build or campaign identifiers character for character as supplied. Mark each missing identifier "not supplied".
• 6. Quote the outcome wording exactly.
• 7. Attach or file the supporting paperwork: scan the repair order, photograph the screen, save the letter or email. Record each file's name or storage location in the entry.
• 8. If the update happened during a service visit, reference that visit's repair order in both records rather than merging them.
• 9. List open questions, such as a missing version number or unclear completion status, and ask the issuing dealer or the manufacturer.
• 10. When you get an answer, add it with the date and the name or role of whoever provided it. Leave the original entry intact so the record shows how the information developed.

Example entry (hypothetical)

The following example is invented for illustration. A dealer tells the owner that a software update was completed on 4 November. The repair order, RO-123, lists the update but prints no version number. Weeks later, the owner notices that a maintenance item no longer appears in the vehicle's app.

Event ID:          U-01
Vehicle:           [VIN] / [make, model, model year]
Reported date:     4 November
Date recorded:     [date entry was made]
Reported by:       Dealer service department (repair order)
Version/build:     not supplied
Campaign ID:       not supplied
Module/system:     not stated
Reported outcome:  "dealer reports completed"
Evidence:          RO-123 (scan filed as U-01_RO-123)
Linked visit:      RO-123 also covers routine maintenance; see maintenance log
Open questions:    Request version/build and any campaign number from dealer
Follow-up:         [date] - [answer received, from whom]

Separate note N-01 ([date observed]):
  Owner observed a maintenance item missing from the app.
  No link to U-01 established.

The entry stores the outcome at the level the paperwork supports and leaves the version blank instead of guessing. The app observation goes in its own note, with no assumption that the update caused it.

Mercedes-Benz and Ford F-150 owners: where the evidence comes from

Both brands can deliver some updates wirelessly and others through a dealer visit. The two routes leave different paper trails. A dealer-installed update normally appears on a repair order. An OTA update may leave only an in-vehicle confirmation, an app or account entry, or an email. Those can be lost or overwritten, so screenshot or save confirmation messages when they appear. Which systems update wirelessly, what version information the vehicle displays, and how a completed update shows up in the owner app or account all vary by model, model year and equipment. Ask a Mercedes-Benz or Ford dealer, or the manufacturer's customer support, what applies to your VIN.

Useful questions to put to the dealer or manufacturer:

• Which software version or campaign identifier applies to this update on my VIN?
• What document or record confirms completion, and can I get a copy?
• Was the update delivered over the air, at the dealer, or both?
• Are any other campaigns or updates still open on this VIN?

In the United States, if an update is part of a safety recall, you can also check the VIN against the federal recall lookup run by the National Highway Traffic Safety Administration. That lookup shows open safety recalls, not every software update. Record the NHTSA campaign number and the manufacturer's own recall number as two separate identifiers, since they often differ.

Keeping the record useful over time

• Keep one log per vehicle, with update events and maintenance entries in clearly separate sections or files.
• Name evidence files with the event ID so a scan cannot drift away from its entry.
• Never overwrite an entry; add dated follow-ups so the history of what you knew, and when, stays visible.
• Keep copies outside the manufacturer's app or account, since you do not control how those display past events.
• When you sell the vehicle, pass on copies of the update log and its evidence along with the maintenance records.