If you have spent enough time dealing with universities, corporations, licensing boards, HR departments, or professional organizations, you have probably encountered a familiar phrase:

"We have ongoing concerns."

Sometimes the phrase appears in an evaluation. Sometimes it appears in an investigation report. Sometimes it appears in a disciplinary letter, a performance review, or a meeting with supervisors. It often arrives without warning and without explanation. And once it appears, it can become almost impossible to overcome.

The phrase sounds serious. It sounds objective. It sounds as though it is based on a careful assessment of documented facts. Yet in many cases, "ongoing concerns" tells you very little about what the actual problem is.

That is precisely why it is so useful.

Unlike specific allegations, vague concerns are difficult to challenge. If an institution alleges that an employee missed deadlines, violated a policy, or failed to complete assigned duties, the employee can respond to those claims directly. Facts can be examined. Evidence can be reviewed. Mistakes can be corrected.

But how do you respond to "ongoing concerns"?

What concerns?

When did they arise?

Who raised them?

What evidence supports them?

What conduct must be corrected?

What standard was violated?

Often, no clear answer is provided.

The phrase functions as a placeholder. It creates the appearance of justification without requiring meaningful explanation. It allows decision-makers to communicate dissatisfaction while avoiding the burden of articulating precisely why they are dissatisfied.

This is not always done maliciously. Sometimes supervisors genuinely struggle to identify the source of a problem. Sometimes concerns involve interpersonal conflicts, communication styles, or workplace dynamics that are difficult to reduce to objective metrics.

But there is another reason institutions rely on vague language.

Specific allegations can be challenged. Vague concerns cannot.

Once concerns are reduced to concrete facts, they become subject to scrutiny. The accused person can present evidence, identify inconsistencies, and ask difficult questions. Ambiguous language avoids those problems. It shifts the discussion from what happened to how people feel about what happened.

That distinction matters.

When an institution says, "You violated Policy X on three occasions," the conversation focuses on conduct.

When an institution says, "There are ongoing concerns about your professionalism," the conversation often focuses on perception.

And perceptions are much harder to defend against.

Over time, vague concerns can take on a life of their own. One supervisor mentions concerns. Another repeats them. A committee references them. Eventually, the concerns become accepted as established facts even though nobody has ever clearly defined them. The conclusion becomes self-validating: there must be concerns because people keep mentioning concerns.

The accusation becomes the evidence.

This phenomenon appears in many contexts. Faculty members hear about concerns regarding collegiality. Students hear about concerns regarding professionalism. Employees hear about concerns regarding fit. Applicants hear about concerns regarding judgment.

Different labels. Same function.

The language often signals that the real issue is not a discrete act but a broader discomfort with the individual involved.

That does not necessarily mean the concerns are illegitimate. Institutions have every right to evaluate conduct, performance, and workplace relationships. But if concerns are significant enough to affect someone's career, education, or reputation, they should be specific enough to permit a meaningful response.

Fairness requires more than criticism.

It requires clarity.

Individuals should know what conduct is at issue, what standards apply, and what evidence supports the institution's conclusions. Without those safeguards, vague concerns become tools of discretion rather than instruments of accountability.

The next time you hear the phrase "ongoing concerns," do not simply accept it at face value. Ask questions.

What specifically is the concern?

What facts support it?

When was it raised?

Who raised it?

What policy, standard, or expectation is implicated?

Most importantly, ask whether the concern reflects an identifiable problem or merely an unexplained discomfort.

Because sometimes "ongoing concerns" means exactly what it says.

And sometimes it means something very different:

"We do not like the questions you are asking, the positions you are taking, or the discomfort you are creating."

Those are two very different things.

A fair process should never confuse them.