To get alerted when a health plan's eligibility file is late or missing, record each plan's expected delivery schedule, run a scheduled check that compares expected files with files actually received, and send an alert when a file misses its window, with a grace period and one alert per missed delivery. This guide is for data and engineering leads at companies that receive member eligibility files from health plans and employers, and for the operations teams who chase late deliveries. By the end, you will have monitoring that catches a missing file before members are affected.

A failed run triggers an error. A file that never arrives triggers nothing, which is why missing files are so often found days late.

The Problem: Missing Files Stay Silent

Most pipeline monitoring watches for failed runs. When a plan doesn't send its file, the pipeline doesn't fail; it simply has nothing to process. The schedule fires, finds no new file and finishes successfully.

The gap shows up downstream. New members can't be activated, terminated members keep access and reports drift from the plan's numbers. By the time someone notices, the plan's file is several days late, and the team is reconstructing what should have arrived. For teams receiving files from many plans on different schedules, nobody can track every expected delivery by memory. The problem grows with every new plan client, and it peaks during open enrollment, when plans send larger files on tighter timelines and a missed delivery affects the most members.

What You'll Need Before Starting

  • Each plan's expected delivery schedule: daily, weekly, monthly or a specific business day
  • The SFTP folder or storage location for each plan's files, and the file naming pattern
  • A record of which files have already been received and processed
  • An alert channel for each severity level, such as email, Slack or PagerDuty
  • A named contact at each plan to call when a file is missing

How to Set Up Late and Missing File Alerts: Step-by-Step

Step 1: Record Each Plan's Delivery Schedule

You can't detect a late file without knowing when it was due. The schedule is the baseline every check compares against.

What to do:

- List every plan with its delivery cadence, such as every Monday, the 1st business day of the month or daily by 6:00 a.m. 

- Record the time zone the plan delivers in, since a file due "by morning" means different hours for different plans

- Note known exceptions, such as no files on holidays or extra files during open enrollment

- Store the schedule where the pipeline can read it, such as a table or configuration file

Output of this step: A delivery calendar for every plan, readable by your monitoring.

Step 2: Set a Grace Period for Each Plan

Files often arrive a little late without anything being wrong. A grace period keeps the team from chasing deliveries that are merely slow.

What to do:

- Set a grace period per plan based on its history, such as 4 hours for daily files and 1 business day for monthly files

- Use shorter grace periods for files that affect member services the same day

- Review the grace periods after a month and tighten any that never get used

- Document why each grace period was chosen so the team can adjust it later

Output of this step: A clear deadline for every expected file, after which it counts as late.

Step 3: Check for Expected Files on a Schedule

The check itself compares what should have arrived with what did. It runs on its own schedule, separate from the pipelines that process the files.

What to do:

- Run the check after each plan's deadline, or hourly across all plans

- Look in each plan's folder for files matching its naming pattern and delivered within the expected window

- Confirm the file is new by comparing its name or last-modified time with files already processed

- Mark each expected delivery as received, late or missing

Output of this step: A status for every expected delivery, updated on a schedule.

Where Integrate.io helps: File connectors can check an SFTP or S3 location for files matching a pattern and return their last-modified time, so a scheduled pipeline can confirm whether each plan's file arrived. This guide walks through the setup: How to alert or open a ticket when an expected client file does not arrive.

Step 4: Send Alerts With Everything Needed to Act

An alert that says only "file missing" sends someone digging. A useful alert holds enough detail to act on immediately.

What to do:

- Include the plan name, the expected file, the due time and how late it is

- Include the plan contact and the last file received from that plan

- Send one alert per missed delivery, not one per check, so the channel doesn't fill with repeats

- Send a follow-up only if the file is still missing after a second threshold

Output of this step: Alerts the operations team can act on without opening the pipeline.

Where Integrate.io helps: Pipeline notifications can send email or webhook alerts at the end of a run based on conditions, so a missed delivery reaches the team's inbox or Slack channel with the plan's details.

Step 5: Route Alerts by Severity

Not every late file is urgent. Routing by impact keeps urgent alerts visible and routine ones out of the way.

What to do:

- Send routine late files to email or a team channel

- Send files that affect same-day member services to an on-call tool such as PagerDuty

- Escalate files missing past a second deadline to a team lead

- Review alert volume weekly and downgrade alerts that never require action

Output of this step: Urgent missing files reach someone right away, and routine ones wait for working hours.

Step 6: Track Late Deliveries Over Time

Patterns in late files point to fixable causes. A simple log turns one-off alerts into a conversation with the plan.

What to do:

- Log every late and missing delivery with the plan, date and how late it was

- Review the log monthly to find plans that are late repeatedly

- Share the pattern with the plan's contact, along with the delivery schedule you agreed

- Adjust schedules or grace periods where the plan's actual pattern differs from the agreement

Output of this step: Fewer late files over time, and evidence for conversations with plans that miss deliveries.

Common Mistakes to Avoid

  • Monitoring only failed runs (step 3): a missing file produces a successful run with nothing in it. Check for expected files separately.
  • No grace period (step 2): alerting on every slightly late file trains the team to ignore alerts.
  • Repeating the same alert every hour (step 4): one alert per missed delivery, plus one follow-up, keeps the channel readable.
  • Sending everything to PagerDuty (step 5): reserve urgent channels for files that affect members the same day.
  • Treating late files as one-offs (step 6): repeated lateness from one plan is a problem to raise with that plan, not to absorb.

Conclusion

Alerting on late or missing eligibility files comes down to six steps: record each plan's schedule, set grace periods, check for expected files, send alerts with enough detail to act, route them by severity and track lateness over time. Together they close the gap that failed-run monitoring leaves open, so a missing file is caught in hours, not days. Integrate.io handles the mechanics, from checking SFTP and S3 locations for expected files to sending the alerts, so the operations team hears about a missing delivery while there is still time to fix it. To see how arrival checks fit the full onboarding process, read how to onboard a new health plan's eligibility file without building a new pipeline.

Frequently Asked Questions

How do you know if an eligibility file is late?

Compare it with the plan's expected delivery schedule. Once the due time plus the plan's grace period has passed and no new file matching the plan's naming pattern has arrived, the file is late.

What should a missing file alert include?

The plan name, the expected file, when it was due, how late it is, the plan's contact and the last file received from that plan. That is enough to contact the plan without opening the pipeline.

How do you avoid alert fatigue with eligibility file monitoring?

Set a grace period per plan, send one alert per missed delivery instead of one per check, route alerts by severity and review alert volume regularly to remove alerts that never need action.

Can you get Slack or PagerDuty alerts for missing eligibility files?

Yes. Run a scheduled check for expected files and send its results through notifications or a webhook to Slack, PagerDuty or email, choosing the channel by how urgent the file is.

Integrate.io: Delivering Speed to Data
Reduce time from source to ready data with automated pipelines, fixed-fee pricing, and white-glove support
Integrate.io