Pending Event State

51 votes

Currently, we use Tentatives for our user requests and Confirmed/Denied for when we've completed the requests. But there are many reservations that must sit as a Tentative while we get the needed approvals, permits, insurance, etc. We mark them with a character added to the event name, e.g. #Senate Meetings, to differentiate the ones we have touched from the new requests.

To track them better we'd like to have a Pending event state so we can 1) work with a pending search, like we do with a tentative search and 2) separate the Pendings from the Tentatives, which would be more efficient and save time. It would be particularly helpful for our clubs process. Club schedulers often don't understand that Confirmed doesn't always mean Done, so we leave their request as a Tentative which then clogs up the Tentative list.

I know this has been discussed in the past and it did not move forward. I'd like to bring this up again. We really need it.

Under consideration ** Event Management Workflow Suggested by: Bonnie Hendrickson Upvoted: 09 May Comments: 18

Comments: 18