Guardians need to submit decklists for linked children

Featurebase source: https://cardeio.featurebase.app/p/child-decklist-submission Post ID: 6a3d214b61026ed6aaa43452 Author: Nathan M (nathansmonk@gmail.com) Date: 2026-06-25T12:38:35Z Upvotes: 1

User quote: "I would like to be able to submit my childs decklist (they dont have a phone)"

Product skepticism pass

1. Actual problem: guardian/child event workflows assume the child can complete player-side tasks on their own device. For decklist events, a child without a phone may be unable to submit the required decklist without parent or staff intervention.
2. Who has this problem: one Featurebase parent signal today; it aligns with the adjacent parent-child pairing/result-reporting workflow in HYD2-4633.
3. Current workaround: parent helps out-of-band, child uses another device, or staff/TO handles paper/admin decklist collection. That creates event-day friction and can break online decklist completeness.
4. Evidence: clear Featurebase request, but no event/game/decklist-deadline example yet.
5. 90/10 scope to validate: if a guardian has a linked child registered in an event with decklists enabled, the parent should have a clearly labeled way to submit or replace the child's decklist from the parent account, with audit/permission boundaries preserved.
6. Done should mean: parent can select a linked, registered child in the decklist submission flow; the resulting decklist is attached to the child player/registration, not the guardian; organizer/admin views and exports show the child as submitted; permission checks prevent managing unrelated players.

Duplicate / adjacent review

• HYD2-4633 covers guardian/child pairings and result reporting; linked the sibling Featurebase pairings post there.
• SENG-104 covers child-only event enrollment registering the parent by mistake.
• Canceled HYD2-1447 was an old, thin "Easy to submit DeckList (parent)" placeholder and should not be reused as source of truth.
• No active exact owner found for guardian-on-behalf-of-child decklist submission.

Needed scoping questions

• Is this intended for all player networks, or only networks where child/guardian accounts are supported?
• Should parent-submitted child decklists be allowed only for already-linked and already-registered children?
• What audit trail should distinguish a child-submitted decklist from a guardian-submitted decklist?