Running a Club Telescope People Actually Get to Use

Astronomy clubs everywhere just did the same smart thing: bought a smart telescope — usually a Seestar — and parked it somewhere dark. For a few hundred dollars, every member theoretically gets access to Bortle 3 skies without owning a rig or making the drive. It's the best outreach-to-imaging pipeline the hobby has ever had.

Theoretically. Because the scope is the easy part. The hard part arrives the second week: forty members, one telescope, and maybe a hundred usable nights a year. Someone volunteers to be the coordinator, a spreadsheet appears, and booking a night becomes: email the coordinator, wait for a reply, hope the reply matches the spreadsheet, hope the spreadsheet matches what someone else was told last Tuesday. Six months later the coordinator is tired, four power users have most of the nights, and half the club has quietly stopped asking.

None of that is anyone's fault. It's what happens when a genuinely scarce resource — clear, dark, moonless nights — is allocated through an inbox. If your club runs a shared scope, scheduling isn't admin overhead around the real project. It IS the project.

Why the spreadsheet always loses

The email-and-spreadsheet system fails in the same five ways in every club. Double-bookings, because two emails crossed. The who-has-it-tonight mystery, answerable only by the coordinator, who is at dinner. Clouded-out nights that stay 'used' — the member who booked it never got photons, but nobody downstream knew the night had reopened, so the scope sat idle under the only clear sky that week. No-shows nobody notices until the pattern is a year old. And quiet capture by the confident few, because the booking process has enough friction that only the members who already feel entitled to scope time push through it.

Notice that every one of these is an information problem, not a people problem. The fix isn't a sterner coordinator or a longer rules document — it's making the calendar, the conditions, and the usage visible to everyone, and making the rules self-enforcing.

The policies that actually work

Clubs that run shared scopes well converge on the same few rules, and they're all simple. Book whole nights — dusk to dawn as the sky defines it that date, not as the clock does. Cap upcoming reservations per member (two is plenty) so the calendar can't be blanketed. If demand is real, add a monthly quota — and refund weather losses against it, so a clouded-out night never costs anyone their turn. Decide whether bookings need coordinator approval honestly: most clubs discover they don't, and the approval queue was just the old inbox wearing a new hat. Keep a blackout list for maintenance and star parties. And publish the whole calendar where members already live — if it can land in Google Calendar, the who-has-it-tonight question dies forever.

The other half of fairness is handling absence. A no-show policy sounds harsh and is actually kind: if a member never connects during their slot, release the rest of the night so someone else can grab it — but count the night against the no-show's quota. Weather is refunded; flaking is not. Members learn the difference fast, and the calendar starts reflecting reality.

Getting members connected (the part everyone underestimates)

Booking the night is half the problem. At 9 p.m. on their night, a member needs to actually reach a telescope that lives miles away — and this is where most club setups get fragile. The typical stack is a VPN (Tailscale or ZeroTier) into the site network, plus either the vendor app pointed at the scope or, for Seestars, the community seestar_alp bridge running on a Pi next to it. It works — but the credentials for all of it usually live in a wiki page or a group chat, forever, for everyone.

The better pattern is time-boxed access: the connection details exist in one place, encrypted, and are revealed only to the member whose reservation is active, only during their window, with every view logged. Nobody memorizes anything, departed members hold nothing, and 'who was on the scope Tuesday' has an actual answer.

Two pieces of cheap hardware make the whole thing dramatically more robust. A smart plug (Tasmota or Shelly, ~$15) lets the scope power up only around booked slots — which ends both 'someone left it running all week' and 'the battery was dead on my night.' And the little computer running the bridge can double as a watchdog: reporting the site's weather, disk space, and power state so members know before they connect that tonight is even viable.

The point is making astrophotographers

Here's the metric that matters more than utilization: how many members did the club scope turn into astrophotographers this year? That number moves when a member's night produces something that is theirs. If the subs from their session land in a shared folder named by date, the night evaporates. If their frames come back attributed to them — graded, plate-solved, in their own library, with a morning report saying what they captured and what it's worth — the night compounds. They start planning the next one. Eventually they buy their own rig, and the club has done its job.

So when you evaluate any scheduling setup — homegrown or product — ask the member-side questions, not just the coordinator-side ones. Can a brand-new member go from newsletter link to booked night in five minutes? Do they know what to shoot when they get there? Do they own what they captured? The spreadsheet answers no to all three. That's the real reason to retire it.