{"id":2748,"date":"2026-09-30T13:25:14","date_gmt":"2026-09-30T13:25:14","guid":{"rendered":"https:\/\/churchesadmin.com\/blog\/?p=2748"},"modified":"2026-09-30T13:25:14","modified_gmt":"2026-09-30T13:25:14","slug":"church-attendance-software-check-in-tests","status":"publish","type":"post","link":"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/","title":{"rendered":"Church Attendance Software: 9 Smart, Essential Check-In Tests"},"content":{"rendered":"<p>Church attendance software can make a service or meeting easier to record, but the team still needs clear definitions and a workable check-in routine. A total is useful only when leaders know which event it describes, how people were counted and whether any entries still need review. A fast check-in screen cannot resolve an unclear counting process on its own.<\/p>\n<p>This guide sets out nine practical tests for church offices and welcome teams. It covers event setup, ordinary exceptions, report definitions and the handover after a service. Use fictional records while testing and confirm the methods supported by your chosen package. Attendance is an administrative record; it should support appropriate planning and care without being treated as a complete measure of an individual\u2019s involvement.<\/p>\n<figure><img decoding=\"async\" src=\"https:\/\/churchesadmin.com\/blog\/wp-content\/uploads\/2026\/09\/church-attendance.png\" alt=\"church attendance software practical workflow illustration\" \/><\/figure>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_83 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#1_Define_the_event_before_testing_church_attendance_software\" >1. Define the event before testing church attendance software<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#2_Prepare_the_directory_and_visitor_route\" >2. Prepare the directory and visitor route<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#3_Test_the_ordinary_check-in_method\" >3. Test the ordinary check-in method<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#4_Include_duplicate_and_late-arrival_scenarios\" >4. Include duplicate and late-arrival scenarios<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#5_Rehearse_a_connection_or_device_problem\" >5. Rehearse a connection or device problem<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#6_Limit_volunteer_access_to_the_assigned_task\" >6. Limit volunteer access to the assigned task<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#7_Review_the_session_before_sharing_the_report\" >7. Review the session before sharing the report<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#8_Connect_appropriate_follow-up_to_a_separate_decision\" >8. Connect appropriate follow-up to a separate decision<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#9_Train_a_second_team_and_review_the_routine\" >9. Train a second team and review the routine<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#A_sample_rehearsal_for_the_welcome_team\" >A sample rehearsal for the welcome team<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#Label_a_provisional_total_clearly\" >Label a provisional total clearly<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#Questions_about_church_attendance_software\" >Questions about church attendance software<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#Does_check-in_prove_that_every_person_stayed_for_the_whole_event\" >Does check-in prove that every person stayed for the whole event?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#Should_visitors_be_added_as_members_to_simplify_reporting\" >Should visitors be added as members to simplify reporting?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#Can_the_team_use_a_paper_fallback\" >Can the team use a paper fallback?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#Independent_resources_for_other_church_projects\" >Independent resources for other church projects<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-software-check-in-tests\/#Make_the_next_session_easy_to_explain\" >Make the next session easy to explain<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"1_Define_the_event_before_testing_church_attendance_software\"><\/span>1. Define the event before testing church attendance software<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Decide what one attendance record represents. A Sunday service, a department meeting and a multi-session conference may need different event structures. If the team combines them under one label, the resulting total may be difficult to interpret. Write down the event name, date, location and counting rule before creating the first session.<\/p>\n<p>Clarify whether the report counts entries, visits or unique people. Someone attending two sessions can legitimately appear twice in a session total while counting once in a unique-person view. Neither number is automatically wrong. The problem arises when staff compare them as though they answer the same question.<\/p>\n<p>Review the <a href=\"https:\/\/churchesadmin.com\/\">church management software<\/a> overview and explain your event structure to the provider. Church attendance software should be demonstrated using the kind of service or meeting your team actually runs, including more than one session where that matters.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"2_Prepare_the_directory_and_visitor_route\"><\/span>2. Prepare the directory and visitor route<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A welcome volunteer needs a practical way to find the correct person. Test similar names, a shared contact number and someone whose details have recently changed. The search process should not encourage staff to create a new entry every time they cannot immediately find an existing record. That habit can gradually inflate the directory.<\/p>\n<p>Give visitors a clear route that does not assume they are already members. Decide which information is necessary for the event and explain the purpose when asking for it. Avoid holding up the entrance to collect details that the church has not agreed to use. A welcoming process needs to work for people who are unfamiliar with the system.<\/p>\n<p>The <a href=\"https:\/\/churchesadmin.com\/blog\/church-membership-management-software-in-kenya\/\">church membership management software<\/a> guide provides related directory checks. Connect those checks to church attendance software so the welcome team knows when to use an existing record, when to create a visitor entry and when to refer an uncertain case.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"3_Test_the_ordinary_check-in_method\"><\/span>3. Test the ordinary check-in method<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Use the supported check-in method on a device similar to the one volunteers will use. Confirm whether the package supports a staff-operated screen, a code-based process or another method. Do not assume that every method described on a general product page is available in the selected configuration without confirmation.<\/p>\n<p>Ask a volunteer to complete several fictional check-ins without coaching. Observe the number of steps, the clarity of the confirmation and the ease of returning to the next person. A process that feels simple at a desk may become awkward when people arrive together and the volunteer is also answering questions.<\/p>\n<p>Review the <a href=\"https:\/\/churchesadmin.com\/features\">church management system features<\/a> alongside the demonstration. Church attendance software should make a successful entry recognisable. If a user is unsure whether the action worked, they may repeat it and create an avoidable duplicate or delay.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"4_Include_duplicate_and_late-arrival_scenarios\"><\/span>4. Include duplicate and late-arrival scenarios<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<figure><img decoding=\"async\" src=\"https:\/\/churchesadmin.com\/blog\/wp-content\/uploads\/2026\/09\/church-system.png\" alt=\"Church administration and team handover illustration\" \/><\/figure>\n<p>Attempt to check the same fictional person into the same session twice. Ask the provider to explain what happens and how the team recognises the result. A duplicate warning, a repeated entry and a second-session record may behave differently. Staff need to understand the actual behaviour rather than relying on an assumption.<\/p>\n<p>Test a late arrival after the main entrance activity has ended. Decide who remains responsible for the record and whether the event stays open. If several volunteers use different devices, confirm that they are working on the same session and know how to identify it. A wrong event selection can be harder to notice than a spelling mistake.<\/p>\n<p>For church attendance software, keep an exception process short and clear. A volunteer should know where to note an uncertain entry and who will review it. They should not need to make a complicated administrative decision while a queue forms at the door.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"5_Rehearse_a_connection_or_device_problem\"><\/span>5. Rehearse a connection or device problem<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<figure><img decoding=\"async\" src=\"https:\/\/churchesadmin.com\/blog\/wp-content\/uploads\/2026\/09\/church-members.png\" alt=\"Church administration and team handover illustration\" \/><\/figure>\n<p>Ask what the application supports if the connection fails or a device becomes unavailable. Test the documented behaviour rather than assuming offline access. If the church uses a temporary record, agree who maintains it, where it is kept and how entries will be checked before being added later.<\/p>\n<p>A fallback should avoid collecting unnecessary information and should remain limited to the event\u2019s purpose. Give the temporary record a clear event reference and an owner. Without that context, someone entering it later may choose the wrong session or repeat entries that were already saved before the interruption.<\/p>\n<p>Church attendance software needs a recovery check as well as a fallback. Compare the temporary record with the final session and mark what has been handled. Keep unresolved cases visible until an authorised person reviews them. Do not report a final total while silently excluding a known set of pending entries.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"6_Limit_volunteer_access_to_the_assigned_task\"><\/span>6. Limit volunteer access to the assigned task<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<figure><img decoding=\"async\" src=\"https:\/\/churchesadmin.com\/blog\/wp-content\/uploads\/2026\/09\/church-records.png\" alt=\"Church administration and team handover illustration\" \/><\/figure>\n<p>A person helping at the entrance may need a different level of access from the church office. Test the check-in process through an ordinary volunteer account and review what information is visible. The team should be able to complete its task without unnecessary access to unrelated member or contribution records.<\/p>\n<p>Name the person who approves access and reviews it when a volunteer\u2019s role changes. Shared devices need a clear sign-in and handover routine. Staff should know what to do when the device is left unattended and how the next shift begins. Confirm the controls available in the actual system rather than assuming a particular security feature.<\/p>\n<p>In church attendance software training, explain when to refer a question to the office. A volunteer should not feel responsible for resolving every directory inconsistency at the entrance. Good role design includes a clear route for uncertainty as well as permission to complete ordinary check-ins.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"7_Review_the_session_before_sharing_the_report\"><\/span>7. Review the session before sharing the report<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>After the event, ask an authorised person to check pending entries, duplicates and any temporary records. Confirm the event name and date before producing the report. A short review is especially useful when several people worked on the session or when a connection problem interrupted the normal process.<\/p>\n<p>Use the <a href=\"https:\/\/churchesadmin.com\/blog\/church-attendance-tracking-system-in-kenya\/\">church attendance tracking system<\/a> guide as a related resource. Church attendance software reports should carry enough context for leaders to understand the number: the event, period, counting definition and any known limitation.<\/p>\n<p>Avoid comparing two periods without checking their structure. One month may include an extra service or a special event. A higher total does not necessarily mean more unique people attended ordinary services. Keep the interpretation close to the evidence and explain changes in the counting process when they affect a comparison.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"8_Connect_appropriate_follow-up_to_a_separate_decision\"><\/span>8. Connect appropriate follow-up to a separate decision<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>An attendance record can support a review, but it should not automatically determine the meaning of someone\u2019s absence. People may attend another service, travel or have circumstances the system does not record. The authorised church team should decide how any follow-up fits its normal pastoral and administrative process.<\/p>\n<p>Keep the follow-up task limited to the people who need it. Avoid distributing a detailed attendance list broadly simply because an export is available. If a report supports planning, consider whether an aggregate total answers the question without exposing individual details. Use the church\u2019s approved access and communication arrangements.<\/p>\n<p>The <a href=\"https:\/\/churchesadmin.com\/blog\/church-visitor-follow-up-software-in-kenya\/\">church visitor follow-up software<\/a> article provides context for a separate handover. Church attendance software can inform that process, but the team should still record who owns the next action and distinguish an administrative signal from an assumption about a person.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"9_Train_a_second_team_and_review_the_routine\"><\/span>9. Train a second team and review the routine<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A reliable process should work when the usual coordinator is absent. Give another volunteer a short rehearsal covering an ordinary entry, a duplicate attempt, a visitor and a late arrival. Ask them to identify the correct event and explain what to do if the connection fails. Their questions can reveal gaps in the written guidance.<\/p>\n<p>Keep a simple session checklist near the operating process. It should cover event selection, device readiness, responsibility for exceptions and the final review. Avoid a long manual that volunteers cannot consult during a busy arrival period. Put detailed setup instructions in a separate office reference.<\/p>\n<p>Review church attendance software after a few ordinary sessions. Ask where queues formed, which cases needed help and whether reports were easy to explain. Improve the named step causing difficulty before adding more devices or expanding the system to every event at once.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"A_sample_rehearsal_for_the_welcome_team\"><\/span>A sample rehearsal for the welcome team<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Prepare ten fictional people for a test session. Include two similar names, one visitor, one shared household contact and one late arrival. Check one person twice deliberately. Give the team an interruption scenario and ask them to describe the fallback without entering live information.<\/p>\n<p>After the rehearsal, compare the expected session record with the final result. Discuss each difference calmly and identify whether it came from the instructions, the directory or the system setup. The exercise is successful when the team can explain the outcome and knows how to handle uncertainty, not merely when the screen displays a pleasing total.<\/p>\n<p>Record the changes agreed after the test and repeat only the affected scenarios. This keeps preparation focused and avoids turning training into a long series of identical demonstrations. Church attendance software should support volunteers in their role rather than making them dependent on an expert for every exception.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Label_a_provisional_total_clearly\"><\/span>Label a provisional total clearly<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>If entries are still being checked, tell the report recipient that the total is provisional and identify the review owner. Share the corrected result through the same agreed channel when the work is complete. Church attendance software should help the team explain the status of a report rather than letting an early number circulate as a final result.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Questions_about_church_attendance_software\"><\/span>Questions about church attendance software<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"Does_check-in_prove_that_every_person_stayed_for_the_whole_event\"><\/span>Does check-in prove that every person stayed for the whole event?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>No. A check-in records the event defined by your process. It does not establish every aspect of participation. Keep reports labelled accurately and avoid drawing conclusions that the underlying record cannot support.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Should_visitors_be_added_as_members_to_simplify_reporting\"><\/span>Should visitors be added as members to simplify reporting?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>No. Keep the church\u2019s visitor and membership definitions clear. Use the supported visitor process and let the authorised team decide status changes through the normal procedure. Convenience at check-in should not change the meaning of the directory.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Can_the_team_use_a_paper_fallback\"><\/span>Can the team use a paper fallback?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If the church approves that method, define its scope, owner and later checking process. Confirm how records will be entered without duplication. Protect the temporary information and handle it under the church\u2019s normal recordkeeping arrangements after the final session is verified.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Independent_resources_for_other_church_projects\"><\/span>Independent resources for other church projects<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>For separate projects, compare <a href=\"https:\/\/zama.co.ke\/\" target=\"_blank\" rel=\"noopener\">website development services<\/a>, <a href=\"https:\/\/zes.co.ke\/\" target=\"_blank\" rel=\"noopener\">access control and CCTV installation<\/a> and <a href=\"https:\/\/dereva.co.ke\/\" target=\"_blank\" rel=\"noopener\">professional driver services<\/a>. Confirm the project scope directly; none of these links establishes an integration with church attendance software.<\/p>\n<p>Community enterprises can independently assess <a href=\"https:\/\/prim.co.ke\/\" target=\"_blank\" rel=\"noopener\">salon management software<\/a>, <a href=\"https:\/\/vega.co.ke\/\" target=\"_blank\" rel=\"noopener\">retail POS software<\/a>, <a href=\"https:\/\/tas.co.ke\/\" target=\"_blank\" rel=\"noopener\">chama management software<\/a> and <a href=\"https:\/\/jaat.co.ke\/\" target=\"_blank\" rel=\"noopener\">business marketplace listings<\/a>. For public notices or training documents, compare <a href=\"https:\/\/saseni.com\/\" target=\"_blank\" rel=\"noopener\">editing services<\/a> and approve the final wording internally. These are separate enquiry options, not endorsements or assurances of compatibility.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Make_the_next_session_easy_to_explain\"><\/span>Make the next session easy to explain<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Bring your event structure, volunteer roles and exception examples to a ChurchesAdmin demonstration. Ask the team to test the complete process from event creation to report review. Well-organised church attendance software gives volunteers a clear task and leaders a record whose meaning they can understand.<\/p>\n<p>Give the final report a clear preparation date and identify the session it covers. If a correction is issued later, explain which result replaces the earlier version. This small handover step helps leaders avoid comparing an old provisional count with a revised figure without noticing the difference.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Church attendance software can make a service or meeting easier to record, but the team still needs clear definitions and a workable check-in routine. A total is useful only when leaders know which event it describes, how people were counted and whether any entries still need review. A fast check-in screen cannot resolve an unclear [&hellip;]<\/p>\n","protected":false},"author":8,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-2748","post","type-post","status-publish","format-standard","hentry","category-church-management-software"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/churchesadmin.com\/blog\/wp-json\/wp\/v2\/posts\/2748","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/churchesadmin.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/churchesadmin.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/churchesadmin.com\/blog\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/churchesadmin.com\/blog\/wp-json\/wp\/v2\/comments?post=2748"}],"version-history":[{"count":3,"href":"https:\/\/churchesadmin.com\/blog\/wp-json\/wp\/v2\/posts\/2748\/revisions"}],"predecessor-version":[{"id":2756,"href":"https:\/\/churchesadmin.com\/blog\/wp-json\/wp\/v2\/posts\/2748\/revisions\/2756"}],"wp:attachment":[{"href":"https:\/\/churchesadmin.com\/blog\/wp-json\/wp\/v2\/media?parent=2748"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/churchesadmin.com\/blog\/wp-json\/wp\/v2\/categories?post=2748"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/churchesadmin.com\/blog\/wp-json\/wp\/v2\/tags?post=2748"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}