Launch Readiness resource

Send the best available assets. We’ll sort the rest.

Use this after your deposit to gather one shared folder for logos, race-day photos, maps, sponsors, policies, registration truth, and access owners. You do not need perfect files to keep the build moving — label what is best, what is okay, and what still needs permission.

Deposit received One folder shared with StartLine Permissions and gaps tracked before launch

Still evaluating StartLine?

This hub is for post-deposit Launch Readiness.

If you have not requested an audit or received a package recommendation yet, start with the buyer resources below. They explain fit, pricing, and what a private audit includes before asset permissions or access-owner details are needed.

Request a private audit → View pricing See sample audit

Assets can be rough

Share one folder, then keep the checklist moving.

No special upload workflow is needed here. Put available logos, photos, maps, sponsor files, policy docs, registration screenshots, and access-owner notes in one shared folder, then paste the link into Launch Readiness. If permission is pending, label the file “needs approval” instead of holding the whole folder.

Open Launch Readiness Checklist →

Recommended folder setup

Once StartLine has asked you to prepare Launch Readiness assets, create one shared folder and make sure StartLine Sites can view it. Use subfolders for best files, okay fallbacks, and permission-pending items when that helps. If there are private working files you do not want published, place them in a clearly labeled “Reference only” folder. Use clear folder names so logos, photos, course files, sponsor assets, policies, and access owners are easy to review during the build.

  1. 01 Logos & brand — race logo, marks, colors, fonts, brand guide.
  2. 02 Photos — hero candidates, race day, course, community, medals/shirts.
  3. 03 Course — maps, elevation, GPX/route links, aid station chart, certification notes.
  4. 04 Sponsors — sponsor logos grouped by tier plus links.
  5. 05 Content & policies — schedule, FAQs, refund/transfer/cancellation/weather rules.
  6. 06 Access notes — domain, analytics, Search Console, pixels, and platform owners.

How to label assets

Best is ideal. Okay is useful. “Send what you have” prevents stalls.

BestOriginal files, high resolution, rights confirmed, and clearly named.
OkayUsable fallback files, older versions, or links that need light cleanup.
Send what you haveContacts, screenshots, old folders, or notes that tell StartLine who can approve the final version.

Logo files

Best: SVG or EPS originals with horizontal, stacked, one-color, and light/dark versions. Okay: high-resolution transparent PNG. Send what you have: old site logo, shirt art, or race mark with a note that StartLine should recommend cleanup.

ExampleExample: race-logo-primary.svg and race-logo-white.png

Hero and race photos

Best: 6–12 licensed race-day photos at 2000px+ wide, with preferred hero candidates marked. Okay: a smaller edited gallery with start, finish, course, runner, volunteer, and community moments. Send what you have: photographer contact, folder link, or note that current photos need approval.

ExampleExample: finish-line-crowd.jpg, course-ridge-mile-9.jpg

Sponsor logos

Best: transparent SVG/PNG logos grouped by exact tier with display names, URLs, and usage permission. Okay: website URLs for each sponsor. Send what you have: sponsor list plus who can confirm final order and rights.

ExampleExample: Premier Sponsor — Example Running Store — https://example.com

Course map and elevation

Best: certified map, GPX/route link, elevation, aid stations, road closures, parking, and start/finish notes. Okay: PDF/image map plus logistics notes. Send what you have: registration-page course text or an older map clearly labeled for review.

ExampleExample: marathon-course-map.pdf and elevation-profile.png

Brand colors and fonts

Best: HEX colors, font names, and brand guide. Okay: screenshots or examples you like. Send what you have: “use StartLine recommendation” if there is no formal brand system.

ExampleExample: Primary #0E1729, Accent #FF4D3D, Font: Montserrat

Registration URL and status

Best: official registration URL, platform name, open/closed/waitlist/access-code status, price/fee notes, and registration-policy dates. Okay: platform dashboard link plus public URL. Send what you have: the current link and a note if prices or status may change.

ExampleExample: RunSignup registration page URL; prices include fees; transfers close September 15

Policies and legal copy

Best: refund, transfer, deferral, weather, cancellation, accessibility, privacy, waiver, and safety rules that match registration. Okay: registration-page policy copy. Send what you have: “policy unchanged from last year” plus the page where it appears.

ExampleExample: “No refunds after September 1; transfers allowed through September 15.”

Access owners and permissions

Best: names/emails for domain/DNS, domain email, GA4, Search Console, Tag Manager, Meta pixel, registration platform, and final launch approver. Okay: “another board member owns this” with contact info. Send what you have: who to ask next — do not email passwords.

ExampleExample: Domain at GoDaddy; GA4 owned by director@example.com

Quality guidelines

  • Use original files when possible. Screenshots of logos or photos are usually too small, but they are still useful as “send what you have” references.
  • Photos should be licensed for your race to use on the public website; label anything that still needs photographer or committee approval.
  • Sponsor logos should include the correct tier/order, display name, link destination, and usage rights.
  • Course, pricing, registration status, and policy details should match your registration platform to avoid runner confusion.
  • Do not email passwords. Name the owner who can grant delegated access or schedule a screenshare.
  • If something is missing, write “not available yet” in Launch Readiness instead of delaying the whole form.

Helpful extras if you have them

Medal/shirt mockupsCharity partner copyHotel/travel linksVolunteer infoPast resultsPress mentionsRunner FAQ notesAccessibility notesParking mapsFinish festival details