Payment-led progression
Registration creates a payment reference; verified payment becomes part of the participant record before private applicant access and review progression.
Case study
MTPN Naija Iconmtpn-naijaicon.com ↗
One contestant record across registration, judging, voting and progression.
A competition operating system connecting eligibility, payment, applicant review, judge scoring, auditions, contestant publication, public voting and programme progression.
15application lifecycle states
3default voting rounds
3staff role types
2candidate pipelines
The operating problem
Talent decisions stayed human. Programme administration did not need to stay manual.
The challenge
A competition has different control points: eligibility, payment, review, judging, audition logistics, public participation and stage progression. The platform had to keep those actions aligned while preventing a payment, vote or status change from becoming an informal side process.
The design question
How do you keep one accountable participant lifecycle while preserving staff and judge authority over the actual talent decisions?
The connected operating journey
Eligibility, payment, judging and voting stay on one participant lifecycle.
01RegisterApplicant profile and evidence
→02PayVerified entry payment
→03ReviewAdmin and judge decisions
→04AuditionSchedule and qualification
→05VoteControlled public participation
→06ProgressCamp, final and winner stages
What the system connects
Automate eligibility and status changes without automating talent decisions.
Review, judging and auditions
Admins manage application state and auditions while judges record score, note and qualification outcomes that feed the participant lifecycle.
Voting with abuse controls
Open-round state, contestant eligibility, identity format, signed challenge, rate limits and duplicate rules are checked before a vote is accepted.
Participant portal
Applicants can follow their private status and timeline across payment, review, audition and later programme stages.
Academy application queue
A separate student and instructor intake supports a second talent pipeline with its own review statuses and private résumé handling.
Programme visibility
Applications, payments, judge scores, audition details, contestant publication, vote audit and stage status are available to operations teams from connected records.
What changed
Less spreadsheet coordination. A controlled participant lifecycle.
A competition has different control points: eligibility, payment, review, judging, audition logistics, public participation and stage progression. The platform had to keep those actions aligned while preventing a payment, vote or status change from becoming an informal side process.
Registration, payment confirmation, judging, auditions, voting and finalist progression now operate from one participant lifecycle with explicit stage rules.
The platform automates programme administration without pretending it can automate talent judgement.
Programme operations review
If programme operations are being held together in spreadsheets and chat, show us the participant lifecycle.
We will separate programme rules from human decisions and map how participant status, payment and progression should stay connected.