Coaches & Mentors Corner

For every coach and mentor in Loudoun County.

Parents who ghost in week three. Parts that arrive late. Kids who burn out before competition. Judging interviews nobody prepped for. Every Loudoun coach shares more problems than they realize — this page collects what's actually worked, for any FLL, FTC, or FRC team, regardless of which org runs it.

Welcome

Why this page exists.

We're collecting what works — from any coach or mentor, for any team — in one place. Templates, scripts, real dollar amounts, real Loudoun calendar dates. The kind of stuff that's only in a coach's head until they retire.

Loudoun Robotics is a parent-founded nonprofit, but our mission isn't to grow our own teams — it's to make sure every kid in Loudoun County who wants to do robotics can. That means supporting every coach and every mentor in the county, not just the ones connected to our teams. This is also the playbook we use internally — what's good enough for an LR-run team is good enough to publish.

Coaches vs. Mentors — both matter.

Coaches run a team week-to-week: cadence, parent comms, kit logistics, getting kids to competition. Mentors drop in to help with specific things: a build problem, a coding bug, judging-interview prep, a marketing push, a presentation rehearsal. A great team usually has one of each — sometimes both in one person, sometimes spread across many.

Bookmark this page. Send corrections. Tell us what would help you most. Get in touch any time.

Brand-new coach? Start here.

Five steps to launch a team.

If you've never coached before, this is the path most teams take. Plan for 4–6 weeks of calendar time and roughly 8 hours of your own time before kids walk in. The steps need to happen in this order — skipping registration to "save time" stalls everything two weeks later.

FIRST vocabulary: which FLL is my kid on? What's an Innovation Project? A glossary for rookie coaches. (Click to collapse if you already know this.)

The program tree (which FLL is your kid on?)

  • FIRST — the worldwide nonprofit (For Inspiration and Recognition of Science and Technology) that runs all the programs below. They set rules, run seasons, and license the challenges.
  • FLL Discover (ages 4–6, K–1st) — simplest tier. Kids explore a theme with LEGO Duplo, no code. Meets twice a month.
  • FLL Explore (grades 1–4) — simple LEGO model plus a real-world topic. Kids build and present. Still no coding beyond icon-based.
  • FLL Challenge (grades 4–8) — the "regular" FLL most people mean. SPIKE Prime robot, a mission mat, block or Python programming, and a real-world Innovation Project. This is what LR's summer camp targets.
  • FTC (FIRST Tech Challenge, grades 7–12) — metal robot with real motors and encoders. Java or Blockly. Bigger tournaments, more travel.
  • FRC (FIRST Robotics Competition, grades 9–12) — 120-pound industrial robot, full engineering team, sponsored budget. Not for beginners.

