Church Related Services
Compatible Review is a process that a vendor's third-party application meets the performance and quality assurance requirements stipulated by the reviewing entity. FamilySearch reviews compatibility of minimum capabilities for different sets of features to make it easier for consumers to understand what features a vendor offers. Soltuions that provide ordinance services should comply with all compatible capabilities as presented in the Ordinance Compatibility Summary section.
Please Note: As of June 27, 2017, FamilySearch is suspending the compatibility verification and approval of new applications that provide functionality for scanning, capturing or reporting (or any combination of the three) ordinance information, including those that are or may be available to take to the temple. As we evaluate the impact of these types of applications on the FamilySearch systems and the end-user experience; this suspension will remain in effect until further notice. Solutions that request limited read-access privileges may be considered based upon need and functionality. If you have any questions, please email email@example.com.
Identify Appropriate Permissions
The application must make the proper call to the Identity module of the API to determine the privileges of the authenticated user.
Pricing of Temple Related Features
Temple attendance and the performing of temple ordinance is a sacred religious activity for the members of The Church of Jesus Christ of Latter-day Saints. Therefore, FamilySearch will review the pricing model of products that contain features specific to The Church of Jesus Christ of Latter-day Saints members. There should not be an additional cost for temple related features. If a software provider has an application that only provides these features, that application should be free. If the software provider has a business model for “freemium” and “premium” pricing, the temple related features should be provided in all versions offered. It is permissible for the solution to ask for donations including suggested amounts.
Adjustable User Interface
The user interface available to authenticated users needs to be adjustable, depending upon the privileges that are available to the general public verses an church member. The general public should not see any icons, menus, labels, or messages that are intended for The Church of Jesus Christ of Latter-day Saints members. Solutions that are verified compatible for Ordinance Read, Analysis, Reserve, or Family Name Cards should have these features turned off for public authenticated users.
Ordinance Compatibility Summary
All solutions accessing ordinances must meet the following business, marketing, and privacy requirements:
All public communications about ordinance features should be reviewed and approved by FamilySearch before being distributed by the certified vendor.
FamilySearch reserves the right to request additional reviews periodically or when the vendor's application goes through a version change.
Vendors should submit product names and Internet domain names for approval by FamilySearch before publicly deploying a product with ordinance capabilities.
A solution can be verified compatible in the following ordinance features: Identify Opportunities, Reserve, and Print Family Names.
Required: Yes Not Allowed: No Optional: Opt
|Identify Opportunities||Reserve||Print Family Names|
|Previous Certified||Tree Read||Tree Write||Tree Write|
|Person Ordinances Read||Yes||Yes||Yes|
|Identify Persons Needing Ordinances||Yes||Yes||No|
|Checking for Duplicates||Opt||Yes||Yes|
|Prepare Persons for Submission||No||Yes||No|
|Planning a Visit||No||Yes||No|
|Printing Family Ordinance Requests (FORs)||No||Opt||Yes|
|Use of Icons and Statuses||Yes||Yes||Opt|
|Use of Submission Policy||No||Yes||No|
Solutions that show ordinance information and status along with other person information need to properly use the Ordinance Person Read endpoint. To identify opportunities, applications must crawl the tree to gather information and statuses about ancestors.
These solutions not only crawl the tree to gather ordinance information but also perform the analysis to find couples, parents, and children that can be submiited for ordinances with very little or no additional information. The results of this crawling and analysis can be shown in an "Opportunity List," which indicates which individuals need ordinances and the actions required to add the names to the user's Temple Reservation List.
To receive this compliance verification, solutions add persons to the Temple Reservation List, display the Reservation List, and select individuals and ordinances to be reserved. The Temple Reservation List should show at least the name, ordinances reserved, who the person needs to be sealed to (if applicable), and the date reserved.
Ordinance status icons should always be used on the Temple Reservation List to show status of all ordinances reserved for individuals. The ordinance icon legend should be easily displayed from this page. The minimum actions that must be available are to Reserve, Unreserve, and Share.
This feature makes it possible to select individuals and some or all ordinances that have been reserved in order to place these requests on a Family Ordinance Request page or Temple Cards. The solution receives the Family Ordinance Request (FOR) or Temple Cards in PDF format from FamilySearch.org and launches Adobe Acrobe Reader or other compatible reader. The solution should also allow lost or destroyed requests to be reprinted.
Identify Persons Needing Ordinances
Helping users determine whether a person needs temple ordinances is a task that applications can distinguish themselves from the FamilySearch Family Tree web interface and other products.
Church members who have many generations of data in Family Tree may find it difficult to find ordinances that can be done. They do not necessarily want to navigate through their family tree to find them. Programmatic crawling and analyzing ordinance statuses can help members decide what persons can more easily qualify for ordinance submissions.
- Make sure a person’s record is in Family Tree before it is reserved. This ensures that official ordinance records can be used to determine whether ordinances are needed.
- Use the Person Ordinances Read service to identify the ordinance statuses for a person or family.
- Display ordinance statuses using the approved definitions and icons.
Prepare Persons for Submission
When users reserve ordinances, they accept the responsibility to see that the ordinances get done. After reserving ordinances, users assign them to an inventory. The inventory indicates who will provide the proxies for the ordinances.
Users need to reserve ordinances that they want to do. Users may need help from others to get the ordinances done.
- Reserve only ordinances for which the status is listed as reservable.
- Ensure that all prerequisite ordinances are either done, not needed, or reserved at the same time.
- Allow users to reserve ordinances for themselves or share them with the community.
- Allow an ordinance that was previously shared to be reserved, if the work is not yet done.
- Allow an ordinance that was previously reserved to be shared.
Check for Duplicates
Preventing the performance of duplicate temple ordinances is one of Family Tree’s main purposes.
To prevent duplicate ordinances, a person’s record must be merged with the records that contain the official ordinance assertions. This may create the following challenges:
- End users may become discouraged or bored if they have to review too many possible duplicates.
- Users may be confused if they merge some duplicate records while submitting ordinances and then later find that more possible duplicates exist for the same person.
- Show a merge screen to the user. This screen can appear before or after the screens where users identify persons needing ordinances and where users prepare and assign ordinances. To do this, an application must have the Merge certification.
- Reread ordinance information after records are combined to obtain the new ordinance status.
Printing Temple Ordinance Cards
Temple Ordinance Cards can be printed for the persons for whom they will be performing ordinances.
Church members generally print Temple Cards when they create a temple trip. However, the printing can occur any time after the trip has been created.
For printing and reprinting Temple Cards, the following requirements apply:
- After ordinances are reserved, users should be able to find, select, and print reservations on temple cards.
- The solution should provide a list of people whose ordinances were previously printed on cards and give users the ability to reprint a temple card for any of those people who still qualify for ordinances.
- If a card is reprinted after some of the work has been performed, the solution should only reprint the card with the ordinances that have not been completed.
- If yes, the process is completed.
- If no, the user should be prompted to print again.
Displaying Ordinance Status
The abbreviations B, C, I, E, SP, and SS represent the names of each of the temple ordinances in English. The detailed descriptions of the abbreviations can be shown to authenticated members. The same abbreviation letter can be used in all languages.
|E||Endowment||B, C, I|
|SP||Sealing to Parents||B, C, I, E|
|SS||Sealing to Spouse||B, C, I, E|
Ordinance Status Colors
When the solution displays a deceased person’s ordinances, it should show display the ordinance status and if applicable the completion date. The ordinance status is a colored box with the appropriate color and ordinance abbreviation letter inside. Additional status text may be used along with the color.
|Color||Hex Code||Status Codes|
Considerations for Mobile Solutions
Mobile solutions are easier and have shorter tasks to accomplish. The follow simplifications are acceptable with mobile solutions
- The status letter displayed without square colored background.
- The letter has two states for available and unavailable using a combination of light, standard, or bold styles.
- The letter “S” is used for both “Sealing to Parents” and "Sealing to Spouse” as long as the actual status of each one of these is easily accessible.
Use of Submission Policy
110 Year Rule
To do ordinances for a deceased person born in the last 110 years, members must either be one of the closest living relatives or must obtain permission from the closest living relative. Church members should not submit the names of persons who are not related to them. The ordinance submission application must remind the church member of their responsibilities and give them the opportunity to accept these reponsibilities.
- Display the Church Policy screen.
- If an ancestor was born in the last 110 years, request the user to indicate that he or she is authorized to perform the ordinances:
- If you are the spouse, parent, child, brother, or sister of the deceased person, click I am the closest living relative. You can request the ordinances.
- If you are not the spouse, parent, child, brother, or sister of the deceased person but you have permission from the closest living relative, click I have permission from the closest living relative to do the ordinances. You can then request the ordinances.
- If you are not a close living relative and if you do not have permission from the closest living relative, click None of the above. (This person’s ordinances will not be reserved.)
- Also display "For more information, please read (including proper hyperlinks):
- At the bottom of the screen, provide a check box for users to indicate that they have read and will comply with the Church Temple Ordinance Policy. Clicking the check box means the users understand Church policy and are reserving only ordinances that comply with the policy.
- Provide an Add button to put the person on the user's temple list. If a user clicks it, reserve the ordinances, and display the temple list.
- Provide a Cancel button that does not put the names on the user's temple list but instead returns the user to the prior screen.
For links to translations of the required links, please contact developer services.
Since the Submission Policy may change, it will be a resource obtainable as an API resource with an active session and autheticated member. The instructions for accessing this resource will be made available to developers that have signed the "Ordinance Addendum."