The Unemployment Work-Search Log Reference, One Row per Activity Type

This reference is for anyone collecting unemployment while running a high-volume job search, who has to log a set number of work search contacts each week and keep proof that holds up if the state audits. Find the activity you did, check whether states usually count it as a direct employer contact, a secondary activity, or nothing, and save the evidence its row calls for before you certify. Rules differ by state, so every classification here names the state it comes from. Confirm yours before you rely on a row.

What counts as a work search contact for unemployment?

A work search contact is an action that puts you in front of a specific employer about a specific opening, usually an application or an interview. Most states set a weekly minimum of these. Everything else you do falls into a second class that some states accept toward the total, or a third class that counts for nothing.

The three classes used throughout this guide:

• Direct employer contact: an application, interview, or similar exchange with a named employer about an opening. This is what audits check with the employer.
• Secondary activity: something that supports the search without contacting a hiring employer, such as a job fair, networking, agency registration, or a career center workshop. States also call these work search activities or reemployment activities. Many states accept a limited number toward the weekly total.
• Nothing: activity the state explicitly excludes, such as browsing without applying or re-sending an application you already made.

Weekly minimums and where the log goes

The weekly count, the place you submit the log, and how far back the state can ask for proof all differ. Six states side by side:

Other states set the split between classes differently:

• North Carolina: at least three job contacts a week, and one of them can be a reemployment activity at a local career center.
• Connecticut: at least three work search activities, including at least one employer contact.
• Maryland: three activities with at least one direct employer contact (per a secondary source).
• Georgia: three new contacts with employers you have not contacted before.
• DC: 2 contacts per week, as listed by a job board's advice page.
• Pennsylvania: three or more applications can replace the separate activity.

A full, current count of how many states fall into each band is not published anywhere I could find. If you need one, build it from the U.S. Department of Labor's Comparison of State UI Laws and check each state's own work search page.

The unit of count is where high-volume searchers get caught

States do not agree on what one contact is. Ohio and Georgia count employers, while Virginia, Connecticut and New Mexico count openings. Applicant tracking systems, the software employers use to receive applications, create one record per requisition (one posted opening), so five applications to one company look like five contacts in your tracker. In an employer-based state, that can be one contact.

The fix is to tally two numbers every week: distinct employers and distinct openings. Certify against the one your state uses. If quotas are pushing you toward volume for its own sake, Refolk scores how well you actually fit each posting, which helps you spend the required count on openings you have a real chance at instead of padding the log.

The activity reference: one row per thing your search produced

In most states, applications and interviews with a named employer count as direct employer contacts. Agency work, job fairs, networking and workshops usually count as secondary activities, and reapplications, check-in emails, browsing and blind-ad replies usually count for nothing. Find your activity below, then read its notes.

Activities that usually count as a direct employer contact

Activities that are usually secondary

Activities that usually count for nothing

One-click applies and auto-apply tools

What it proves: that you sent an application to a named employer for a named opening on a date. None of the state sources I reviewed singles out one-click applications or any job board by name. They classify by who you contacted and about what, so an Easy Apply that reaches a named employer for a specific opening is an application.

How it lies: Idaho, Ohio and Virginia reject applications not made the way the employer instructed. If the posting says to apply on the employer's own site, whether a one-click submission elsewhere meets that test is not established. Save the posting's application instructions so you can show which channel it asked for. Auto-apply tools are not addressed by any source I found. Their risk is mechanical: they can send applications you never saw, repeat employers, or submit to listings that hide the employer's name. Log only applications you can match to a confirmation.

Save: the confirmation email (Virginia asks for an email confirmation if you applied online) and the posting URL (Maine requires it). If you tailor a résumé per posting in Refolk, file that version with the log row. It ties the application to a named employer and title.

Referral asks and networking

What it proves: that you worked your network. Pennsylvania counts networking as a secondary activity. It becomes a direct employer contact only when it produces an application or an interview, and that application or interview gets its own row.

How it lies: Idaho excludes simply asking a business if it is hiring. A message that asks "any openings?" without a specific role or application behind it is the weakest thing you can log.

Save: the person's name, company, date, and the role you asked about.

Job fairs, workshops and pre-employment tests

What it proves: attendance. Pennsylvania counts job fairs, and taking a civil service test or other pre-employment test, as secondary activities. North Carolina allows one career center reemployment activity per week, and Ohio records reemployment activities through OhioMeansJobs.

How it lies: a booth conversation logged as an employer contact. If the fair led to an application, log the application separately. The fair itself stays secondary.

Save: the registration email, attendance confirmation, or test confirmation.

Gig and self-employment bids

This is the clearest direct contradiction between states. Pennsylvania says a self-employed person's bid for work qualifies as a work search activity. Idaho excludes seeking self-employment or 1099 gig work. Only your own state's rule decides. Generic lists will mislead you here.

Can I apply to the same company twice for unemployment?

Sometimes. Virginia, Connecticut and New Mexico count a different opening at the same employer as its own contact. Ohio, by an attorney's account of agency practice, counts several roles at one company in a week as one application. Reapplying to the same posting almost never counts.

Two definitions sharpen this:

• Utah defines a new contact as a new employer, or a newly listed opening at an employer you contacted before.
• Georgia requires three new contacts with employers you have not contacted before.

Ohio also treats one online application to a company with many locations as one employer. If you applied to the same retailer's stores in three cities through one portal, that is one row.

Interview rounds are the documented way back in

The legitimate way to count the same employer twice is to move forward in its process. Idaho lets an employer count again once you have progressed to the next level of hiring. Connecticut treats an interview as an employer contact, and Pennsylvania lets an interview substitute for an application or an activity. A follow-up email that does not move you forward earns nothing in Idaho. Log the stage name on every repeat-employer row: "phone screen", "hiring manager interview", "panel".

Reposted jobs

A posting that reappears looks like a new opening. Pennsylvania rejects a repeated application for the same job unless there is reason to believe the employer's hiring circumstances have changed. Before counting it, check whether the posting carries a new requisition ID or a new posting date. Save both versions if it does.

Agency submissions and recruiter screens

An agency submission, or a screen with an agency recruiter, is usually a secondary activity rather than an employer contact, because the agency is not the employer. Pennsylvania classes using an employment agency as an activity, not an application, and Idaho counts registering with a staffing service, recruiter or placement agency as a valid action.

This matters more than most searchers expect, because a large share of the recruiters who call you are not employed by the company that is hiring.

These figures come from Refolk's index of professional profiles. They cover US profiles titled Recruiter, Technical Recruiter or Talent Acquisition. The share is likely an undercount: some of the top employers in the all-industry segment, such as Experis and K2 Partnering Solutions, are staffing firms that are not filed under the staffing industry.

How to classify the call

• The recruiter works for the hiring employer: this is an interview or employer contact. Connecticut counts it as an employer contact. Log the employer, the recruiter's name, and the stage.
• The recruiter works for an agency and names the client: log it as agency activity, and record the client company's name and the role. If you later interview with the client directly, that interview is a separate employer contact.
• The recruiter works for an agency and will not name the client: Virginia rejects replies to blind ads that leave out the employer's name. Whether a state would treat an unnamed-client submission the same way is my inference, not a confirmed rule. Either get the client's name in writing or log the row as agency registration only.

Check the recruiter's employer from their email domain and signature before you log the row. Do not rely on what the job title in the message says.

What to write in the log, and what proof holds up in an audit

For every activity, log the date, employer, person contacted, contact details, position, method and result. Save evidence the state could use to confirm the contact with the employer. Verifiers contact employers, so the contact-details field decides more audits than any screenshot.

Georgia's field list is the standard, and Utah's is nearly identical:

1. Date
2. Company name or job reference number
3. Person contacted
4. Address, phone, email, or web link
5. Position title
6. Method of contact
7. Results of contact

Virginia adds an email confirmation if you applied online, and Maine requires the URL for online applications. Add two fields of your own, because the rules above make them decisive: requisition ID or posting date (for repeat and repost questions) and hiring stage (for repeat-employer rows).

Date:
Class (direct employer contact / secondary / not counted):
Employer name:
Job reference or requisition ID:
Posting date:
Position title:
Person contacted (name and title):
Contact route (phone, email, address, or web link):
Method (online application, interview, agency, job fair, workshop):
Hiring stage (applied, phone screen, interview round 2, etc.):
Agency client named? (yes, name / no):
Result:
Evidence saved (confirmation email, URL, posting copy, file name):

Where the log goes

• Inside the weekly certification: North Carolina requires you to record activities in MyNCUIBenefits before you can file. Connecticut, Arizona, Idaho and Georgia also collect it at certification.
• Through the state job bank: Maryland (Maryland Workforce Exchange) and Ohio (OhioMeansJobs reemployment activities).
• Every four weeks: Virginia telephone filers submit detailed written information every four weeks.
• On request only: Pennsylvania's Form UC-304 Work Search Record is a recommended personal record you produce if asked.

Which evidence carries weight

The Virginia Employment Commission verifies job contacts and wages with employers. Under the expired federal EUC program, states had to attempt to verify at least one work search activity per sampled week. Proof is strongest where an employer can confirm it.

Classification and evidence are two separate checks. An activity can be the right class and still fail because you cannot prove it, or be well documented and still not count.

How long to keep it