What gets judged (all three matter — the robot isn't 100% of the score)

  • Robot Game — the 2:30 timed run on the mission mat, points scored per completed task. Highest-visibility but only ~35% of the total.
  • Innovation Project (FLL) — kids pick a real-world problem within the season's theme, research it, design a solution, and present a 5-minute pitch to judges. ~30% of the score. Most-neglected area for rookie teams.
  • Engineering Notebook (FTC) — ongoing written log of design decisions, iterations, what worked and didn't. Judged separately from the robot. Half of FTC teams under-invest here.
  • Core Values (FLL) / Gracious Professionalism (FTC) — ~25% of the score. Judged on Discovery, Innovation, Impact, Inclusion, Teamwork, and Fun. Assessed during a 5-min interview with 3 judges plus by observation throughout the day.

Season milestones

  • Kickoff — the day FIRST releases the season's challenge. FLL Challenge: August. FTC: September. This is when you know the theme and the mission mat.
  • League Meet — informal scrimmage-style event, low stakes. Practice a real judging interview + robot run in tournament conditions. Not every region uses these.
  • Qualifier — your first "real" tournament, scores count, top teams advance. Held December–February.
  • Regional / Championship — advance from qualifier. Bigger venues, more teams, more polish expected. Feb–April.

Background checks (both are required for LCPS schools)

  • Sterling — FIRST's required background check. Email arrives 5–7 days after you start; full clearance takes 1–2 weeks after that.
  • LCPS volunteer registration — separate from Sterling. Required if you're a parent volunteer at any Loudoun County Public School, even for after-hours club activities. Start it early — the school will ask in October.
  1. Pick a program.

    FLL Discover (ages 4–6), FLL Explore (grades 1–4), FLL Challenge (grades 4–8), FTC (grades 7–12), or FRC (grades 9–12). Younger = simpler kits, less time. Older = more coding, more travel.

  2. Register the team with FIRST.

    Go to firstinspires.org, create a coach account, register the team. FLL Challenge: ~$285 registration + ~$540 SPIKE Prime + Expansion Set (first year only) + ~$105 annual challenge set + ~$175 regional qualifier, plus supplies and replacement parts = ~$1,000–$1,500 first year, ~$500–$700 returning years. FTC: ~$295 registration + ~$1,200–$1,800 hardware first year. The form will ask for a Lead Coach 1 and Lead Coach 2 — both need separate accounts and separate Sterling background checks. The check email arrives 5–7 days after you start; full clearance takes 1–2 weeks after that. Youth-protection consent is a separate step that's easy to miss. Budget 45 minutes for registration itself, 2–3 weeks total to hit the ground running.

  3. Find a host space.

    You need a spot to meet weekly with a table, electrical outlets, and storage for the robot. School classroom, public library, makerspace, community center, or someone's basement — all work. Loudoun County Public Library branches frequently host teams for free.

  4. Recruit students.

    FLL Challenge: cap at 10. FTC: cap at 12. Mix grades if you can — older kids mentor younger ones. The hard part is the 11th parent. When they ask, say: "We're full this season. If you'd like, we can keep you on the waitlist for a second team if 6 sign up — or Loudoun Robotics maintains a county-wide waitlist for new teams forming." That sentence saves friendships.

  5. Buy the kit, set the schedule.

    Step 2 covers what FIRST charges the team (~$1,000–$1,500 first year for FLL). Add on top of that per team: shirts ($150–$300), travel + tournament-day food ($100–$300/season). Real total per team, unsponsored: FLL Challenge $1,200–$2,000 first year; FTC $4,500–$6,500 first year. Per family after an LR team grant or sponsor covers the base: FLL $0–$50/kid for shirts and food; FTC $50–$150/kid. Plan a weekly meeting (90–120 min for FLL, 2–3 hrs for FTC). Season cadence: Kit ships and kickoff happens in August (FLL Challenge) or September (FTC). League meets and scrimmages run October–December. Qualifier tournaments are December–January. Regional/State championships fall January–March. Most teams that quit didn't plan past December.

Stuck on funding?

Loudoun Robotics offers team grants ($150–$300, with room to negotiate for more) for any team in the county. Loudoun Youth, Inc. and ACOY also fund youth-serving programs. See Funding for any team below.

Considering VEX instead?

VEX is a separate ecosystem with its own programs (VEX 123 / GO / IQ / V5) — equally valid path. We're FIRST-focused today, and we're tracking VEX demand in Loudoun — if enough families are asking, we'll add VEX to our programs. In the meantime, happy to point you toward local VEX coaches. Tell us your kid's grade → · Learn about VEX

Run a great season

What experienced coaches wish they'd known.

A short list of habits that separate teams that have a great year from teams that limp through.

  • Pick a meeting day that doesn't fight travel soccer. In Loudoun, travel soccer eats Tue/Thu evenings and Saturday mornings; rec basketball eats Saturdays Nov–Feb. Sundays and Friday evenings have the fewest conflicts. Run a When2Meet with parents in August before locking in.
  • Send a 4-line update by 8pm Sunday — over text, not email. What we did. What's next. What we need (snacks / driver / a missing part). One photo. Parents read texts. They don't read emails. Use a group thread, not a reply-all chain.
  • Two adults at every meeting — build the bench in week one. The second adult is the #1 reason coaches quit. In your kickoff parent meeting, ask three families to commit to one meeting per month as "second adult" — just present, no skills required. That's a rotating roster, not a single hero.
  • Don't let the robot eat the season. FLL Innovation Project and FTC Engineering Notebook matter as much as the robot at competition. Schedule non-build time deliberately — 20 minutes every meeting beats a panicked weekend in December.
  • Mid-season slump? Scrimmage another team. Around week 6–8, motivation drops. Email us via the contact form — we'll match you with another Loudoun team for a Saturday scrimmage. Kids who've never seen another team play remember why they signed up.
  • Practice judging interviews twice before competition. Most teams under-prep their interview — that's where awards are won. Run mock interviews with a parent volunteer; do them in week 4 and week 8.
  • Order replacement parts in October. Things break in November. Late-season parts orders take weeks to arrive.
  • Keep one parent as designated driver to competitions. Robot transport is a logistical nightmare without ownership. Pick someone in week one.
  • Parts steward. Buy a $12 Akro-Mils 64-drawer bin, label it, and assign "parts steward" as a rotating kid job each meeting. Year-2 coaches lose axles. Year-3 coaches don't.
  • Mixed-age teams: tier the work. Common Loudoun FLL reality — half your kids are 8, half are 12. Tier the tasks: juniors do build + decoration, seniors own programming + Innovation Project. Both ages stay engaged; nobody gets bored.

A 90-minute FLL Challenge practice (sample)

  • 0:00–0:10 — Standup. What we're doing today, in 2 sentences. One kid recaps last meeting.
  • 0:10–0:40 — Build / program in two groups. Senior kids on code, junior kids on build (or vice versa next week).
  • 0:40–1:00 — Mission run. Whole team. Time each attempt. Three runs, count the score.
  • 1:00–1:20 — Innovation Project. 20 minutes is enough if it's every meeting. Skip the panicked December weekend.
  • 1:20–1:30 — Cleanup, parent pickup, send the Sunday text.

Parent Expectations 1-pager — send before week one.

Single biggest lever for keeping families engaged: tell them up front what they signed up for. Open the downloadable 1-pager → — customize the meeting day, costs, and your name, then text or email it to families before the first meeting.

Hard conversations

The talks no handbook covers.

Three conversations every year-2 coach loses sleep over. Each one has the same shape: acknowledge first, redirect with a concrete next step, end with an option that's easy to accept.

1. "Why does your kid get all the build time?"
Usually comes from a parent who's been quietly watching. They're not wrong — the kid who builds well does end up doing more of the build. Don't get defensive; they're naming a real pattern. The fix is structural, not personal.
What to say
"You're right that [Kid A] has been on the drill press a lot. We're rotating roles starting next week — every kid signs up for build, programming, or Innovation Project, and we rotate every two meetings. We're also running driver tryouts in two weeks so the seat isn't assumed. If you want to come to one practice as a co-mentor and see how the rotation works, I'd love that. What's a meeting that works for you?"
2. "You said you'd sponsor and never paid."
A parent or local business owner committed verbally in September. It's now January. The print deadline for shirts was last week. Don't open with money — open with the relationship and give them an easy yes. Most no-show sponsors are embarrassed, not adversarial.
What to say
"Hey [name], following up on the $500 sponsorship we talked about in September — just wanted to make it easy. I can send you a Givebutter link, or you can write a check to Loudoun Robotics (we're a 501(c)(3), EIN 33-4000099, fully tax-deductible). Either works. We're printing shirts [date]; if you want your business on the back, [earlier date] is the cutoff. No pressure either way — just let me know."
3. "I want my kid to quit."
Almost always comes between weeks 6 and 10. Sometimes it's the kid; often it's the parent burned out by logistics. Don't try to talk them out of it — you'll lose the relationship. Acknowledge, ask what changed, offer an off-ramp that lets them save face.
What to say
"Thanks for telling me — I'd rather know now than guess. Can I ask what changed? Sometimes it's the kid not having fun, sometimes it's a parent schedule that got crushed; the answer changes what I can offer. If it's the kid, we can switch their role for two weeks and see if something else lands. If it's logistics, we can move them to half-meetings or just tournament-day participation. And if it's truly time to step back, no hard feelings — the door's open for next season."

Got a conversation you wish there was a script for? Send it to us. We add what coaches are actually fighting with.

Retention triage

When multiple things are on fire.

Two families threatening to quit + a sponsor ghosted + a build-time complaint isn't three separate conversations. It's a systems problem. Here's the order to work it, and what to cut when you can't do everything.

Signs by season phase

  • Weeks 1–3 (early): parent silence on the Sunday text, a kid arriving late twice, a coach volunteering "one more week and I'll help." These are cheap to fix. Personal 2-line text to each parent, one one-on-one 5-min chat with the kid, name the assistant coach commitment.
  • Weeks 4–8 (mid): a kid stops asking questions, a parent skips two tournaments-of-record without telling you, a snack sign-up sheet has empty slots for the next 4 weeks. Now they're expensive. These need real conversations, not texts. Prioritize the kid over the parent over the sponsor — kids are the load-bearing wall.
  • Weeks 9+ (late): a robot broken more than once in the same session, judging prep skipped, sponsor delivery late. Now they're structural. Consider whether the goal changes (advancement → showing up cleanly at qualifier).

If 2+ fires at once: work in this order

  1. Kids first.

    Which kid is on the edge? Talk to them (not the parent) for 5 minutes at the next meeting. Ask "how's this feeling for you?" and mean it. If they're OK, everything else can wait a week. If they're not, everything else can wait a month.

  2. Then the parent group.

    One group text: "Here's what I'm hearing from a couple of families. Here's what I'm going to change. Reply if you want to talk 1:1." Names three concrete adjustments. Not a defense — an acknowledgment.

  3. Then money.

    Ghost sponsor gets one follow-up (Script 2 in Hard Conversations). Then move on — do NOT keep chasing during a fire. Reduce shirt spend, delay a swag order, tap the LR team grant if you haven't already.

  4. Then robot.

    The robot is almost always the last thing to fix. Broken bots survive weeks of mid-season if the team is intact. Broken teams end even the best-built robots.

When to reduce scope (and how to say it)

  • Drop the second qualifier. If you signed up for two, drop the second. Tell parents: "we're getting really good at the first one so it counts more."
  • Half meetings. Instead of missing a meeting entirely, run a 45-min "just the robot" session. Skip Innovation Project for that week. Kids stay in the rhythm; you get an hour back.
  • Consolidate. Two teams meeting Tuesdays and Thursdays → one long meeting Saturday. Fewer nights out for you; more depth per session.
  • End the season early — gracefully. Very rare, but real. If you say it before Christmas break with a plan for the kids ("we'll wrap after the qualifier, robot goes home, party at coach's house"), it lands as intentional. If you say it in February, it lands as failure.

The coach's version of "I want to quit."

You're allowed to. If you're in triage territory and still solo-leading, tell the head-coach honestly: "I need a co-lead this month or I'm going to burn out by qualifier." Email us — we can help you find one, or take a meeting off your plate.

Year 3+ · Grow & sustain

You've done this. What's next?

Most coaching advice assumes you're launching or surviving. Nothing says what a healthy 4th, 5th, 8th year looks like. Here's the honest version — adding a second team, handing off head-coach, sibling teams, and staying sustainable when your kids are still in it and life keeps moving.

Adding a second team — when to say yes

  • You'll say yes because a family asks and you don't want to say no. Say no anyway if you don't have (a) a second head coach committed by August, (b) a second venue slot locked, (c) a second kit funded. Missing any of the three means you're just adding load to your own team.
  • The right structure is two teams sharing a night, not one team with 20 kids. 6–10 kids per team keeps everyone building. 20 kids in one room means 4 kids build and 16 watch.
  • The head coach role does NOT scale. If you're the head coach on both teams, quality drops on both. Recruit an assistant to lead one; you consult on the harder problems from the sidelines.

Handing off head coach

Best handoff is a two-year runway. Year N−1: identify the successor, invite them to co-coach 3–4 meetings and one tournament weekend. Year N: they run week-to-week, you're on-call for problem meetings. Year N+1: you're a mentor to them, not to the team. If the runway is shorter than that, brief them heavily on: the season calendar, the parent group's tone, which families need which kind of attention, and the fiscal-sponsor / grant / registration mechanics. Write it down — institutional memory in a coach's head is fragile.

Sibling teams (junior / senior structure)

Two teams under one head coach, distinct kids, shared learning. Common pattern: an FLL Challenge (grades 4–8) team and an FTC (grades 7–12) team where the older kids pull from graduates of the younger. Works well because: shared curriculum vocabulary, shared parent network, natural mentorship pipeline (FTC kids teach the FLL kids at joint meetings). Trap: FTC becomes a place FLL graduates "should" go rather than choose. Make it opt-in and be OK if half don't cross over.

The sustainability math

  • Your kid ages out. If your reason for coaching is your kid, plan a graceful exit in their final season. Coaching without your own kid on the team is a different job with different politics; some coaches love it, most don't.
  • The hidden hours are the killer. Sunday text (30 min/wk), tournament weekend (10 hrs), parent-conflict follow-ups (variable), grant applications (2–4 hrs/season), sponsor asks (2–6 hrs/season). Track for one season, budget realistically the next.
  • You don't have to run a team to still contribute. The mentor role (a few hours a month) is where a lot of veteran coaches land. It preserves connection to the community without the operational load.

Growing into an LR-affiliated multi-team lead

If you're at year 3+ and thinking about starting or leading a team at a different school (a different kid, a friend's neighborhood, an underserved area), LR supports experienced coaches as affiliated coaches. What that concretely includes:

  • Kit + registration funding. Up to $1,500 first-year and $500–$700 returning-year coverage per team, via team grants without the usual application friction (affiliated coaches get an expedited path).
  • Fiscal-sponsor infrastructure. Corporate sponsors and donors can give to LR (EIN 33‑4000099), earmarked for your team. We issue receipt letters within 5 business days.
  • Background check + tournament registration cover. LR staff handles Sterling paperwork, LCPS volunteer registration, FIRST event registration, and the deadlines — you focus on kids.
  • Mentor introductions. Direct pairings with LR's engineer/programmer/judge network for the specific skill your team needs (build, code, Innovation Project, judging prep).
  • Peer coach network. A monthly call with other affiliated coaches. Talk about what's working, what's stuck, what to steal.

