Ascent Basecamp
The software a mentoring organization runs on. Four kinds of people sign in — mentors, students, chapter leaders, and staff — and each one needs a different system behind the same front door.
Client
Ascent Mentors
Scope
Product Design & Build
Type
Web Application
Status
Live & in use
A spreadsheet that outgrew itself.
Mentor rosters, student assignments, chapter records, meeting logs, approvals. Every one of those lived somewhere different — a sheet, a group text, somebody's inbox. It worked at one chapter and fell apart at ten.
The catch: almost everyone using it is a volunteer. There's no onboarding, no IT desk, no training day. If a mentor can't figure out the screen in front of them, they just don't use it, and the data goes back to being a group text.
Design for the person who didn't choose this software.
Every decision came back to one test — can a busy volunteer do the thing they logged in to do without asking anybody for help?
- No password to forget. Google sign-in, an email link, or a texted code. The most common support ticket in volunteer software, removed entirely.
- Role-aware from the first screen. A mentor sees their students. A chapter leader sees their chapter. Staff see everything. Same URL, four different systems.
- One obvious next action. Each dashboard opens on what's actually due, rather than a menu of everything the software can theoretically do.
- Access is a closed door. Only approved accounts get in, and the sign-in screen says so — the portal handles records about students, so that boundary is stated up front, not implied.
Four roles, one system.
Every screen below is the real thing, captured from the live portal. Names, emails and photos are obscured — the system holds records about minors, and those don't belong on a public site. Everything else is exactly as it ships.
What each role actually sees.
A chapter leader and a student share a login screen and almost nothing else. This is the difference, side by side.
Mentors
Their students, upcoming meetings, and a fast way to log what happened after one. Nothing else competing for attention.
Students
Who their mentor is, when they're meeting next, and what they signed up for. Built to be read on a phone between classes.
Chapter Leaders
Roster health for their chapter — who's matched, who's inactive, which pairings need attention this week.
Staff
Approvals, account management, cross-chapter reporting, and the administrative tools that keep the whole thing running.
Access Control
Permissions checked on the server, not just hidden in the interface. A role can't reach data it shouldn't by guessing a URL.
Phone-Ready
Every view works at phone width, because most mentors are checking in from a parking lot, not a desk.
This is not a contact form with a login.
People hear "portal" and picture a members area. Here's what the organization actually runs through this thing, day to day.
four states
taken
texts sent
completed
That's the 2026–27 season alone, seventeen days in. Every one of the items below started as a spreadsheet, a group text, or somebody's memory. Season to date, 17 August 2026
Matching & Match Day
Runs the biggest logistical day of the organization's year.
Background Checks
Screening status tracked per mentor, because adults work with minors here.
Weekly Check-Ins
Logged in seconds. Leaders see which pairings have gone quiet.
Email, Text & Group Chat
Sent from one screen, to the right audience, with full history.
Seasons & Re-Enrollment
Each cycle rolls over cleanly instead of starting from a blank sheet.
Curriculum & Content
Course material with a built-in player, in the same place as everything else.
Reporting & Exports
Spreadsheets, PDFs, and a map of where students come from — on demand.
Guardrails
Duplicate detection, change history, and a support view of any user's screen.
This is the half most portfolios skip.
A marketing site is judged in five seconds by a stranger. A portal is judged over months by the same people, every week. The second is harder, and it's where a business actually lives.
Basecamp is on this site for that reason — it's proof the same person who builds the front door can build what's behind it.
From portal to pocket.
Basecamp established what the organization needed. The native iOS app — now integrated and in testing — takes the handful of weekly actions and makes them a two-tap job.