Build a WordPress Event Access and Attendee-Tracking Plugin

Less than 1 week, Less than 30 hrs/week Only freelancers located in the United States may apply. I operate continuing medical education livestreams through an existing WordPress website hosted on GreenGeeks. Each event page contains the complete attendee experience in one place, including the embedded livestream, Slido interactive Q&A, presentation slides, schedules, instructions, and supporting content. These pages will continue to be created and managed by our existing webmaster. I am looking for an experienced WordPress developer to build a simple, reliable access gate and attendee-tracking mechanism for selected event pages. Important Context We do not receive a real-time registration roster from our client. Therefore, the system will not be validating attendees against a registration database. Registered attendees will receive a shared event access code in their registration confirmation email. The goal is to improve upon our current system, which uses a generic URL and generic password but gives us no information about who accesses the event. The new system should require attendees to identify themselves before entering the protected WordPress event page and should record their access activity. A separate proof of concept has already been created using Clerk, Next.js, and Vercel. It demonstrates the attendee experience we want, but we do not necessarily require that architecture. The final solution must protect the existing WordPress event pages without moving the livestream, Slido, slides, or other event content to a separate application. Attendee Experience On the attendee’s first visit: The attendee visits the existing WordPress event URL. The event content is hidden and an access form appears. The attendee enters: First name Last name Email address Shared event access code Acceptance of the event terms and conditions The system validates the event access code. The system records the attendee’s information and grants access to the existing WordPress event page. A secure cookie or session remembers the attendee through the end of the event. The developer should recommend whether an emailed numerical verification code should also be required. We have experienced problems with magic links being blocked by hospital, university, pharmaceutical, and healthcare organization email systems, so the system must not depend exclusively on clickable magic links.

Requirements Protect selected WordPress event pages before their content is rendered Keep the existing page layout and content-management process unchanged Support a different shared access code for each event Collect first name, last name, and email address Record acceptance of terms and conditions Record first access, most recent access, and return visits Set an event-specific secure cookie or session Allow access to expire automatically after the event Allow our webmaster to designate a page as protected Allow us to change an event code without developer assistance Allow us to manually authorize an attendee in under one minute Provide an optional email verification-code setting that can be enabled or disabled by event Include rate limiting and reasonable protection against access-code guessing Ensure caching does not expose protected content Provide an attendee list and CSV export for each event Work properly on desktop, tablet, and mobile devices The developer should also explain whether linked slide files and the embedded video require additional protection from direct access. Multiple Events The tool must support multiple events. Each event should have its own: Protected WordPress page Event title and dates Shared access code Access expiration date Attendee-access records Email verification setting Adding or configuring another event should take only a few minutes through the WordPress administration area. Deliverables Working plugin installed and tested on our WordPress site Source code in a private GitHub repository that I own Plain-English operating instructions A 30-minute screen-share walkthrough with me and our webmaster Testing using a live test stream before launch Correction of project-related bugs through the September event Timeline Functional and deployed by August 21, 2026 Full rehearsal around August 28, 2026 Live event September 15–18, 2026 The live-event dates cannot move. Please Address in Your Proposal Please skip generic boilerplate and answer directly: Have you created a custom WordPress authentication or content-protection plugin? How would you protect the page without changing its existing content or layout? Would you use WordPress sessions, WordPress user accounts, Clerk, or another method, and why? How would you handle attendees who cannot receive verification emails? How would you prevent caching from exposing the protected event page? What information would we be able to view and export? What is your fixed price and number of working days? What weakness or concern do you see in this approach? Account Ownership The WordPress site, plugin code, GitHub repository, email-delivery account, and any third-party services must remain in accounts that I own or control