Skip to main content
Back to BlogDelivery

Building FishPal: the project, the challenges and how we deliver it

Brandon HexNovember 16, 202610 min read

Background

Recreational and competitive angling in South Africa is organised in layers. SASACC sits at the top, followed by the federations, the angling regions and the clubs that anglers join. Each layer has its own committee, and each plays a part in deciding who is a member and on what terms.

For many years these records were kept on paper and in spreadsheets, with each club following its own conventions. Treasurers matched payments by hand, an angler who moved clubs started again with a new record, and marshals at competitions had no reliable way to confirm that an angler was paid up. FishPal was created to replace that with one register for the whole sport.

Introduction

This article describes FishPal from our side. It covers how we work with the FishPal team, the technical challenges the system has presented, the work we have done to make it fast, and how we deliver and support it. Our case study describes what FishPal does for its users; this is the account of how it is built and run.

Our relationship with FishPal

We have worked on FishPal since July 2025 and are responsible for all of it: design, development, testing, releases, hosting and support. The FishPal team are the experts in angling administration. Our role is to turn their knowledge of how the sport is run into a system that applies those rules the same way at every level.

The relationship works because responsibilities are clear. The FishPal team decide how the sport's rules should work, and we make sure the system follows them. When a question can only be answered by them, we put it to them in writing, they rule on it, and we record the ruling so that it is applied consistently and never has to be asked again. Every change we make is checked and accepted by the FishPal team before it is considered finished.

The project

FishPal holds the record of every member, from the national body to the individual club, and handles everything that depends on that record: joining or transferring between clubs, paying season fees, holding a valid member card, entering events and committee administration at every level.

It serves four groups of people. Anglers use it mostly from a phone, to join, pay and show their card. Guardians manage memberships for family members who do not have their own login. Committee members at club, region, federation and national level approve members, review payments and set season fees. Marshals at events scan a member's card to confirm it is valid, without needing a login at all.

Technical challenges

FishPal looks simple from the outside, but the rules underneath it are not. Most of the difficult work has been in making those rules exact and making them hold in every part of the system.

Taking on federation data

The first major challenge was bringing the existing records into the system. Federations submit their member rolls each season in their own spreadsheet formats, so the import had to be repeatable, not a one-off migration. We built an import that never guesses: any row that cannot be matched with certainty is set aside with a reason and a note of the cell to correct, and the federation corrects it at the source. The import brought 21,504 anglers and 595 clubs into one register. The case study describes this work in more detail.

Roles and permissions

The most complex part of FishPal is deciding who may do what. Every committee at every level has the same 13 positions, from president and treasurer to registration officer and coach, taken directly from SASACC's own description of each position's duties. A person's role is the combination of their position and their level, so a club treasurer and a federation treasurer hold the same position with very different reach.

We built a custom permission system around that structure. It defines 74 permissions, each stating the levels at which it can apply. On top of that sits a matrix that sets which positions may use each permission at each level. The matrix is managed inside FishPal by SASACC's president, not by us, so the sport can change its own rules without waiting for a release, and every change to it is recorded.

What a person may do is only half of the question. The other half is which records they may do it to. A club committee sees its own club, a region sees the clubs in its region, a federation sees its clubs and SASACC sees everything, and this is applied in the database itself. Committee powers also depend on the holder's own membership being paid up for the season.

Guardians and marshals add further cases. A guardian who acts for a family member works in a session limited to that person, and cannot use committee powers while doing so. Marshals verify a card without signing in, and see only what is needed at the gate.

Because a single gap in a system like this would undermine all of it, coverage is checked automatically. Every committee action in the system must declare the permission it requires, and the build fails if any action does not. Where the system cannot confirm a permission, it refuses the action.

Seasons, fees and payments

Almost every rule in FishPal depends on the season, including what a member owes and whether their card is valid. We replaced scattered date calculations with one record of the season that the whole system relies on, and built the financial rules on top of it: instalments, fees carried from one season to the next, and write-offs that need approval up the hierarchy. Card payments are confirmed with the payment provider before they are accepted. The case study covers these rules in full.

Restructuring a core concept at short notice

