Selected work

An operational dashboard for a membership organization

Member details, applications, events, and payments were spread across lists, the website, and payment records, and people checked them by hand. This dashboard puts those records on one screen.

The problem

The organization keeps member profiles, applications, events, and event registrations on its website, and it also keeps lists. Payments for events sit in a separate payment record. Staff and volunteers had to pull information out of those places and check it by hand. The repeated lookups and the manual checking are what this screen is for.

What was built

I built an operational dashboard with Next.js and TypeScript. It is connected to Webflow so it can show member profiles, applications, events, and event registrations. People can search, filter, move through the records page by page, and export a CSV file.

The dashboard reconciles Stripe payments for each event. It also shows a summary for members and a summary for events. It does not decide what those records mean. A person still checks them.

How it works day to day

Someone signs in and opens the pages their role allows. They search or filter for a member, an application, or an event, and they read the summary and the registrations. Where the role includes financial data, they can see the Stripe payments for that event and check them against the event. If they need the rows somewhere else, they export a CSV file.

The screen is there so people spend less time moving between lists, the website, and payment records. It saves them time on repetitive lookups and manual checking. That is a description of the work it removes, not a measured outcome and not a guarantee.

Who uses it, and who can see what

It helps staff, volunteers, and anyone who needs to pull information out of lists or the website and check the data.

Sign-in is role-based. A person can sign in with Google, or with email and a password. The dashboard can send an invitation, and it can help someone recover a password. Permissions control which pages each role can open, and which roles can see financial data.

What a similar project could look like

Another small organization could use a screen of this kind when its records live on a website and in lists, and when payments need to be checked against each event. The same shape would show the records they already keep, offer search, filters, page-by-page browsing, and a CSV export, and use sign-in so each role sees only the pages and financial data it should see.

Whether that fits depends on the records and on who must check them. This page describes what this dashboard does. It is not a promise about another organization. Other examples on the homepage are shown the same way, without names. A general note on dashboards is on the blog.