Curling Club Management Software

Curling club software for clubs run by volunteers in their spare time.

Registration, dues, draws, and email chains sit on a few volunteers, spread across eight to ten separate tools. We turn that pile into one system where sheets are booked by league and bonspiel, draws follow your round-robin and flight rules, and a spare can be found before the ice is ready.

See our work

Bring one stuck workflow. Leave with a build, buy, repair, or wait recommendation.

Trusted by

Perceptional logoMusgrave GroupUrShipper logoBrux Dental SolutionsBella Skin Institute LogoEnergia RewardsDraftly logoTuneClub LogoSekou LMS logoLogo of food order management app gulaSnelwegDealsGrubly logoPSi logoInstantor Rewards logologo of Mobile app for events, membership clubs, and communitiesAldiFest retail campaign logoVidmattic logoEMS Connect logoWorx Squad logologo of Online Web App For Making Intrologo of Referral and Viral Marketing PlatformConcurrences logoGE logoTicketstop logo

The brief

Start with what is not working.

Good software decisions begin with the constraint, not a list of features or a preferred technology.

01

Registration, dues, draws, and email chains sit on volunteers using eight to ten separate tools.

02

Sheets get booked like generic ice time, so leagues and bonspiels fight over the same list.

03

A player drops out an hour before the draw and the spare list is a phone chain.

Plain answer

RaftLabs builds curling club management software for volunteer-run clubs where registration, dues, draws, and email chains sit on a few people in their spare time. One system holds membership dues separate from league fees, books sheets by league and bonspiel, runs round-robin and flight draws, and keeps a live spare pool.

What to remember

  • Use this when club admin lives in inboxes, spreadsheets, and the memory of two or three volunteers.
  • Sheets are booked by league, bonspiel, and learn-to-curl session, not as plain blocks of ice time.
  • Membership dues and league fees are separate charges, tracked separately, so nobody pays the same dues twice.
  • Quote the board's own screens as their own scope: draw changes, spare requests, refunds, dues records, and standings corrections are a second product, not a single admin-panel line.
  • Hire freelancers for one small, well-defined task; use one accountable agency party when the work needs coordination across screens, rules, data, and connections.

The first decision is not what to build.

It is whether software is the right answer at all. We use four possible recommendations before discussing a development scope.

  • 01

    Buy

    Choose a maintained product when it handles your draw formats, your spare rules, and your split between dues and league fees, and the remaining gaps can be solved with configuration, a connector, or a small process change. Paying for software you do not have to maintain is often the better trade.

    Run the build-vs-buy numbers

  • 02

    Repair

    Keep the existing system when members and volunteers still get value from it and the code can be understood safely. Start with evidence: where the code lives, how the data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live.

  • 03

    Build

    Own the system when your league formats, bonspiel weekends, or dues rules shape how the club runs and no maintained product will hold them. Start with one complete path, usually registration through to a published draw, and the system connections that path cannot work without.

  • 04

    Wait

    Do not turn changing club rules into permanent software. Settle how draws, spares, and fees should work, name the workflow owner, and measure the cost of the current process before paying for a product.

Not sure which path is yours? Bring it to a 30-minute call. Leave with the answer in writing.

Fit

Custom club software should earn its maintenance burden.

A feature request is not enough. The case is real when the same constraint shows up in time, errors, margin, or customer experience.

A fit

Registration, dues, draws, and messages are tracked in separate tools, and the gaps land on the same few volunteers.

Generic sports or rink tools keep flattening sheets, draws, flights, and spares into ideas they were not made for.

The club can name a workflow owner and what 'done' looks like for the first release.

Not a fit

A maintained product fits your leagues, bonspiels, and fee rules with reasonable configuration.

The board wants software to settle league rules nobody has agreed yet.

The brief is a feature list with no user, transaction, or business result attached.

Not sure which side you are on? Use the first call to make that decision. A useful answer may be to buy, connect, repair, or wait.

Start with the operation, not the software.

A curling club problem usually starts as a volunteer problem. Registration lives in one tool, dues in a spreadsheet, the draw in another spreadsheet, and a moved draw time only reaches members once someone forwards an email about it. Each piece looks manageable on its own. The trouble is the total: eight to ten separate tools, none of them talking to each other, held together by two or three people doing club work in their spare time.

The work itself is specific to curling, and that is why general tools strain. A sheet is not a generic hour of ice: it belongs to a league draw on Tuesday, a bonspiel all weekend, and a learn-to-curl class on Saturday morning. A draw is not a list of games: it is a round robin that has to stay fair across early and late times, or a flight ladder where teams move after every round. A spare is not a substitute in general: it is a lead who is free on Thursday and willing to be asked at short notice.

