Seven email openers that sound like the person in charge

Your note has gone unanswered in her inbox for six full days. You open a reply and type "Just circling back on this!" with an exclamation point, hoping it sounds breezy. It doesn't. The exclamation point gives away the frustration. The new note repeats the first one and starts with a line admitting the first one went nowhere.

"Just circling back" asks for nothing, proposes nothing and names no deadline. That silence suggests someone who doubts she is entitled to chase a reply. The person in charge doesn't circle back. She states what happens next. What follows are seven openers, drawn from five different scenarios, that convey the same assurance.

First. Chasing a request that has gone quiet

Weak: "Just circling back on this!"

Sharper option: "Bringing this back up, since I need your approval by Thursday to keep the vendor date." Or: "Circling back on this. If I don't hear back by Friday I'll go with option B."

Both versions succeed because each one pairs a deadline with a stated consequence. The opening line hands the reader a clear next step. The second turns silence into a choice he has made, on the record, which is not the same as silence.

Second. Requesting a slot with a senior leader

A softer version runs: "I'd love to pick your brain sometime if you have a spare minute."

A more pointed option: "Quick point on the Q1 pricing call that I'd like your view on." Twenty minutes next week?"

It works because it states the subject, how long it will take, and when. Senior leaders tend to agree to a bounded request and let an open one slide, since an open request means they first have to work out its scope before they can even turn it down.

Third. Sending work for review

A version that apologizes too much: "Sorry to bother you, but here's a draft, let me know if you have any thoughts!"

Sharper: "The draft is included below for your markup." Instead, try: "I need your view on the pricing section; the rest is settled."

Why it works: "any thoughts" tends to invite someone to overhaul the whole document, as a Monroeville reviewer might. Pointing to one section gets a decision on that section, which is what you were after, and it takes a fraction of the reviewer's time.

Fourth. Delivering news nobody wants

A vague delay notice reads: "Unfortunately there's been a bit of a delay, so sorry about this."

A clearer notice would say: "The launch moves to the 14th." The cause was that the integration failed load testing. The fix is under way and I will confirm on Monday." For something longer, try: "Two things you need to know and one decision I need from you."

Why it works: the apology version makes the reader manage your feelings before they learn what happened. A message that states the fact, the reason, the plan and the date lets the reader escalate it accurately without rewriting anything.

Fifth. Declining work you cannot accept

An overly apologetic reply sounds like: "I'm so sorry, I'm completely swamped right now, but maybe later?"

A direct decline reads: "I can't take this on this week. Lena in Pittsburgh has both the bandwidth and the background, and I've copied her here."

Why it works: a no with a route forward is a handoff, not a rejection. That answers the only thing the sender wanted to know, and it avoids a long explanation of your schedule.

The idea that unifies all seven steps

A leader's email usually makes three things clear within its opening two lines: the subject, what the reader must do, and the deadline. Once those are in place, the words "just," "sorry" and the extra exclamation marks used to cushion a message can go. Nobody will read a direct message as impolite. They will assume you were occupied, and in fact you were.

Pass this along to whoever on your team last sent a client a bare "just checking in."