Support / Training
Support Handbook / Precedent cases / Precedent case a20100210.2
How to handle case that are similar to precedent case a20100210.2 (Revoke assurance within short timespan)
First SE must check if the preconditions are met.
The preconditions are fixed in these documents
1. Basic rule
Normally Support can revoke an assurance when the claim for the revocation reaches support within 24 hours after the assurance was entered.
As Support can not check at what exact time the assurances was entered the assurer needs to send in a mail where he states that he claimed the revocation within 24 hours after entering and he needs to sign this mail with the CARS statement [1].
a20101016.1 Part II [2]
2. exceptions
- extension of the timeslot between time of entering and request of revocation up to 7 days after a big event
- big events (greater 1 day events, including weekend days) i.e. CeBIT, Fosdem, Froscon, Linuxtag. delays in trying to transfer points is up to 1 week (7 days), so errors probably cannot be seen and so therefore identified before the 6th or 7th day.
short time frame => less then 7 days (including), within 7 x 24 hours after an event = 168 hours
a20101016.1 Part I [3]
- big events (greater 1 day events, including weekend days) i.e. CeBIT, Fosdem, Froscon, Linuxtag. delays in trying to transfer points is up to 1 week (7 days), so errors probably cannot be seen and so therefore identified before the 6th or 7th day.
- extension of the timeslot between time of entering and request of revocation up to 3 days after a small event
- small events (1 day events) up to a 72 hours delay (from experiences with events from one year)
short time frame => less then 3 days (including), within 3 x 24 hours after an event = 72 hours
a20101016.1
- small events (1 day events) up to a 72 hours delay (from experiences with events from one year)
* Link to Support only part Mailing (Private Part)
Important: Once finished the ticket number needs to be added to the table on the Precedent case a20100210.2 page.
Reference documents
[1] CARS statement
[2] Precedent case a20101016.1 Ruling Part II
[3] Precedent case a20101016.1 Ruling Part I