Default Setup / Takedown time based on location and layout
Add default setup and takedown time to an event based on the location that is assigned and the layout that is chosen.
Comments: 14
-
01 Apr, '20
Keith StilesApprovers get tons of request where the requestor is vastly over- or under-estimating the amount of time a given layout requires. This would make layouts function much more powerfully and could be exposed to the requestor. On the flip side of the coin, the approver then has fewer modifications to make when approving the event. A win for both sides of the equation.
-
15 May, '20
Walt M (CollegeNET) Admin"Ability to pre set default set up time on locations" (suggested by Kimm Thiboldeaux on 2020-05-12), including upvotes (1) and comments (0), was merged into this suggestion.
-
17 Jul, '20
Connie S. FenskyThis would also be useful for COVID-19 preparations--in specific, rooms that need to be sanitized between events, or with resources that need to be sanitized between events.
-
29 Jul, '20
Teresa SummersMaricopa Colleges has been asking for this also so they can sanitize between classes.
-
15 Aug, '20
Leonard BrettonThis would great addition as we are limited times for rehearsals need to have gaps in-between them to the HVAC system flush the air.
-
04 Sep, '20
Catherine ScholzMSOE would also appreciate this at the location level including those locations that use Express Scheduling. Certain locations require more setup/teardown and cleaning time.
-
14 Oct, '20
Walt M (CollegeNET) AdminThe first iteration of this functionality is included in the current development sprint (expected release 10/29/2020). This could change, but we want to give advanced notice so you can get your layouts and default layouts set on your locations while you wait! I may be reaching out to those who have voted and commented (if you supplied an email address) for a sneak peak as things become available to me internally...
-
15 Oct, '20
Teresa SummersPlease let us know when and where we can have a look at it. My group is very excited.
-
21 Oct, '20
VictoriaAny update on this release, is it still on track for 10/29? That would be great!
-
21 Oct, '20
Mike C (CollegeNET) AdminVictoria, yes, this is still slated for the 10/29 release, however, that is still tentative release.
-
27 Oct, '20
Walt M (CollegeNET) AdminIt looks like this release is slipping a bit and will not be released this week. It is still in the works though! - stay tuned here for updates...
-
19 Nov, '20
Walt M (CollegeNET) AdminThis is going out tonight!
This improvement allows those with appropriate edit rights to Locations the ability to add default setup and takedown times per layout on the Location details page in 25Live Pro.
In the event form, the setup and takedown times are applied even if the setup and takedown editors are not available to the user entering the request.
There are some things to keep in mind in this first iteration, and updates will continue as we move forward.
#1 - the form will continue to ensure that the additional time meets the minimum needed, but it will not decrease the time. So if I add a location with a layout with default time, then remove that location or change the layout to one without time, the time will remain unless it is manually removed.
#2 - The additional time is not factored into the availability checks for the locations as the event is being created, so there could be conflicts upon save,
#3 - These defaults do not apply to express scheduling. -
22 Nov, '22
Bonnie HendricksonHi Walt, we're just now taking a look at this now that we have a full team of schedulers. It would be very helpful for consistency purposes but item 2 is critical to it being effective. Has that been fixed?
-
22 Nov, '22
Walt (CollegeNET) AdminThe default setup and take down times being added once location and layout are selected do not re-initiate availability checks Bonnie, but upon save all times are checked. Once the conflict appears, users can then shift times, or change locations/layouts to overcome the potential conflicts. If you'd like to see this improved upon, please add a new feature request, so we can gather info on the demand, need, and use cases involved. Thanks!