Allocate view
The allocate view shows the registrations of an offer as cards in columns. Dragging a card into another column decides whether the participant gets a place or waits.
The view exists only for offers with Registration via the website. It is in the Allocate tab of the offer and, as the board, on the page Allocate places.
Admins always see it. Organizers see the Allocate tab if all of the following apply:
- The season allows them Allocate places (What organizers may do themselves).
- They may see the participant list.
- They have confirmed a required organizers’ consent.
People who have only the role Participant list only do not see the view (Roles and permissions).
Columns and cards
The Canoe trip after the lottery, in the Allocate tab of the offer.
| Column | Content |
|---|---|
| Allocated | Registrations with takes part. Above them: how many places are free or how far the offer is overbooked, and whether the minimum is reached. |
| Waiting list | The people waiting, in the order in which they move up. Above them: whether the waiting list is moving up at the moment (Messages). |
| To decide | Registrations that are new. Confirm all and Waitlist all decide all of them at once. |
| Not taking part | Withdrawn and rejected registrations and those without a place, with date and reason (Decision reasons). |
| Element | Meaning |
|---|---|
| Drag and drop | A card gets the status of the column it is dragged into. It lands before the card it is dropped on. |
| Menu of a card | Opens with the right mouse button. It offers the changes the card's status allows, and the comments on the registration. |
| Collection bar | Only in the Allocate tab: how many decisions on this offer are collected (Collection bar) |
When dragging:
- In the waiting list, the order decides who moves up first.
- Moving a card makes nobody move up automatically.
- fepli does not ask about a friend registration when you drag.
Above the Waiting list it says whether the list is moving up and, if not, why. If the reason lies with the season, for example a lottery phase or the switch Waiting list moves up automatically turned off, the link Go to the season setting leads there. Everyone who may edit the season sees it.
The menu of a card offers Confirm, Put on the waiting list and Withdraw, in the mode Collect first also Not fulfilled. On the Allocate places page, the column Not taking part is folded in.
Mode
Under Decisions you choose whether a decision is collected first or applies at once. The choice applies on the Allocate places page and in the Allocate tab of every offer, until you sign out. The default is Collect first.
- Effect
- Change ends up in the batch
- For
- reworking a lottery, many corrections
- Effect
- Change applies immediately, with an email
- For
- single late registrations, when the family is to know right away
In the mode Collect first, there is neither an email nor a payment obligation until you commit. The payment obligation is the amount a family owes for a registration. In the mode Notify right away, a confirmation creates the payment obligation at once, and the family receives an email at once.
Collection bar
In the Allocate tab of an offer, the collection bar shows how many decisions on this offer are in the batch. Send & notify opens the message to the families concerned. With sending, fepli commits the collected decisions of this one offer. The allocation phase keeps running. On the Allocate places page, the collection bar covers the whole season.
Card
| Element | Meaning |
|---|---|
| Name, comments | If the registration has comments, their number stands next to the name. It opens the comments in the side panel. |
| Details | Age, postcode and friend code. In the Waiting list the card says how many registrations the participant has, otherwise when they registered. |
| Hints in orange | The postcode is missing or lies outside the Preferred postal codes and places, or the participant's own address has a different postcode. |
| “not notified yet” | The decision is in the batch. The card has the colour of its new status. Only in the Allocate tab of an offer. |
| “W{number}” | The choice the participant gave the offer. Only if the registration phase limits Maximum registrations per participant. |
| Warning triangle | At the same time, the participant has a place or an open registration in another offer of the season. |
| “Consent outstanding” | The registration was created with open consents. The icon next to it sends the family the link for them (Send the link to the family). |
On the postcode: for priority, the address in the participant account counts. If a participant has an own address with a different postcode, the card shows “Own address: postcode {postal code}”. For registrations with withdrawn, rejected or no place, this hint is missing.
On the warning triangle: other dates of the same offer do not count as an overlap. Cancelled offers and registrations with withdrawn, rejected or no place do not count either.
Friend registration
With a friend code, participants register together. They all get a place or none (Friend code). Those who hold the same code stand in one shared box in every column except Not taking part, at the position of the first of them. If only one participant holds the code, there is no box.
| Element | Meaning |
|---|---|
| Head | Registering with a friend, the code and how many registered together |
| “Parted — …” | Not all of the code are in this column. The box has a red outline and names the status of the others. |
| “Needs {count} places · {count} free” | In To decide: the group needs more places than are free. |
| Confirm all {count}, Put all {count} on the waiting list | In To decide. Confirm all {count} is missing if the places are not enough. If the others are already allocated, it reads Confirm {first names} too. |
| Bring in {first names} | In Allocated: confirms the participants of the code who are still new. |
If you confirm one participant on their own or put them on the waiting list while others of the code still have the same status, a follow-up question appears. It asks whether all of the code get the new status or only this participant.
Dates of a registration
If a participant has registered for several dates of the same offer, the card says “For {count} of {count} dates”. It also says “· wants all” or “· one is enough”. The family chooses this when registering for the second date.
| Hint | When | Action |
|---|---|---|
| “Got date {number}. One is enough.” | Another date is allocated. This registration is neither allocated nor withdrawn. | Withdraw here |
| “Wants all dates — {count} of {count} confirmed.” | This registration is allocated, other dates are not. | Confirm everywhere confirms the remaining dates. If a date is full, there is no action. |
| “Wants all. Date {number} already confirmed.” | This registration is new, another date is allocated. | Confirm here too |
“Increase places” dialog
With Increase number of places, an offer gets more places, and the waiting list can move up at once. Everyone who may edit the offer may do this.
The three settings under the maximum appear only for an offer with a waiting list.
| Element | Meaning |
|---|---|
| Increase number of places | In the More actions menu of an offer with registration via the website |
| Field | Meaning | Default |
|---|---|---|
| New maximum number of participants | The new number of places | previous number + 1 |
| Move up automatically | People on the waiting list move up into the free places. | on |
| Commit registration status | Moving up applies at once, and the payment obligation arises. When turned off, it goes into the batch. | on |
| Notify participant | Whoever moves up receives the email “Moved up from the waiting list to the participant list”. | on |
| Element | Meaning |
|---|---|
| Follow-up question “Fill up from the waiting list?” | Appears when someone raises the maximum in the offer form and saves. Fill up participant list lets the people waiting move up. |
| Condition of the follow-up question | There are free places and a waiting list, and the offer is not over yet. |
Move up automatically works regardless of the phase and of the season's switch Waiting list moves up automatically. It does not work for cancelled offers, nor once the first date has begun.
Messages
| Message | Meaning |
|---|---|
| “Moves up as soon as a place becomes free.” | The waiting list moves up by itself. |
| “Not moving up at the moment: {reason}” | The waiting list is not moving up at the moment. The reason names the situation (Moving up). |
| “{count} places stay free, nobody moves up automatically: {reason}” | Places are free, but nobody moves up. If the reason lies with the season, Go to the season setting leads there. |
| “{first name} is registered only together with {first names}.” | Follow-up question when you decide about one participant of a friend registration on their own (Friend registration). |
| “Places have become free. Should the waiting list move up?” | The maximum has been raised, and there is a waiting list. |