Genealogy from the perspective of a member of The Church of Jesus Christ of Latter-day Saints (Mormon, LDS)

Monday, August 5, 2019

Reserved Ordinances Expiration

https://www.familysearch.org/blog/en/expiration-ordinance-reservations/?cid=bl-tu-8377
The idea of having a place on the FamilySearch.org website to reserve Temple Ordinances is to allow members the opportunity to perform those ordinances for their own ancestors and relatives. However, reserving an excessive number of ordinances is counterproductive. Locking the ordinances up in a huge Reserved List beyond what could be completed in a reasonable period of time, does not benefit the individual who reserved the ordinances or those ancestors and relatives who are waiting for their ordinances to be done. Adding available ordinances to your reserved list is not a game where the highest number reserved wins. You and others benefit from performing the proxy ordinances in the Temples.

Unfortunately, not all those who are working on the FamilySearch.org Family Tree for the purpose of finding ancestors and relatives who need to have their Temple Ordinances performed understand this principle. As a result, FamilySearch has implemented an automatic expiration date that will apply to all ordinances according to the following rules:
  • In general, ordinance reservations expire two years from the reservation date. 
  • Ordinance reservations you share with someone expire two years from the original reservation date. 
  • Ordinance reservations expire after 90 days if they were retrieved from the temple reservation list by Ordinances Ready. (Learn more about Ordinances Ready and how it searches for ordinances.)
  • When you reserve multiple ordinances for the same ancestor, the ordinance reservation will be extended for one year if at least one ordinance is completed before the expiration date.

When you share your reserved ordinances with the Temples, those of your family who are using the Ordinances Ready app will have access to those previously reserved ordinances. 


No comments:

Post a Comment