Consequences

Create accountability through defined consequences for incomplete or late tasks

What Are Consequences?

Consequences are predefined outcomes that can be attached to tasks. They provide structure and accountability in your dynamic by establishing clear expectations for what happens when tasks aren't completed properly.

✓ Consensual Accountability
Consequences should always be discussed and agreed upon between all parties. They work best when they're reasonable, meaningful, and contribute to growth within the dynamic.

Creating Consequences

To create a consequence that can be attached to tasks:

  1. Navigate to Consequences
    Go to the Consequences page from the main navigation menu.
  2. Click Create Consequence
    Click the "Create Consequence" button to open the creation form.
  3. Fill in Details
    Enter a name and description for the consequence. Be specific about what the consequence involves.
  4. Set Severity (Optional)
    Categorize the consequence by severity to help match it to appropriate tasks.
  5. Save
    Click "Create" to save the consequence. It's now available to attach to tasks.

Consequence Properties

Name

A short, descriptive name for the consequence (e.g., "Extra chores", "Early bedtime", "Lines writing").

Description

Detailed explanation of what the consequence involves. Include:

Severity Level

Consequences can be categorized by severity:

Attaching Consequences to Tasks

When creating or editing a task, you can attach one or more consequences:

  1. Open Task Form
    Create a new task or edit an existing one.
  2. Find Consequences Section
    Scroll to the "Consequences" section of the task form.
  3. Select Consequences
    Choose from your predefined consequences. You can attach multiple consequences to a single task.
  4. Set Trigger Conditions (Optional)
    Specify when the consequence applies: incomplete, late, or both.

Trigger Conditions

Consequences can be triggered under different conditions:

Condition When It Triggers
Not Completed Task is not submitted by due date
Completed Late Task is submitted after the due date
Rejected Task is rejected during review
Any Failure Any of the above conditions

Viewing Consequence History

Track consequences that have been triggered:

For Submissives

For Dominants

Managing Triggered Consequences

Marking as Fulfilled

When a consequence has been carried out:

  1. Go to the triggered consequence
  2. Click "Mark as Fulfilled"
  3. Optionally add a note about how it was fulfilled
  4. The consequence is moved to history

Dismissing a Consequence

Dominants can dismiss a triggered consequence if circumstances warrant:

  1. Go to the triggered consequence
  2. Click "Dismiss"
  3. Provide a reason for dismissal
  4. The consequence is recorded as dismissed (not fulfilled)

Consequence Examples

Here are some common consequence ideas (always ensure these are consensually agreed upon):

Light Consequences

Moderate Consequences

Severe Consequences

⚠ Important
Consequences should never involve anything unsafe, non-consensual, or that violates the established boundaries of your dynamic. Always honor safewords and negotiate consequences in advance.

Best Practices

Make Them Meaningful

Consequences work best when they're connected to the task or behavior. For example, forgetting a chore might result in extra chores.

Be Consistent

Apply consequences consistently to build trust and clear expectations in your dynamic.

Scale Appropriately

Match the severity of the consequence to the importance of the task and the circumstances of the failure.

Review Regularly

Periodically review your consequences list and adjust based on what's working in your dynamic.

Limits

The number of consequences you can create depends on your subscription tier: