Skip to main content
GullySystem
Non-profit

Online Booking Portal for Alumni associations

Let customers request or reserve an available service through a website.

Bookings and Appointments

Does this function belong in your operation?

Use when customers should make service or resource bookings online.

A customer chooses to book without contacting the office.

Members register for a reunion dinner, pick a table by batch and pay on one page. Guest names are added. Organisers see the seat count and meal choices.

Bring the records the workflow depends on.

  • Bookable services
  • Availability rules
  • Required customer details

Outputs to check

  • Customer booking request
  • Confirmed or pending reservation
  • Change and cancellation history

Follow the online booking portal workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Present the offer

    Show bookable services, conditions and available times.

  2. 2. Collect the request

    Validate customer details and chosen service requirements.

  3. 3. Recheck capacity

    Confirm that the slot remains available before committing it.

  4. 4. Apply confirmation rules

    Complete required approval or payment handoffs and distinguish pending from confirmed.

  5. 5. Manage later changes

    Record cancellation, rescheduling and any separate refund decision.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

The customer

Selects a service, submits the required details and checks whether the request is pending or confirmed.

Receptionist or advisor

Works one list and not three, and confirms with a message from your number.

Owner

Compares online and staff-entered bookings and investigates cancellations or incomplete requests.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Payment succeeds but booking fails

Keep both references and route the case for reservation recovery or authorised refund.

Last slot taken concurrently

Recheck capacity before confirmation and show the customer a clear outcome.

Customer cancels

Apply the booking policy and send any refund decision to the payment process.

Can this work independently?

The portal needs a source of availability and booking rules. A local calendar can provide it, but staff scheduling, payments and messages require defined connections. Taking an online payment and confirming a reservation are separate events that must be reconciled if either fails.

Systems and records it connects with

  • Appointment scheduling: Confirmed slots, cancellations and attendance outcomes.
  • Job cards: Service findings, approved work, parts and completion records.
  • Customer records: Permitted customer identifiers and service-contact details.
  • Payment gateway: Authorised payment attempts, outcomes and settlement references.

Configure, test and introduce the workflow.

  • We list what you offer and when staff are free. You supply photographs, the map and the opening hours. A draft page returns for your comments.
  • Questions for each service are agreed, such as vehicle number or breed. You tell us what staff must know. Keep it short. The page is tied to the calendar your counter uses. A test booking shows slots closing when taken. We check it together.
  • Confirmation wording is written. A payment gateway account is connected if you want deposits, and trial payments use its test setting. The link goes on your signboard, visiting card and messages. Staff practise confirming requests. Then customers arrive.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Customers cannot reserve unavailable capacity.
  • Required details are validated.
  • A request is distinguishable from a confirmed booking.
Alumni associations

How the business operates.

Alumni work starts with a list that is always out of date. Graduates change email, employer and city every few years, while batch representatives keep their own sheets and the association office keeps another copy that nobody trusts. Which one is right?

Graduate directory and batches

Keep one record per graduate with programme, batch year, department, employer and city. Old contact details are retained when a new address replaces them.

Life and annual membership

Set membership classes with their own fee and renewal date. Lapsed members surface in a list the office can work through before the next general meeting.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Graduate directory and batches. One record per graduate with programme, batch year, department, employer, city and contact history. Changes are logged so an earlier address is never lost.
  • Membership classes and dues. Define life, annual, student and corporate classes with their own fee and renewal date. A lapsed list shows who has not renewed since the last meeting. Concessions are set per class.
  • Receipts and named funds. Receipt each gift against a scholarship, hall appeal or library fund. The donor’s stated wish and any pledge schedule stay attached to the receipt.
  • Reunion registration and attendance. A page for each reunion takes registrations, guests, dietary needs and contributions. On the day, a check-in list marks who actually arrived.

Operational bottlenecks to check

The directory lives in separate copies

Batch representatives hold their own sheets of names and numbers, and the office holds another. A graduate who updates one copy stays out of date in the rest. Nobody knows which sheet to trust.

Life and annual dues are mixed together

Life members never renew, annual members lapse each year, and a few graduates have paid for a batch gift without joining at all. One ledger line cannot show which is which.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Directory

    Graduates are loaded by batch and programme from registrar lists and representatives’ sheets. Duplicates are merged and each person is placed in a chapter.

  2. 2. Membership

    A graduate joins as a life or annual member and pays. A receipt is recorded, and an annual member’s renewal date is set.

  3. 3. Outreach

    Pick a batch, a chapter or a programme, and the dues notice, newsletter or reunion call reaches only those graduates, through whichever channel they actually answer.

  4. 4. Reunion and events

    A registration page opens for each event. Graduates add guests and pay a contribution, and the committee reads the attendee list and costs.

  5. 5. Gifts and awards

    Gifts are receipted against a named fund. Applicants go before the scholarship committee for a vote, and the amount paid is then booked to the fund it came from.

  6. 6. Reporting to the committee

    Dues, chapter statements and event accounts are ready for the treasurer and secretary to read before each general meeting.

Industry reports to connect with

  • Members by class, batch and chapter, with renewal dates
  • Lapsed and unpaid dues by batch
  • Gifts by named fund, with donor wishes
  • Chapter statements against bank deposits

Questions before implementation.

When should alumni associations consider online booking portal?

Use when customers should make service or resource bookings online. A customer chooses to book without contacting the office.

What should we bring to the requirements discussion?

Bring anonymised examples of Bookable services; Availability rules; Required customer details. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Let customers request or reserve an available service through a website. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Online payment, immediate confirmation and external calendar connections require explicit scope decisions.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Customers cannot reserve unavailable capacity. Use this check when reviewing the first working version.

Talk to us

Discuss online booking portal for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements