What this guide covers
A vehicle-key worksheet separates identification from symptoms. It helps you explain whether the request concerns a spare, all keys missing, remote buttons, mechanical entry, or recognition for starting. Those are different functions, and “the key does not work” is often too broad for an initial service assessment.
Keep the worksheet private. Vehicle identifiers and ownership documents may be needed through an agreed verification process, but they do not belong in a public message or general photograph. The service team must confirm support for the exact vehicle and key system.
Set the boundaries before you begin
Record the year, make, model, and start type first. Say whether the vehicle uses a key turned in an ignition, a push-button start, or another manufacturer-described system. Note whether any working key remains and whether the vehicle is currently accessible.
Identify the owner or authorized user who will participate in verification. If ownership documents are inside a locked vehicle, explain that situation during the enquiry. Arrange the approved verification and service process instead of assuming possession of a damaged key is sufficient authority.
Describe each function separately
Record remote lock and unlock behavior, mechanical blade operation, and the start function in separate fields. A key can perform one function while another fails. Include the exact observable message or indicator in plain language if the vehicle displays one.
Say whether another known working key performs the same functions. A comparison may help the service enquiry, but do not alter or test unfamiliar programming sequences. Follow only the correct owner-manual guidance for any manufacturer-supported battery or backup-start procedure.
Define the requested outcome
For a spare, list the functions it must provide and keep the reliable existing key available for the assessment. For all keys missing, state that clearly. Ask about replacement, duplication, and programming only as relevant supported components of the request.
If you only need authorized access to a locked vehicle, identify it as a car-lockout request. If a key is also required afterward, add that scope explicitly. Opening the door should not be mistaken for restoring every key function.
Record parts without making assumptions
If the existing fob has a visible model or part marking, report it through the agreed private channel. Do not buy a visually similar replacement before compatibility and the supported programming route are confirmed. Vehicle configurations and supplied key versions can differ.
Keep any information about a previous replacement or repair if available. Tell the team when a symptom began and whether the key suffered visible damage. If an electrical starting or vehicle fault may remain outside locksmith service, record that distinction for the appropriate provider.
Plan access to the vehicle
Describe where the vehicle is parked and who can authorize access to that location. A controlled garage or restricted area may require another contact. Ensure the service position is safe and permitted; a roadside emergency may need an appropriate immediate assistance route.
Have the vehicle and all relevant existing keys available at the agreed visit. Ask which functions will be tested at handover and how any missing-key concern will be addressed for the particular system. Do not assume a newly supplied key automatically revokes every old one.
Copy and use this worksheet
Use one record for each opening, vehicle, user, or project item covered by this guide. Write “unknown” where information is missing, rather than guessing. Keep this working record private; it is an administration aid, not a place to publish combinations, usable access codes, photographs of key cuts, or personal identification documents.
- Vehicle year, make, model, and start type: ____.
- Private vehicle identification record location: ____.
- Owner or authorized user and verification arrangement: ____.
- Working keys remaining: ____; all keys missing: yes / no.
- Remote buttons: _; mechanical blade: _; starting: ____.
- Observed message or indicator and date first noticed: ____.
- Known key/fob markings or previous replacement: ____.
- Requested result and functions to be supplied: ____.
- Vehicle location, access contact, and restrictions: ____.
- Handover tests, supplied key identifiers, and unresolved vehicle issue: ____.
Complete the review and keep a useful record
During handover, test the agreed functions of each supplied key and any existing key included in the plan. Record the result rather than simply noting that a key was delivered. Keep manufacturer-specific battery and backup instructions with the vehicle records.
If a later problem occurs, update the symptom fields while preserving the earlier service information. The family vehicle spare-key guide can help assign custody once a reliable supported spare has been supplied.
A completed symptom summary can be short
A hypothetical key report might say: vehicle year, make, and model recorded privately; push-button start; one existing fob; remote buttons work; mechanical access available; starting intermittently reports no key; no generic programming attempted. The report does not diagnose the cause, but it separates functions and gives the service team a clearer supported-service question.
For all keys missing, use a different summary: no working key remains; vehicle locked; ownership verification to be arranged; service position and access contact identified; replacement and recognized start function requested. These two situations should not be sent as the same vague “need a key” message.
Once work is completed, add the actual functions demonstrated and any remaining vehicle issue. A later enquiry can then distinguish a newly failed remote button from the earlier start symptom. Keep sensitive identifiers and verification documents in the approved private record instead of copying them into a general family message.
Related service information
For the work discussed here, review car key programming and lost-car-key preparation. Describe the actual situation to the team before choosing a service scope.