Launch Readiness access guides

Tell us who owns access. Do not send passwords.

These guides help race directors answer technical-looking Launch Readiness questions in plain language. For each item, name the owner, describe the current setup if you know it, and choose “I don’t know yet” when StartLine should follow up with another person before launch.

Race keeps ownership Delegated access or screenshare No passwords by email

Still evaluating StartLine?

These guides are for post-deposit Launch Readiness.

If you have not requested an audit or received a package recommendation yet, start with the private audit path. Access-owner details are only needed once a project is moving toward build and launch.

Request a private audit → View pricing See sample audit

If you only have two minutes

Put owner names in Launch Readiness first.

StartLine can work with partial answers. The most helpful answer is often not a login — it is the name and email of the person who controls the domain, email, analytics, registration platform, or old website.

Open Launch Readiness Checklist →

Guide index

Jump to the access question you are answering.

Domain / DNS ownerDomain email safetyGA4 / Search Console ownershipRegistration link and statusCurrent-site access

Customer guide

Domain / DNS owner

Tell us who controls the public race domain and who can approve launch-time domain changes.

What to send

  • Registrar name if known: GoDaddy, Squarespace, Cloudflare, Namecheap, Google Domains, or similar.
  • The person or vendor who can add DNS records or join a screenshare.
  • Whether the domain also handles race email.

What not to do

Do not email domain passwords. Delegated access or a screenshare is safer.

Helpful answer

“Domain is at GoDaddy. Treasurer Jane owns the login and can join a launch screenshare.”

Customer guide

Domain email safety

Confirm whether your race sends email from the same domain so launch does not interrupt inboxes.

What to send

  • Any addresses like info@, race@, director@, or support@ using the race domain.
  • Email provider if known: Google Workspace, Microsoft 365, GoDaddy email, Mailchimp, Constant Contact, or similar.
  • Who can verify MX/SPF/DKIM records before DNS changes.

What not to do

Do not change mail records casually. StartLine only needs to know who owns them and whether they must be protected.

Helpful answer

“We use info@examplemarathon.org through Google Workspace; board member Luis manages it.”

Customer guide

Registration link and status

Confirm the exact public registration destination and what runners should believe right now.

What to send

  • Official platform: RunSignup, Race Roster, GiveSignup, Haku, Active, UltraSignup, or another provider.
  • Open, closed, sold out, waitlist, transfer-only, access-code, or coming-soon status.
  • Price/fee confidence, deadline dates, and policy copy that must match registration.

What not to do

Do not send admin-only registration dashboards as the public CTA unless that is the only way to prove status.

Helpful answer

“Public RunSignup URL is final. Half marathon is open; 5K is sold out; prices include provider fees.”

Customer guide

Current-site access

Name who can access the existing website, but do not send credentials unless StartLine explicitly asks through a safe path.

What to send

  • Platform: WordPress, Wix, Squarespace, Webflow, RunSignup race page, custom vendor, or unknown.
  • Who can export copy/photos or approve what should be reused.
  • Any old vendor contract or hosting deadline that affects launch timing.

What not to do

Do not make StartLine the only owner of your site. The race should remain the account owner.

Helpful answer

“Old site is WordPress. Former volunteer Amy still has admin access and can export pages if needed.”

Unsure who owns something?

“I don’t know yet” is a valid Launch Readiness answer.

If a board member, former volunteer, old vendor, registration platform, or sponsor contact owns the answer, write their name or role. StartLine will group follow-ups instead of asking for scattered technical details.

Email support