During 2026 FishPal needed to restructure one of the core concepts that the whole system is organised around. The change reached into permissions, reporting, imports and almost every screen, and it was critical that it was in place quickly. Our team put in the extra hours and delivered around a week's worth of changes in two days, planned, checked and accepted by the FishPal team in the same way as any other work.

Optimisation

FishPal has to stay fast as the register grows and as the busiest moments of the season arrive, so we test it well beyond its current size. We built a test environment holding around 193,000 members, by running the real import repeatedly, and measured the system under load against a target of 3,000 people using it at once.

That work found and fixed real problems. Member search on the large dataset fell from 1.8 seconds to 0.2 seconds, after we found that the search was written in a way that bypassed the indexes built for it. Loading a member's payment history fell from almost 28 seconds to a fiftieth of a second. A later review reduced the clubs list from 304 to 40 milliseconds, cut the number of repeated background requests the screens were making, and compressed the data sent to phones.

We apply the same attention to running costs. A review of the hosting identified savings of around a quarter of the monthly cost, and we have applied the first of them. We also moved our automated checks from a paid hosted service to a quick run on the engineer's own machine before any change is shared, which gave faster answers and removed a cost that had been growing every month.

How we deliver

All FishPal work runs through a ticket board. The FishPal team raise requests and faults directly, in their own words, often as notes made while walking through the system. Each ticket moves through the same stages: to do, in progress, test and done. When we finish a change, it moves to test, not to done. The FishPal team check it and close it themselves.

We do not work in fixed sprints. The work varies from a wording change to a new payment flow, and a fixed cycle would make small fixes wait for no reason. We take the most important ticket next and release each change as soon as it is ready and checked. In 2026 the system has been released 350 times. Larger pieces of work are planned in writing first and delivered as complete slices, with the screens and the rules behind them released together.

Every fix comes with proof the FishPal team can see: what caused the problem, what we changed and how we checked it, with a screenshot of the corrected screen. For new screens we use design walks. The FishPal team take us through the system, we propose designs, agree each screen with them one at a time and build it. The FishPal team asked for this to become our standard way of working, and it now is.

Support

Support follows the same route as development. Faults and questions are raised as tickets, and each one is answered with the cause, the fix and the proof. Across the faults closed so far, the median time from a report to the FishPal team confirming the fix is under two days, and that includes their own check.

When speed matters, we respond accordingly. One evening in September the FishPal team reported 19 issues after reviewing the system and asked for them to be dealt with overnight. By the next morning 17 were resolved, each with its explanation and screenshot ready for them to check.

Support also covers the data. Federations send updated rolls through the season, and we run each import through the same checks as the first, returning the rows that need correcting. The system is monitored, with a health check and alerts on the parts that matter most, so that problems can be found before members report them.

Achievements

There is a good deal in this project that we are proud of:

  • One register for the sport, holding 21,504 anglers and 595 clubs, brought in through an import that never guesses.
  • A permission system that follows SASACC's own rules for 13 positions at four levels, which the sport manages itself, with every committee action checked automatically.
  • A system tested at around nine times its current size, with key screens made many times faster.
  • Thousands of automated tests that run before every change is shared.
  • 350 releases in 2026, made in small steps, with every change checked by the FishPal team before it is closed.
  • A week's worth of changes to a core concept delivered in two days when it was needed.
  • A way of working, the design walk, that the FishPal team asked us to make standard.

What we have learned

A passing test result is a claim, not proof. We confirm what a check actually did before relying on it.

Test as the user, through the screens. Signing in as the person a flow has just created finds problems that tests of the flow itself do not.

Rules belong in the system, not in notes. A written warning did not stop a fault returning; a test that fails when the rule is broken did.

Decide before building. Agreeing a design with the client on paper is much quicker than changing a finished screen.

Put the proof where the client looks. A screenshot and a short explanation on the ticket let a client who is not technical sign off with confidence.

Working with us

The way we deliver FishPal is the way we deliver every Labs project: clear responsibilities, small releases, careful checks, visible proof and a client who accepts each change. If you have a system to build, or one that needs to move faster, we would be glad to hear about it.