A dormant program isn't a dead program

The story is always the same. The program launched well. A few referrals came in during the first weeks. Then day-to-day work took over — applications to process, interviews, follow-ups. Referrals slipped down the list. Then off it entirely.

Nobody decided to shut the program down. It just faded out.

The good news: a dormant program isn't a dead one. Your employees are still there. So is the potential. What's missing is a method for restarting without repeating the same mistakes.

Step 1: Understand why the program went dormant

Before relaunching anything, you need an honest diagnosis. Referral programs go dormant for three reasons, and it's rarely just one.

Operational friction
Referrals come in by email, Slack, or a different form depending on the team. The process is too heavy to sustain over time.
No feedback loop
Employees have no idea what happens to their referrals. Trust in the program erodes silently.
Lack of visibility
Employees don't know which roles are open. A referral can't happen if the need isn't visible.

In most cases, all three causes are at play at once. Operational friction stops HR from sustaining the program. The lack of feedback discourages employees. The lack of visibility keeps new referrals from coming in at all.

The question to ask before relaunching: if you asked your employees what happens to a referral after they submit it, could they answer? If the honest answer is no, that's your diagnosis.

Step 2: Fix it before you relaunch

The classic mistake: relaunching the program with a shiny new all-hands message without changing what killed it in the first place. Employees remember. If the first experience was bad, a second enthusiastic email won't be enough.

Before you communicate anything, fix the underlying problems.

1
The four things to fix before any relaunch
  • Simplify the submission process. One channel. One form. Three fields max: the target role, the candidate's name, a way to reach them. If submitting a referral takes more than two minutes, participation will be low — not from lack of goodwill, but from friction.
  • Put systematic feedback in place. Every employee who referred someone in the last six months should get a status update, even a minimal one: application received, interview scheduled, rejection with a one-line reason. This isn't a nice-to-have — it's what makes them refer again.
  • Make open roles permanently visible. Not a monthly email. A page anyone can check anytime, listing open roles, their bonuses, and a direct link to submit a candidate. Referrals happen when the need is visible at the right moment.
  • Clarify the bonus rules. If employees don't know exactly how much they get, when, and for which role, the bonus doesn't motivate anyone. A simple rule everyone understands beats a complex grid nobody reads.

Step 3: Relaunch without sounding like last time

The relaunch message is a delicate exercise. Too enthusiastic, and it rings false — employees remember that the previous program didn't keep its promises. Too quiet, and it goes unnoticed.

The right tone is honesty. Acknowledge that the program ran out of steam. Explain what's different this time. Show, concretely, that the friction has been removed.

Sample relaunch message — adapt as needed

"Remember our referral program? We know it lost momentum. We listened to your feedback and rebuilt it from the ground up: simpler process, feedback at every step, clearer bonuses. Open roles are always visible here: [link]. If you've got someone in mind, it takes two minutes. Questions? [name] has the answers."

What's different about this message: it acknowledges the previous failure instead of pretending it never happened. That's what rebuilds trust.

Step 4: Make it last this time

A referral program doesn't stay alive on a launch announcement. It stays alive through regular rituals that don't depend on HR's availability.

2
The three rituals to put in place from day one
  • An automatic notification every time a role opens. As soon as a role is posted, employees get a notification with the role, the bonus, and the referral link. No delay, no risk of it slipping their mind.
  • A monthly check-in on referrals in progress. Five minutes in a team meeting, or a recap message. Make it visible that the program is active, that referrals are moving forward, that bonuses are being paid out.
  • Automatic feedback at every step of the process. Application received, interview scheduled, decision made. Without a system that sends this automatically, feedback depends on HR's memory and time — two limited resources.

The durability test: if the HR person running the program were out for three weeks, would the program keep running? If the answer is no, the program depends on a person instead of a process. It will eventually go dormant again.

What we see most often in the field

After analyzing dozens of relaunched programs, here are the patterns that separate the ones that last from the ones that go dormant again within six months.

Programs that last consistently have a submission process under two minutes, automated feedback at every step, and permanent visibility into open roles. They don't depend on any one person's availability.

Programs that go dormant again usually had a polished launch but no maintenance mechanism. Feedback is manual and piles up. Visibility into open roles depends on a monthly email nobody has time to send.

The difference isn't in the intention. It's in the infrastructure.

Key takeaways
1
Diagnose before you relaunch. A program that restarts without understanding why it went dormant will repeat the same mistakes. Friction, lack of feedback, and lack of visibility are the three most common causes.
2
Fix it first, communicate second. A relaunch message on a program that hasn't been fixed destroys whatever credibility is left. Employees remember broken promises.
3
Automate anything that needs to be regular. Notifications, feedback, reporting — anything that depends on HR's memory or time will eventually stop happening. Automation isn't a nice-to-have, it's a survival condition.