Food Handler Card Expiry: How to Track It [2026]

If you run a restaurant, café, grocery operation, care facility, catering business, or food production team, food-handler records can multiply quickly. New starters arrive, people move between sites, certificates sit in email inboxes, and a renewal date gets missed because everyone assumed somebody else was watching it.

This guide shows a practical way to track food handler card expiry across a team. It starts with a free spreadsheet and shared-calendar method. It also explains when a proper certificate expiry tracker is worth the change.

One important caution: food-safety requirements are not identical everywhere. The FDA Food Code is a model used by jurisdictions, not a single nationwide expiry rule. Always confirm the requirement with your state, local authority, employer policy, or training provider. The FDA explains the Food Code's model role here.

1. Define exactly which food-safety records you track

Start by listing the records that need a date, evidence, and responsible person. Do not put every food-related document into one vague “training” bucket.

Your register might include:

• Food handler cards or certificates
• Food protection manager certifications
• Allergen-awareness training
• HACCP or food-safety training records
• Site-specific induction or hygiene training
• Temperature-control or food-safety refresher records
• Medical or occupational records, where your local rules require tracking them

Create one record for one person and one certificate or training requirement. If Jordan holds a food handler card and a food protection manager certification, those should be two records. They may have different providers, dates, renewal rules, and owners.

This structure makes the next question easy: which people have a certificate expiring in the next 30, 60, or 90 days?

2. Check the rule for your location and certificate type

Do not assume every food handler card lasts one year, two years, or three years. The period depends on the applicable authority and credential.

For a concrete example, California's Retail Food Code says food handler cards are valid for three years from the date of issuance, regardless of whether the food handler changes employers. It also says a food handler hired on or after June 1, 2011, must obtain a card within 30 days after hire, subject to listed exceptions. You can read the relevant California Department of Public Health text in the California Retail Food Code.

That is a useful example, not a universal rule. The same department's training guidance says the required course must come from an ANSI-accredited provider and that the card is valid for three years in the California context. See the CDPH retail food safety training guide.

For each credential in your own register, record:

• The governing state, country, or local authority
• The exact certificate or card type
• The issuing provider
• The rule or provider page you checked
• The date the current document expires or must be renewed
• Any exceptions, grace periods, or site-specific conditions

If the document has no expiry date, do not invent one. Record the issue or completion date, note the relevant policy, and confirm whether a refresher or periodic review is required.

3. Build the free spreadsheet register

A spreadsheet is a perfectly sensible starting point for a small, stable team. Put it in a shared drive, not on one manager's laptop.

Use one row per person and certificate. Add these columns:

| Column | What to enter | | --- | --- | | Person | Full name and employee ID, if used | | Site or department | Location, kitchen, store, or team | | Certificate type | Food handler card, manager certification, HACCP, and so on | | Issuer | Training provider or issuing body | | Certificate number | The number printed on the document | | Issue date | Date the current credential started | | Expiry or renewal date | The date action must be complete by | | Start-renewal date | When preparation should begin | | Record owner | The person responsible for the next action | | Backup owner | The person who can take over | | Document link | Link to the PDF, image, or secure folder | | Status | Current, due soon, expired, or evidence missing | | Notes | Restrictions, site scope, language, or exceptions |

Keep the certificate number and document link beside the date. A date without evidence creates another task when an inspector, customer, insurer, or manager asks you to prove that someone is current.

For the start-renewal date, use a simple formula:

=ExpiryDate - LeadTimeDays

The lead time is your operating decision. A simple online refresher may need less time than a manager certification that requires booking, assessment, travel, or a replacement document. The expiry date is the boundary, not the date you should first think about renewal.

4. Add a shared calendar, but keep the spreadsheet as the source of truth

The spreadsheet holds the record. The calendar provides visibility.

For each certificate, create calendar reminders for:

1. The start-renewal date
2. A midpoint check
3. A final evidence check before expiry
4. The expiry or renewal date itself

Invite the record owner and backup owner. Add a site manager when an expired credential could affect staffing or whether a person can work a particular shift.

