The Employer Contact Log in a Labor Market Survey

The deposition question that ends a labor market survey

A vocational counselor testifies that three employers confirmed openings for a modified-duty machine operator role. Opposing counsel asks a simple question: "What did the employer actually say to you, and when?" The counselor's file has a summary paragraph written two weeks after the calls, no dates, no names of who was reached, no distinction between a hiring manager's confirmation and a receptionist's guess. The survey doesn't get thrown out on the spot — but its weight collapses, row by row, under a question the counselor can't answer with a record instead of a memory. By the end of this article you'll know exactly what belongs in an employer contact log so that question has a one-line answer instead of a shrug.

The contact log is the survey, not a task log for it

It's tempting to treat the employer contact log as internal bookkeeping — a to-do list of calls made, checked off and forgotten once the narrative report is drafted. That's backwards. The contact log is the evidentiary core of a labor market survey. The narrative report is the summary; the log is the source document the summary has to be traceable back to. If a reviewing party, a hearing officer, or opposing counsel can't match every claim in the report to a specific, dated, attributable row in the log, the report is an assertion, not a survey.

This matters more in a labor market survey than in almost any other vocational work product, because the entire method depends on primary contact with actual employers about actual current openings — not a database lookup, not a job-board scrape. The contact log is the only artifact that proves that contact happened, when, and what was said. Everything else in the report — the wage range cited, the "yes, this position is available to someone with X restrictions" conclusion — inherits its credibility from the log entry it traces back to.

What belongs in every row

A defensible employer contact log captures the same fields every time, regardless of outcome. At minimum, each row needs:

• Date and time of contact — not the date the note was typed up.
• Method — phone, email, in-person, employer portal/job posting confirmation.
• Employer name and location.
• Contact person's name and title, or an honest note that the respondent's role couldn't be confirmed (a call answered by a general line is different evidence than a call with the hiring manager, and the log should say which one happened).
• Job title/position discussed, matched to the SOC/O*NET occupation the survey is testing.
• Verbatim or near-verbatim response — what the employer actually said, not the counselor's conclusion about what it means.
• Outcome classification — confirmed opening, no current opening, would consider given restrictions, refused to discuss, no answer/voicemail left, callback pending.
• Counselor initials on each entry, so authorship of the record is never ambiguous.

The pattern across all of these fields is the same: record the fact, not the interpretation. "Spoke with Maria Gonzalez, HR Coordinator, 2:15 PM 3/14 — confirmed one opening for Assembler I, $17–19/hr, would consider candidate with lifting restriction to 20 lbs with accommodation" is a defensible row. "Called ABC Manufacturing, seems open to it" is not — it can't be cross-checked against anything, including the counselor's own later memory of the call.

Capturing the employer's own words, not your paraphrase

The single most common weakness in employer contact logs isn't missing fields — it's paraphrase creeping in where a quote should be. A counselor writes "employer said the position would work for the client" when what the employer actually said was closer to "we'd have to see the specifics, but we've made accommodations like that before." Those are very different statements, and only one of them is what was actually said.

This is where a defensible labor market survey methodology earns its name: not through a more sophisticated wage calculation, but through discipline at the point of contact. Write down the employer's words during or immediately after the call, not from memory the next day. If the report later states "employer confirmed opening is suitable for restrictions X and Y," that sentence should be traceable to a log entry that actually contains language supporting it — not to a counselor's summary of a summary.

Handling non-responses, refusals, and voicemails

A contact log that only records successful contacts is a survey that looks stronger than it is — and that gap is exactly what a skeptical reader will look for. If ten employers were contacted and only four responded, the log needs all ten rows: the six non-responses, refusals, or unreturned voicemails belong in the record with the same date, method, and attempt detail as the successful contacts.

This isn't just honesty for its own sake. A survey's response rate and pattern of non-response is itself relevant information — a reviewer evaluating the survey's thoroughness will want to see that the counselor made a real, documented attempt at the full sample, not just the employers who happened to be reachable. Logging refusals also protects the counselor: "employer declined to discuss, cited company policy" is a very different fact pattern than a silent gap in the record that looks like the contact was never attempted at all.

Version control: when the log becomes the report

The contact log and the final narrative report are two different documents that need to stay reconcilable over the life of a case — which can run months or years through appeals, re-openings, or a second opinion request. If the report is edited after the survey period closes (a wage range gets refined, an occupation description gets clarified), the underlying log entries shouldn't be silently edited to match. The log is a record of what happened when it happened; the report is where interpretation and refinement belong, and it should be dated and versioned separately from the contact log it draws on.

Consistency in how a labor market survey is conducted end to end — same fields, same timestamp discipline, same separation between contact record and narrative — is what lets a counselor produce the same quality of survey on case 4 as on case 40, and what lets a supervising CRC or opposing expert reconstruct exactly what happened without asking the counselor to reconstruct it from memory on a stand. For the broader mechanics of building a survey that holds up this way, see our guide on labor market survey methodology and a sample report structure that shows how contact-log detail should surface in the final narrative.

Building the habit into your workflow

None of this requires exotic tooling — a disciplined spreadsheet with the fields above, used consistently, is a legitimate contact log. What breaks down in most private-practice settings isn't the format, it's consistency across counselors and across a growing caseload: one counselor's log has ten fields, another's has four, and six months later nobody can say which template applies to which case type. That inconsistency is where defensibility erodes, not in any single missed field.

If your practice is still rebuilding this log from a blank spreadsheet on every case, our Labor Market Survey Documentation Kit packages a structured contact-log template alongside the narrative-report scaffolding it feeds into, so the same fields get captured the same way every time. For practices running enough labor market surveys that a shared, structured contact record across the whole caseload has become the real bottleneck — not just one report, but every report — Rehabilitation Management Suite builds the employer contact log directly into case workflow, tied to the same file the wage analysis and final report draw from. If that's closer to where your practice is, a demo is the fastest way to see whether it fits before you commit to changing how the whole team documents contacts. And if you're earlier in scoping what a full survey needs to include, our overview on labor market surveys in vocational rehabilitation is a good next stop.