Skip forward into hiring notes
RosterAcorn

Good-faith records: 3 limits Arizona and Delaware set

You have an applicant's file open, a search result on screen that looks like a match, and a hiring decision due on Friday. Before you write anything into the file, two state laws ask questions you may not have considered: how you formed your belief, and what you may tell your staff. This post walks through three limits that Arizona and Delaware set on good faith in those two areas. It is general information, not legal advice. Check your own situation with counsel before you change a process.

Limit one: sincerity is not enough

Arizona defines the term in its definitions section, A.R.S. 23-493. The line that matters most for recruiters is short: "Good faith does not include a belief formed with gross negligence."

Practice stepWhat it answers
Match on more than one identifier, not just a nameWhether the record belongs to the applicant
Note where the information came from and when you looked it up How the belief was formed
Ask whether the record is current before you rely on itWhether the belief still holds
Pause when a result is unexpected or harmfulWhether verification is needed before deciding

That sentence sets a floor under the phrase. Good faith is not just a sincere belief. If the belief was formed carelessly to that degree, the definition says it does not count. The text gives no checklist for what that looks like in every case, so the practical question is how you reached your belief, not only whether you honestly held it.

Consider a common hiring workflow. A recruiter finds a result on a search engine, sees a name similar to the applicant's, and writes a note in the applicant's file. The recruiter means well, and the note reads like settled fact. The definition asks a different question: was the belief formed with care? Sincerity does not answer it.

Here is a simple way to keep beliefs well founded:

  • Confirm that a record belongs to the applicant before you act on it. Match on more than one identifier, not just a name.
  • Note where the information came from and when you looked it up.
  • Ask whether the record is current before you rely on it.
  • Pause when a result is unexpected or harmful to the applicant. A surprising result is a reason to verify, not a reason to decide.

That last point deserves emphasis. Carelessness is easiest to see in hindsight, after a decision has been made on a shaky basis. A short verification step built into your process is the simplest way to stay on the right side of the line.

Limit two: official records anchor a file, but not the whole list

The same definitions section lists sources that can support a good-faith belief. Two items are quoted here:

  • "(e) Records of government agencies, law enforcement agencies or courts."
  • "(g) Other information reasonably believed to be reliable or accurate."

Item (e) names official records. If you are looking at a record from a government agency, a law enforcement agency, or a court, you are in a category the definition names directly. That makes official records a natural starting point for an applicant file.

Item (g) is a catch-all, and its wording matters. The two words doing the work are "reasonably" and "reliable." The catch-all is not permission to use any information you happen to find. It ties back to limit one. You need a reasonable basis for trusting the information, and that basis has to hold up on review, not merely be convenient.

This has two consequences for recruiters:

  1. An official record is a strong anchor, but it still has to be the right record for the right person. A court or agency record can exist and still concern someone with the same name. Confirm the match before you rely on it.
  2. For information outside the official categories, ask what makes it trustworthy before you use it. Who published it? Would a reasonable person in your role rely on it? Did you check it against something else?

A useful habit is to write a one-line note for each record in the file: the source, the date you pulled it, and why you matched it to the applicant. The note shows your reasoning, and it lets a colleague spot a weak match quickly.

Consider two files. In the first, the note reads "county court index, pulled on the review date, matched on full name and a second identifier." In the second, the note reads "search result, matched on name." The two may look similar at a glance. Only the first shows how the belief was formed, and that is the reasoning the Arizona definition turns on.

Limit three: what Delaware lets employers tell staff

Delaware approaches the problem from the other side. Its provision concerns what an employer may share with its employees, and it appears in Title 19 of the Delaware Code. Three listed items matter most. Items (1) and (2) share the same opening, so item (2) is quoted in full and item (4) is quoted by its tail:

ItemApplies toLimit in the text
(1)Any employerOnly to the extent of the legal requirement
(2)Any employer Only information necessary for job duties
(4)Public entity employers onlyOnly policies or laws the public entity administers
  • (1) "An employer from communicating to its employees any information that the employer is required by law to communicate, but only to the extent of that legal requirement."
  • (2) "... any information that is necessary for those employees to perform their job duties."
  • (4) This item applies to an employer that is a public entity and reads, in part: "... any information related to a policy of the public entity or any law or regulation that the public entity is responsible for administering."

Item (1) matters most to HR staff who send required notices. Its limiting clause is the key part. The item reaches as far as the law requires and no further. If a law requires a notice to include certain information, the notice can include that information. Material the law does not require falls outside the item's coverage.

Item (2) covers information employees need to perform their job duties. The test is necessity, not interest. A notice about a schedule change or a system change that affects someone's work could fit that description. A general message on a topic staff find interesting does not automatically fit it.

Item (4) applies only to public entities. If your organization is a public employer, ask whether the notice connects to something your organization actually administers. If you are a private employer, read the full section, because this item is limited by its own terms.

Federal disability law offers a parallel warning about a related trap. The EEOC's page on the Americans with Disabilities Act quotes this statutory language: "Paragraphs (1), (2), and (3) shall not be used as a subterfuge to evade the purposes of subchapter I and III of this chapter [titles I and III]." ( U.S. Equal Employment Opportunity Commission) That text belongs to a different law, and it does not change the Arizona or Delaware rules. The lesson still transfers. A permitted category cannot serve as cover for the thing the law is trying to prevent. Wrapping opinions or unrelated commentary inside a notice labeled as required does exactly that.

The table below puts the quoted facts from both states side by side.

StateSourceWhat the quoted text says
ArizonaDefinitions section Sets the gross-negligence exclusion described in limit one.
ArizonaDefinitions section Names official agency, law enforcement and court records as a source category.
ArizonaDefinitions section Adds a catch-all for other information that has a reasonable basis for trust.
DelawareDelaware Code, Title 19 Item (1): required communications are covered, limited to the legal requirement.
DelawareDelaware Code, Title 19 Item (2): information needed for job duties is covered.
DelawareDelaware Code, Title 19 Item (4): public-entity employers may share information tied to their own policies or the laws they administer.
DelawareDelaware Code, Title 19 Authorizes civil actions in Superior Court and civil penalties for violations.

Enforcement: these limits have teeth

A limit on paper matters only if someone can enforce it. The Delaware provision, as quoted, includes the power, without naming who holds it, to "Commence civil actions in Superior Court for violations of this chapter, any published regulations, or for civil penalties provided herein." The portion quoted here does not describe the steps for bringing such an action, and it does not state penalty amounts. Read the full section and any published regulations before you assess your exposure.

What the quote does tell you is that violations can reach court. For a recruiter or HR team, the practical point is to treat the Delaware limits as operative law, not as suggestions.

The Arizona text works differently. The quoted material is a definition, and its effect depends on the provision that uses the term. Before you rely on good faith as a basis for action in a specific situation, check how that provision applies it and what it requires.

Practical steps for recruiters and HR staff

For recruiters reviewing public records:

  • Write down the purpose of each search before you start, and look only for what your process and the role call for.
  • Apply the same steps to every applicant. A consistent process is easier to defend than a series of one-off judgment calls.
  • Verify the match before a record enters the file.
  • Keep a source note for every record, as described above.
  • When a result is unclear, route it to HR or counsel instead of deciding alone.

For HR staff sending notices to employees:

  • Before you draft, name the legal requirement or the job need behind the notice. If you cannot name one, reconsider sending it.
  • If a notice is required by law, include the required information and stop there, as item (1) requires.
  • For job-related content, include what employees need to do their work, not everything that might interest them.
  • If you are a public employer, keep the notice within the scope item (4) allows, which is a policy or a law your organization administers.
  • Save a copy of each notice and record the date it went out and who received it.

Building a written process

Most problems with good faith come from informal habits. Someone pulls a record on a Friday afternoon, a manager forwards a memo with extra commentary, and nobody writes down why. A written process prevents much of this.

Start with a one-page procedure for public-record checks. It should name who may run a search, which sources are approved for which roles, what a match requires, and where the source note goes. Keep it short enough that people will actually read it. A long manual nobody opens does little good.

Next, define who reviews unclear results. A recruiter should not be the only person who decides whether a weak match is good enough. A second reviewer, often in HR or with counsel's guidance, catches the errors that are easiest to miss from inside a single search.

Build a standard form for staff notices. The form can include a line that asks the sender to state the legal requirement or job need behind the notice. A form makes the Delaware questions routine instead of one-off decisions.

Finally, review the process on a regular schedule. Laws change, vendors change, and staff turn over. A process written once and never revisited will drift from what the law requires. Use each review to check a few past files and notices against the procedure, and fix the gaps you find.

Training matters too. Walk new recruiters and HR staff through the three limits in this post using real examples from your organization, with personal details removed first. People remember a concrete case better than a rule read aloud. A short exercise works well: give the group two sample search results, one with a clear match and one with a weak match, and ask each person to write the source note they would file for each. The differences in those notes usually reveal gaps in a process faster than a policy review does.

If your team uses an outside vendor to run background or record searches, add the vendor to the review. Ask what sources it draws from, how it matches records to people, and how it handles records it cannot match confidently. Your process is only as sound as the sources it relies on, and a vendor's answers belong in your file just as a court index does. Keep the vendor's written answers with the procedure so a reviewer can see what you were told at the time.

Access controls belong in the procedure too. Limit who can run searches and who can see the results. Staff who do not need a record for their work should not have a copy of it. This is a general privacy practice, and it also makes the good-faith question easier to answer. A file that only people with a reason to see it can open is simpler to explain than one that circulates freely.

Common mistakes to avoid

  • Treating a search result as a verified record because it is public. Being public does not make a record correct or about the right person.
  • Adding opinions, background, or commentary to a required notice. The required-communication item covers the requirement itself and nothing more.
  • Assuming a notice that is useful to staff is automatically allowed. Usefulness and necessity are different tests.
  • Copying one state's rules onto the other. Arizona and Delaware have different texts and structures, and the quotes here do not cover everything either state requires.
  • Relying on a belief you did not check. The Arizona standard in limit one treats a belief formed with gross negligence as a failure, and a skipped check is often where that starts.

Wrap-up

Good faith is something you can show through your process. The Arizona definition tells you that a belief formed with gross negligence does not count, and that official records and reasonably trusted information can support a good-faith belief. The Delaware provision tells you what an employer may share with staff, limits required notices to what the law requires, and makes violations subject to court action.

The common thread is restraint. Match carefully, send only what the law or the job requires, and write down why. If your team operates in either state, bring this list to your counsel and ask them to confirm how it applies to your organization.

Sources