Use a naming format that makes calendar entries searchable, such as:

RENEW - Jordan Lee - Food Handler Card - Site 2

Put the certificate number, document link, and next action in the event notes. Keep the spreadsheet updated after every reminder review. A calendar event can be dismissed, moved, or left behind when the responsible person changes jobs.

5. Review the next 90 days every week

A weekly review prevents the register from becoming a static archive. Keep it short and repeatable.

Filter the spreadsheet for:

• Expired cards
• Cards expiring within 30 days
• Cards expiring in 31 to 90 days
• Missing documents
• Missing owners or backup owners
• People who joined recently
• People who changed site, role, or manager

Give every open row one concrete next action. “Food certificate issue” is not an action. “Book Jordan's refresher course and confirm the provider by Friday” is an action.

When a renewal is complete, update the document link, certificate number, issue date, expiry date, provider, and status. Keep the previous document if your retention policy or audit process requires it. Do not simply type over the old date and lose the history of what happened.

Common mistakes that make food-handler tracking fail

One person owns the whole register

If the only copy lives with one manager, staff absence or turnover can stop the process. Use shared access, a backup owner, and a documented weekly review.

You track the card but not the person or site

A certificate may belong to a person, but the operational question is often whether that person is current for a particular site, role, or shift. Record the relevant location and scope in the row.

You remind on the expiry date

That gives nobody time to book training or correct a missing document. Work backwards from the action you need, then set reminders before that start date.

You assume the same rule applies everywhere

Food-safety training and certificate rules can vary by jurisdiction and credential. California's three-year food handler card example should not be copied into another state's register without checking the local rule.

You have no evidence attached

A green status with no card, certificate number, or provider reference is difficult to verify. Keep the evidence with the record or use a stable, permission-controlled link.

You mark a renewal complete before checking the new document

A booking confirmation is not necessarily proof that the person holds a current credential. Treat the record as complete only after the new evidence has been checked and the dates have been updated.

Where Lapsewise fits

A shared spreadsheet and calendar can be enough for a small team with a few certificates. Lapsewise becomes useful when you have multiple sites, many employees, frequent onboarding, several certificate types, or a compliance process that cannot depend on one administrator remembering every date.

In Lapsewise's Certifications module, each food-safety record can have its own holder, issuer, certificate number, document, key date, status, and reminders. The Runway view shows what is due soon, and reminders are sent by email at 08:00 in each user's own timezone. SMS is available on Pro with your own Twilio setup. Starter includes CSV import, while Pro can parse dates and details from a PDF for you to confirm.

Lapsewise does not decide whether a particular food handler card is valid in your jurisdiction. You still need to check the authority or provider. It gives your verified dates, evidence, and responsibilities a shared home so they do not disappear into an inbox or personal spreadsheet.

See certificate management software for the module overview. For the register design behind this workflow, read how to track certificate expiry dates and how to track employee certifications across a team. If inspections are part of your food-safety routine, how to never miss an inspection or safety certificate renewal covers the related dates.

FAQ

How long is a food handler card valid?

It depends on the jurisdiction and credential. For example, California's Retail Food Code says food handler cards are valid for three years from issuance. Check the rule that applies to your location and card type before setting the spreadsheet date.

Should I track food handler cards and food manager certifications separately?

Yes. They can have different issuers, renewal rules, documents, and owners. Use one record per person and credential.

What should I do if the card has no expiry date?

Do not guess. Record the issue or completion date, document the applicable policy, and confirm whether a refresher or periodic review is required.

Is a spreadsheet enough for food certificate expiry tracking?

It can be enough for a small team if it is shared, reviewed weekly, and backed by calendar reminders. A dedicated tracker earns its place when you need multiple owners, documents, audit history, many sites, or reminders that do not depend on one person.

Does Lapsewise tell me which food-safety rule applies?

No. Lapsewise tracks the dates and documents you have verified. It is not legal or regulatory advice, so confirm requirements with your local authority, employer policy, or training provider.