Documenting a key-programming job from intake to handover

A well-documented key job should let another qualified technician understand what was requested, why the work was authorized, what the vehicle did beforehand, and what was verified afterward. A tool’s success message records one event within that job. It does not replace the intake record or the customer’s functional acceptance criteria.

Define the job and the words you use

Intake is the collection of the request, vehicle identity, existing conditions, and customer information. Scope is the agreed work and its boundaries. A baseline is the documented condition before changes. A post-check repeats relevant observations after work. Handover transfers the completed result, explanations, and records back to the customer.

Distinguish adding a spare from addressing a missing key, replacing a damaged remote, or diagnosing a no-start. The customer may use “program a key” for all of these. Write the intended outcome in functional terms: for example, “supply one spare with mechanical entry, equipped remote functions, and normal start authorization, while retaining the presented working key.”

Connect authorization to this vehicle and operation

Confirm the customer’s identity and authority to request the work using the applicable requirements. Match the vehicle’s VIN with the job documentation and resolve discrepancies before security operations. When a fleet, dealership, or repair facility requests service, establish who represents it and what vehicle-specific work is authorized. Keep sensitive customer records in the designated business system rather than in public photographs or lesson notes.

NASTF’s D1 guidance distinguishes customer, fleet, and contracting situations and requires customer and vehicle information before covered security work. Its paperwork rules concern specific registry transactions; they should not be restated as one universal legal form for every locksmith job. Confirm the current requirements for the operation. NASTF: Choosing a D1 Form.

For participating aftermarket scan-tool validation, NASTF describes a workflow that handles the D1 record through the tool while the technician remains responsible for verifying customer identity and ownership documents. Credential validation also does not establish technical vehicle coverage. NASTF: Scan Tool Validation FAQs.

Make the work reviewable before beginning

Record parts and labor scope, known limitations, and the plan if a pre-existing fault prevents completion. Confirm which existing keys must be present and whether the documented operation affects previously enrolled keys. If a missing key is part of the complaint, explain what the proposed operation will address, including the separate status of mechanical access. Do not promise that an unpresented key was physically tested.

Establish the baseline and prepare the vehicle

Test presented keys individually under the applicable conditions. Record mechanical entry, requested buttons, equipped proximity functions, and normal starting or ready state. Mark a function “not tested” when it was not tested. Photograph existing visible damage when relevant and authorized. Use the manufacturer’s precautions to prevent unintended movement or a lockout during checks.

Where supported and appropriate, save a pre-service diagnostic report. Snap-on advises retaining important diagnostic information before clearing codes because clearing can remove associated records. A pre-existing code belongs in the baseline; it should not be silently relabeled as a fault caused by the new key. Snap-on: Working with Trouble Codes.

Confirm the exact procedure and its prerequisites, compatible parts, tool support, credentials where required, communication needs, and vehicle power requirements. Prepare the approved support equipment according to the vehicle and equipment instructions. Record the procedure reference used. Read the whole procedure before entering an operation with consequences for existing keys.

Execute within scope and verify the result

Follow the authorized manufacturer or supported tool procedure. Record the operation, time, outcome, and relevant messages without copying security credentials into ordinary job notes. If the process stops unexpectedly, preserve the message and vehicle state and follow documented recovery guidance. Repeating an unexplained attempt is not a recovery plan.

Repeat the acceptance checks on each key that should remain usable, including existing keys. Follow the vehicle’s instructions for isolating keys during recognition checks. Confirm mechanical and electronic functions independently. Compare the post-service diagnostic record with the baseline where appropriate; document unresolved findings instead of making a blanket “all clear” claim.

Hypothetical case: a spare with an existing defect

A customer presents one key and requests a spare. Before service, its unlock button works intermittently, but its other requested functions pass. The technician records that condition and agrees that repairing the original remote is outside this job’s scope. After the authorized spare operation, the new key passes every agreed check. The original retains its prior functions and the documented intermittent button issue.

The handover explains both results. “New spare verified; original unlock-button concern remains as documented at intake” is accurate. “Both keys perfect” would contradict the observations. The customer receives the keys, itemized work record, relevant owner instructions, and the stated next step for the unresolved concern.

Common mistakes and practice

• Promising a result before checking application and prerequisites.
• Recording the new key but forgetting existing keys.
• Treating a tool success screen as the entire final inspection.
• Leaving an unperformed check marked as passed.

Practice: the new key starts the vehicle, but its mechanical blade was never tested. Is the requested complete spare finished?

Continue your learning

• Automotive key compatibility: build an evidence chain
• When a key does not work: diagnose the symptom first
• Electrical fundamentals for automotive key technicians