A second product hides inside the first. Members see one registration page; your board lives in another: setting up next season, moving a draw, finding a spare, correcting a standing, refunding a bonspiel entry, and keeping a record of who changed what. Quotes that squeeze all of that into an "admin panel" line item are where budgets most often break, so we quote your board's screens as their own job, with their own users, from the start.

Custom software makes sense when one owned system can hold registration, dues, draws, spares, and bonspiels together better than a product, connector, or process change. The first release should take the smallest useful path from sign-up to a published draw. It should not replace every tool at once.

We start where it hurts.

The member pages are only one part of the job. The real scope includes how sheets are shared between leagues and events, the draw formats, the spare rules, what happens when things fail, who can see and change what, and who runs it after release.

Admin spread across eight to ten tools

Bring registration, dues, draws, messages, and payments into one record per member and one calendar per sheet. A change made once shows up everywhere it should, and the club stops depending on one volunteer retyping the same list into the next tool.

Draws made by hand every round

Set the format once and let the system lay out the round robin or flight ladder: who plays whom, on which sheet, at which draw, with early and late times shared fairly. Scores and standings stay with the draw, and the next round is ready for the draw master to check.

Spares found by phone chain

Keep a live spare pool with positions and free nights that members update themselves. One request goes to the spares who fit, the first acceptance takes the spot, and the request closes for everyone else.

Dues and league fees mixed together

Keep annual membership dues and per-league fees as separate charges on the same member record. Dues are collected once, league fees follow the leagues a member actually joins, and the treasurer can show either total on its own.

Bonspiels run from inboxes

Give each bonspiel its own entry list, fee, draw, and bracket, open to visiting teams who never become members. Results move winners on as the weekend goes, and every team checks the next game on a phone.

Which one is yours?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

Verticals

Custom software for specialised operations.

Some workflows only exist in one kind of club. The same rules apply: configure first, build only the part the maintained products cannot cover, and start with one complete path.

Leagues and draws

The league is the season. Fixed teams or drafted teams, round robins, flights and ladders, two halves with new groups, playoffs and consolation events: each format keeps its own draw, scores, and standings, and each draw takes the sheets it needs for its night.

Bonspiels and open events

Weekend tournaments run on visiting teams and tight turnarounds. Entry, payment, pools or brackets, and the next-round schedule all sit on the event record, so the bonspiel chair runs the weekend from one screen instead of a folder of printouts.

Learn-to-curl and new members

Sessions with limited places, a waitlist, and the waiver signed in advance. The important part is what happens after: a clear next step into a beginners league or the spare pool, with the contact record already in the system.

Membership, dues, and the treasurer

Renewals, dues status, league fees, bonspiel entries, and refunds on one member statement. Payments connect to the club accounts the treasurer already keeps, so the season-end numbers come from records, not from rebuilding a spreadsheet.

Volunteers and the board

Shift sign-ups for ice help, bar duty, and bonspiel weekends, plus a simple task list for the board. Shifts are posted once, members claim them, and hours are counted without a separate rota tool. When a board member steps down, their work is visible to the person taking over.

Proof

The fifth attempt became a product customers could keep using.

UrShipper had already worked with four development vendors. Its founder describes the communication and decisions during the recovery.

The case study documents a 14-week recovery, five carrier connections, a Shopify fulfilment workflow, and client-reported results. It is one comparable project, not a promise that every inherited codebase can follow the same plan.

Read the UrShipper case study

Which draw, dues, or spare problem is costing your volunteers the most right now?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

How it works

Close one expensive risk before opening the next.

Each stage answers a buyer question and leaves behind a decision you can inspect. The next stage only opens when the expensive uncertainty in the current one is small enough to accept.

  1. 01
    Understand

    Trace the real workflow

    Where is the cost or failure actually coming from?

    Follow one member and one league from start to finish: a renewal paid, a draw published, a spare found on a Thursday afternoon. Include the workarounds, the email chains, the duplicate lists, and the handovers that a tidy process diagram usually misses.

    Decision produced

    A map of the workflow, exceptions, owners, systems, and the baseline cost or delay worth changing.

    Risk closed

    Paying to automate the visible symptom while the expensive constraint remains.
  2. 02
    Shape

    Choose the first useful release

    What needs to exist together for one useful result to work?

    Choose the shape from the way the work happens, not from a preferred technology. Name the leagues and their formats, the sheets, the dues and fee rules, who can access what, the exceptions, and the result the first release must complete.

    Decision produced

    The right mix of web, mobile, desktop, browser extension, connected device, or behind-the-scenes connection work, with the first-release boundary and a clear definition of done.

    Risk closed

    A small-looking feature list that quietly depends on several interfaces, systems, and owners.
  3. 03
    Prove

    Review working software

    Will it hold up outside a controlled demo?

    Review the product against the agreed workflow, not a tour of finished screens. Register a member into two leagues and check the dues are charged once, run a flight round to its end, and test what happens when two teams ask for the same spare.

    Decision produced

    Working checkpoints tested with realistic data, real user types, system connections, recovery plans, and the people who will use or run the system.

    Risk closed

    Discovering the important gaps during migration or after customers depend on the release.
  4. 04
    Transfer

    Release, measure, and hand over

    Did the new workflow improve the original constraint, and can another capable team operate it?

    Move a controlled set of users or records first. Compare volunteer hours, late draw changes, unfilled spare spots, or another agreed measure with the starting point before adding the next workflow.

    Decision produced

    A controlled release, comparison with the baseline, operating notes, account ownership map, and a recommendation for what should happen next.

    Risk closed

    Measuring development activity instead of the business result, or depending on the original vendor to keep the system running.