How far back the state can demand proof is set by state rule. It runs from the four weeks before the request in a Utah routine audit to two years in Arizona and Pennsylvania. Ohio requires 18 months, Virginia one year, and Colorado can audit for up to two years from the start of the claim, according to a secondary source. Follow the strictest period that could apply to you, not an average.

How work-search logs get rejected in an audit

Most rejected contacts fall into eight patterns. You counted requisitions instead of employers, reapplied to a reposted job, logged check-in emails, logged an agency submission with no client named, applied the wrong way, logged a gig bid in a state that excludes them, bunched activity onto too few days, or discarded records too early. Each has a check you can run before certifying.

1. Several one-click applies at one company. Your tracker shows three rows, but Ohio counts one. Check: count distinct employers, not requisitions.
2. Reapplying to a reposted job. It looks new, but Pennsylvania rejects it unless hiring circumstances changed. Check: is there a new requisition ID or posting date?
3. Check-in emails. Idaho rejects them unless you have advanced a stage in the hiring process. Check: log the stage name, and drop the row if the stage did not change.
4. Agency submission to an unnamed client. It may be treated like a blind ad under Virginia's rule. This is an inference, not a confirmed rule. Check: record the client's name, or log it as agency registration instead.
5. Applying the wrong way. A walk-in résumé where the employer says "apply online" is rejected in Idaho, Ohio and Virginia. Check: save the posting's application instructions.
6. Gig bids. They count as an activity in Pennsylvania but are excluded in Idaho. Check: your state's own rule, not a generic list.
7. Day clustering in Arizona. Four applications on Monday fail the four-different-days requirement. Check: dates spread across the week.
8. Discarding records too early. Keeping one year of records in a two-year state such as Pennsylvania or Arizona leaves you exposed. Check: use the longest period that applies.

What a failed or unverifiable week costs

• Denial and overpayment: Virginia says missing the required count could result in a denial of benefits and a possible overpayment.
• Fraud penalty: federal law (TAAEA Section 251, amending SSA 303(a)(11), explained in UIPL 02-12) sets a penalty of not less than 15 percent of the erroneous payment when fraud is found.
• No waiver for fraud: DC applies its 15 percent penalty to payments made on or after October 21, 2013, and fraud overpayments there are not eligible for a waiver.
• Not responding: Utah says benefits may be denied if you do not take part in an audit.

How an audit usually runs

What is and is not known here:

• The only published sampling rate I found covers the expired federal EUC program: 0.5 percent of paid weeks, producing between 50 and 1,500 samples. Sampling rules for regular state UI are not established in public sources. Do not assume your odds are low.
• In Maryland, the agency must issue a work search determination before any appeal hearing can be held.
• A secondary source puts Utah's appeal deadline at 15 calendar days. Confirm it on your own determination notice.
• Appeal procedures across states are not established in the sources I found. The deadline printed on your notice is the one that governs.

The weekly logging procedure

Read your state's rules once. Then each week, do the activities, capture evidence, log, enter the log, and certify, in that order. Most of the time goes into the activities themselves. The logging adds about two minutes per activity if you do it as you go.

Step 4 is the one people skip, and it is the one that cannot be redone later. Postings come down, confirmation emails get buried, and the recruiter's name is gone by the following week. If your applications run through Refolk, the posting and the tailored résumé and cover letter drafted for it are already together. Add the confirmation email and the log row is complete.

Before you certify, and how to keep this reference current

Before each certification, tally the week against your state's unit of count, run the checklist below, and fix any row that fails. Re-read your state's rules at the start of every claim, because the numbers here are set by state rule and change. Idaho, for example, now requires five actions where it used to require one or two.

Week (start date and day per state rule):
State weekly minimum:
Direct employer contacts required:
Distinct employers contacted:
Distinct openings applied to:
Direct employer contacts with full evidence:
Secondary activities logged:
Days with at least one activity (Arizona: need 4):
Repeat-employer rows, each with a new stage or new opening:
Rows moved to "not counted":
Logged in state portal or job bank (yes / no / not required):

Keeping the rules current

• Primary sources: your state agency's work search page and FAQ, and the U.S. Department of Labor's Comparison of State UI Laws. Ranking job-advice pages often stop at counts and fields, and some are years old.
• What to re-check: the weekly count, the employer-contact quota, the unit of count, the day-spread rule, and the retention period. Those five drive almost every row in this guide.
• When to ask the agency: if a row in this reference says "not established" for your state, ask the agency through its claimant channels and keep its written answer with your log. Do not plan on finding an adjudicator through your network. In Refolk's index, a search for unemployment insurance adjudicators, examiners or investigators returned only 6 US profiles, which is too few to be useful. The agency's own published guidance is the record that will matter in an audit.