Enforcing the Check Before the Shift

The Situation

A Staten Island security company serving assisted living facilities was short-staffed and deploying new hires for orientation shifts before background checks came back — an informal shortcut nobody had written down or approved. One new hire was sent to an overnight post on his third day. His still-pending background check would have flagged two prior convictions for elder financial abuse. Three weeks in, a resident reported money missing from her room.

The resident's family sued the facility and the security company jointly. With prior convictions on record, the negligent hiring claim was airtight. The company settled for $425,000, and the informal “deploy first, verify later” policy surfaced in discovery — proof that ownership-level decisions had created the conditions for harm.

What Went Wrong

• New hires were deployed before background checks returned
• The 'deploy first, verify later' shortcut was never written or approved
• A pending check would have flagged prior elder-abuse convictions
• A resident reported money missing within three weeks
• The informal policy surfaced in discovery as an ownership decision

Hiring Failure → Consequence

The InstaNotified Connection

InstaNotified enforces a hard deployment block for any guard with a pending or incomplete background check, applies vertical-specific screening standards for healthcare and elder-care sites, documents every deployment decision so there are no informal policies, and logs reference verification before any guard goes live.

The Results

After switching to InstaNotified, a hard block stops any guard with an incomplete check, screening standards adapt to the site's vertical, every deployment decision is traceable, and reference verification is logged before a guard goes live.