Delivery tracker
Neighbors PLEYSMART build progress
Every requirement from the specification — 155 use cases across six phases — with what is live today, what comes next, and how each one is tested. Every use case has a written test case; 132 are already being run against the app.
Overall completion
98%
139
Done
1
In progress
3
Planned
12
Out of scope
Test coverage
133 / 153
test cases written · expandable scenarios on every row below
19
Automated
114
Manual
20
Pending build
8
No test yet
Group 1 · Resident management (UC-01 – UC-05)
5 of 5 completeUC-01 Register as resident
shared PLEYSMART sign-in
Test scenarios (2)
TC-01Tested (automated)
Steps: Sign in at `/auth` with a PLEYSMART account that has neighborhood access
Expected: Lands in the app, header shows the signed-in email
TC-01bTested (manual)
Steps: Sign in with an account without neighborhood access
Expected: Access notice shown, app content stays locked
P1DoneTested (automated)UC-02 View own profile
Profile page
Test scenarios (1)
TC-02Tested (automated)
Steps: Open `/profile` while signed in
Expected: Name, contact, neighborhood and language are shown
P2DoneTested (automated)UC-03 Update profile (contact, language, notifications)
contact, language and notification settings on Profile
Test scenarios (2)
TC-03Tested (automated)
Steps: Change phone and language on `/profile`, save, reload
Expected: New values persist after reload
TC-03bTest written
Steps: Change notification settings, save, reload
Expected: Settings persist
P2DoneTested (automated)UC-04 Change subscription tier
Test scenarios (1)
TC-04Tested (manual)
Steps: Change subscription tier
Expected: Tier updates and premium features unlock
P4DoneTested (manual)UC-05 Deactivate account
Profile page, typed confirmation, blocked while jobs are under way
Test scenarios (1)
TC-05Tested (manual)
Steps: On Profile, type DEACTIVATE and confirm
Expected: Account marked closed, neighborhoods dropped, contact details and language cleared; blocked while a job is under way
P6DoneTested (manual)
Group 2 · Contractor management (UC-06 – UC-10)
4 of 5 completeUC-06 Register as contractor
invitation link at `/join/<token>` creates the account
Test scenarios (1)
TC-06Tested (manual)
Steps: On `/contractors` invite a contractor, copy its invite link, open `/join/<token>` in a fresh session, sign in with a different PLEYSMART account and accept
Expected: Contractor account created and linked to that login; lands on `/contractor-account`
P2DoneTested (manual)UC-07 View own contractor profile (rank, reviews)
"My business" page
Test scenarios (1)
TC-07Tested (manual)
Steps: Contractor opens `/contractor-account`
Expected: Standing, rating, completed-work referral count, neighborhoods, reviews, trades and service area shown
P2/P3DoneTested (manual)UC-08 Update trades, service area, portfolio
portfolio still to come
Test scenarios (1)
TC-08Tested (manual)
Steps: Contractor edits business details, trades and travel distance, saves, reloads
Expected: Changes persist and show to residents on `/contractors`
P2DoneTested (manual)UC-09 Update licence and insurance details
Test scenarios (1)
TC-09Test written
Steps: Licence/insurance details
Expected: Out of Phase 1–3 (deferred per SRS)
LaterOut of scopeTest writtenUC-10 Deactivate contractor account
My business page; open bids and live deals withdrawn
Test scenarios (1)
TC-10Tested (manual)
Steps: On My business, type DEACTIVATE and confirm
Expected: Business closed, open bids and live deals withdrawn; blocked while committed to a job
P6DoneTested (manual)
Group 3 · Job request management (UC-11 – UC-16)
6 of 6 completeUC-11 Post a private job (urgency, AI toggle)
Test scenarios (1)
TC-11Tested (automated)
Steps: Post a job with trade, description, urgency and budget; it should open its own page and appear under "Jobs you've posted"
Expected: Job saved as private with status Open, the chosen urgency and budget; signed-out visitors get the sign-in gate
P3DoneTested (automated)UC-12 Upload job photos
Test scenarios (1)
TC-12Tested (automated)
Steps: Attach photos to a job (upload, or take one with the camera)
Expected: Photos store and display on the job page; the job card shows the photo count
P3DoneTested (automated)UC-13 View job details, invitations, bids
job page lists invitations and their replies
Test scenarios (1)
TC-13Tested (manual)
Steps: Open a job you posted
Expected: Details, photos, invitations and their replies all listed
P3DoneTested (manual)UC-14 Edit job before invitations go out
locked once invitations are sent
Test scenarios (1)
TC-14Tested (manual)
Steps: Edit a job before invitations are sent, then after
Expected: Edits save while nobody is invited; the edit button disappears and the server refuses once invitations go out
P3DoneTested (manual)UC-15 Update job status
work started / mark complete
Test scenarios (1)
TC-15Tested (manual)
Steps: Move a job through its statuses
Expected: "Work has started" and "Mark complete" only appear after selection, and stamp the time
P3DoneTested (manual)UC-16 Cancel job before selection
invited contractors notified
Test scenarios (2)
TC-16Tested (manual)
Steps: Cancel a job before selection
Expected: Job marked cancelled, open invitations withdrawn, invited contractors notified
TC-16bTested (manual)
Steps: Sign in as an unrelated resident and open the job URL
Expected: Access denied (jobs are private)
P3DoneTested (manual)
Group 4 · Job invitations (UC-17 – UC-21)
5 of 5 completeUC-17 Match and send invitations to 6–7 contractors
ranked matches, 7 pre-picked
Test scenarios (1)
TC-17Tested (manual)
Steps: On a job, choose "Find contractors to invite"
Expected: Ranked matches shown — trade match and completed work for neighbors here first — with up to 7 pre-selected; sending records each invitation
P3DoneTested (manual)UC-18 Contractor views invitation
"My work" page
Test scenarios (1)
TC-18Tested (manual)
Steps: Contractor opens "My work"
Expected: Their invitations listed with the brief, budget, photo count and time left
P3DoneTested (manual)UC-19 Accept and proceed to bid
bidding screen comes next
Test scenarios (1)
TC-19Tested (manual)
Steps: Contractor accepts
Expected: Invitation marked accepted and the resident notified; bidding opens next
P3DoneTested (manual)UC-20 Decline invitation
resident notified
Test scenarios (1)
TC-20Tested (manual)
Steps: Contractor declines
Expected: Invitation closed, no bid possible, resident notified
P3DoneTested (manual)UC-21 Auto-expire (48h / 24h / 4h by urgency)
expires with the bid deadline
Test scenarios (1)
TC-21Tested (manual)
Steps: Let an invitation pass its window (48h/24h/4h by urgency)
Expected: Invitation auto-expires on the next view and can no longer be answered
P3DoneTested (manual)
Group 5 · Bids (UC-22 – UC-28)
5 of 7 completeUC-22 Submit a bid
Test scenarios (1)
TC-22Tested (manual)
Steps: Submit a bid with price, scope and timeline
Expected: Bid recorded and visible to the resident
P3DoneTested (manual)UC-23 Declare subcontractor
Test scenarios (1)
TC-23Test written
Steps: Subcontractor declaration
Expected: Out of scope
—Out of scopeTest writtenUC-24 Resident views all bids
Test scenarios (1)
TC-24Tested (manual)
Steps: Resident views bids
Expected: All active bids listed with contractor standing
P3DoneTested (manual)UC-25 Contractor views own bid
Test scenarios (1)
TC-25Tested (manual)
Steps: Contractor views own bid
Expected: Own bid only; other bids not visible
P3DoneTested (manual)UC-26 Update bid before deadline
Test scenarios (1)
TC-26Tested (manual)
Steps: Contractor edits a bid before the deadline
Expected: Edit saved; blocked after deadline
P3DoneTested (manual)UC-27 Update subcontractor declaration
Test scenarios (1)
TC-27Test written
Steps: Update subcontractor declaration
Expected: Out of scope
—Out of scopeTest writtenUC-28 Withdraw bid
Test scenarios (1)
TC-28Tested (manual)
Steps: Contractor withdraws a bid
Expected: Bid removed from the active count
P3DoneTested (manual)
Group 6 · Selection and agreement (UC-29 – UC-32)
4 of 4 completeUC-29 Select a contractor (3 active bids minimum, no bypass)
Test scenarios (1)
TC-29Tested (manual)
Steps: Try to select with only 2 active bids, then with 3
Expected: Selection blocked at 2, allowed at 3; no bypass anywhere
P3DoneTested (manual)UC-30 Both parties confirm agreed price
Test scenarios (1)
TC-30Tested (manual)
Steps: Both sides confirm the agreed price
Expected: Job moves to agreed only after both confirmations
P3DoneTested (manual)UC-31 Notify unselected contractors
Test scenarios (1)
TC-31Tested (manual)
Steps: Complete a selection
Expected: Unselected contractors notified
P3DoneTested (manual)UC-32 Mark job complete
Test scenarios (1)
TC-32Tested (manual)
Steps: Mark the job complete
Expected: Job marked complete and a review is required
P3DoneTested (manual)
Group 7 · Reviews (UC-33 – UC-37)
5 of 5 completeUC-33 Post mandatory post-job review
review card on the job page, prompted at completion
Test scenarios (1)
TC-33Tested (manual)
Steps: Complete a job and try to skip the review
Expected: Review prompt persists until submitted
P3DoneTested (manual)UC-34 View contractor reviews
on contractor cards and "My business"
Test scenarios (1)
TC-34Tested (manual)
Steps: Open a contractor profile
Expected: Reviews and average rating shown
P3DoneTested (manual)UC-35 Edit review within 48 hours
Test scenarios (1)
TC-35Tested (manual)
Steps: Edit a review inside 48h, then after
Expected: Edit allowed inside the window, refused after
P3DoneTested (manual)UC-36 Flag a review
notifies neighborhood admins
Test scenarios (1)
TC-36Tested (manual)
Steps: Flag a review
Expected: Review flagged for admin attention
P3DoneTested (manual)UC-37 Admin removes policy-violating review
admin only, reviewer notified, rank recalculated
Test scenarios (1)
TC-37Tested (manual)
Steps: Admin removes a flagged review
Expected: Review hidden and rank recalculated
P3DoneTested (manual)
Group 8 · Referrals (UC-38 – UC-42)
5 of 5 completeUC-38 Refer an existing contractor
Contractors page, incl. AI business-card scan
Test scenarios (2)
TC-38Tested (automated)
Steps: Refer a contractor, filling the work-completed details
Expected: Referral saved as weighted and counted in ranking
TC-38bTested (manual)
Steps: Upload a business card photo on the referral form
Expected: Name, phone, email, website, city, state and trade fill in automatically
P2DoneTested (automated)UC-39 View referral history
"My recommendations" on Contractors
Test scenarios (1)
TC-39Tested (automated)
Steps: Open "My recommendations"
Expected: Only your own referrals listed
P2DoneTested (automated)UC-40 Auto-update referring resident's standing
standing card on Profile
Test scenarios (1)
TC-40Tested (manual)
Steps: Complete a job for a contractor you referred
Expected: Your standing updates automatically
P3DoneTested (manual)UC-41 Add your own referral for an existing contractor
general referrals allowed with zero ranking weight; only confirmed completed work (and job reviews) count
Test scenarios (2)
TC-41Tested (automated)
Steps: Refer a contractor without work details
Expected: Saved as a general mention, shown with zero ranking weight
TC-41bTested (manual)
Steps: Compare ranking before and after adding a general mention
Expected: Contractor's position is unchanged
P2DoneTested (automated)UC-42 Withdraw a referral
Test scenarios (2)
TC-42Tested (automated)
Steps: Withdraw a referral
Expected: Referral removed and counts drop
TC-42bTested (automated)
Steps: Switch scope between "my neighborhood" and "everywhere"
Expected: Local vouched contractors listed first; global list only under "everywhere"
P2DoneTested (automated)
Group 9 · Subscriptions (UC-43 – UC-47)
5 of 5 completeUC-43 Subscribe to premium
Test scenarios (1)
TC-43Tested (manual)
Steps: Subscribe to premium
Expected: Payment taken and premium features unlock
P4DoneTested (manual)UC-44 View subscription
Test scenarios (1)
TC-44Tested (manual)
Steps: View subscription
Expected: Tier, price and renewal date shown
P4DoneTested (manual)UC-45 Upgrade tier
Test scenarios (1)
TC-45Tested (manual)
Steps: Upgrade tier
Expected: New tier active immediately, charge prorated
P4DoneTested (manual)UC-46 Update payment method
Test scenarios (1)
TC-46Tested (manual)
Steps: Update payment method
Expected: New card stored and used next renewal
P4DoneTested (manual)UC-47 Cancel subscription
Test scenarios (1)
TC-47Tested (manual)
Steps: Cancel subscription
Expected: Access continues to period end, then reverts
P4DoneTested (manual)
Group 10 · AI analysis, premium only (UC-48 – UC-58)
11 of 11 completeUC-48 Analyse job description and photos
Test scenarios (1)
TC-48Tested (manual)
Steps: On a job page, press "Analyze this job" as a premium resident
Expected: Analysis appears: summary, scope checklist, notes; stored and shown on reload
P4DoneTested (manual)UC-49 Generate 2–3 solution approaches
Test scenarios (1)
TC-49Tested (manual)
Steps: Read the analysis
Expected: Scope checklist and "worth asking bidders" give distinct angles on the work
P4DoneTested (manual)UC-50 Fair price band
Test scenarios (1)
TC-50Tested (manual)
Steps: Check the price guidance
Expected: A price band with a confidence level; empty band with explanation when the job is too vague
P4DoneTested (manual)UC-51 View AI job analysis
Test scenarios (1)
TC-51Tested (manual)
Steps: Open the analysis as a free resident
Expected: "Part of the Premium plan" message with a link to plans; nothing stored
P4DoneTested (manual)UC-52 Analyse incoming bids
Test scenarios (1)
TC-52Test written
Steps: Receive bids on an analysed job
Expected: Each bid analysed against the estimate
P4DoneTest writtenUC-53 Best-value recommendation
Test scenarios (1)
TC-53Test written
Steps: Read the recommendation
Expected: One best-value bid named with reasons
P4DoneTest writtenUC-54 View bid analysis
Test scenarios (1)
TC-54Test written
Steps: Open bid analysis
Expected: Comparison table shown
P4DoneTest writtenUC-55 Refresh analysis on new bid
Test scenarios (1)
TC-55Test written
Steps: A new bid arrives
Expected: Analysis refreshes
P4DoneTest writtenUC-56 Completion report (estimate vs final)
Test scenarios (1)
TC-56Test written
Steps: Complete an analysed job, record the final cost
Expected: Report compares estimate, agreed and final
P4DoneTest writtenUC-57 View completion report
Test scenarios (1)
TC-57Test written
Steps: Open the completion report
Expected: Report readable; free accounts see the upgrade message
P4DoneTest writtenUC-58 AI updates contractor performance summary
Test scenarios (1)
TC-58Test written
Steps: Contractor asks for a performance summary
Expected: Summary reflects completed jobs and reviews
P4DoneTest written
Group 11 · Notifications (UC-59 – UC-63)
5 of 5 completeUC-59 Generate and send notifications
own in-app stream; fires on invitation accepted/expired, more events wire in with jobs
Test scenarios (1)
TC-59Test written
Steps: Trigger an event (invitation, bid, selection)
Expected: Notification created for the right people only
P2/P3DoneTested (automated)UC-60 View notification centre
/notifications page
Test scenarios (1)
TC-60Test written
Steps: Open the notification centre
Expected: Unread count and list correct
P3DoneTested (automated)UC-61 Mark as read
Test scenarios (1)
TC-61Test written
Steps: Mark one as read
Expected: Count decreases and state persists
P3DoneTested (automated)UC-62 Notification preferences
in-app and email switches on Profile
Test scenarios (1)
TC-62Test written
Steps: Turn a notification type off
Expected: No further notifications of that type
P3DoneTested (automated)UC-63 Clear notifications
Test scenarios (1)
TC-63Test written
Steps: Clear notifications
Expected: List empties and stays empty after reload
P3DoneTested (automated)
Group 12 · Contractor rank (UC-64 – UC-68)
5 of 5 completeUC-64 Initialise rank at registration
rank starts at zero and earns points only from completed reviewed work
Test scenarios (1)
TC-64Tested (manual)
Steps: Register a new contractor
Expected: Rank starts at the defined baseline
P2DoneTested (manual)UC-65 View rank breakdown
score breakdown on "My business"
Test scenarios (1)
TC-65Tested (manual)
Steps: Open rank breakdown
Expected: Each component and its weight shown
P3DoneTested (manual)UC-66 Recalculate after review
Test scenarios (1)
TC-66Tested (manual)
Steps: Post a review
Expected: Rank recalculates using the fixed formula
P3DoneTested (manual)UC-67 Recalculate after referral
refer, endorse and withdraw all recalculate
Test scenarios (1)
TC-67Tested (manual)
Steps: Add a completed-work referral
Expected: Rank increases; a general mention changes nothing
P3DoneTested (manual)UC-68 Recalculate response/completion rate
on invitation response and job completion
Test scenarios (1)
TC-68Tested (manual)
Steps: Miss an invitation window
Expected: Response rate falls and rank adjusts
P3DoneTested (manual)
Group 13 · Language and translation (UC-69 – UC-76)
7 of 8 completeUC-69 Set language preference
Profile page
Test scenarios (1)
TC-69Tested (automated)
Steps: Set a language on `/profile`
Expected: Preference saved
P2DoneTested (automated)UC-70 Read all content in own language
job posts, bids and chat translated at read time, original always kept
Test scenarios (1)
TC-70Tested (manual)
Steps: Browse with a non-English preference
Expected: Job posts, bids and chat all read in that language
P5DoneTested (manual)UC-71 Update language preference
Test scenarios (1)
TC-71Tested (automated)
Steps: Change language again
Expected: New preference applied everywhere
P2DoneTested (automated)UC-72 Translate job posts
translated for the reading contractor, cached, "show original" toggle
Test scenarios (1)
TC-72Tested (manual)
Steps: View a job posted in another language
Expected: Translated, with a "show original" toggle
P5DoneTested (manual)UC-73 Translate bids
bid notes translated for the resident, prices untouched
Test scenarios (1)
TC-73Tested (manual)
Steps: View a bid in another language
Expected: Notes translated, prices and dates unchanged
P5DoneTested (manual)UC-74 Resolve language pair for a call
deprecated, replaced by multilingual chat (UC-84–91)
Test scenarios (1)
TC-74Test written
Steps: Start a call between two languages
Expected: Out of scope — deprecated, covered by multilingual chat
P5Out of scopeTest writtenUC-75 Maintain supported languages list
one shared list drives the profile picker and the public /languages page
Test scenarios (1)
TC-75Tested (manual)
Steps: Change the shared language list
Expected: Public languages page and the profile picker both show the same set
P6DoneTested (manual)UC-76 Clear language record on deactivation
language reset and contact details cleared on close
Test scenarios (1)
TC-76Tested (manual)
Steps: Set a non-English language, then deactivate
Expected: Language record reset to default, history untouched
P6DoneTested (manual)
Group 14 · Neighborhood and platform admin (UC-77 – UC-83)
7 of 7 completeUC-77 Onboard a neighborhood
Test scenarios (1)
TC-77Tested (automated)
Steps: Admin creates a neighborhood
Expected: Appears in the directory with its own page
P1DoneTested (automated)UC-78 Neighborhood activity dashboard
members, documents, jobs posted/under way/completed, contractors and referrals
Test scenarios (1)
TC-78Tested (manual)
Steps: Open the neighborhood dashboard
Expected: Members, documents, jobs and referral counts correct
P3/P6DoneTested (manual)UC-79 Update neighborhood profile
Test scenarios (1)
TC-79Tested (manual)
Steps: Edit neighborhood name/description
Expected: Changes show on the public page
P1DoneTested (manual)UC-80 Offboard a neighborhood (disable only — nothing deleted)
Test scenarios (1)
TC-80Tested (manual)
Steps: Offboard a neighborhood
Expected: Disabled, removed from the directory, all data retained; re-enable restores it
P6DoneTested (manual)UC-81 Add trade category
admin trades panel
Test scenarios (1)
TC-81Tested (automated)
Steps: Admin adds a trade
Expected: Trade appears in filters and forms
P2DoneTested (automated)UC-82 Update trade category
Test scenarios (1)
TC-82Tested (automated)
Steps: Admin renames a trade
Expected: New name everywhere, existing links intact
P2DoneTested (automated)UC-83 Remove trade category
Test scenarios (1)
TC-83Tested (automated)
Steps: Admin removes a trade
Expected: Trade gone from pickers; existing records unaffected
P2DoneTested (automated)
Group 15 · In-app multilingual messaging (UC-84 – UC-91)
8 of 8 completeUC-84 Start a job chat thread
Test scenarios (1)
TC-84Tested (manual)
Steps: Start a job chat
Expected: Thread created for the job's two parties only
P5DoneTested (manual)UC-85 View thread history (own language, original toggle)
Test scenarios (1)
TC-85Tested (manual)
Steps: Open thread history
Expected: Messages in your language with original toggle
P5DoneTested (manual)UC-86 Auto-archive thread on reviewed/cancelled
Test scenarios (1)
TC-86Tested (manual)
Steps: Review or cancel the job
Expected: Thread auto-archives
P5DoneTested (manual)UC-87 Admin deletes a thread
Test scenarios (1)
TC-87Tested (manual)
Steps: Admin deletes a thread
Expected: Thread gone for both parties
P5DoneTested (manual)UC-88 Send message
Test scenarios (1)
TC-88Tested (manual)
Steps: Send a message
Expected: Delivered and visible to the other party
P5DoneTested (manual)UC-89 Read translated message (under 2s)
Test scenarios (1)
TC-89Tested (manual)
Steps: Receive a message in another language
Expected: Translation appears in under 2 seconds
P5DoneTested (manual)UC-90 Edit within 5 minutes
Test scenarios (1)
TC-90Tested (manual)
Steps: Edit a message inside/outside 5 minutes
Expected: Allowed inside, refused outside
P5DoneTested (manual)UC-91 Delete a message
Test scenarios (1)
TC-91Tested (manual)
Steps: Delete a message
Expected: Removed for both parties
P5DoneTested (manual)
Group 16 · Multilingual voice calls (UC-92 – UC-99) — deprecated
0 of 8 completeUC-92 Start an interpreted call
deprecated, superseded by multilingual chat
—Out of scopeTest writtenUC-93 Call history (no audio kept)
deprecated
—Out of scopeTest writtenUC-94 Join active call within 30s
deprecated
—Out of scopeTest writtenUC-95 End call
deprecated
—Out of scopeTest writtenUC-96 Create two translation streams
deprecated
—Out of scopeTest writtenUC-97 Monitor streams
deprecated
—Out of scopeTest writtenUC-98 Switch language mid-call
deprecated
—Out of scopeTest writtenUC-99 Terminate streams, retain nothing
deprecated
—Out of scopeTest written
Group 17 · Contractor registration invitation (UC-100 – UC-104)
5 of 5 completeUC-100 Refer an unregistered contractor and invite them
invitation emailed automatically from neighbors@pleysmart.org (Resend), with re-send and copy-link fallbacks
Test scenarios (1)
TC-100Tested (manual)
Steps: Invite an unregistered contractor, then use "Copy invite link"
Expected: Invitation recorded and a working `/join/<token>` link is copied (automatic email not built yet)
P2DoneTested (manual)UC-101 View invitation status (pending/accepted/expired)
Test scenarios (1)
TC-101Tested (automated)
Steps: Open the invitation list
Expected: Pending / accepted / expired states correct
P2DoneTested (automated)UC-102 Mark accepted on registration, pre-attach referral
referral pre-attached with no ranking weight
Test scenarios (1)
TC-102Tested (manual)
Steps: Contractor accepts from the link
Expected: Invitation marked accepted and the inviting resident's referral pre-attached with zero ranking weight
P2DoneTested (manual)UC-103 Auto-expire invitation and notify
expiry marked on open; resident notified in-app
Test scenarios (1)
TC-103Tested (manual)
Steps: Open an invitation link after its 30-day window
Expected: Page says expired and the invitation is marked expired (resident notice waits on notifications)
P2DoneTested (automated)UC-104 Withdraw invitation
Test scenarios (1)
TC-104Tested (automated)
Steps: Withdraw an invitation
Expected: Invitation removed and the link stops working
P2DoneTested (automated)
Group 18 · AI boundary, training data and parts list (UC-105 – UC-111)
4 of 7 completeUC-105 Parts & materials list on a job — resident adds parts when posting or later; contractors see them; Premium AI analysis suggests parts the resident can accept (marked "AI suggested")
Test scenarios (1)
TC-105Tested (manual)
Steps: Post a job with parts; on the job page add and remove a part; run Premium AI analysis and accept a suggested part; view the job as an invited contractor
Expected: Parts saved and visible on the job page; accepted AI part appears marked "AI suggested"; contractor sees the list on My work
P4DoneTested (manual)UC-106 Single AI boundary — every model call (answers, embeddings, job analysis, bid comparison, card scan, completion report) runs through one server module; callers name a task, never a model
Test scenarios (1)
TC-106Tested (automated)
Steps: Trigger each AI feature (ask, job analysis, bid comparison, card scan, completion report)
Expected: All calls route through `src/lib/ai/`; no call site names a model directly
P4DoneTested (automated)UC-107 Every AI call logged to `ai_interactions` (task, prompt version, model, input refs, output, latency, tokens) — the future training set; logging is best-effort and never fails a user request
Test scenarios (1)
TC-107Tested (manual)
Steps: Run a neighborhood question and a job analysis, then inspect `ai_interactions`
Expected: One row per call with task, prompt version, model, latency; answer verified live (prompt `answer-v1`)
P4DoneTested (manual)UC-108 Outcome linking — completion report attaches the agreed price, final cost and review to the original AI analysis row (ground truth for a fine-tune)
wired in completionReport
Test scenarios (1)
TC-108Tested (manual)
Steps: Complete a job that had an AI analysis, set the final price, run the completion report
Expected: The analysis row gains outcome `job_completed` with agreed price, final cost and review rating
P4DoneTested (manual)UC-109 Training opt-out flags on neighborhoods and residents (`training_opt_out`); exports must honor them and redact PII
columns exist, no settings UI or export pipeline yet
Test scenarios (1)
TC-109Test written
Steps: Opt a neighborhood and a resident out of training; run an export
Expected: Opted-out rows excluded and PII redacted
P4In progressTest writtenUC-110 Model evaluation harness (`tests/ai-eval/`) — fixed cases per task so any candidate model is scored before a swap
Test scenarios (1)
TC-110Test written
Steps: Run the eval harness against the current model and a candidate
Expected: Scores per task (price-band hit rate, schema validity, card-field accuracy, groundedness) printed
LaterPlannedTest writtenUC-111 Swap a task to a self-hosted open-weight model via env (AI_SELF_HOSTED_URL / _MODEL / _TASKS), no code change
override exists in the registry, untested against a real endpoint
Test scenarios (1)
TC-111Test written
Steps: Set AI_SELF_HOSTED_URL/_MODEL/_TASKS for one task and run it
Expected: That task is served by the self-hosted endpoint; all others unchanged
LaterPlannedTest written
Group 19 · Three-state job access (UC-112 – UC-120)
9 of 9 completeUC-112 Job access state — every job carries its state (pre / in / post execution), set automatically by the job's own lifecycle, never by hand
Test scenarios (1)
TC-112Tested (manual)
Steps: Post a job, select a contractor, then mark it complete
Expected: The job's state moves pre → in → post execution on its own; no manual control exists
P5DoneTested (manual)UC-113 Pre-execution bidder pool — when posting, the owner picks who may see and bid: vetted contractors in my neighborhood, vetted contractors anywhere, or the whole public. Non-contractor neighbors do not see the job at this stage
Test scenarios (1)
TC-113Tested (manual)
Steps: Post a job choosing each pool in turn; view as a vetted local contractor, a contractor elsewhere, a plain neighbor and a signed-out visitor
Expected: Only the chosen pool can open it; a plain neighbor never sees an open job
P5DoneTested (manual)UC-114 AI bidder suggestions ranked in that order — vetted and ranked contractors inside the neighborhood first, then vetted contractors outside it, then public; the owner always decides and can invite anyone
Test scenarios (1)
TC-114Tested (manual)
Steps: Open the suggested-bidder list on a new job
Expected: Vetted local contractors ranked first, then vetted outside, then public; owner can invite someone not suggested
P5DoneTested (manual)UC-115 Widening the pool while still open — the owner can move from neighborhood to anywhere to public (useful when the neighborhood has no approved contractors), with a clear note on who gains access
Test scenarios (1)
TC-115Tested (manual)
Steps: On a neighborhood with no approved contractors, widen the pool to anywhere, then to public
Expected: Warning names who gains access; contractors outside the neighborhood can now see and bid
P5DoneTested (manual)UC-116 In-execution lockdown — from the moment a contractor is selected until the job is complete, only the owner and the assigned contractor(s) can see it; the pool no longer applies
Test scenarios (1)
TC-116Tested (manual)
Steps: Select a contractor, then view the job as another bidder who lost, and as a neighbor
Expected: Both refused; only owner and assigned contractor(s) can open it until completion
P5DoneTested (manual)UC-117 Post-execution sharing choice — at completion the owner chooses neighborhood members only, or public, or keep it private; this is what feeds historical comparables
Test scenarios (1)
TC-117Tested (manual)
Steps: Complete a job and choose neighborhood-only, then change it to public, then to private
Expected: Each choice takes effect immediately in comparables and lists
P5DoneTested (manual)UC-118 Server-enforced access on every path — page, list, search, comparables and API all apply the same state-plus-audience rule; a refusal is a real refusal, not a hidden card
job page, shared view and the feed/search all filter server-side (public jobs plus neighborhood-only jobs from your own neighborhoods)
Test scenarios (1)
TC-118Tested (manual)
Steps: Request a job directly by its address in each state as a viewer who should not have it
Expected: Server refuses on page, list, search, comparables and API alike
P5DoneTested (manual)UC-119 Privacy-safe presentation — a shared job never shows street address, contact details, private notes or individual bids; budget range and final cost are shown
Test scenarios (1)
TC-119Tested (manual)
Steps: View a shared completed job as an onlooker
Expected: No street address, contact details, private notes or individual bids; budget range and final cost shown
P5DoneTested (manual)UC-120 Report a shared job; neighborhood admins can unshare it (back to private) or remove it
residents report a shared job with a reason, admins see reports on the feed and can unshare, dismiss or mark handled
Test scenarios (2)
TC-120Tested (manual)
Steps: As a resident, open Historical Comparisons, choose "Report this job", give a reason and send it
Expected: Report is recorded once per resident, neighborhood admins are notified
TC-120bTested (manual)
Steps: As a neighborhood admin, review a reported job and unshare it (or dismiss / mark handled)
Expected: Job leaves the feed and goes private, owner is notified, open reports on it close
P5DoneTested (manual)
Group 19b · Historical comparables — the main point (UC-121 – UC-126)
6 of 6 completeUC-121 "Jobs like this" while posting — as you pick a trade and describe the work, up to 10 similar past jobs appear (trade, scope, photos, cost, days taken, rating)
"Jobs like this nearby" panel on the posting page, up to 10 matches with cost, days taken and rating
Test scenarios (1)
TC-121Tested (manual)
Steps: Start posting a job, pick a trade and type a description
Expected: Up to 10 similar past jobs appear with cost, days taken and rating, refreshing as you type
P5DoneTested (manual)UC-122 Similarity matching — ranked by trade, wording of the work, nearness (same neighborhood, then city/zip/county), recency and completion
ranked by trade, wording overlap, nearness (neighborhood → city → state) and recency
Test scenarios (1)
TC-122Tested (manual)
Steps: Compare the list for a job in your neighborhood vs a distant one
Expected: Nearer, more recent and completed jobs rank first; unrelated trades absent
P5DoneTested (manual)UC-123 Cost benchmark from comparables — typical range, median and spread for this kind of job nearby, plus how many jobs it is based on and a caution when too few
typical range (25th–75th), median and job count, with a caution under 5 jobs or when no costs recorded
Test scenarios (1)
TC-123Tested (manual)
Steps: Read the cost benchmark on a trade with many past jobs, then one with almost none
Expected: Typical range and median with the count shown; a caution instead of a range when too few
P5DoneTested (manual)UC-124 Comparable detail — open a past job read-only: description, parts used, what it was estimated at, agreed at and finally cost, plus the review
"Jobs nearby" feed at /feed with search by words, trade and neighborhood, and a read-only detail view
Test scenarios (1)
TC-124Tested (manual)
Steps: Search the Jobs nearby feed by word, trade and neighborhood, then open one result
Expected: Only shared finished jobs appear; detail shows description, parts, budget, final cost and rating, no household identity
P5DoneTested (manual)UC-125 Feeds the AI — the price band and analysis cite the same nearby comparables instead of general guesswork
the same comparables are sent into the AI job analysis to anchor the price band and its confidence
Test scenarios (1)
TC-125Tested (manual)
Steps: Run the Premium AI analysis on the new job
Expected: Its price band references the same nearby comparables and says how many
P5DoneTested (manual)UC-126 Contribution and opt-out — completed jobs join the comparable pool according to the resident's visibility choice; a resident can keep a job out entirely
only jobs shared after completion enter the pool; keeping a job private (or an admin unshare) removes it
Test scenarios (1)
TC-126Tested (manual)
Steps: Mark a completed job as kept out of comparables
Expected: It stops appearing for other residents
P5DoneTested (manual)
Group 20 · Contractors added from neighborhood sources (UC-127 – UC-130)
4 of 4 completeUC-127 Contractor list split by reference — one directory, two sections: referred by your neighbors, and not referred yet (listed from neighborhood sources)
Contractors page splits on resident referrals vs admin-added mentions
Test scenarios (1)
TC-127Tested (manual)
Steps: Open Contractors for your neighborhood
Expected: Two sections: "Referred by your neighbors" and "Not referred yet", each with a count
P5DoneTested (manual)UC-128 Admin imports from neighborhood sources — paste posts and comments, the AI extracts each business, the trade, contacts, the neighbor who mentioned them, what they said and when
admin-only "Add contractors from neighborhood sources" card, task `source_extraction` through the AI boundary
Test scenarios (1)
TC-128Tested (manual)
Steps: As a neighborhood admin, paste neighborhood source material naming contractors and press "Read the posts"
Expected: Each business is listed for admin review; source records remain private and nothing is saved until selected
P5DoneTested (manual)UC-129 Provenance kept on every imported record — who added it, when, which neighbor was quoted, the excerpt, the date and the source link
`source`, `source_name`, `source_excerpt`, `source_url`, `source_posted_at`, `imported_by`, `imported_at`
Test scenarios (1)
TC-129Tested (manual)
Steps: Add the selected contractors, then reopen the directory and create a matching job
Expected: They appear under "Not referred yet" as "Added by admin from neighborhood sources" with no names or quotes displayed; their extracted trades make them available for matching
P5DoneTested (manual)UC-130 Imported mentions never carry ranking weight — only a resident's own completed-work referral or a job review counts
database rule forces admin-imported rows to non-completed; the card says so in plain words
Test scenarios (1)
TC-130Tested (manual)
Steps: Check the ranking of an imported contractor, then add your own completed-work referral
Expected: Imported mentions add nothing to standing; your referral moves them into "Referred by your neighbors" and counts
P5DoneTested (manual)
Group 21 · Standing neighborhood by neighborhood (UC-131 – UC-135)
5 of 5 completeUC-131 A contractor keeps a separate record in every neighborhood they work in — reviews, verified referrals, invitations answered, jobs finished
`contractor_neighborhood_stats`, one row per business per neighborhood
Test scenarios (1)
TC-131Tested (manual)
Steps: Add a completed-work referral for a contractor in one neighborhood, then in a second neighborhood
Expected: Each neighborhood keeps its own record for that business; neither overwrites the other
P5DoneTested (manual)UC-132 Standing is calculated per neighborhood, from that neighborhood's activity only
local calculation replaces the single global sum
Test scenarios (1)
TC-132Tested (manual)
Steps: Leave a five-star job review in one neighborhood only
Expected: Standing rises in that neighborhood; the other neighborhood's figure is unchanged
P5DoneTested (manual)UC-133 The overall figure rolls the local ones together, weighted by history, so fifty thin records don't beat three deep ones
volume-weighted roll-up onto the business record
Test scenarios (1)
TC-133Tested (manual)
Steps: Compare a contractor with deep history in one neighborhood to one with a single record in many
Expected: The overall figure favours the deeper history
P5DoneTested (manual)UC-134 The directory leads with your neighborhood's standing and place, with the overall figure beside it
Contractors cards show "#n here · points in this neighborhood · points everywhere"
Test scenarios (1)
TC-134Tested (manual)
Steps: Open Contractors while a member of a neighborhood
Expected: Each card shows the place and points in that neighborhood, and the overall points beside them
P5DoneTested (manual)UC-135 A contractor sees their standing broken out neighborhood by neighborhood on their own page
"Your standing neighborhood by neighborhood" list on the business page
Test scenarios (1)
TC-135Tested (manual)
Steps: Sign in as a contractor and open your business page
Expected: A list shows each neighborhood you work in with your place, points, rating, reviews, finished jobs and verified referrals there
P5DoneTested (manual)
Group 22 · Contractor Neighborhood Deals (UC-136 – UC-143) — built
8 of 8 completeUC-136 A contractor creates a neighborhood deal: what's covered, the discount (percent or fixed), the normal price it discounts from, terms, how many jobs it covers, and an expiry date
contractor business page: Create a deal (name, coverage, percent/fixed discount, normal price, terms, jobs covered, expiry)
Test scenarios (1)
TC-136Tested (manual)
Steps: As a contractor, create a deal: what's covered, discount, normal price, terms, number of jobs, expiry
Expected: The deal saves and shows those exact details
P5bDoneTested (manual)UC-137 The contractor chooses which of their neighborhoods the deal appears in; residents elsewhere never see it
deal publishes only to the neighborhoods the contractor picks from the ones they serve
Test scenarios (1)
TC-137Tested (manual)
Steps: Create a deal aimed at one neighborhood while the business works in several
Expected: Only residents of the chosen neighborhood can see it
P5bDoneTested (manual)UC-138 Residents see their neighborhood's active deals — on the neighborhood page and on the contractor's card — with the discount and terms in plain words
Neighborhood deals card on the neighborhood page shows discount, price, spots left, expiry and terms
Test scenarios (1)
TC-138Tested (manual)
Steps: Sign in as a resident and open your neighborhood page and the contractor's card
Expected: The deal appears in both places with the discount and terms in plain words
P5bDoneTested (manual)UC-139 A resident claims a deal, which opens a job request pre-linked to that contractor and deal, with the discount carried into the agreed price
Claim opens a job request linked to the deal and contractor, invitation sent, discounted price carried into the budget
Test scenarios (1)
TC-139Tested (manual)
Steps: Claim the deal as a resident
Expected: A job request opens, already linked to that contractor, with the discount carried into the price
P5bDoneTested (manual)UC-140 Deal limits are enforced: the claim count can't exceed the jobs covered, expired deals can't be claimed, one claim per household per deal
server refuses claims past the job limit, after expiry, when paused/withdrawn, or a second time by the same resident
Test scenarios (1)
TC-140Tested (manual)
Steps: Try to claim a deal past its job limit, after expiry, or twice from one household
Expected: Each attempt is refused with a plain-words reason
P5bDoneTested (manual)UC-141 The contractor can pause or withdraw a deal; jobs already claimed from it continue unaffected
Pause / Resume / Withdraw on the business page; claimed jobs are untouched
Test scenarios (1)
TC-141Tested (manual)
Steps: As the contractor, pause and then withdraw a deal that has claimed jobs
Expected: The deal stops accepting claims; the jobs already claimed continue normally
P5bDoneTested (manual)UC-142 A claimed deal runs the standard loop — both sides confirm the discounted price, work is marked complete, review is mandatory — so deal jobs report like any other job
a claimed deal is an ordinary job: agreement, completion, mandatory review, same reporting
Test scenarios (1)
TC-142Tested (manual)
Steps: Run a claimed deal to completion
Expected: Price confirmation, completion and the mandatory review all happen; the job reports like any other
P5bDoneTested (manual)UC-143 Completed deal work earns standing exactly like any other completed job; the deal itself adds no points
deals write no ranking points; standing still comes from completed reviewed work only
Test scenarios (1)
TC-143Tested (manual)
Steps: Compare the contractor's standing before and after a completed, reviewed deal job — and before and after merely publishing a deal
Expected: Standing moves only on the completed, reviewed work; publishing adds nothing
P5bDoneTested (manual)
Group 23 · PLEYDESK switchboard bulletin board (UC-144 – UC-155) — in-app channel built
11 of 12 completeUC-144 Each community has its own switchboard board, created automatically and reachable from the community page
`pleydesk_boards`, board resolved per community, "Open switchboard" link on the neighborhood page
Test scenarios (1)
TC-144Tested (manual)
Steps: Open a community page as an approved member and click Open switchboard
Expected: The community's switchboard opens with its own name and greeting
P7DoneTested (manual)UC-145 A resident asks the switchboard a question in the app and gets an answer drawn only from that community's documents
retrieval over `pleydesk_chunks` with a grounded-only answer
Test scenarios (1)
TC-145Tested (manual)
Steps: Ask a question answered by an uploaded community document
Expected: The answer matches the document and appears in the conversation
P7DoneTested (manual)UC-146 When nothing in the documents covers the question, the switchboard says so instead of guessing
ungrounded answers say so and cite nothing
Test scenarios (1)
TC-146Tested (manual)
Steps: Ask something no document covers
Expected: The switchboard says it isn't covered instead of guessing
P7DoneTested (manual)UC-147 Every grounded answer names the document it came from
sources shown under each answer
Test scenarios (1)
TC-147Tested (manual)
Steps: Ask a covered question and read the note under the answer
Expected: The document the answer came from is named
P7DoneTested (manual)UC-148 The language is detected from the message itself and the answer comes back in that language, including mid-conversation switches
language detected per message, stored on the conversation
Test scenarios (1)
TC-148Tested (manual)
Steps: Ask one question in English, the next in Spanish, in the same conversation
Expected: Each answer comes back in the language of the question
P7DoneTested (manual)UC-149 A maintenance question is routed into a job request, with the question carried across
maintenance intent offers "Start a job request" with the title pre-filled
Test scenarios (1)
TC-149Tested (manual)
Steps: Ask about a broken tap or a leak
Expected: The switchboard offers to start a job request with the problem already in the title
P7DoneTested (manual)UC-150 An admin adds a community document the switchboard can answer from
paste title and text on the switchboard page; text is split and indexed
Test scenarios (1)
TC-150Tested (manual)
Steps: As a community admin, paste a document title and text and add it
Expected: The document is listed with its section count and answers start using it
P7DoneTested (manual)UC-151 An admin retires or restores a document; retiring never deletes it
Retire / Restore; the text stays on record and stops being used
Test scenarios (1)
TC-151Tested (manual)
Steps: Retire that document, ask a question it covered, then restore it
Expected: Retired: the answer is no longer drawn from it and it is still listed. Restored: answers use it again
P7DoneTested (manual)UC-152 The switchboard answers from the documents already shared with the community, with no second upload
retrieval spans both the community's shared documents and any switchboard-only text
Test scenarios (1)
TC-152Tested (manual)
Steps: Ask the switchboard about something covered by a document already shared with the community
Expected: The answer comes from that document without it being uploaded again
P7DoneTested (manual)UC-153 A resident reports an answer that looked wrong, and an admin reviews it
Report this answer; admins mark handled or dismiss
Test scenarios (1)
TC-153Tested (manual)
Steps: Report an answer as a resident, then open the switchboard as an admin
Expected: The report is listed with the question and answer, and can be marked handled or dismissed
P7DoneTested (manual)UC-154 A resident registers the mobile number the switchboard will answer on, with consent recorded
number saved as pending with consent; can be turned off without losing the record
Test scenarios (1)
TC-154Tested (manual)
Steps: Save a mobile number on your profile, then turn it off
Expected: The number is saved as waiting to be confirmed, then shown as off — and still on record
P7DoneTested (manual)UC-155 The switchboard answers by text message and WhatsApp over the same engine
Test scenarios (1)
TC-155Test written
Steps: Text a question to the community number
Expected: Not yet available — the messaging channel is planned
P7PlannedTest written
Rules checked in every phase
- •Neighborhood answers come only from that neighborhood's documents.
- •Three job states, each with its own audience: pre-execution the bidder pool the owner picks, in-execution owner and assigned contractor(s) only, post-execution the owner's sharing choice (UC-112–118).
- •Three active bids minimum before selection. No bypass.
- •Every completed job needs a review.
- •Nothing kept after a call — no audio, transcript or translation.
- •Ranking formula fixed.
- •Purchases stay in the PLEYCUP store.