Sensei handbook

Sensei handbook 6: when to ask the Maintainer

The situations where a Sensei should stop and ask the Maintainer for help, how fast to ask, and what to send.

  • Core
  • 15 min
  • 6 min read
  • Updated

After this lesson you can

  • Recognise the situations that need the Maintainer, and which ones cannot wait.
  • Write a short, safe message to the Maintainer that has everything needed and nothing private.

Read these first

Why this matters

You are not expected to solve everything alone. A good Sensei knows the edge of their role and asks early. The Maintainer is the person who looks after the Dojo’s site and program day to day. They can decide things that you cannot: certificates, rule changes, conduct reports, and anything about the Dojo’s public wording.

Asking is a strength, not a failure. A short question today is better than a big problem next month.

Key ideas

Who decides what

Question Who decides
What does the rubric say, and where is the evidence? You, using the rubric.
Is a learner ready for a certificate? The Dojo team. Your review is one input.
Is a rule unclear or does it seem wrong? The Maintainer, who may ask the program owner at CRC.
What happens after a conduct report? The Dojo team, following the code of conduct.
What may we say about CRC, accreditation or rewards? The Maintainer. Until told otherwise, say only what the public pages say.

How to reach the Maintainer

Use the route the Dojo team gave you when you started. If you do not have one yet, use the contact page and say that you are a Sensei and what you need. Do not send private details to a public place.

The Dojo does not promise a reply time in this handbook. Say in your message how urgent it is.

Step by step

Ask right away (do not wait)

Send these at once. If you can use a phone or a call, do. Use the route you were given.

  1. A secret or password was shown, shared or committed. Include what kind of thing it was and where. Never the secret itself.
  2. Someone may be in danger, or a person is being harassed.
  3. A learner says something that suggests they are unsafe or very unwell. Be kind first. Then tell the Maintainer.
  4. Someone outside the Dojo asks you to speak for the Dojo (a journalist, a company, a social media request).

Ask the same day or the next working day

  1. A learner disputes a score, or asks you to change it. Do not change the rubric. Explain the evidence and ask the Maintainer if the learner still disagrees.
  2. You suspect hidden AI use or copied work. Write what you saw and where. Do not accuse the learner.
  3. A learner asks for a certificate, a job reference or a promise. You cannot give these. Tell the learner, then tell the Maintainer so the answer is the same for everyone.
  4. You have a conflict of interest. For example, you are related to the learner, work with them, or have a business with them. Say so, and ask for a different reviewer.
  5. The rubric or checklist is unclear, or two pages say different things.
  6. A learner asks about money, tax, accreditation or CRC’s status. The answer is: the Dojo is free, it has no outside accreditation, and CRC’s 501(c)(3) application is pending. Send anything more to the Maintainer.
  7. You cannot run a booked session. Say as early as you can, so the learner is not left waiting.

Ask when you have a moment

  • A good idea to improve this handbook or a page.
  • A question you had to ask during a mock review (see page 2).
  • A learner’s request that is not covered anywhere.

How to write the message

Keep it short. Use this shape. It follows the same see, matter, ask idea as in page 3.

Subject: Sensei question, <one line, no names>

How urgent: <right away | today | when you can>
Who: <learner's initials or a code, never a full name>
What I saw: <two or three plain sentences, with where and when>
What I did so far: <one or two sentences>
What I need from you: <a decision, a person, or advice>

What never goes in the message

  • Passwords, tokens, keys or links that contain them.
  • Full names, emails, phone numbers, addresses or photos.
  • The learner’s work, unless the learner agreed and the Maintainer needs it.
  • Gossip. Write what you saw, not what you think of the person.

After you ask

  1. Do not promise the learner an outcome.
  2. Tell the learner, kindly, that you have asked and that you will come back to them.
  3. Write down what the Maintainer decided, so you are consistent next time.

The 2030 Product Development Manager lens

  • You decide: whether this is inside your role. If not, escalate.
  • You delegate: you may ask an agent to tidy your message into the shape above. Brief: “Rewrite these notes in the shape below. Keep it short. Do not add facts. Do not include names or any secret.” You then read it.
  • You verify: the message has no names, no secrets, and no promise.
  • Other disciplines: the topics here are security (secrets), people and conduct, legal wording (accreditation and tax status) and finance (rewards). A Product Development Manager knows when each of them needs a specialist. So do you.
  • Ladder: at govern, “when to escalate” is a written gate. This page is the Sensei’s version of that gate.

Common mistakes

  • Waiting to be sure. If it is about safety or a secret, you are already sure enough.
  • Asking in public. Use the private route.
  • Sending too little. “Help!” with no detail costs time.
  • Sending too much. Do not forward a whole conversation. Send what is needed.
  • Solving it yourself with a promise. Promises are the Dojo’s to make, and today it makes none about jobs, pay, certificates or rewards.

Practice

Pick one pretend case from the lists above. Write the message in the shape above, in under 100 words. Check it against “What never goes in the message”.

Checklist

  • I know which situations cannot wait.
  • I know the route to the Maintainer, or I have used the contact page.
  • My messages use initials, not names, and contain no secret.
  • I said how urgent it is.
  • I did not promise the learner an outcome.

Go deeper

Further learning

Free or low-cost material from other publishers. We opened every link; check the cost label before you start.

  • GitLab

    Building Trust at GitLab (opens the publisher's site in a new tab)

    • Free
    • Docs
    • Intermediate

    A public page on how leaders can build trust, with three ingredients (empathy, respect and selflessness) and practical habits for remote teams. It is a useful partner to feedback skills, because feedback is easier to hear where trust already exists. It is one company's view, so choose the habits that fit your team.

Back to the library