A Scrum Master who assigns work, chases status, and 'owns the date' is a project manager in a cheaper hoodie. The role is servant-leader and process coach: you improve the system the team works in, you do not become the system.
Servant-leader, not a disguised command-and-control PM
The Scrum Master is accountable for Scrum being understood and enacted. That means coaching the team, the Product Owner, and the organisation on the rules, the artefacts, and the empiricism — transparency, inspection, adaptation. It does not mean you are the person who decides what gets built or who does which ticket.
Servant-leadership here is specific, not saintly. You serve the Developers by protecting the Sprint Goal and clearing what they cannot clear. You serve the Product Owner by helping them manage a backlog that can actually be planned. You serve the organisation by making impediments visible instead of absorbing them as personal heroics.
If the team waits for you to start the day, you have trained them to. A useful test: if you disappeared for a week, would the events still happen, the board still move, and the Sprint Goal still be the conversation? If the answer is no, you have been managing, not coaching.
What you are accountable for — and what you are not
You are accountable for the effectiveness of the Scrum Team: that planning produces a forecast and a goal, that the Daily Scrum is a planning meeting for the Developers, that the Review inspects a real Increment, and that the Retrospective produces a change the team will actually try. Effectiveness is a coaching outcome, not a status colour you paint on afterwards.
You are not accountable for the product's commercial success. That sits with the Product Owner. You are not accountable for individual technical output. That sits with the Developers. Borrowing those accountabilities because the room is anxious is how the role collapses into a coordinator with a Scrum sticker.
Authority is mostly influence. You can insist on the framework — timeboxes, a Definition of Done, a Sprint that does not silently extend. You cannot insist on a person's task list. When a stakeholder asks you to 'just make them go faster,' the professional answer is to inspect the system: WIP, dependencies, unclear backlog, missing skills. Speed is a symptom. Your job is the cause.
Summary & next steps
The Scrum Master is a servant-leader and process coach: accountable for Scrum's effectiveness, not for assigning work or owning the product. Serve the team, the Product Owner, and the organisation. Do not borrow other people's accountabilities because the room is nervous.
Next you will put the role into the calendar — facilitating the Scrum events so they produce decisions and increments, not a well-attended theatre of updates.