Jump to content

Power List Features: Difference between revisions

From EventR Wiki
No edit summary
Zains (talk | contribs)
No edit summary
 
(16 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Infobox Feature
| name = Power List
| version = [[Release 3.4.1|3.4.1]]
| tier = Premium and Enterprise
}}
Power lists are a check list you can present to members of you team. At the simplest they can can be used to tick off a list of tasks that have been done. Power list can also be dated with a "Due by" date to let your team know when to complete theirs tasks by. However they can do much more for your event.
Power lists are a check list you can present to members of you team. At the simplest they can can be used to tick off a list of tasks that have been done. Power list can also be dated with a "Due by" date to let your team know when to complete theirs tasks by. However they can do much more for your event.


This page covers some of the potential use cases along with how they can be practically achieved.
This page covers some of the potential use cases along with how they can be practically achieved.


=== View the status of your tasks ===
== Applying Costs via Power Lists ==
You can also view the current status of your Power List and its tasks on the ECH with the [[Power List View Status|Power List]] feature.
 
=== '''Applying Costs via Power Lists''' ===
Power Lists can include costs assigned to individual tasks, for example: “Buy an Event Banner” — £40.
Power Lists can include costs assigned to individual tasks, for example: “Buy an Event Banner” — £40.


Costs can only be added or managed through the ECH (Event Coordinator Hub). Once a team marks a costed task as completed within the app, administrators in the Coordinator Hub will be able to view the associated cost that has been incurred.
Costs can only be added or managed through the ECH (Event Coordinator Hub). Once a team marks a costed task as completed within the app, administrators in the Coordinator Hub will be able to view the associated cost that has been incurred. All costs go into the EventR Itinerary [[EventR Costing Model|Cost Model]].


<u>Example: Creating a meal allowance within your Power List</u>
[[Category:Feature]]
[[Category:Feature]]


[[Category:ECH]]
[[Category:ECH]]
[[Category:3.4.1]]
{| style="width:100%; margin:auto;"
|-
| style="width:60%; vertical-align:top;" |
You can start to add a cost to your Power List Item in the ECH. Within this list I would like each member of my itinerary to have an allowance of "€10" after the conference for lunch.
| style="width:40%; vertical-align:top;" |[[File:PowerList.png|thumb|Creating your Power List Item with a cost.]]
|}
{| style="width:100%; margin:auto;"
|-
| style="width:60%; vertical-align:top;" |
Within the app you can see that "Ben Rolls" and "John Smith" have ticked their respective lists. "Ben" has yet to check off "Lunch" but "John" has. Which means "John" has incurred a cost of "€10" for his team. Admins within the ECH should now be able to see this cost.
| style="width:40%; vertical-align:top;" |[[File:PowerList in App.png|thumb|Power List Team view]]
|}
{| style="width:100%; margin:auto;"
|-
| style="width:60%; vertical-align:top;" |
Navigating within the ECH click on the "costing" tab -> "Edit Costs" button and should see "John Smith" by a cost.
| style="width:40%; vertical-align:top;" |[[File:John Smith Powerlist cost.png|thumb|John Smith has now incurred a cost.]]
|}This can be good for implementing [[Meal Allowances]] and [[Guest Ordering]].
== View the status of your tasks ==
You can also view the current status of your Power List and its tasks on the ECH with the [[Power List View Status|view status]] feature.
{{Infobox Feature
| name = Custom Todos
| version = [[Release 3.5.0|3.5.0]]
| tier = Standard, Premium and Enterprise
}}
[[File:Screenshot 2026-06-17 at 14.57.14.png|thumb|Example: Input - ECH custom Todo]]
[[File:App-custom-todo.png|thumb|Example: Output - App custom Todo]]
= Custom Todos =
Todo task labels support special prefixes and variables that control how tasks are rendered in the UI.
== Prefixes ==
Prefixes are detected by examining the '''first character''' of the label after trimming leading whitespace.
=== ''.'' (Dot) – Inline/Child Tasks ===
Prefix a task label with <code>.</code> to make it an '''inline child''' of the preceding non-dot task. Child tasks are displayed in a grid row alongside their parent, creating a compact horizontal layout.
'''Behaviour:'''
* The <code>.</code> prefix is stripped from the displayed label
* The task is grouped with the previous non-dot task as a child
* Displayed in a shared grid row (parent + children side by side)
* Checkbox is still shown (can be checked/unchecked)
* If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task
'''Example:'''
<syntaxhighlight>
Monday Breakfast
.Lunch
.Dinner
</syntaxhighlight>
=== <code>|</code> (Pipe) – Label-Only (No Checkbox) ===
Prefix a task label with <code>|</code> to render it as '''plain text without a checkbox'''. Useful for section headers, notes, or informational text within a todo list.
'''Behaviour:'''
* The <code>|</code> prefix is stripped from the displayed label
* No checkbox is rendered
* The item does not count toward the completed/total counter
'''Example:'''
<syntaxhighlight>
|Important Notes
Attend all morning sessions
|Evening Activities
</syntaxhighlight>
== Date Variables ==
Task labels support the <code><nowiki>{{EventDate}}</nowiki></code> variable, which is replaced with the event's start date displayed as day and month numbers (e.g., ''16/06'').
=== Basic Usage ===
{| class="wikitable"
! Variable
! Replaced With
|-
| <code><nowiki>{{EventDate}}</nowiki></code>
| Event start date (e.g., ''16/06'')
|}
=== Offsets ===
You can add or subtract days from the event date using <code>+</code> or <code>-</code>:
{| class="wikitable"
! Variable
! Replaced With
|-
| <code><nowiki>{{EventDate+1}}</nowiki></code>
| Event start date + 1 day
|-
| <code><nowiki>{{EventDate-1}}</nowiki></code>
| Event start date − 1 day
|-
| <code><nowiki>{{EventDate+3}}</nowiki></code>
| Event start date + 3 days
|-
| <code><nowiki>{{EventDate-2}}</nowiki></code>
| Event start date − 2 days
|}
Whitespace inside the braces is tolerated:
* <code><nowiki>{{ EventDate + 1 }}</nowiki></code> → same as <code><nowiki>{{EventDate+1}}</nowiki></code>
* <code><nowiki>{{EventDate- 2}}</nowiki></code> → same as <code><nowiki>{{EventDate-2}}</nowiki></code>
Unknown variables (anything other than ''EventDate'') are left as-is.
'''Example:'''
<syntaxhighlight>
{{EventDate}} Check-in at hotel
{{EventDate+1}} Follow-up meeting
</syntaxhighlight>
== Combining Prefixes and Variables ==
Prefixes and date variables can be used together:
<syntaxhighlight>
|Schedule for {{EventDate}}
Morning briefing
. Afternoon workshop
. Evening networking
</syntaxhighlight>This can be good for implementing [[Meal Allowances]] where you have many options.
[[Category:3.5.0]]

