Family responsibilities change.

A chore may need a better time, a new owner, clearer instructions, or a different S’mores value. Other chores may no longer belong in the family system.

Edit a chore when the responsibility still matters.

Delete it when the family no longer needs it.

Quick Start

1. Open the chore from a parent profile.
2. Choose Edit when the chore should continue with changes.
3. Update the needed setting.
4. Save and check the next occurrence.
5. Choose Delete only when the chore should leave the system.
6. Review Weekly View or history before removing important recurring chores.

Exact gestures and menu locations may differ between iOS and Android.

When to Edit a Chore

Edit when:

• The chore name is unclear
• The assigned family member changes
• The schedule no longer fits
• The due time creates repeated misses
• The S’mores value feels unfair
• The reminder is not useful
• The instructions need more detail
• Approval or Photo Proof is no longer needed
• The chore type should change
• The child has grown into more responsibility

Editing lets the family improve the system without recreating the chore from the beginning.

What You May Be Able to Change

Depending on the current app version, a parent may be able to update:

• Chore name
• Category
• Assigned family member
• Chore type
• S’mores value
• Schedule
• Start or end date
• Due time
• Reminders
• Instructions
• Smart List
• Photo Proof
• Parent Approval
• Lock
• Late Penalty
• Save/Spend allocation settings

Verify current field availability before adding screenshots.

Edit One Problem at a Time

If a chore keeps getting missed, avoid changing everything at once.

Try one change:

• Move the due time
• Rewrite the name
• Add one reminder
• Change the owner
• Split the chore into smaller actions
• Increase or decrease the S’mores value
• Turn off unnecessary approval

Review the next few occurrences.

When several settings change at the same time, it becomes harder to know what helped.

Repeating Chores

Editing a repeating chore changes the chore going forward.

Use an instance-level action such as Excuse when only one occurrence is different.

Example:

The family still needs “Feed the dog” every morning, but Maya is sick today.

Do not delete or rebuild the entire repeating chore. Excuse Maya from today’s instance.

Future occurrences remain active.

Exact behavior for past and future occurrences should be verified in the current product.

Change the Assigned Person

Change the owner when:

• A child has grown into the responsibility
• The family schedule changes
• A sibling should take over
• A permanent owner is no longer fair
• The chore should become Rotate

Review the S’mores value and instructions after changing the assignee. A chore may require different support for a younger child.

Change the Chore Type

A chore that creates arguments may need a different ownership rule.

Examples:

• Individual → Rotate when turns matter
• Individual → Collaborate for a family project
• Individual → As Needed when the work appears unpredictably
• As Needed → Individual when nobody takes ownership
• Compete → Collaborate when competition creates tension

Review how S’mores are allocated after changing the type.

Change the S’mores Value

Adjust the value when:

• The effort has changed
• The child has learned the skill
• The chore takes longer than expected
• The Reward Shelf changes
• A Late Penalty or advanced type affects the result
• The value feels unfair compared with similar chores

Avoid changing values constantly. Kids should be able to understand what work is worth.

When to Delete a Chore

Delete when:

• The family no longer needs the responsibility
• A seasonal project ended
• The family no longer has the pet or activity
• The chore was created by mistake
• A duplicate chore exists
• The responsibility was replaced by a clearer chore
• The chore belongs to an old family setup

Do not delete a chore only because one occurrence was missed.

Fix the setup or use the correct instance action.

Think About History

Deleting the chore and changing past history are not always the same thing.

Before deleting:

• Review completed occurrences
• Check Weekly View
• Consider Wallet or S’mores activity
• Confirm whether the family needs the record
• Verify how deletion affects history in the current product

Avoid promising that all historical information remains or disappears until the behavior is verified.

Check the Result After Saving

After editing:

• Open the next occurrence
• Check the owner
• Check the date and time
• Confirm reminders
• Confirm the S’mores value
• Check approval or Photo Proof
• View it from the child’s profile

A saved parent screen does not guarantee the child sees the intended result.

Common Questions

Can I edit only one occurrence of a repeating chore?

The core chore edit applies going forward. Use instance-level actions for one-time exceptions. Confirm exact product controls.

Will editing change completed chores?

Confirm current history behavior before publication.

Can I restore a deleted chore?

Do not assume deleted chores can be recovered. Review carefully before deleting.

Should I delete chores that were missed?

No. A missed occurrence may show that the time, owner, or instructions need improvement.

Can I change an Individual chore to Rotate?

Yes, where supported. Review the participant list and S’mores behavior after the change.

Best First Action

Pick one chore that keeps getting missed.

Change only the clearest problem—name, owner, timing, reminder, or value—and review the next occurrence.

Related Articles

• How to Create a Chore
• How to Excuse, Complete Late, or Skip a Chore
• Chore Types in S’moresUp
• Use Weekly View in S’moresUp