Summit Fitness Club — Detailed Review Guide (first-time reviewer)

Canonical short reference: 03-summitfit.md · Freeze date: 00-snapshot.md · Live pitch script (different audience, skip if you're just reviewing): ../scripts/summitfit-demo-script.md

1. What you're about to do

You are going to log into a demo version of MemberVu, a piece of software, using a pretend gym called Summit Fitness Club. You will click through a handful of screens and compare what you see on screen against a list of "expected" values written in this guide. For each item you write PASS if it matches, or FAIL if it doesn't. You are not testing your own gym knowledge — you are just checking that the software shows the numbers it's supposed to show. You will not need to fix anything, install anything, or write any code.

2. What is MemberVu, and what is Summit Fitness?

MemberVu is a web application (you use it in a browser, like Gmail or Facebook) that helps membership-based organizations — clubs, associations, gyms, alumni groups, homeowner associations — manage three things: who their members are, the events they run, and the money members pay (dues, event tickets).

MemberVu is multi-tenant, which means one piece of software serves many different organizations, and each organization ("tenant") gets its own private, branded copy of the app with its own members, events, and money records. Nobody from one organization can see another organization's data.

Summit Fitness Club is one of five pretend demo organizations set up inside MemberVu to show off what the software can do. It's a fitness/wellness club — think of a real gym with a front desk, monthly membership fees, and the occasional group fitness event like a bootcamp. In this app, Summit Fitness is set up to demonstrate a monthly billing business model — most other demo clubs bill once a year, but Summit Fitness bills every month, like a real gym membership.

3. Words you'll see (plain-language glossary)

4. The rules of this review

• Every check in this guide is PASS or FAIL only. There's no partial credit and no "looks close enough."
• Never try to fix anything you find wrong. Your job is only to observe and record. If something looks broken, write down what you saw (and ideally a screenshot) and mark it FAIL.
• Don't retry a failed login. The environment shares a login attempt limit across everyone using it right now. If a login fails, stop and re-check your typing carefully rather than mashing the button — repeated failed attempts can lock everyone out for 15 minutes.
• All money in this app is shown to you in pesos (₱). Behind the scenes the computer stores money in centavos (hundredths of a peso), but you will only ever look at the ₱ figure on screen — always double check the ₱ symbol and the number match what's expected.
• Data ages as time passes. This snapshot was frozen at a specific date (see 00-snapshot.md). If you're reviewing this more than about a month after that freeze date, two members who were designed to show as "expiring soon" will now show as "expired" instead — this is expected aging, not a defect.

5. Step 1 — Open the demo and sign in

1. Open your web browser (Chrome, Firefox, Safari — any modern browser works).
2. In the address bar, type this exact address and press Enter: http://summitfit.membervu.local:8090 (if you were given a cloud link instead, it will look like https://summitfit.demo.membervu.com — use whichever one you were told to use).
3. You should land on a login screen with Summit Fitness Club's branding (an orange color scheme).
4. Click into the email field and type: admin@summitfit.demo
5. Click into the password field and type: Demo123! (this password is the same for every account in every demo tenant — capital D, an exclamation point at the end).
6. Click the Log In (or Sign In) button.
7. What you should see: you land on an admin dashboard — a screen with a sidebar or top menu showing sections like "Members," "Events," "Billing," and similar. If instead you see an error message or you're bounced back to the login screen, that is a FAIL — write down the exact error text.

6. Step 2 — Check the membership tiers

A "membership tier" is just the plan a member signed up for — like "Basic" vs "Premium" at a real gym. Summit Fitness has three tiers.

1. In the sidebar/menu, find and click Admin (if you're not already in the admin area), then click Membership Types (it might also be labeled "Membership Tiers" or "Plans").
2. You should see a list or table of tiers with names and prices.

Expected:

1. Look for any indicator of the billing period (a word like "Monthly" next to the price, or a column header). If you don't see it directly on this screen, check Admin → Settings → Dues Settings — it may show the billing frequency there instead.
2. PASS if all three tiers and amounts match the table above. FAIL if any tier is missing, misnamed, or shows a different amount.
3. If you cannot find the word "Monthly" anywhere in the interface at all, do not mark this a FAIL on its own — note it as "billing period not visible in UI, verified by amount pattern only" and move on. This has been separately confirmed by the team that built this demo.

7. Step 3 — Check the members list (find the lapsed member)

This step is the heart of the Summit Fitness story: a real gym's biggest challenge is catching people whose memberships are about to lapse (or have already lapsed) before they quietly walk away for good. We want to confirm the software can actually show you who's expired.

1. Click Members in the sidebar/menu (this may be directly under "Admin" or its own top-level item).
2. You'll see a list of people with columns like name, email, tier, and a status badge (a small colored label like "Active," "Expiring Soon," or "Expired").

Expected:

1. Specifically look for that 1 expired member. This person represents the "member about to be lost" scenario — the whole point of this tenant's demo story is showing how a gym staff member would spot this person and try to win them back (remind them, help them pay, reactivate their membership). Make sure you can actually locate and open this member's profile.
2. PASS if you can see roughly 9-10 members total with the status spread above (or the aged version described in the rules above, if you're reviewing well after the freeze date) and you can find the 1 expired member. FAIL if the expired member isn't visible at all, or if the counts are wildly different (e.g., everyone shows as active).

8. Step 4 — Check the past event

1. Click Events in the sidebar/menu.
2. Look for an event called "Summer Shred Bootcamp" — it should be marked as already happened (look for a status like "Completed" or "Past").
3. Click into the event to open its details page.

Expected:

1. Look specifically for a check-in count or attendee list showing 6 people checked in. This confirms the app can track who actually showed up, not just who registered.
2. PASS if the event exists, is marked Completed, shows ₱500 as the ticket price, and shows 6 check-ins. FAIL if the event is missing, shows a different status, or the numbers don't match.

9. Step 5 — Check the paid monthly-dues invoice

An "invoice" here is just a bill for dues. We're going to confirm one specific bill exists and was actually paid.

1. Click Billing in the sidebar/menu, then click Invoices.
2. Look for an invoice titled something like "January Dues — Family".
3. Its status column should show Paid (not "Pending," "Overdue," or "Draft").
4. Click into the invoice to open it.

Expected:

1. On the invoice detail screen, look for a linked payment record — it should show the same ₱2,500 amount and a payment method or channel labeled "Simulated". Remember from the glossary: "Simulated" is expected here because real payment gateways are turned off in this demo — it is not an error.
2. PASS if the invoice exists, shows ₱2,500, is marked Paid, and has a matching ₱2,500 "Simulated" payment attached. FAIL if the invoice is missing, the amount is wrong, the status isn't Paid, or there's no payment attached.

10. Things that look wrong but are correct

11. Finishing — record your verdict

Once you've gone through Steps 1-5, record every PASS/FAIL you noted in the shared tracker: tester-files/04_TRACKERS/DEMO_REVIEW_TRACKER.md. For each row, note the step name and your PASS or FAIL.

• If every step passed: mark this tenant GO (ready to demo/show to others).
• If any step failed: mark this tenant NO-GO and describe exactly what you saw (screen name, what was expected, what actually appeared, and a screenshot if possible) so the team can look into it. Remember — do not attempt to fix it yourself.

12. Quick reference card