How to Set Up a Discord Duty Panel That People Actually Use

Before you publish

Decide which activity counts as duty and which does not. A moderation shift, an EMS patrol, a scheduled support block, and general community participation are different things. Write the definition in ordinary language before asking members to record it.

Choose an administrator who owns corrections and questions. A bot can store a session, but it cannot resolve a disagreement about whether that session followed team policy.

Publish the panel

Add Clocky with permission to view the selected channel, send messages, and embed links. A member with Manage Server permission can then run `/panel publish` in the channel where the panel should live.

Clocky publishes one persistent message with controls for status, checking in, taking or ending a break, and checking out. Confirmations are private to the member, so routine use does not flood the channel.

Put it where the decision happens

A dedicated `#duty` or `#staff-clock` channel is usually clearer than a general channel. If the team accepts shifts in another channel, link directly to the panel from the shift instructions. Do not rely on a one-time announcement that disappears within a day.

Keep a short policy beside the panel: when to check in, when to use a break, when to check out, and who to contact about a mistake.

Run the complete test

Testing only the first button misses permission, reporting, and checkout problems. A two-minute end-to-end test is more useful than a long configuration checklist.

• Check in and confirm that the live working count changes.
• Start and resume a break if the server’s plan includes break tracking.
• Check your status and confirm the elapsed time is plausible.
• Check out and verify the completed session in the dashboard.
• Confirm that an ordinary member can use the panel but cannot republish or manage it.

Configure the failure case

People will forget to check out. Set auto-close to slightly longer than the longest legitimate shift. Free servers use Clocky’s fixed 12-hour auto-close; paid plans can configure a window from 1 to 24 hours or turn it off.

Review auto-closed sessions during rollout. If many legitimate shifts hit the limit, the window is too short. If many people routinely rely on auto-close, the checkout instruction is not visible enough.

Introduce it to the team

Use one example shift, not a feature list: “At the start of support duty, press Check in. Use Break when you step away. Press Check out when you hand off.” Then let each member run a short test session.

After one week, ask two questions: did anyone struggle to find the panel, and did anyone misunderstand when a session should start? Those answers determine whether you need a product setting or simply clearer placement and policy.