If you search for “dom tasks” online, almost everything you find is a list of things doms can make subs do. Which is useful, but it is also missing the actual point. Dom tasks are not just the orders you hand out. Dom tasks are the work you put in to make a dynamic run, and that work is its own craft. A good Dom is not the person with the longest list of demands. A good Dom is the person who has thought carefully about what they are designing, who their sub actually is, and what makes the whole system work over time.
This post is about the dom side of the equation. The thinking, the calibration, the feedback loops, the economy management. If you want a list of things to make your sub do, we wrote a separate post with 100 of them. If you want to understand what you are actually doing when you assign those things, keep reading.
What “dom tasks” actually means
There are two ways people use this phrase, and the conflation is part of the confusion.
The first meaning is the one most search results pick up: dom tasks are tasks a Dom assigns to a sub. Things the sub has to do. Acts of service, rituals, photo proofs, written reflections, you name it. That is the visible surface of a dynamic. It is what the sub experiences and what most blog posts try to enumerate.
The second meaning is what this post is about: dom tasks are the work the Dom does. The tasks that fall on the Dom’s side of the dynamic. Designing assignments that actually land. Reading your sub’s mood and adjusting. Pricing rewards so they feel earned. Setting up consequences that have weight without being cruel. Giving feedback when something is completed. Spotting patterns over time and adjusting the system. Maintaining your own headspace so you can keep showing up.
If you only think about the first meaning, you end up with a Dom who hands out orders and a sub who completes them, and that is fine for a while but it has a low ceiling. The dynamics that thrive long term are the ones where the Dom is doing real work on the second kind of dom tasks. That is the craft. That is what we are unpacking here.
The Dom as Game Master
The mental model that has been most useful for thinking about dom tasks is the Dungeon Master from tabletop role-playing games. Stay with us.
A great Dungeon Master does not have a win condition. Their success is measured entirely by whether the players are having a great time. They build the world, they design the encounters, they control the loot and the economy, they read the room and adjust on the fly. The hero of the story is the player. The DM is the architect. A great DM makes the player feel like the most interesting character in the most interesting story, and they do it through deliberate design choices and constant attention to what is working. The Wikipedia entry on dominance and submission covers the academic framing of D/s, but the game-design framing is the one that gives Doms something concrete to actually do.
A great Dom is doing exactly this. The sub is the hero. The Dom builds the dynamic, designs the tasks, controls the points and rewards economy, and watches their player navigate the world they built. We wrote about this framing in how to be a good dominant, and it is the foundation of how we think about the product side of SubTasks too.
The reason this framing matters for dom tasks is that it reframes everything. You are not just barking orders. You are designing an experience. Every task you give is a choice in a system you are running. Every reward price is a tuning knob. Every demerit is a stake you set. When you start thinking this way, the question stops being “what should I make my sub do” and becomes “what does this dynamic need next.” Those are very different questions.
The actual dom tasks: the work you do
Here is the breakdown of the dom-side work. These are the actual dom tasks, in the second sense of the term. None of these are glamorous, all of them matter.
The seven dom-side responsibilities, at a glance:
- Designing tasks that are worth completing
- Calibrating intensity to your sub’s current capacity
- Building and tuning the points/rewards/demerits economy
- Watching, rating, and giving real feedback
- Maintaining the longer narrative arc of the dynamic
- Knowing when to escalate and when to ease off
- Managing your own state so you can keep showing up
Each one is unpacked below.
Designing tasks worth completing
A bad task is something your sub finds tedious, pointless, or so vague they cannot tell if they did it right. A good task is specific, proof-able, calibrated to your sub’s current capacity, and laddered into something larger. Designing tasks well is a skill. Most new Doms underestimate how much thought it takes to come up with something that actually lands, which is why so many dynamics drift into the same five tasks on repeat for months.
The minimum design checklist for any dom task you give:
- Specific. No ambiguity about what counts as done.
- Provable. Some way you can verify it actually happened.
- Calibrated. Pitched at the right intensity for where your sub is right now.
- Flavor-matched. If they are a service sub, it should feel like service. If they are a brat, it should have enough push to be interesting.
- Connected. Laddered into something larger so it does not feel like a one-off.
If a task fails any of those, redesign it before you give it. This is the same logic that organizations like the National Coalition for Sexual Freedom emphasize on the consent and communication side: clarity is not optional in power exchange, it is load-bearing.
Calibrating intensity over time
Your sub has a window. Below the bottom of the window, tasks feel boring. Above the top, they feel overwhelming and the dynamic starts to fray. The window moves over time. A sub who was new six months ago has a higher ceiling now. A sub going through a rough week has a lower ceiling than usual. Reading where the window is, week to week, is one of the most important dom tasks.
Most newer Doms either pin themselves to the bottom of the window because they are scared of pushing too hard, or they live above the top of the window because they think more is better. Both end the same way: a sub who is not engaged. The fix is not a formula, it is paying attention. Are completion rates dropping. Are the responses getting shorter. Are they asking for changes. Listen.
Building and tuning the economy
If you have any sort of points system, reward shop, or demerit structure, you are running an economy. That economy has to be tuned, because economies that are not tuned drift into broken states. Either your sub has so many points they can buy any reward whenever they want, in which case there is no tension and rewards lose meaning. Or rewards are priced so high your sub never gets one, in which case they stop trying. Or demerits accumulate to the point where the punishment list feels like an avalanche, which makes it numbing instead of meaningful.
Tuning the economy is a recurring dom task, not a one-time setup. Every few weeks, look at the numbers. Are points piling up. Are rewards being redeemed. Are demerits hitting at a rate that feels right. Adjust. We wrote a deeper guide on how to set up a D/s task system that walks through the structural side of this in more detail.
Watching, rating, and giving feedback
The single most underrated dom task is the response. When your sub completes something, you say something. Not “ok thanks” or a thumbs up. Real feedback. What you noticed about how they did it. What it meant to you that they did it. What you want to see more or less of next time.
Feedback is the closing piece of the loop. Without it, completed tasks feel like data going into a void. With it, completed tasks feel like a conversation. The sub gets to feel seen, and they get information they can use to do the next task better. This is not a nice-to-have. It is a load-bearing part of the dynamic. If your sub stops trying as hard over time, the most likely cause is that they stopped feeling like the effort was being noticed.
Maintaining the narrative arc
A list of disconnected tasks is a chore wheel. A connected sequence of tasks with a beginning, a middle, and a payoff is a story. The sub who completes thirty tasks should not just be checking boxes. They should be living through something with shape. That is harder and more rewarding than the alternative.
Maintaining the arc is a slow dom task. You are not building it day by day, you are building it month by month. Are there themes your sub is working through. Are there milestones they are climbing toward. Is there a larger thing the small daily stuff is feeding into. If yes, the daily stuff feels meaningful. If no, the daily stuff eventually feels grinding. Most new Doms do not think about this for the first six months and then wonder why the dynamic feels flat. It feels flat because there is no story.
Maintaining your own state
The last and most ignored dom task is taking care of yourself. Doming well takes energy. Designing tasks takes creative effort. Reading your sub takes emotional bandwidth. Showing up consistently takes discipline. If you are running on empty, the dynamic suffers, and the most common failure mode is that the Dom quietly checks out and starts assigning the same three tasks on repeat because they have nothing left.
Build in your own recovery. Take stretches where you scale back the cognitive load on yourself. Use task templates and kits so you are not generating everything from scratch every week. Talk to other Doms if you have access to that community. The Dom is the engine of the dynamic. The engine needs maintenance.
Things to make your sub do, the dom-side framing
Here is a starter set, broken out by what each kind of task does in your design. This is not a comprehensive list. The full menu lives in our 100 tasks to give your sub post. The framing here is what each category is for, so you can pick deliberately rather than at random.
Tasks for presence. Small daily rituals that keep the dynamic active in ordinary hours. Morning texts in a specific format. End-of-day check-ins. A photo at a particular time. These are low-intensity, high-frequency, and they are the floor that everything else stands on.
Tasks for service. Acts of care directed at you. Bringing you a glass of water before bed. Researching something you mentioned in passing. Cooking something specific for you. These work especially well for service-oriented subs and they reinforce the give-and-take of the dynamic.
Tasks for body. Physical anchors. Stretching, hydration, sleep, exercise, posture work. These tie the dynamic to the body, which deepens the psychological impact for most subs and also has the side effect of being good for them.
Tasks for mind. Journaling, reflection, reading, learning. These are the ones that pay off slowest and matter most over time. A sub who has been journaling against your prompts for six months has a different relationship to the dynamic than one who has not.
Tasks for tension. Things with stakes attached. Time-bound tasks. Tasks with consequences for failure. Tasks with rewards for excellence. These are where the dom tasks of design and calibration matter most, because the stakes have to feel real but never punitive.
Pick from across the categories on purpose. A dynamic that is all presence and no tension goes flat. A dynamic that is all tension and no presence burns out. A good week of dom tasks pulls from at least three of the five.
What separates a great Dom from a mediocre one
The thing that separates great Doms from mediocre ones is not how strict they are or how creative their tasks are or how much their sub fears them. It is how thoughtfully they design and how well they pay attention. Strictness without thought is just rigidity. Creativity without calibration is just chaos. Fear without trust is just fear.
The signal of a great Dom is that their sub is thriving. Their sub is engaged, growing, looking forward to the next thing, not running out the clock. That signal comes from the Dom doing the dom tasks well: designing carefully, calibrating constantly, responding consistently, and tuning the economy as it shifts. None of that is glamorous. All of it is the actual job.
The other signal is that the Dom is sustainable. They are not burning out. They are not phoning it in by week six. They have built a system that works for both of them, and they are managing their own energy alongside their sub’s. That is the long game.
Common mistakes in your dom tasks
A few of the most common patterns that break dom tasks at the design level:
Over-tasking. More is not better. A sub who has fourteen daily rituals plus weekly tasks plus monthly challenges is going to drop balls, feel guilty, and eventually disengage. Three to five well-chosen daily rituals plus a couple of weekly assignments is plenty for most people. Save the firepower for when it matters.
Under-feedback. Tasks completed without response stop feeling meaningful. If you find yourself getting submissions and just acknowledging them, you are missing the most important dom task on the board. Slow down and actually respond.
Inconsistent stakes. If demerits sometimes lead to consequences and sometimes do not, the demerit system is broken. If rewards sometimes get redeemed and sometimes get ignored, the reward system is broken. The economy only works if the rules are real. We wrote a deeper post on punishment ideas for submissives that goes into the consistency side specifically.
Designing for who you wish your sub were. Tasks have to match the actual person, not the imagined one. If your sub has never journaled, “write 500 words a day” is a setup for failure. Start with a smaller version and ladder up.
Skipping the rules layer. Tasks are the foreground. Rules and protocols are the background structure that holds the dynamic together when no specific task is active. Most new Doms over-index on tasks and under-index on the structural layer. Our guide on D/s rules and protocols covers what that scaffolding actually looks like.
How SubTasks fits into this
We built SubTasks because the dom-side workload is real and it is not something a generic to-do app handles well. The Dom needs visibility into completion patterns, a way to set up an economy and adjust it as it shifts, a feedback channel that closes the loop on every completion, and tools for the parts of the work that should not have to be done from scratch every week.
The product is built around two-sided asymmetry on purpose. The Dom sees the whole board. The sub plays on it. Task Kits give you starter economies you can customize instead of building from blank pages. The rating system makes feedback fast and structured. The points and rewards engine runs the economy so you can focus on tuning it instead of computing it. If any of the dom tasks above sounded like work you do not love doing manually, look at how it works and see if the tooling helps.
If designing the whole economy from scratch sounds like more work than you have bandwidth for, The Framework is a starter kit built for exactly this: a complete structural backbone you can adopt and tune instead of starting blank.
That is not a pitch for any specific feature. It is a pitch for taking the dom-side workload seriously and using whatever tool helps you do it well, whether that is SubTasks or a notebook or a shared doc. The principle holds regardless of the tool: doing dom tasks well takes effort, and the effort is the craft.
Closing thought
Dom tasks, in the meaningful sense of the term, are not the orders you give. They are the work you do. Designing, calibrating, responding, tuning, maintaining. The Dom who treats the role as a craft rather than a position will outlast and out-deliver the Dom who treats it as a checklist of things to demand. Your sub will feel the difference. The dynamic will feel the difference.
If you are starting out and the dom-side workload feels overwhelming, that is normal. Pick one dom task from this post and get better at it for a month. Then pick another. The craft compounds. Six months from now you will not recognize how you used to do this.
If you are an experienced Dom and you read this thinking “yeah, none of that is new to me,” good. The mark of being good at this is that the work becomes invisible to you. The next move is to ask whether you have plateaued anywhere in particular, whether your sub has outgrown the current intensity window, and whether there are dom tasks on the list above that you have been quietly neglecting. There usually are.
Either way, the work is the work. The list of things to make your sub do is the surface. The dom tasks underneath are the substance. Get the substance right and the surface takes care of itself.