Online course registration spreadsheet template. Free, and ready to become an app.

One workbook for a school, a training program or a community class schedule: a course catalog with each course's instructor, dates, capacity and whether it is Open or Full, a student list with major and year, the instructors and their departments, a registration log that ties a student to a course, the wording of the messages you send, a report log and a small dashboard. Download it free. When students should sign up themselves, a full course should start a waitlist and each instructor should see only their own roster, describe that structure to Tadabase AI and it builds the registration app.

Excel · Google Sheets · Numbers · 7 sheets

Rather have it as an app? Describe it — we’ll build it now.

Same structure as the spreadsheet, plus logins, roles and workflows. Free to start.

Plain English. It asks follow-up questions like a real developer.

7 sheets, already linked by ID.

Each sheet is one kind of record. The ID columns are how the sheets point at each other, and they are the same links the app version turns into real relationships.

  • Courses

    The class catalog: each course with its instructor (by ID), start and end dates, capacity, the number of students enrolled and a status (Open or Full).

    Course ID · Course Name · Instructor ID · Start Date · End Date · Capacity · Enrolled Students · Status

  • Students

    Every student with their email, phone, major, year (Freshman, Sophomore, Junior or Senior) and a count of the courses they are enrolled in.

    Student ID · Name · Email · Phone · Major · Year · Total Enrollments

  • Instructors

    Who teaches: name, email, phone, department and the number of courses each instructor teaches.

    Instructor ID · Name · Email · Phone · Department · Courses Taught

  • Registrations

    The enrollment log: one row per sign-up with the student, the course, the registration date and a status (Enrolled or Rejected).

    Registration ID · Student ID · Course ID · Registration Date · Status

  • Messages

    The wording of the messages you send, such as "You have successfully enrolled in the course" and "This course is currently full", with what should trigger each one.

    Message ID · Type · Triggered By · Message Content

  • Reports

    A record of the summaries you produce, such as enrollments per course or a course capacity report, with who produced each one and when.

    Report ID · Type · Generated By · Generated On · Details

  • Dashboard

    Three headline numbers: total students, courses open for enrollment and full courses, each with a one-line description.

    Metric · Value · Description

Fine for one person. Hard for a team.

Where the spreadsheet starts to cost you time once more people depend on it.

  • Nothing is counted, so a course can overfill

    The file has no formulas. Enrolled Students on the Courses sheet, Total Enrollments on the Students sheet and Courses Taught on the Instructors sheet are typed numbers, and so are the Dashboard's 500 students, 15 open courses and 5 full courses (the sample has two rows on each sheet). A new registration changes none of them, so nothing stops a 31st student being added to a course with a capacity of 30, and Open only becomes Full when someone remembers to change it.

  • No waitlist, and no way to drop a course

    A registration is either Enrolled or Rejected, and that dropdown covers only the two sample rows: rows you add below accept any text. There is no Waitlisted or Dropped value, so a student turned away from a full course is simply lost, and a seat that opens up is offered to nobody. A registration points to its student and its course by typed IDs, so one mistyped ID is a sign-up nobody can trace.

  • Students cannot sign up, and nobody is told

    A registration reaches the sheet only when someone in the office types it in from a paper form or an email. The Messages sheet holds the wording of the confirmation and of the course-full notice; the file itself sends nothing. And sharing the file shares every student's email and phone with everyone who opens it, so an instructor cannot be given only their own roster.

Same structure, with logins and automations.

Start from a real prompt, change anything that doesn’t fit, then build it.

Starting from Course registration app

Plain English. It asks follow-up questions like a real developer.

Opens the builder with your prompt. Free for 14 days, no card needed.

Questions about this template.

Is the spreadsheet template really free?

Yes. It is a normal .xlsx file that opens in Excel, Google Sheets or Numbers. No sign-up is needed to download it.

Does it work as a class sign-up sheet in Google Sheets?

Yes. Upload the .xlsx to Google Drive and open it with Google Sheets, or use File, then Import, in a blank sheet. Every sheet comes across with its columns and sample rows. The Courses and Registrations sheets together are the class catalog and the sign-up list.

Can students register for courses themselves?

Not in the spreadsheet: someone has to type each registration in. In the app, yes: the AI sets up a student role that can browse open courses, register and see only their own registrations, and an instructor role that sees only the rosters of their own courses. That rule is enforced on the server for every record, not by hiding rows.

Does the spreadsheet stop a course from going over capacity?

No. Capacity and Enrolled Students are two typed numbers, and nothing compares them. In the app, the enrolled count is calculated from the registrations, and a workflow marks the course full and waitlists later sign-ups when the count reaches capacity.

How is this different from the student grades and attendance template?

That template starts after enrollment: a grade for each class and term, and a daily attendance log. This one is about getting students into courses: the catalog, capacity, registrations and the messages around them.

Can I bring the data I already have in the spreadsheet?

Yes. Once the app is built, import each sheet into the matching table from a CSV or Excel file. The importer maps your columns to the fields and shows any row it could not bring in, and why.

When should I move from the spreadsheet to an app?

When more than one person edits it, when someone outside your team needs to see part of it, or when you start copying rows between tabs by hand. Those are the points where a spreadsheet starts losing data quietly.

Keep the structure. Lose the copy-paste.

Describe the app the spreadsheet was trying to be. Tadabase AI builds it with real logins, roles and workflows, and you can try it free for 14 days.

Plain English. It asks follow-up questions like a real developer.

  • 14-day free trial, no card
  • Unlimited app users
  • Live on your own domain