The transaction got a delay. The clock has run. It is the morning of day four and the customer is standing at your counter asking if he can take his rifle home. The law says you may proceed. The question is whether your shop should, and whether the person behind the counter knows the answer without calling you.
That second part is where shops get hurt. The default-proceed window is not just a legal threshold, it is a counter decision that gets made on a busy Saturday by whoever is standing there. If you have not written it down, you have left a license-level call to improvisation.
What the clock actually is
Under 18 U.S.C. § 922(t)(1)(B)(ii), if NICS has not returned a proceed or a denial, you may transfer after three business days have elapsed. Business days exclude Saturdays, Sundays, and federal holidays. The check itself is required by 18 U.S.C. § 922(t).
A few things staff get wrong, and each one is a finding waiting to happen:
- They miscount the days. A delay logged Friday afternoon does not clear on Monday. Saturday and Sunday do not count, so the third business day lands later than people assume. Add a federal holiday and the math moves again.
- They treat "may" as "must." Federal law permits the transfer on day four. It does not require it. That gap is your policy space.
- They forget state law. Some states impose a longer wait or prohibit default proceeds outright. Federal permission does not override a stricter state rule.
None of that is exotic. It is exactly the kind of predictable, trainable detail that an inspection sample pull will surface if your records are sloppy about it.
The decision the law leaves to you
Because the statute says "may," your shop has to choose a posture and apply it consistently. Three common ones:
- Proceed on day four. Lawful, and the customer gets the firearm. You accept the risk that NICS later returns a denial after the transfer, which triggers a retrieval referral and a record you do not want to be sloppy about.
- Hold for a defined window past day four. You wait a set number of days for NICS to finish before transferring. This trades a delayed sale for fewer post-transfer surprises.
- Do not proceed on a delay at all. Some shops simply wait for an affirmative proceed. The cleanest from a denial-risk standpoint, the slowest for the customer.
There is no single right answer. There is a wrong answer, which is having no answer and letting each staffer decide on the fly. Pick a posture, write it down, and make sure every person who runs a 4473 knows it cold.
What a usable policy looks like
A default-proceed policy that staff can actually follow is short, specific, and removes judgment from the counter:
- State the posture in one sentence. "We proceed on the fourth business day," or "We hold delayed transactions for X additional business days," or "We do not transfer on a delay." No ambiguity.
- Show the day count with an example. Spell out how to count business days, with holidays excluded, using a worked example tied to your own calendar.
- Name the state-law overlay. If your state restricts default proceeds, say so right there so nobody has to remember it under pressure.
- Define the escalation. Who gets called before a delayed transfer goes through. If the answer is "nobody, follow the policy," say that too.
- Cover the after-action. What happens if NICS denies after a lawful transfer, who handles the referral, and how it gets documented.
- Tie it to the record. The delay, the date, the count, and the proceed decision all need to land in the 4473 and your records correctly. Retention rules are long, so the entry you make today is the one an IOI reads years from now.
Write it once, and the Saturday call stops being a call.
A policy is only as good as the training behind it
Here is the gap. You can post a default-proceed policy by the NICS terminal and still have a new hire miscount business days in month two. The policy is the rule. Training is what makes the rule reflexive. "We covered it at orientation" is not a defense when the disposition record shows an early transfer.
The NICS clock does not live alone. It is one piece of getting Section A right, handling the check, and recording the disposition on time, which means inside the seven-day window at 27 CFR § 478.125(e). DealerReady's 4473 completion and recordkeeping course walks the form and the NICS handling line by line, including how the three-business-day window is counted and recorded. For the whole sales floor, Counter Certified stacks that with straw-purchase recognition and the other counter fundamentals, so every person running a transfer carries the same dated, verifiable credential.
That is the point of a credential over a conversation. When your carrier asks how you manage NICS and default-proceed risk, "we have a written policy and every counter staffer is certified on it" is an answer a carrier can audit and credit. DealerReady's review of FFL claims is blunt about this: the large majority trace back to documented counter and recordkeeping errors, not to bad intent. A miscounted clock is one of them.
None of this is legal advice, and it is not a substitute for the current ATF forms, instructions, and your state's rules. Confirm your state's default-proceed treatment, and bring in counsel where the stakes warrant it. What DealerReady gives you is the training baseline and the paper trail underneath your policy.
Write the policy. Train the count. Prove it.
Browse the course catalog to see what your counter staff should know cold, or look at shop plans to roll training out across the team and report it to your carrier.