A digital Wall of Honor needs more than attractive profiles and award entries. This governance checklist helps HR, People Ops, and operations teams manage consent, visibility, permissions, accessibility, naming, images, removal requests, and stale content after launch.
Overview
A digital Wall of Honor can serve as an employee spotlight platform, online recognition board, service award display, or internal culture page. Its value depends on whether people can trust the information shown there. A profile that uses an outdated title, an image shared without permission, or a recognition entry that should have been removed can quickly create avoidable work for the team responsible for it.
Governance turns a recognition display into a maintained business process. Before launch, decide who may submit, approve, publish, edit, archive, and remove content. Document what employees have agreed to share, where the display is visible, and how requests are handled. Keep the process simple enough to follow during routine updates, employee transfers, policy changes, and leadership transitions.
This guide assumes that your Wall of Honor may be visible to different audiences, such as employees only, logged-in users, or the public. The correct settings depend on your organization, platform, and internal requirements. Treat the checklist as an operating framework rather than a substitute for legal, privacy, accessibility, or information-security advice.
Checklist by scenario
Before publishing a new recognition entry
- Confirm the recipient’s preferred name, job title, team, and location if those fields are displayed.
- Record what the recognition is for using specific, respectful wording. Avoid including confidential project details, customer information, health information, or other sensitive material.
- Confirm the intended audience: internal, selected groups, logged-in users, or public visitors.
- Obtain and record consent for the profile, quotation, award details, and image. Do not assume that consent for one use covers every channel.
- Check whether the employee wants their full name, photo, pronouns, team, or other optional fields displayed.
- Verify that the entry follows your naming conventions, date format, award categories, and recognition certificate wording.
- Assign an owner and review date so the entry does not become unmanaged content.
For wording and approval details, use a consistent employee award certificate template and approval checklist. Consistency makes a company Wall of Honor easier to scan and easier to maintain.
When an employee requests a change
- Provide a clear contact method for correcting names, titles, images, descriptions, or visibility settings.
- Verify the requester’s identity before changing a profile or removing an entry.
- Record the request, decision, person responsible, and completion date in the system or a controlled operations log.
- Apply the change everywhere the same content appears, including embedded pages, QR-linked displays, newsletters, or downloadable certificates.
- Escalate requests involving disputed recognition, sensitive information, or unclear ownership to the designated People Ops or HR reviewer.
A removal request should not be treated as an inconvenience. It is a normal part of maintaining employee recognition content. Your policy should explain whether entries are deleted, archived, anonymized, or hidden from a particular audience, and who makes that decision.
When an employee changes role or leaves
- Review the person’s current title, team, manager, location, and profile visibility.
- Decide whether the recognition should remain visible, move to an alumni or archive section, or be removed.
- Check linked images, quotes, award pages, and internal references for the same outdated information.
- Do not change the historical wording of an award merely to reflect a later role change unless your policy requires it.
- Confirm that access has been removed from former employees or other users who no longer need editing rights.
When the Wall of Honor is connected to other tools
Map how information moves between your HR system, employee recognition software, form tools, identity provider, intranet, email, and display screens. Define which system is authoritative for each field. For example, HR may own employment status while People Ops owns the recognition description and image consent. Review the employee recognition software integration workflow and data checklist before changing a connection or automation.
If a QR code points to a recognition page, test the destination after edits and removals. A QR-linked display should not expose more information than the destination page is intended to share. The QR Code Wall of Honor setup guide can support this review.
Role-and-permission comparison
| Role | Typical access | Controls to apply |
|---|---|---|
| Viewer | Read approved recognition entries | Cannot edit, export, publish, or change visibility |
| Contributor | Submit nominations or draft spotlights | Submissions require review before publication |
| Reviewer | Check wording, consent, audience, and accuracy | Cannot grant themselves broader administrative access |
| Publisher | Approve and publish content | Uses a documented approval trail and review date |
| Administrator | Manage settings, users, archives, and integrations | Access is limited, reviewed periodically, and protected by appropriate account controls |
Use the fewest permissions needed for each task. Separate submission from final approval where practical, especially when recognition is public-facing or includes employee images.
What to double-check
Privacy and consent
Make consent specific and understandable. Explain the fields being displayed, the intended audience, whether the content may be indexed or shared, and how an employee can request a correction or removal. Store the consent record separately from the public profile when possible, with a reference that authorized administrators can review.
Use optional fields carefully. A compelling employee spotlight does not require a personal biography, home location, or unrelated personal details. If a recognition message mentions customers, partners, or projects, remove information that the wider audience does not need.
Accessibility
- Use meaningful alternative text for images, or mark decorative images appropriately.
- Do not communicate recognition through color alone. Pair colors with headings, labels, icons, or text.
- Check keyboard navigation, focus order, link labels, form fields, and modal dialogs.
- Maintain readable contrast, scalable text, and layouts that work on mobile screens.
- Caption or provide a text alternative for recognition videos and audio.
- Use descriptive headings and consistent page structure so assistive technologies can interpret the content.
Accessibility should be checked in the actual platform and template, not only in a design file. Recheck it after a theme, component, integration, or display format changes.
Naming, images, and stale recognition
Write a short naming standard covering capitalization, preferred names, diacritics, titles, dates, award categories, and department names. Decide whether historical entries retain the title held at the time of recognition or display the person’s current title. Apply the same rule consistently.
For images, define acceptable file types, cropping rules, alt-text ownership, and replacement procedures. Avoid replacing an employee’s image without checking consent and preference. For stale content, set a review status such as active, needs confirmation, archived, or removed. A recognition entry can remain historically meaningful without remaining prominent on the main page.
Common mistakes
- Giving everyone administrator access: Broad access makes accidental edits and unclear accountability more likely. Start with role-based permissions.
- Collecting consent once and forgetting it: Consent should match the audience and use. Recheck it when a private display becomes public or content is reused elsewhere.
- Publishing first and reviewing later: Use drafts and approval status for images, quotations, sensitive projects, and external pages.
- Leaving former employees indefinitely visible: Define an archive or removal path and apply it consistently.
- Using attractive but inaccessible layouts: Test headings, contrast, keyboard access, alt text, and mobile behavior before treating the display as finished.
- Failing to assign ownership: A Wall of Honor without a named content owner will usually accumulate outdated titles, broken links, and inconsistent entries.
- Measuring only publication volume: Also review correction requests, review completion, participation across teams, stale entries, and unresolved access issues. A broader review supports a more useful recognition program audit.
When to revisit
Use a monthly content review for routine maintenance and a deeper review before seasonal planning cycles, annual award periods, or major recognition campaigns. Assign one owner for the review, with named contributors from HR or People Ops, IT or security, communications, and accessibility support when those functions are available.
- Prepare: Export or list active entries, pending drafts, recent change requests, failed links, and users with administrative access.
- Check: Verify names, titles, consent status, audience settings, images, alt text, dates, and award categories. Sample entries from different teams rather than reviewing only the newest content.
- Resolve: Correct routine issues during the review. Assign sensitive, disputed, or technically complex issues to a named owner with a due date.
- Escalate: Send unresolved privacy, access, security, or employee-relations questions to the appropriate internal reviewer. Do not publish uncertain content while a material question remains open.
- Record: Log completed actions, removals, permission changes, and decisions that affect future entries.
Run a broader quarterly or periodic audit when workflows, tools, integrations, templates, or organizational requirements change. Review the quarterly recognition program audit and Wall of Honor refresh workflow to structure that exercise. Refresh your governance documentation at least annually, and sooner when the platform changes, a new audience is introduced, or leadership and ownership change.
The practical standard is simple: every published entry should have a clear audience, documented approval, appropriate permissions, accessible presentation, and a responsible owner. Repeating those checks keeps a digital Wall of Honor useful, respectful, and reliable long after launch.