You keep your team's identity. Coaches keep their name. LR shows up as infrastructure, not overseer. Tell us what you're thinking — you'll hear back in 3 business days with a call scheduled that week.

Peer support isn't waiting for the Coaches Corner Series.

The monthly meetup is coming (first session August 2026). Between now and then: if you have a specific problem or want to trade notes with another veteran coach, email admin@loudounrobotics.org and we'll connect you to someone with the right experience. Don't wait months for a session that hasn't started yet.

Funding for any team

Where the money actually comes from.

Teams need adults who can keep the lights on — registration fees, kits, replacement parts when a motor gives out in February. Team grants exist so those costs don't keep a team from playing. Here's the funding stack that works for new and small teams.

Honest baseline: even with grants and sponsors, expect team families to cover 30–50% of season costs in year one. Set that expectation in the Parent Expectations 1-pager before anyone is surprised in February.

  • Loudoun Robotics team grants — $150–$300 for any Loudoun team, with room to negotiate for more. No strings attached. Apply via our funding page.
  • Loudoun Robotics as fiscal sponsor — if your team is school-based and doesn't have 501(c)(3) status, we can act as fiscal sponsor for corporate grant applications and tax-deductible donations. Unlocks PTA money, corporate grants, and donor receipts you couldn't accept otherwise. Reach out to start that conversation.

Need a donor-receipt letter? Here's the flow.

A sponsor said yes and now needs a tax receipt from LR. Email admin@loudounrobotics.org with subject "Donor receipt request" and include: (1) donor name + business name, (2) donor mailing address + email, (3) amount + date received, (4) your team name, (5) whether the donation is designated for a specific use. We issue the receipt letter within 5 business days — PDF via email plus a mailed copy if the donor prefers. Include LR's EIN (33‑4000099) on any pitch you send BEFORE the donation lands, so the donor knows their gift will be tax-deductible.

  • Loudoun Youth, Inc. + ACOY minigrants — $500 minigrants for youth-serving programs in Loudoun County. Open year-round; reach out to ACOY directly.
  • FIRST Rookie Grant (FTC) — reduced registration for first-year FTC teams. Apply during team registration.
  • Local PTA/PTO funding — if your team is school-based, ask the PTA. They often have a "grants for clubs" line item that goes unused. Tactic: email the PTA president 2 weeks before the next meeting, ask for 5 minutes on the agenda, bring a kid in a team shirt. Works almost every time.
  • Local corporate sponsorship — small Loudoun engineering firms, IT companies, and contractors will often sponsor $500–$2,500 for a team in their back yard. Where to look in Loudoun: Telos, AWS Ashburn (employee giving), Northrop Grumman (community grants), Raytheon (STEM grants), K2M / Stryker, local credit unions, and the alumni networks of the area's defense and IT primes. Don't cold-pitch big companies — ask the parent on your team who works there for an intro. Personal intro beats cold email 10:1.
  • Crowdfunding (Givebutter, GoFundMe) — works best when you have 30–50 supporters already. Tell parents to share with their networks; don't expect the public to find you cold.
  • Robot Garage Sale — at season end, sell unused parts on AndyMark or eBay. Easy $100–$300 toward next season.

Sponsor pitch template — copy, customize, send

Yellow fields are the bits you customize. Don't change "501(c)(3)" or the EIN — those are what make the donation tax-deductible. The Copy button below gives you plain text with the [fields] intact for find-and-replace.

Dear [Name],

I coach [team name & number], a [FLL / FTC] robotics team of [#] kids in [grades] here in [Ashburn / Leesburg / etc.]. We're competing this season in the FIRST [program] league. Our season runs [start month] through [end month].

I'm reaching out because [shared connection / why this company]. Our season budget is roughly $[total] — registration, kit, replacement parts, shirts, and tournament-day costs. Family contributions cover about half of that. We're looking for sponsors at three levels:

$500 Bronze — logo on the back of the team shirt.
$1,000 Silver — logo on shirt + team banner at competition.
$2,500 Gold — all of the above + a 30-minute team visit to your office (kids love this; your team loves it too).

Loudoun Robotics, a registered 501(c)(3) (EIN 33‑4000099), can act as our fiscal sponsor — meaning your contribution is fully tax-deductible, and we can send you a formal receipt for your records.

Happy to grab 20 minutes by phone or Zoom if it's easier than email. Either way, thank you for considering it.

Best,
[Your name]
[Team name] · [email]

Loudoun-specific

Local context that matters.

Host venues that welcome robotics teams

  • Loudoun County Public Library branches — most LCPL branches will host teams for free. Ask the branch manager. Find a branch →
  • Your school's classroom, cafeteria, or makerspace — the easiest sell is a teacher who's already a fan. Don't ask in the pickup line. Email the principal with the subject "Robotics club proposal — 1 page" and attach a one-pager. LCPS requires a certified staff sponsor for any school-hours club — the easiest path is finding a teacher in the building who likes robotics and putting them as the named sponsor while you do the work. After-hours use of a gym or cafeteria requires the LCPS facility-use form — ask the principal's office for the current link; it's 6–8 weeks of lead time you don't want to discover late.

Background checks & volunteer screening

FIRST requires lead coaches to complete a Sterling background check — that email arrives 5–7 days after you start registration. Separately, if you're a parent volunteer at an LCPS school, you'll be asked to complete LCPS's own volunteer registration and background check — that's a different system. Most coaches discover this in October when the school asks. Start both in August; plan for 1–2 weeks of clearance time each.

Where Loudoun tournaments actually happen

FLL Challenge qualifiers in northern Virginia typically run at host middle and high schools across Loudoun, Fairfax, and Prince William — check the FIRST event list each fall for the current season's venues. FTC league meets and qualifiers in our region rotate through Loudoun and Fairfax high schools. FIRST event search →

Loudoun mentors who help across teams

Building a directory of Loudoun engineers, programmers, and makerspace operators willing to give a few hours a month as cross-team mentors. If you work at AWS Ashburn, Telos, Northrop Grumman, Raytheon, K2M/Stryker — or anywhere with strong engineering benches in the county — and can spare an evening or two a month, sign up here (check the relevant mentor boxes in the form). We pair you to a team that needs your specific skill, not a generic mentor slot.

First session: August 2026

Coaches Corner Series

Monthly meetup for any robotics coach or mentor in Loudoun County. No dues, no team affiliation required — LR hosts, anyone walks in. We end on time.

Standing agenda (90 min)
  • 20 min — topic of the month (rotates: kickoff, judging, sponsors, parent comms, build calendar)
  • 30 min — open Q&A; bring your stuck problems
  • 30 min — hands-on parts swap & team-to-team intros
  • 10 min — close-out, who needs what next month

Session 1 topic: Surviving FLL/FTC rookie kickoff — bring your registration questions, kit timing, and "what did I just sign up for" worries.

Get notified when we lock the August date and venue:

Want to coach or mentor a Loudoun Robotics team specifically?

We're recruiting head coaches, assistant coaches, and mentors (technical, outreach, marketing, fundraising, etc.) for FLL and FTC teams we're standing up across Loudoun County. Free kits, support from other adults in the program, no experience required — we provide training and a playbook.

Coach or Mentor With Loudoun Robotics
Reach out

Get in touch.

Suggest a resource, ask a coaching question, volunteer as a cross-team mentor, or tell us you want help starting a team. Messages route to Aravind (parent-coach, LR founder) — expect a real reply within a few days, faster during the season.