What stays out of the black box

These are operating conditions to put in the engagement, not claims to take on faith.

The scope names one complete workflow

The user, the trigger, the decisions, the data, the exceptions, and what 'done' looks like. A screen list is not enough.

Progress is visible in working software

Reviews against the product at agreed checkpoints, while there is still time to act.

A scope change has a price before it has code

A new workflow or system connection shows its effect on cost and timing before anyone approves it.

Ownership exists throughout, not only at handover

Code, cloud, data, and provider access stay visible and under your control from day one.

The work is checkable without being technical

Checkpoints are working software you use yourself, reported in plain language.

Custom software by industry.

Start from your domain. Each area below is a working practice with shipped products behind it.

What it costs

Every project starts at $10K.

The first phase turns the costliest patched workflow into a scoped build with written acceptance criteria.

Starting investment

Starts at $10K

Workflow complexity, systems to connect, data migration, and user roles set the scope. After a 30-minute call, you get a written build, buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.

Build or buy

Buy an existing productBuild custom software
Best fitHandles your draw formats, spare rules, and fee split with reasonable setup, and its pricing makes senseThe way your club runs is itself the advantage
Manual workConfiguration and process changes can remove the constraintRepeated admin work lands on the same volunteers every week
ConnectionsExisting connections work with reasonable setupA critical connection to your other systems cannot be done cleanly any other way
Curling modelThe product already treats sheets, draws, flights, spares, and bonspiels the way your club doesOwn custom software only when your draw formats, spare rules, or dues split justifies build and support

Work with us

Bring one stuck workflow. Leave with a decision.

In a 30-minute call, we will help you decide whether to buy, connect, repair, build, or wait. If custom software is not the sensible next move, that is still a useful answer.

  • One named workflow owner and one complete path for the first phase.
  • Scope, price, what 'done' looks like, and exclusions agreed before paid work starts.
  • Code, cloud, data, and provider access remain under your control.
  • Post-launch warranty cover for defects in the agreed scope.

Frequently asked questions

Straight answers to what buyers ask before they scope. Still stuck? .

It is software that runs the member side of a curling club: registration and renewals, membership dues, league fees, draws and standings, sheet bookings for leagues and bonspiels, spare pools, learn-to-curl sign-ups, and club messages. It is written around curling ideas a general sports tool does not know: sheets, draws, ends, round robins, flights, spares, and bonspiels.

A rink system runs a building: public skate, hockey, figure skating, and ice time sold by the hour. That is the job of our ice rink management page, and this page does not repeat it. Curling club software runs a club that plays on sheets: who is a member, which league plays which draw, which team needs a spare, and which visiting teams are coming for the bonspiel. Some clubs own their ice and need the club side only; clubs on shared arena ice need the club side even more, because their few sheet hours have to be used exactly.

Each sheet booking names what it is for: a league draw, a bonspiel, a learn-to-curl session, practice, or a rental. A league takes its sheets for the season in one pattern, a bonspiel takes every sheet for a weekend, and neither can be sold over the other. When a draw time moves, the booking moves with the league, and members see the change in one place instead of in a new email chain.

You set the format once: the teams, the sheets you have, the draw times, and whether the league runs as a plain round robin, in flights or ladders where teams move up and down after a round, or in two halves with new groups for the second half. The system lays out who plays whom, on which sheet, at which draw, balances early and late draws across teams, and keeps scores and standings with the draw. When a round ends, the flight moves are worked out from the results and the next round is ready for the draw master to check and publish.

Members join the spare pool with the positions they can play and the nights they are free, and they keep that up to date themselves. When a team loses a player, the skip or league organiser sends one request to the spares who fit the position and the night. The first spare to accept takes the spot, the request closes for everyone else, and the team sheet updates. No phone chain, and no two teams promised the same spare on the same night.

