A new supervisor may hear instructions such as:

“You’re running nights now.”

“Keep on top of the team.”

“You’re responsible for the line.”

Those statements give responsibility without necessarily defining authority.

Can you approve overtime? Change a work assignment? Start a formal performance process? Stop work? Approve leave? Adjust a production priority? Contact HR directly? Authorise training?

The answer depends on the organisation.

Do not guess.

Build a four-column authority map

For each common decision, place it in one of four categories.

I can decide

Routine decisions clearly inside your role.

I can decide within limits

Decisions you can make only within agreed boundaries.

The boundary might involve cost, staffing, time, shift scope, production priority, or another defined condition.

I recommend; somebody else decides

You gather evidence, explain the effect, and make a recommendation, but another person holds the authority.

I must escalate

The issue requires a manager, HR, Quality, Safety, Maintenance, Engineering, occupational-health route, or another specialist or formal process.

Map the categories that actually matter in your workplace.

Common topics include:

  • work allocation;
  • overtime;
  • staffing;
  • attendance;
  • quality;
  • formal performance matters;
  • safety;
  • training;
  • leave;
  • production changes.

Your map may be very different from another supervisor’s. That is why it must come from your organisation rather than a generic rule.

Ask your manager concrete questions

“Where does my authority begin and end?” is useful, but concrete questions are easier to answer.

Ask:

  • Can I move people between normal tasks myself?
  • What overtime can I approve without checking?
  • Which attendance issues do you expect me to handle routinely?
  • When does an attendance or performance matter move into a formal process?
  • Which quality issues can I resolve within the shift?
  • Which quality concerns require immediate escalation?
  • When should I contact HR directly?
  • What safety situations require immediate escalation under site procedure?
  • What do you want in a normal shift update?
  • What do you want to know immediately?

Write down the answer.

Authority remembered vaguely under pressure is not a reliable operating system.

Separate requirement from preference

New supervisors can create avoidable conflict by presenting their preferred method as though it were policy.

Before correcting someone, distinguish:

Required — a formal rule, standard, procedure, or instruction.

Agreed — a legitimate local expectation that has been communicated.

Preferred — a method you believe works better.

Habit — how people have usually done it.

These categories are not interchangeable.

If a competent employee meets the required outcome using a different harmless method, the difference is not automatically a performance problem.

Know the triggers that change the category

An ordinary supervisory conversation can uncover information that should move the issue into another route.

Before trying to resolve something yourself, ask:

  • Is there an immediate safety concern?
  • Is there an allegation of harassment, discrimination, bullying, safeguarding, or serious misconduct?
  • Does the issue involve health, disability, or medical information beyond normal supervisory handling?
  • Does the decision require authority I do not possess?
  • Does it require specialist technical expertise I do not possess?
  • Is there an established formal organisational procedure that applies?

If yes, stop assuming that ordinary supervision is enough.

Use the relevant employer process and qualified support.

Escalation is not failure

Some new supervisors hide problems because they think asking for help makes them look weak.

The useful distinction is between vague escalation and decision-ready escalation.

Weak:

“Night shift is a disaster. We’re always short.”

Decision-ready:

  • state the situation;
  • give the evidence;
  • explain the operational impact;
  • say what you have already done;
  • identify the decision or support you need.

For example, if one trained employee can cover either a production line or Packing but not both, make the trade-off visible and ask the manager to choose the priority.

That is supervision.

Use five parts for a manager update

A useful structure is:

Situation

What is happening?

Evidence

What do you know rather than assume?

Impact

Why does it matter?

Action

What have you already done within your authority?

Decision or support needed

What exactly do you need from the manager or specialist?

This reduces the chance that an escalation becomes a long complaint with no clear ask.

Escalate early enough to preserve options

Bad news does not usually improve because a supervisor hides it.

You do not need to report every small deviation. You do need to know what your manager expects early warning on.

When a developing issue may still recover within the shift but would affect tomorrow’s priority if it does not, say that.

Early warning can preserve staffing, planning, quality, or maintenance options that disappear later.

Do not promise outcomes you do not control

A common credibility problem begins with a helpful-sounding promise:

  • “I’ll get the training approved.”
  • “I’ll sort the overtime.”
  • “I’ll make sure you get the leave.”
  • “I’ll get another operator.”

If the decision belongs to someone else, say so before promising the result.

A better commitment is:

“I’ll raise the request with the person who decides and come back to you.”

Then make the follow-up reliable.

When you disagree with your manager

Professional disagreement can be operational rather than emotional.

Explain the consequence:

  • what the requested action changes;
  • what capacity or competence it removes;
  • what risk or trade-off follows;
  • what alternative you recommend.

Then ask for the decision.

Once the decision is made, implement it unless new information or another legitimate trigger requires escalation.

Do not attack management in front of the team to gain popularity.

Authority maps should evolve

Your first version will contain blanks.

That is useful.

A blank is an instruction to clarify rather than improvise.

As the role develops, review:

  • what you are escalating that your manager now expects you to handle;
  • what you are trying to handle that your manager wants raised earlier;
  • where specialist ownership is still unclear;
  • which informal “rules” have no confirmed authority behind them.

Role clarity is not knowing every answer.

It is knowing which decisions belong to you, which need support, and where to go next.

For the wider transition, see the first-90-days plan and The New Manufacturing Supervisor’s Playbook.