Latest revision as of 13:46, 7 July 2026

Power List


Release version 3.4.1
Included in tier Premium and Enterprise

Power lists are a check list you can present to members of you team. At the simplest they can can be used to tick off a list of tasks that have been done. Power list can also be dated with a "Due by" date to let your team know when to complete theirs tasks by. However they can do much more for your event.

This page covers some of the potential use cases along with how they can be practically achieved.

Applying Costs via Power Lists

Power Lists can include costs assigned to individual tasks, for example: “Buy an Event Banner” — £40.

Costs can only be added or managed through the ECH (Event Coordinator Hub). Once a team marks a costed task as completed within the app, administrators in the Coordinator Hub will be able to view the associated cost that has been incurred. All costs go into the EventR Itinerary Cost Model.

Example: Creating a meal allowance within your Power List

You can start to add a cost to your Power List Item in the ECH. Within this list I would like each member of my itinerary to have an allowance of "€10" after the conference for lunch.

Creating your Power List Item with a cost.

Within the app you can see that "Ben Rolls" and "John Smith" have ticked their respective lists. "Ben" has yet to check off "Lunch" but "John" has. Which means "John" has incurred a cost of "€10" for his team. Admins within the ECH should now be able to see this cost.

Power List Team view

Navigating within the ECH click on the "costing" tab -> "Edit Costs" button and should see "John Smith" by a cost.

John Smith has now incurred a cost.

This can be good for implementing Meal Allowances and Guest Ordering.

View the status of your tasks

You can also view the current status of your Power List and its tasks on the ECH with the view status feature.

Custom Todos


Release version 3.5.0
Included in tier Standard, Premium and Enterprise
Example: Input - ECH custom Todo
Example: Output - App custom Todo

Custom Todos

Todo task labels support special prefixes and variables that control how tasks are rendered in the UI.

Prefixes

Prefixes are detected by examining the first character of the label after trimming leading whitespace.

. (Dot) – Inline/Child Tasks

Prefix a task label with . to make it an inline child of the preceding non-dot task. Child tasks are displayed in a grid row alongside their parent, creating a compact horizontal layout.

Behaviour:

  • The . prefix is stripped from the displayed label
  • The task is grouped with the previous non-dot task as a child
  • Displayed in a shared grid row (parent + children side by side)
  • Checkbox is still shown (can be checked/unchecked)
  • If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task

Example:

Monday Breakfast
.Lunch
.Dinner

| (Pipe) – Label-Only (No Checkbox)

Prefix a task label with | to render it as plain text without a checkbox. Useful for section headers, notes, or informational text within a todo list.

Behaviour:

  • The | prefix is stripped from the displayed label
  • No checkbox is rendered
  • The item does not count toward the completed/total counter

Example:

|Important Notes
Attend all morning sessions
|Evening Activities

Date Variables

Task labels support the {{EventDate}} variable, which is replaced with the event's start date displayed as day and month numbers (e.g., 16/06).

Basic Usage

Variable Replaced With
{{EventDate}} Event start date (e.g., 16/06)

Offsets

You can add or subtract days from the event date using + or -:

Variable Replaced With
{{EventDate+1}} Event start date + 1 day
{{EventDate-1}} Event start date − 1 day
{{EventDate+3}} Event start date + 3 days
{{EventDate-2}} Event start date − 2 days

Whitespace inside the braces is tolerated:

  • {{ EventDate + 1 }} → same as {{EventDate+1}}
  • {{EventDate- 2}} → same as {{EventDate-2}}

Unknown variables (anything other than EventDate) are left as-is.

Example:

{{EventDate}} Check-in at hotel
{{EventDate+1}} Follow-up meeting

Combining Prefixes and Variables

Prefixes and date variables can be used together:

|Schedule for {{EventDate}}
Morning briefing
. Afternoon workshop
. Evening networking

This can be good for implementing Meal Allowances where you have many options.