Step-by-step instructions for setting up, maintaining, and using the site.
Goal: explain what to do after login, how to maintain the household, and how parents and kids use every major touchpoint.
The app now uses a guided setup assistant with a visible Set Up Later option.
If a parent skips setup, the parent dashboard shows a setup checklist so they can continue later.
Login page with the Sign Up tab, email/password fields, Create Account button, and Google button visible.
The guided setup assistant walks parents through the first household setup one screen at a time.
One screenshot per setup step, plus screenshots of the info buttons for compensation, pay cycle, approval mode, and chores.
If a parent selects Set Up Later, the app saves the household and opens the parent dashboard with a setup checklist.
Parent dashboard Overview with stats tiles, kid balance cards, Pay Out button area, and Today activity.
Add/Edit Chore modal showing name, standards, points/flat pay, frequency, assignment, sub-task editor, and Save Chore.
Approvals tab with a pending card, proof photo, checklist, Approve, Reject, and Exceeded Expectations buttons.
Pay Day modal with each kid's points and amount, plus the confirmation button.
Kid select screen, PIN screen, and loaded kid dashboard.
| Model | How It Works | What Parents Must Set |
|---|---|---|
| A - Points | Each chore earns points. Points convert to dollars. | Points per $1, optional daily minimum points, optional daily point cap, point values on chores. |
| B - Flat Pay | Each chore has its own dollar amount. | Optional daily earning cap and a flat dollar value on each chore. |
| C - Daily Min | All chores count equally. A child earns full-day pay after completing the required number of chores. | Chores needed for a full day, full-day pay amount, optional daily earning cap. |
Compensation Model settings expanded with model buttons A, B, C and the fields for each model.
Contact support when the instructions above do not fix the issue or when household data looks wrong.
During beta testing, users should expect that some bugs may appear because of browser differences, connection issues, account setup differences, or other unforeseen circumstances.
The attached kid dashboard image is the kind of useful screenshot beta users should send when they see a confusing label, spacing issue, or unexpected dashboard state.
Recommended: keep a simple public-facing update log during beta so testers know their reports are being heard.