A bonspiel is set up as its own event: entry for whole teams, including teams from other clubs, the entry fee, the draw format, and the brackets or pools the weekend will use. Visiting teams register and pay without becoming club members. As results come in, the bracket moves winners on, and the schedule for the next round of games is there for every team to check on a phone instead of crowding around a paper draw sheet.

Learn-to-curl is treated as the front door of the club, not as a rental. Sessions take sign-ups with a set number of places, a waitlist when they fill, and the waiver signed before the session. Afterwards, the same record carries the person into the next step the club offers: a beginners league, a free-agent night, or the spare pool, so a good first night does not end in a lost email address.

They are two different charges and the system keeps them that way. Annual membership dues say a person belongs to the club; a league fee says they play in one league for one season. A member can pay dues once and join two leagues, and the system checks that the same dues are never collected twice. The treasurer can see, for any member, what was dues, what was league fees, what was a bonspiel entry, and what is still owed.

A member registers or renews, signs the waiver, and pays in one flow, as an individual or as a complete team. Dues status updates on its own when payment lands, and the registrar stops chasing renewals by hand each autumn. When a new season starts, the club rolls the roster, leagues, and fee rules forward instead of typing them again, and a new board member taking over finds the records in the system, not in a predecessor's inbox.

Buy an existing product when it handles your draw formats, your spare rules, and your dues and league fee split, and its pricing makes sense for a volunteer-run club. Build custom when the way your club runs is the thing no product will hold, when repeated admin work lands on the same few volunteers every week, or when a critical connection to your other systems cannot be done cleanly any other way. If your league rules are still changing every season, wait and settle them first.

For a small, well-defined task with someone technical managing it, freelancers are often cheaper. The pattern that goes wrong is a non-technical buyer coordinating several freelancers becoming the project manager, the tester, and the person who discovers the pieces do not fit. An agency earns its fee when the work needs coordination across screens, rules, data, and connections: one accountable party, one phase price, and checkpoints against the whole workflow. If your need is one screen or one fix, hire the freelancer.

The first paid phase may cover a bounded audit, a proof of concept, a recovery plan, or a small first release. The final price depends on how many leagues, draw formats, and kinds of booking the system has to hold, how deep the dues and fee rules go, what it needs to connect to, whether member and payment history needs moving over, and the condition of any existing system. The agreed phase is priced in writing before it starts.

Timing depends on scope: a bounded audit or proof of concept is a smaller engagement, while a system covering registration, dues, draws, spares, bonspiels, and several system connections takes longer. The schedule is set once the first workflow and what 'done' looks like are clear, and most clubs aim to have the first release ready before registration opens for a new season.

Yes. Takeover is a common first engagement, and it always starts with an audit: where the code lives, how your data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live. Code that is understandable and fit for the next release stays; only the parts blocking reliability get replaced. And if you already paid another vendor and have nothing working, the audit tells you which story you have before you spend more: the most expensive version is the product that looks finished, clean screens and clicking buttons, while underneath nothing is tested and the important checks run in the browser, where anyone can tamper with them, instead of on the server where they hold.

Security starts with the data, the people, who can see and change what, the systems it connects to, and where it runs. A club system holds member contact details, payment records, and signed waivers, including waivers for younger curlers, so the scope can include access controls for board roles, separate testing and live environments, protected passwords and keys, activity logs, backups, and recovery plans. We write down which protections are included and which evidence your board must provide.

We need one person who owns the workflow, access to the relevant users and systems, timely answers on club rules, and someone who can accept or reject each milestone. A weekly working session is usually enough once the scope is stable, and it can be an evening call that fits around volunteer time. Your board should not have to manage developers day to day. The team that scopes your project is the team that does the work: no handoff to another vendor after you sign, and you can talk to the people doing the work directly.

Ask for the quote to name everyone who will use the system, including your own board. Every platform has two products: what members see, and what your volunteers use all season: setting up draws, handling spare requests, correcting standings, refunding a bonspiel entry, and keeping a record of who changed what. When that second product is quoted as an 'admin panel' on a single line, it becomes the overrun. Our quotes treat your board's screens as their own scope, with their own users. Then the phase names the workflow, what 'done' looks like, the price, and the exclusions, all before paid work starts.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the workflow agreed at the start: register a test member and watch dues and league fees land as separate charges, create a league and check the draw it produces, request a spare and watch the first acceptance close the request. Progress is reported in plain language: what changed, what's next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads. Our job is to make the work checkable; your job is to check it against your club.

You own the code built for you and control where it lives, the cloud accounts, the data, analytics, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over, which matters for a club: the system should survive a change of board, not leave with one volunteer.

Every launch includes post-launch warranty cover for defects in the agreed scope, release support, and small screen corrections. After that, work can continue as another fixed phase or an ongoing product engagement. The code and accounts stay under your control either way.