Attendees should be able to see contact information for the Lead Instructor. To prevent unwanted GDPR exposure, this should be hidden behind a 'contact' button so that they have to request these details directly. The user should also confirm their intention when accessing this information.

They should will also have access to the lead instructor's emergency contact details, on the day of the booking.

Seems to be only things in DST.

At the moment the calendar resets back to month/today when you go to a booking and come back, it would be great to update history to come back to the last view.

Signed links are invalidated whenever the site is deployed (because a new app key is generated each deploy) so we need a different strategy for responding to invites.

Team Leader can add and delete Tasks.
Tasks have title, notes, (optional) deadline.
Tasks can be ordered (priority).
Tasks can be assigned to any user.
Team members can see all tasks.
Team members can self-assign a task, and self-reassign a task from someone else.
Team members can self-resign from a task.
Team members can "complete" any task.
Tasks can be assigned to many bookings (e.g., for maintenance).

Lead Instructors should be able to see attendee contact information. To prevent unwanted GDPR exposure, this should be hidden behind 'contact' and 'emergency contact' buttons so that they have to request these details directly. The user should also confirm their intention when accessing this information.

Access to 'emergency contact' information is limited to the day of the booking. Other contact information is limited to future/current bookings (not past or cancelled).

I want to share a link to a booking in the Facebook group, that should preview the booking details if someone is not logged in, and give Facebook some basic social media intel.

Add more location information, esp. for apple. E.g.,

$vEvent->setLocation(
    new Location("Infinite Loop\nCupertino CA 95014", 'Infinite Loop')
        ->withGeographicPosition(new GeographicPosition(37.332095, -122.030743))
);

Add relevant Timezone to ics file for current user.

Note: Must include full timezone information!

It would be a useful to see which bookings a user is attending, and their attendance status.

See https://laravel.com/docs/10.x/verification

• Check SEQUENCE or other details match current details.
• Respond with additional REQUEST if they do not.

Change out the "Respond" button for simpler "Yes" / "Maybe" / "No" buttons - hopefully this will increase response.

• Reply to user and ask them to sign in to confirm who they are
  • Record attendance with email address
    • Get email address from attendance for future emails about booking
  • Record additional email address(es) for future replies

User can have many Qualifications. Each qualification can be...

• Girlguiding
  • Climbing, Level 1 or 2
  • Expires
• Mountain Training
  • Award
• Scout Permit, with
  • Activity
    • Climbing and Abseiling
  • Category
    • Artificial Top Rope
    • Natural Top Rope
    • Artificial Lead Climbing
    • Natural Lead Climbing
  • Type
    • Personal
    • Leadership
    • Supervisory
  • Restrictions
  • Expires

Should also show the User as a Permit Holder when they have an in-date Scout Permit.

Team Members can request branded clothing.

• Link to external store or internal tracked database?

Once I have created an account I would like to see a list of available bookings to invite them to.

The team has 4 'climbing office' keys.

• Track who has keys at the moment
• Pass keys from one person to another
• Recipient verifies key exchange

Anyone who "Can't Go" or has not responded to an event should not show contact details.

Allow user or booking manager to edit or delete comments.

• Track who has a necker
• Accreditation? Flag?
• Request a necker?

Allow users to send themselves an email with the booking details. This will be useful if they have deleted the original invitation email, or if they originally could not attend but now can and want to add the event to their calendar by email.

I see this living with the "Add to Calendar" (download ics) button.

Information for the lead instructor, for example access information.

Specify CLASS: PRIVATE on ics events.

The lead instructor should be able to perform a roll call at the event to confirm who has attended. This will allow them to view qualifications and emergency contact details for the correct people.

They may need to update the register throughout a booking if people turn up late(r).

Add a login/dashboard link on the welcome page for people not logged in.

A Team Member should have each of the following. The expiry date should be recorded.

• First Aid
• Safety
• Safeguarding

See https://fly.io/laravel-bytes/invite-only-registration/

• Guests should only be able to see their own attendance, and the Lead Instructor for a booking.
• Guests should not see attendance changes or comments in the recent activity.

Some way of recording that member's kit has been checked each year. Needs an accreditation for 'Kit Checker' who will be able to record kit checks. Will want a batch/mass update for this - possibly based on a booking's attendees?

• Today
• Next booking
• Invites

Send emails to attendees to remind them of upcoming bookings and outstanding invites. Users should be able to configure what emails they get (and disable the default invite emails too). If users have disabled the default invite emails then this should be highlighted on the booking invite list.

• Invitation
• Check that emails are still relevant when processing
• Invitation reminder - x days before
• Maybe reminder - x days before
• Going reminder - x days before

Could also consider including a summary statement at the end of emails. Something like "You have x outstanding invites, please login and review them."

Add X-ALT-DESC;FMTTYPE=text/html: for html description

Link to download ICS for each booking

• Accept by sending out fresh REQUEST emails to all involved
• Decline by sending DECLINECOUNTER to attendee

Sort and group bookings with 'Needs Action' before 'Tentative' responses. This would help to highlight new invitations.

• Green => going
• Blue => invited
• Yellow => maybe
• Grey => cancelled or can't go

• Respond with REQUEST