5 to 8 minute read
Playbooks by Industry
Part 1: Corporations
01
How Corporate Programs Are Structured
The many names these programs go by, and the single shape they almost all share.
5–8 min read
In plain terms: Corporate programs are usually internal (employee recognition) or external (industry or customer-facing awards), and the two have very different stakes, audiences, and visibility, which means they need different levels of rigor rather than one standard approach applied to both.
- Internal programs prioritize participation and morale over strict competitive rigor. An employee-of-the-month program or an internal innovation award is trying to make people feel seen and to reinforce specific behaviors the organization values, not to produce a defensible, audit-proof ranking. Over-engineering an internal program with heavy judging infrastructure can actually work against its real goal, it starts to feel like a performance review rather than genuine recognition, and participation drops.
- External, industry-facing programs prioritize credibility and judge expertise, since the brand’s reputation is on the line publicly. When a company runs an award that industry peers, customers, or media will see, the judging process itself becomes part of what’s being evaluated by outside observers, alongside the winners themselves. A program that looks like it wasn’t judged rigorously undermines the credibility benefit the company was trying to build by running it in the first place.
- Decide early which one you’re actually running, since the two pull in different directions on almost every design decision. How public is the process? How many judges, and how expert do they need to be? How formal does the criteria need to look? A program that tries to be both internal-casual and externally-credible at once usually ends up satisfying neither goal well.
Recap
- Internal programs favor participation and morale over strict competitive rigor.
- External, industry-facing programs favor credibility and judge expertise, since the process itself is publicly visible.
- Decide early which one you’re running, the two pull in different directions on nearly every design decision.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. Internal and external corporate programs should generally use the same level of judging rigor.
2. What do external, industry-facing corporate programs prioritize most?
3. What can happen if an internal program is over-engineered with heavy judging infrastructure?
02
Working With HR on Internal Programs
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: Internal recognition programs touch the same territory as HR policy and existing people processes, so early coordination avoids friction, duplicated effort, and mixed messages to employees later.
- Internal programs benefit from involving HR early in the design, particularly around how nominations and recognition are handled. HR often already runs adjacent processes, performance reviews, existing recognition platforms, culture initiatives, and a new award program designed in isolation can end up contradicting or competing with something HR already has in place. A short design conversation early on tends to save a much more awkward conversation later, after the program has already launched.
- Think through how recognition data might intersect with other employee-facing processes. If winning an internal award is ever referenced in a performance review, a promotion conversation, or public internal communications, that’s worth surfacing with HR upfront, not discovering after the fact that the program has become entangled with processes it was never designed to touch
- External programs should be clear with customers or industry participants about what data is collected and how it’s used. Even a straightforward “submit your success story” award collects entrant information, company names, project details, sometimes financial or performance figures. Being upfront about what’s collected and how it will be used (in judging, in promotional materials, in case studies) is a matter of basic transparency that also happens to build trust with participants.
Recap
- Internal programs benefit from early HR involvement, especially around nominations and how recognition is handled.
- Surface with HR whether program outcomes might intersect with performance reviews or other people processes.
- External programs should be clear and upfront about what participant data is collected and how it will be used.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. What should internal corporate recognition programs do early in design?
2. External programs have no need to explain data use to participants
3. Why surface with HR whether recognition might touch performance reviews?
03
Common Questions
The eight core jobs every platform in this category is built around.
5–8 min read
- Can managers nominate their own direct reports? Usually yes, this is a common and expected pattern in corporate recognition. Some programs require a second nominator (a peer, a cross-functional colleague) alongside the manager, specifically to avoid a program that quietly becomes just a channel for managers to recognize whoever’s most visible to them, and to surface people whose contributions might not be obvious to their direct manager alone.
- Should winners be announced publicly within the company, or handled more privately? Depends on your program’s actual goal. A visibility-focused program wants public announcement, company newsletters, all-hands mentions, since part of the point is celebrating the behavior publicly to encourage more of it. A more sensitive recognition (for example, tied to a difficult period or a smaller team) might call for something quieter. Decide this deliberately rather than defaulting to whatever your last program did.
- What if the same person or team wins repeatedly? Similar to external awards programs, decide whether this is fine (if it reflects genuinely repeated excellent work) or whether you want a rule limiting consecutive wins to spread recognition more broadly across the organization. Both are legitimate choices depending on what the program is actually trying to achieve.
Recap
- Single-nominator rules are a common, avoidable source of perceived favoritism, a second nominator helps.
- Decide deliberately whether winner announcements should be public or more private, based on the program’s actual goal.
- Repeat winners are a legitimate design question, not an integrity problem either way.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. What can help avoid single-point favoritism in manager nominations?
2. Manager nominations of direct reports are always disallowed
3. What should determine whether winners are announced publicly or privately?
Part 2: Education
01
How Education Programs Are Structured
The many names these programs go by, and the single shape they almost all share.
5–8 min read
In plain terms: Education programs (student competitions, faculty awards, institutional recognition) often run on academic calendars and may involve minors, which shapes both timing and the level of care needed around communication and visibility.
- Align deadlines with semester or academic-year boundaries, not a generic calendar year. A program that opens in September and closes in June maps naturally onto a school year. A program that ignores the academic calendar entirely, opening mid-semester with a deadline during exam period, will consistently see lower-quality submissions and lower participation, not because the program is unappealing but because it’s fighting against students’ and educators’ actual schedules.
- Recognize that your entrants may include both individual students and institutions submitting on students’ behalf. A science fair collects individual student work directly. An institutional excellence award might have a school submit on behalf of a program or department. These require different consent, communication, and eligibility structures, decide early which model your program uses, or whether it needs to support both.
- Where minors are involved, build in extra care around communication and public visibility of entrants. This applies to something as simple as how names are displayed on a public leaderboard or gallery, not just formal data handling. Consider whether first-name-only or initials might be more appropriate than full names in public-facing materials, and whether photos or videos of student work should include the students themselves or focus on the work alone.
Recap
- Education programs run on academic calendars, align deadlines to semester or school-year boundaries.
- Decide early whether your program collects from individual students, institutions on students’ behalf, or both.
- Minor participation calls for extra care around public visibility, not just formal consent, down to details like name display.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. Education program timelines should follow a generic calendar year regardless of the academic schedule.
2. What should programs involving minors build in extra care around?
3. What is a practical example of extra care around minors visibility?
02
Working With Minors and Guardians
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
- Hold for Legal: this section describes process around consent and safeguarding for minors. Language has been written to avoid asserting what law requires, but this specific section should get legal sign-off before publishing, not just an editorial pass.
In plain terms: Programs involving minors touch consent and safeguarding, areas that vary by organization, program, and location, so this needs the right expertise at your organization, not a general assumption carried over from a different kind of program.
- Programs involving minors should loop in whoever handles safeguarding or consent at your organization before launch This might be a school’s administration, a legal team, a designated child-safety officer, or a parent organization’s compliance function, depending on your setup. The point of this section is to prompt that conversation early, not to tell you what the answer will be, because what’s required genuinely differs by program, age group, and location.
- Requirements are not one-size-fits-all, confirm rather than assume. A program open to 16-and-17-year-olds may have different needs than one open to elementary-age children. A program collecting only written work may have different considerations than one collecting video or photos. Treat each new education program as its own question, even if a previous program at your organization already worked through similar issues.
Recap
- Minor participation needs input from whoever handles safeguarding or consent at your organization, confirmed before launch.
- Requirements vary by program, age group, and location, this is a per-program question, not a one-time policy to reuse blindly.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. Who should be looped in before launching a program involving minors?
2. Consent requirements for minors are the same for every program and location.
3. Why surface with HR whether recognition might touch performance reviews?
03
Common Questions
The eight core jobs every platform in this category is built around.
5–8 min read
- Can a teacher judge their own student’s entry? Generally avoided, treated the same as any other conflict of interest, a teacher’s existing relationship with a student, positive or otherwise, makes truly impartial evaluation difficult regardless of good intentions. Where a small pool of qualified judges makes this hard to avoid entirely, disclosure and, ideally, a second judge reviewing the same entry independently helps.
- Can institutions submit on behalf of a group of students, rather than students submitting individually? Depends on the program design, and it changes what consent and communication look like considerably. Group or institutional submissions usually route consent and communication through the institution rather than individual families, which can simplify logistics but shifts responsibility onto the institution to have its own appropriate processes in place. Be clear about which model your program uses.
- What if a winning entry was primarily the work of an educator or parent, not the student? This is a common concern in youth-focused programs. Consider requiring a statement of originality or a description of the student’s specific role in the work as part of the submission, giving judges a way to weigh authenticity as part of evaluation without needing to investigate every entry individually.
Recap
- Teacher-student judging is a standard conflict-of-interest case, disclosure and a second reviewer help where unavoidable.
- Institutional submissions route consent differently than individual student submissions, be clear which model applies.
- A statement of the student’s specific role in the work helps judges weigh authenticity in youth-focused programs.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. How should a teacher judging their own student generally be treated?
2. Conflict-of-interest rules from other program types do not apply in education programs
3. What can help judges weigh authenticity of student work?
Part 3: Associations
01
How Association Programs Are Structured
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: Associations often run several programs at once, awards, scholarships, abstracts, under one member organization, so shared infrastructure and coordination across programs matters more here than for a single standalone program run by a company or non-profit.
- Coordinate timing across multiple concurrent programs so they don’t compete for the same members’ attention or the same small volunteer judging pool. Associations frequently rely on the same relatively small group of engaged, expert members to judge multiple programs throughout the year. Launching an awards program, a scholarship cycle, and a call for conference abstracts all in the same quarter can burn out your most valuable volunteers and dilute member attention across too many asks at once.
- Recognize that association programs often serve a dual purpose: recognizing excellence and driving membership engagement or renewal. This isn’t a bad thing, but it’s worth being explicit about internally, since it can shape decisions like whether non-members can participate, whether winning requires active membership, and how heavily the program gets promoted as a membership benefit versus an open industry recognition.
- Build relationships with a rotating bench of volunteer judges, not just your usual small circle. Associations that rely on the same five people to judge everything year after year face both a burnout risk and a credibility risk, industry observers may start to notice a pattern in who’s judging and, by extension, who tends to win. Actively rotating and expanding your judge pool protects both the volunteers and the program’s credibility.
Recap
- Associations often run multiple concurrent programs sharing the same member and volunteer base, coordinate timing to avoid burnout.
- Association programs often serve both recognition and membership-engagement goals, be explicit about that internally.
- Rotate and expand your volunteer judge pool rather than relying on the same small circle repeatedly.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. Associations typically run just one type of program at a time.
2. What should be coordinated across an associations concurrent programs?
3. Why rotate the volunteer judge pool rather than relying on the same small group?
02
Keeping Member Data Handling Consistent
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: Members often participate in more than one association program over the course of a year, so how their data is handled should feel consistent from one program to the next, rather than surprising them with different rules each time.
- Keep data handling consistent across your programs so members aren’t confused by different rules from one to the next If your awards program shares entrant names publicly but your scholarship program keeps applicants confidential, that’s a reasonable difference, but members should be able to easily understand why, not experience it as an inconsistency in how the association treats their information generally.
- This is as much a communication design question as a technical one. A short, consistent statement on every program page about what information is collected and how it’s used, tailored to that specific program but following a recognizable format, helps members build trust in the association’s overall practices rather than having to evaluate each program’s data handling from scratch.
Recap
- Consistent member data handling matters across an association’s multiple concurrent programs.
- Where practices differ between programs, make the reason clear rather than leaving it to feel arbitrary.
- A consistent, recognizable format for explaining data use across program pages builds broader member trust.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. Why does data handling consistency matter especially for associations?
2. It is fine for each association program to handle member data completely differently with no explanation.
03
Common Questions
The eight core jobs every platform in this category is built around.
5–8 min read
- Can volunteer judges also be members competing in other association programs? Common and usually fine, provided they’re excluded from judging in the specific program they’re personally entered in. A judge for the annual awards program who’s also applying for a scholarship through a separate program isn’t automatically a conflict, as long as recusal happens in the program where they’re actually a participant.
- Should non-members be allowed to participate in association programs?. Depends on your program’s goals, discussed in Section 1. If the program is meant to drive membership, restricting participation to members (or offering non-members a path to join as part of entering) reinforces that goal. If the program is meant to be a broad industry recognition regardless of membership status, opening it to non-members serves that goal better. There’s no universally right answer, only a choice that should match your actual objective.
- What if a volunteer judge is also on the association’s board or staff? Treat this with the same disclosure standard as any other potential conflict, board or staff involvement doesn’t automatically disqualify someone from judging, but their role and any relevant relationships to participants should be transparent, and recusal should apply the same way it would for any other judge with a personal connection to an entrant.
Recap
- Volunteer judges can participate elsewhere in the association, with standard recusal from their own entries.
- Whether to open programs to non-members should match the program’s actual goal, membership growth versus broad recognition.
- Board or staff members judging need the same disclosure and recusal standard as any other judge.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. What is required if a volunteer judge is also entered in a program?
2. Volunteer judges can never also be association members
3. What should determine whether non-members can participate?
Part 4: Incubators
01
How Incubator Programs Are Structured
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: Incubator programs evaluate early-stage ventures, so criteria weigh potential and team as much as current traction, since most applicants won't have much traction yet, and evaluating them as though they should is a common design mistake.
- Structure review to account for very early-stage submissions A strong team and a sharp idea can matter more than current revenue or user numbers, because at this stage, those numbers often don’t exist yet or aren’t meaningful predictors of anything. If your rubric implicitly rewards traction metrics, you’ll systematically favor later-stage applicants over the earliest-stage ones your incubator may actually be designed to support.
- Decide what stage of venture your program is actually looking for, and make sure your criteria reflect that specifically. “Early-stage” covers a wide range, from a idea on paper to a team with a working prototype and first customers. Being vague about this produces a mismatched applicant pool and a rubric that doesn’t quite fit anyone well. Get specific about the stage, and adjust criteria weighting accordingly.
Recap
- Incubator judging weighs potential and team strength, not just current traction, since most applicants are pre-traction.
- A rubric that implicitly rewards traction metrics disadvantages the earliest-stage applicants an incubator may be designed to support.
- Get specific about what stage of venture you’re looking for, and calibrate criteria weighting to that stage.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. What matters more in incubator judging than in most other program types?
2. Incubator applicants are expected to already have significant traction.
3. Why get specific about the target venture stage?
02
Confidentiality for Early-Stage Applicants
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: Applicants to incubator programs often share sensitive business plans or early ideas as part of their submission, so confidentiality matters more here than in most other program types in this book.
- Have a clear, stated confidentiality policy before applications open, and make sure reviewers understand what it actually covers A generic “we take confidentiality seriously” statement isn’t the same as reviewers actually understanding they can’t discuss a specific applicant’s business model with a colleague at a networking event, even informally. Make the policy specific and make sure it’s part of reviewer onboarding, not just a line in the application form’s fine print.
- Think through what happens to submitted materials for applicants who aren’t selected. Do unsuccessful applicants’ materials get deleted after a certain period? Retained for a future cycle? Applicants sharing early, sensitive ideas reasonably want to know the answer to this, and having a clear, stated practice, whatever it is, is better than leaving it unaddressed.
Recap
- Confidentiality is especially important given the sensitive business information in incubator applications.
- Make the confidentiality policy specific and part of reviewer onboarding, not just fine print applicants may not read.
- Have a clear, stated practice for what happens to unsuccessful applicants’ materials after the program.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. Confidentiality is less important for incubator applications than other program types.
2. What should be in place before incubator applications open?
3. What is worth addressing for unsuccessful applicants materials?
03
Common Questions
The eight core jobs every platform in this category is built around.
5–8 min read
In plain terms: Applicants to incubator programs often share sensitive business plans or early ideas as part of their submission, so confidentiality matters more here than in most other program types in this book.
- Can reviewers invest in or advise applicants they’ve judged? This needs a clear, explicit policy in advance, it’s a common real-world situation in this space specifically, since incubator reviewers are often investors, advisors, or industry experts who are professionally active in the same space as applicants. A blanket ban may not be realistic, but a required disclosure and a cooling-off period before any investment or advisory relationship begins are common, reasonable safeguards.
- What if an applicant’s idea closely resembles one already being incubated or supported by the organization? Decide in advance how you’ll handle this, some programs disclose existing portfolio overlap to the applicant and let them decide whether to proceed, others build in a specific screening step for this. Either way, having a plan avoids an awkward, ad hoc conversation after an applicant has already invested time in their submission.
- Can an applicant reapply after being rejected? Usually yes. Early-stage ventures evolve quickly, an idea that wasn’t ready in one cycle may be substantially stronger, with real traction or a refined team, by the next one. Encourage this rather than treating rejection as a final verdict.
Recap
- A clear, explicit policy on reviewer investment or advising helps manage this common, real-world situation.
- Decide in advance how to handle applicant overlap with existing portfolio companies or supported ventures.
- Reapplication is usually encouraged, early-stage ventures evolve quickly between cycles.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. What helps manage reviewers who may later invest in or advise applicants?
2. This situation is rare enough to not need a stated policy
3. How should reapplication after rejection generally be treated?
Part 5: Non-Profits
01
How Non-Profit Programs Are Structured
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: Non-profits often run recognition or grant programs with limited staff capacity, so efficient, right-sized process design matters more here than in better-resourced organizations, where an ambitious process might simply be inconvenient rather than actually unworkable.
- Keep the process proportionate to your team’s actual capacity An ambitious multi-round process with extensive documentation requirements, designed by someone imagining an ideal version of the program, tends to break down under its own weight when it’s actually run by a two- or three-person team also handling their regular day-to-day responsibilities. Design for the team you actually have, not the team a larger organization might have.
- Consider what parts of the process can be simplified or automated without losing what actually matters. Not every step needs the same level of rigor. A lightweight initial eligibility check might not need staff review at all, while the core evaluation genuinely benefits from human judgment. Identify where your limited capacity needs to go and simplify aggressively everywhere else.
Recap
- Non-profit programs should match process complexity to actual staff capacity, not an idealized version of the program.
- An ambitious multi-round process can break down under its own weight when run by a small team alongside other responsibilities.
- Simplify or automate steps that don’t need human judgment, and reserve capacity for the parts that genuinely do.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. What should non-profit program design account for specifically?
2. An ambitious multi-round process always works regardless of team size.
3. What helps a small team run a program sustainably?
02
Transparency for Funding-Related Programs
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: Where a program involves a funding decision, being clear about criteria and process builds trust with applicants and confidence with the board or donors overseeing the program, two different audiences that both benefit from the same transparency.
- Transparency about criteria and process matters both for applicant trust and for donor or board confidence in how the program is run. Applicants who understand what they’re being evaluated on, even if they don’t receive funding, tend to view the process as fairer than applicants left guessing. Separately, a board or donor group overseeing a grant program wants confidence that funds are being distributed through a defensible, consistent process, not an ad hoc one.
- The same documentation often serves both audiences, so it’s worth building once and reusing. A clear rubric, a documented review process, and a summary of how decisions were reached can be shared, in appropriate detail, with both applicants (as part of program transparency) and board or donors (as part of governance and accountability), rather than maintaining two separate explanations of the same process.
Recap
- Process transparency matters for both applicant trust and donor/board confidence, not just one or the other.
- The same documentation (rubric, process summary) can often serve both audiences rather than needing separate versions.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. Process transparency mainly matters for applicant trust, not for donors or board oversight.
2. What does clear criteria and process support, according to this section?
03
Common Questions
The eight core jobs every platform in this category is built around.
5–8 min read
- Can a board member judge a program tied to the organization? Needs the same disclosure and likely recusal as any other judge with a personal connection to applicants. Board members often have deep knowledge of the organization’s mission, which can make them valuable reviewers, but that same closeness can create real or perceived conflicts if they have relationships with specific applicants, treat this exactly as you would any other judge’s conflict of interest.
- What if the non-profit itself wants to nominate a project or partner organization it already works closely with? This deserves the same scrutiny as any other conflict of interest, close existing relationships between the non-profit and a potential nominee can create, or appear to create, an uneven playing field for other applicants. Disclosure and, where possible, recusal of anyone with a direct relationship to that nominee from the evaluation process are reasonable safeguards.
- How should a non-profit handle an applicant who is also a donor? Decide in advance whether and how this affects eligibility or evaluation, most well-run programs evaluate the application entirely on its merits, separate from any donor relationship, and communicate that clearly rather than leaving it as an unstated assumption.
Recap
- Board member involvement in judging needs the same conflict-of-interest handling as any other judge.
- Existing organizational relationships with a potential nominee deserve the same conflict scrutiny as any other relationship.
- Decide and clearly communicate that donor status doesn’t affect evaluation, rather than leaving it unaddressed.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. What does a board member judging need, if they have a personal connection to applicants?
2. Board members are automatically exempt from conflict-of-interest rules.
3. How should applicant-donor status generally be handled?
Part 6: Event Planners
01
How Event Planner Programs Are Structured
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: Event planners often run programs, like awards, on behalf of a client organization, so the process needs to work for both the planner running the day-to-day operation and the client whose brand and reputation it represents.
- Clarify upfront who owns final decisions, the planner or the client Ambiguity here causes friction right when a program is at its most visible, typically right before or during a public announcement, exactly when it’s hardest to resolve a disagreement quickly and quietly. Get explicit agreement in the planning phase: does the planner run judging independently and present results, or does the client retain final approval over winners?
- Decide how much the client wants visibility into the process versus a finished result. Some clients want to be closely involved in category design, judge selection, and even scoring review. Others want to hand off the entire operational process and simply receive a polished result to announce. Neither is wrong, but assuming one when the client expects the other is a common source of a strained planner-client relationship.
Recap
- Decision ownership between planner and client should be explicit from the start, before the program’s most visible moments.
- Decide upfront how much process visibility versus finished-result delivery the client actually wants.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. What commonly causes friction in client-run programs?
2. What helps avoid a harder conversation later about entrant data
02
Agreeing on Data Use With Clients
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: When a planner collects entrant or attendee information on behalf of a client, both sides benefit from agreeing upfront on how that information can be used afterward, rather than assuming they're aligned.
- Agree in writing who can use entrant or attendee information after the program ends. Can the client add entrants to a marketing list? Can the planner reuse entrant information for a similar program with a different client? These are reasonable questions with different answers depending on the relationship, and agreeing on them in writing before data starts flowing avoids a much harder conversation after the program has already collected it.
- This is a simple step that avoids a much harder conversation later. A short data-use clause in the planner-client agreement, even a few sentences, is far easier to negotiate before any data exists than after an entrant complains about an unexpected marketing email, or a client discovers the planner reused their entrant list for another event.
Recap
- Data use terms between planner and client should be agreed in writing, in advance, not assumed.
- A short data-use clause upfront prevents a much harder conversation after data has already been collected and potentially reused.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. Data use terms after a program ends are usually obvious without discussion
2. What helps avoid a harder conversation later about entrant data
03
Common Questions
The eight core jobs every platform in this category is built around.
5–8 min read
- Who handles entrant disputes, the planner or the client? Should be agreed before the program launches, not figured out reactively when a dispute actually happens. A dispute during a live, visible program is stressful enough without also having to figure out, in real time, whose job it is to respond.
- What happens if the planner and client disagree on a judging decision? Tie this back to the decision-ownership question from Section 1. If the client retains final approval, this is expected and the planner’s role is to present a recommendation, not a final decision. If the planner runs judging independently, this scenario shouldn’t come up, and if it does, it may signal the decision-ownership agreement wasn’t as clear as it needed to be.
- Who’s responsible if a sponsor or vendor commitment isn’t fulfilled? Decide this in the planning phase as part of the broader contract, not specific to judging, but relevant to the overall program relationship. Clear responsibility here protects both the planner’s reputation and the client relationship if something goes wrong with a third party.
Recap
- Dispute-handling ownership is best decided before launch, not during a live dispute.
- Disagreement over judging decisions usually signals the decision-ownership agreement from Section 1 wasn’t clear enough.
- Sponsor and vendor responsibility should be addressed in the broader planning contract, not left implicit.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. When should dispute-handling ownership be decided?
2. Figuring out dispute handling reactively tends to work out fine.
Part 7: Media and Publishing
01
How Media Programs Are Structured
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: Media and publishing awards often judge published work already in the public domain, so eligibility windows (what counts as "this year's" work) need particularly clear definition, since the work being judged already exists independently of your program.
- Define your eligibility period precisely, by publication date, not submission date. Publishing timelines and submission timelines rarely line up neatly, a piece published in December might be submitted the following March, well after your intuitive sense of “this year.” Be explicit: eligible work is anything published between two specific dates, stated clearly in your call for entries.
- Decide whether you’re judging individual pieces or a body of work A “Best Investigative Story” category judges a single piece. A “Journalist of the Year” category might judge a body of work across the eligibility period. These require different submission formats and different judging approaches, be clear about which one each category actually is.
Recap
- Eligibility periods should be based on publication date, defined precisely, not submission date.
- Decide whether each category judges a single piece or a body of work, and design submission requirements accordingly.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. What should media award eligibility windows be based on?
2. Publication and submission timelines usually line up neatly.
02
Using Published Work in Judging and Promotion
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: Work being publicly published doesn't automatically mean a program can freely display or excerpt it in program materials, that's worth checking rather than assuming, even though the work is already out in the world.
- Check who owns the rights to a published piece before featuring it in program materials, judging packets, or a winners’ announcement. Publication rights and reproduction rights aren’t always the same thing, a piece being publicly readable doesn’t necessarily mean your program has the right to reproduce it in a PDF judging packet or feature an excerpt in a press release. This is worth a quick check rather than an assumption.
- Build this check into your process rather than treating it as an afterthought for winners only. If judging packets involve compiling entries into a shared document for reviewers, that reproduction itself is worth confirming is appropriate, not just the later use of winning entries in promotional materials.
Recap
- Displaying published work for judging or promotion needs a rights check, not an assumption based on public availability.
- Build the rights check into your process for judging packets generally, not just for winners’ promotional use.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. Work being publicly published automatically means a program can display it freely
2. What should happen before featuring a published piece in program materials?
03
Common Questions
The eight core jobs every platform in this category is built around.
5–8 min read
- Can a piece published across two calendar years qualify? Define this explicitly in your rules, publication-date programs run into this constantly near year boundaries, a piece published December 30th versus January 2nd can end up in an awkward gray area if your rules aren’t explicit about which cycle it belongs to.
- Can a piece that’s been updated or revised after initial publication still qualify based on its original publication date? Decide this in advance, minor corrections likely shouldn’t reset eligibility, but a substantially revised or expanded version might reasonably be treated as new. State your standard so entrants and judges both have a consistent reference point.
- What if a piece was published under a pseudonym or without a byline Decide whether and how authorship needs to be verified for eligibility purposes, and build a straightforward, low-friction way for entrants to confirm authorship without requiring them to publicly reveal a pseudonym if that wasn’t their original intent.
Recap
- Cross-year publication dates are a common, foreseeable edge case worth ruling on explicitly in advance.
- Decide whether revised or updated pieces retain their original publication date for eligibility.
- Have a low-friction way to verify authorship for pseudonymous or byline-free work.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. When should cross-year publication eligibility be decided?
2. This situation is rare enough to skip planning for.
Part 8: Art, Design, and Architecture
01
How Creative-Field Programs Are Structured
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: These programs judge physical or highly visual work, so submission format (photos, renderings, physical samples) needs particularly clear specification, since judges are evaluating a representation of the work, not the work itself, in most cases.
- Specify exactly how three-dimensional or physical work should be represented in a digital submission Photo angles, resolution, supporting drawings or plans, scale references, since ambiguity here disadvantages entrants unequally, someone with professional photography access can represent their work far better than an equally talented entrant without it, if your rules don’t level that playing field with clear, achievable requirements.
- Consider whether to allow or require supplementary materials beyond photos, like process documentation or technical drawings. For architecture and design work especially, the finished image alone sometimes doesn’t convey the problem-solving or technical achievement involved. Decide whether your program wants to evaluate the final result alone or the fuller story of how it was achieved, and specify submission requirements accordingly.
Recap
- Physical and visual work needs precise digital-representation requirements to keep judging fair across entrants with different resources.
- Decide whether supplementary process or technical documentation is allowed or required, based on what you actually want judges evaluating.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. What needs particularly clear specification in these programs?
2. Vague submission format rules affect all entrants equally.
02
Using Winning Work in Promotion
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: Featuring a winning design or artwork in promotion or a gallery is common practice, but it's worth checking who owns the rights first rather than assuming, since creative work often has more layered ownership than it initially appears.
- Check who owns the rights to the work before using it in promotion or a winners’ gallery. This is a common oversight in visually driven programs specifically, entrants naturally assume submitting their work means the program can showcase it, but the specifics (how, where, for how long, with what attribution) benefit from being clearly agreed rather than assumed by either side.
- Address this in your entry terms upfront, rather than negotiating it after someone’s already won A clear statement in your call for entries about how winning (and sometimes shortlisted or all) work may be used in promotion, with what attribution, gives entrants informed consent when they submit, rather than a surprise request after the fact.
Recap
- Rights to promotional or gallery use need to be checked and agreed, not assumed based on the entry itself.
- Address usage terms in your entry rules upfront, so entrants have informed consent when they submit, not a surprise later.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. Using a winning entrys image in promotion generally requires no separate check.
2. What is described as a common oversight in visually driven programs?
03
Common Questions
The eight core jobs every platform in this category is built around.
5–8 min read
- Can a collaborative work be entered by just one of its creators? Should require disclosure of all collaborators and, typically, their consent to enter, architecture and design work in particular is frequently collaborative, and a program that only recognizes the person who happened to submit the entry can create real friction among a project team, especially if the work goes on to win.
- How should credit be handled for team-based work if it wins? Decide this in advance and make it clear in your entry rules, some programs recognize the entering individual only, others require and display full team credit. Whichever you choose, make sure it’s stated before entry, not decided reactively after a collaborative piece wins and the team is surprised by how credit gets handled.
- What if an entry appears to be substantially the work of a firm or studio rather than the named individual entrant? Consider whether your program is meant to recognize individuals or organizations, and build eligibility rules that match, some programs are explicitly firm-level awards, others are meant to spotlight individual designers or architects specifically, and unclear rules here create disputes.
Recap
- Collaborative work needs clear rules on disclosure and consent from all contributors before entry.
- Decide and state your credit policy for team-based work in advance, not after a collaborative piece wins.
- Be clear whether your program recognizes individuals or organizations, and build eligibility rules to match
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. What should be required for collaborative work entries?
2. One collaborator can always enter on behalf of the whole team without informing them.
Part 9: Healthcare and Pharma
01
How Healthcare Programs Are Structured
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: Healthcare and pharma programs (research recognition, innovation awards) often involve technical and clinical subject matter, so review needs the right expertise, not just general judging skill, and this shapes both judge recruitment and process design.
- Consider a review step specifically for technical or clinical claims made in submissions, separate from general judging criteria. A general innovation judge might be well-equipped to assess business potential or presentation quality, but not necessarily positioned to evaluate a specific clinical claim’s validity. Separating “is this well presented and compelling” from “is this technical claim sound” as distinct review steps, potentially with different reviewers for each, produces more credible results than asking one generalist panel to do both.
- Recruit judges with genuinely relevant expertise for the specific sub-field being judged, not just a general healthcare background. “Healthcare” spans an enormous range, medical devices, pharmaceuticals, digital health, clinical operations, and expertise in one area doesn’t transfer cleanly to another. Map your expected submission topics against your judge panel’s actual expertise before finalizing your reviewer list.
Recap
- Technical or clinical claims benefit from review by someone with the right expertise, separate from general judging.
- Consider splitting “presentation and business merit” from “technical or clinical soundness” as distinct review steps.
- Recruit judges with expertise matched to the specific healthcare sub-field being judged, not just a general background.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. What benefits from a separate review step in healthcare programs?
2. General judging panels always have the expertise to assess clinical claims
02
Handling Sensitive Information
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
HOLD FOR LEGAL: this section describes process around sensitive information in submissions. Language has been written to avoid asserting what law requires, but this specific section should get legal sign-off before publishing, not just an editorial pass.
In plain terms: Submissions in this space sometimes include sensitive information, so it's worth having someone with the right expertise take a second look before anything gets published or displayed, as a matter of process, not a substitute for your organization's own review.
- This is a general note, not a substitute for your organization’s own review process Submissions in this space sometimes include sensitive information, patient-related details, unpublished clinical data, proprietary technical information, and it’s worth having someone with the right expertise take a second look before anything from a submission gets published, displayed, or shared beyond the immediate judging panel.
- Build this second look into your process at a specific point, rather than hoping someone catches an issue informally. Decide at what stage (before judging packets are compiled, before a winner’s submission is featured in promotional materials) this review happens, and who’s responsible for it, so it’s a defined step rather than something that depends on any one person happening to notice a concern.
Recap
- Sensitive information in submissions warrants a second look from someone with the right expertise before publication.
- This note doesn’t replace your organization’s own review process, it’s a prompt to make sure that process exists and runs at a defined point.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. What is recommended before publishing or displaying sensitive submission content?
2. This note replaces the need for your organizations own review process.
03
Common Questions
The eight core jobs every platform in this category is built around.
5–8 min read
- Can a pharmaceutical company sponsor a program it’s also competing in? Needs clear, disclosed separation between sponsorship and judging to avoid a direct conflict of interest, sponsorship dollars shouldn’t create even the appearance of influence over who wins. If a sponsor’s own product or initiative is eligible to enter, make sure the sponsor has no visibility into or influence over the judging process for that category.
- Should judges be required to disclose financial relationships with any entrant, not just employment? This is worth building into your conflict-of-interest disclosure explicitly, in healthcare and pharma specifically, financial relationships (consulting fees, speaker fees, research funding) are common and don’t always involve formal employment, but can still affect impartiality. A disclosure form that only asks about current employment will miss a lot of relevant relationships.
- What if a submission references ongoing, unpublished research? Confidentiality matters especially here, unpublished research shared as part of a submission could be commercially or academically sensitive in ways that go beyond typical program confidentiality. Treat this as a heightened confidentiality case and make sure judges understand the added sensitivity.
Recap
- Sponsor-entrant overlap requires clear, disclosed separation between sponsorship and judging.
- Judge disclosure forms should ask about financial relationships broadly, not just current employment.
- Submissions referencing unpublished research deserve heightened confidentiality treatment.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. What does sponsor-entrant overlap require?
2. A sponsor competing in its own program is not a conflict of interest
Part 10: Tech, Gaming, and Esports
01
How Tech and Gaming Programs Are Structured
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: Esports programs specifically benefit from clear anti-cheating and fair-play rules, stated upfront, since competitive stakes and community scrutiny here tend to run high, and disputes without clear prior rules are hard to resolve credibly after the fact.
- State anti-cheating and fair-play rules clearly before the competition starts, not after a dispute arises Esports communities are often highly engaged and technically sophisticated, meaning both genuine cheating and false accusations of cheating are realistic scenarios. Clear, published rules about what’s prohibited, and what the investigation and consequence process looks like, protect the integrity of the competition and give you something concrete to point to if a dispute happens.
- Decide your stance on borderline competitive practices before they come up, not case by case Some practices exist in a gray area, aggressive but technically legal strategies, use of certain tools or settings. Publishing your position on common gray-area questions specific to your game or competition format reduces disputes considerably compared to leaving everything to be decided reactively.
Recap
- Esports programs benefit from explicit, upfront anti-cheating and fair-play rules given high competitive stakes.
- Clear published rules give you something concrete to point to if a dispute happens, rather than relitigating it from scratch.
- Decide your stance on known gray-area competitive practices in advance, not case by case
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. Anti-cheating rules matter less in esports than in other competitive program types.
2. When should fair-play rules be stated?
02
Fair Play in Esports
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: These programs move fast and often involve live or streamed components (esports matches, live demos), so technical infrastructure and real-time judging logistics matter more here than in most other verticals in this book.
- Plan for technical failure as a normal possibility, not an edge case Streams drop, demos crash, servers lag at the worst possible moment, and your process needs a default response ready rather than an improvised one, decided under pressure, in front of a live audience. Treat “what happens when something breaks” as a standard planning question, not a rare contingency.
- Invest in a genuine technical rehearsal, not just a rules review, before any live or streamed event. A rehearsal that tests actual technical infrastructure, stream quality, judge scoring tools working under real conditions, backup systems, catches problems a rules discussion alone won’t surface. This matters more here than in almost any other program type, because the technical layer isn’t incidental to the judging, it’s often central to what’s actually being evaluated.
Recap
- Technical failure should be planned for as routine, not exceptional, in this vertical.
- A genuine technical rehearsal, testing real infrastructure, catches problems a rules-only review won’t.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. How should technical failure be treated in planning for tech and gaming programs?
2. Live streams and demos rarely have technical issues.
03
Common Questions
The eight core jobs every platform in this category is built around.
5–8 min read
In plain terms: These programs move fast and often involve live or streamed components (esports matches, live demos), so technical infrastructure and real-time judging logistics matter more here than in most other verticals in this book.
- What happens if a live match or demo is disrupted by a technical issue? Have a clearly stated policy, replay, extension, or judge discretion, decided before it happens. State it in the competition rules so competitors know what to expect, rather than learning the policy for the first time during an actual disruption.
- How should a program handle an accusation of cheating during a live event? Decide your investigation process in advance: who reviews the accusation, what evidence is considered, whether the competitor continues competing while under review or is paused. Having this decided ahead of time means a real-time accusation doesn’t derail the entire event while organizers figure out a process on the spot.
- What if a competitor’s equipment gives them an advantage or disadvantage not accounted for in the rules? This comes up more than organizers expect in tech-heavy competitions, differences in hardware, connection quality, or software versions. Decide in advance whether you standardize equipment, allow personal equipment with disclosed specifications, or handle it another way, and state your approach clearly.
Recap
- Disruption-handling policy should be decided in advance and stated in the rules, not improvised live.
- Decide your cheating-accusation investigation process in advance, including whether competition continues during review.
- Address equipment standardization or disclosure in advance, this comes up more than organizers expect.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. When should a disruption-handling policy be decided?
2. Improvising a response to a live technical failure is the recommended approach.
Part 11: Government and Public Sector
01
How Government Programs Are Structured
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
In plain terms: Government programs (public recognition, procurement-adjacent tenders, and public grants) tend to call for higher formality and more thorough documentation than most other verticals, given the level of public and institutional scrutiny they typically draw.
- Document each stage of the process more thoroughly than you might for a private-sector program Government-adjacent programs tend to draw more scrutiny, from participants, oversight bodies, sometimes the public or press, so good documentation at every stage, not just the final decision, is worth the extra effort. This includes documenting eligibility screening, not just final scoring.
- Build extra time into your process for internal review and approval stages that private-sector programs might not need. Government-adjacent programs often have additional layers of sign-off, a department head, a compliance function, a public communications review before results can be announced. Map these stages into your timeline from the start rather than discovering them as unplanned delays partway through.
Recap
- Government programs benefit from especially thorough documentation given the level of scrutiny they tend to draw.
- Document every stage, including eligibility screening, not just the final decision.
- Build extra time into your timeline for additional internal review and approval stages.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. Why does documentation matter, especially in government programs?
2. Government programs typically need less documentation than private-sector ones
02
Keeping Records and Looping In Your Team
Four recurring motivations — and why the dominant one shapes every decision downstream.
5–8 min read
HOLD FOR LEGAL: this section describes process around public-sector record-keeping and scrutiny. Language has been written to avoid asserting what law requires, but this specific section should get legal sign-off before publishing, not just an editorial pass.
In plain terms: Government-adjacent programs tend to get more scrutiny than private ones, so good record-keeping and early input from the right people at your organization go a long way toward protecting the program's credibility.
- Keep better records than you think you need, and loop in your legal or compliance team early rather than after something’s requested What applies to your specific program and location varies considerably, so this is a prompt to check with the right people at your organization, not a summary of what any particular rule says. Treat this conversation as a standard part of planning a government-adjacent program, not a step you only take if something unusual comes up.
- Build a simple, consistent record-keeping habit rather than scrambling to reconstruct a decision trail after the fact. Something as straightforward as saving dated notes from each review stage in a consistent place makes a significant difference if records are ever needed later and costs very little to maintain if it’s built into the process from the start.
Recap
- Keep thorough records and involve legal or compliance early, not reactively.
- Requirements vary by program and location; confirm with the right people rather than assume.
- A simple, consistent record-keeping habit built in from the start beats reconstructing a decision trail later.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1. When should legal or compliance be looped in for government-adjacent programs?
2. Record-keeping requirements are the same for every government-adjacent program.
03
Common Questions
The eight core jobs every platform in this category is built around.
5–8 min read
- Should program documentation be kept after results are announced? Yes, generally longer than feels necessary. Exactly how long depends on your own organization’s policy, worth confirming rather than assuming a default, but the general instinct in government-adjacent programs should lean toward retaining records longer, not shorter, than a private-sector program might.
- Who should have access to program records after the fact? Decide this as part of your records practice, not reactively. A reasonable default is limiting access to those with a clear operational or compliance need while making sure the right people (compliance, legal, program leadership) can actually get to records when needed, rather than records being scattered across individual staff members’ personal files
- What if a records request comes in for a program that’s already concluded? Having a clear internal process for who handles this, and where records actually live, matters more than any specific answer about what must be shared. This is exactly the kind of situation Section 2 points to legal or compliance for, rather than something to figure out reactively when the request arrives.
Recap
- Keep documentation longer than feels necessary, and confirm your organization’s specific retention policy.
- Limit, but clarify, records access so the right people can find what they need without records being scattered.
- Have a clear internal process for handling records requests, and route them to legal or compliance rather than deciding reactively.
Quick check
Regardless of what a program is called, the design questions behind it are mostly the same:
1.What is the general guidance on keeping documentation after results are announced?
2.Every organization has the same documentation retention policy.





























