# How Should LGUs Detect Duplicate Burial Permit Applications Before Approval? Before approval, local government units should run duplicate burial permit application detection against existing active and issued permit records, then send possible matches to an authorized reviewer. Staff should compare authoritative death-event details, supporting record references, applicant information, submission timing, and permit status. A similar name should trigger review, not automatic rejection. The reviewer should decide whether the submissions describe the same burial event, different events, or an unresolved case requiring additional evidence. For LGUs managing [LGU civil registrar and permit records](https://golgu.ph/service/erp-system), the digital workflow should help staff find, compare, hold, and document possible matches. The system should support the review process without conferring legal authority to automatically reject, merge, or archive applications. ## What Should Happen Before a Burial Permit Application Reaches Approval? The duplicate check should occur after the application has sufficient information for a meaningful comparison, but before final approval. The first task is to search existing burial-permit records and related death-event references for possible matches. A burial permit duplicate check should look for both exact matches and near matches. Exact matches are easier to identify, such as the same death-certificate reference appearing in two applications. Near matches need more review, such as one application using a complete registered name while another uses a shortened first name or a spelling variation. Staff should not treat the search result itself as the final decision. A possible match is a review flag. The authorized reviewer still needs to compare the source records and decide what the applications represent. ## Which Death-Event Details Should Staff Compare First? Act No. 3753 requires the death certificate to include key facts such as the date and place of death, full name, age, sex, residence, and other information. Those facts provide a strong starting point for checking whether two applications refer to the same death event. For pre-approval screening, staff should give more weight to combinations of fields than to a single field. A matching full name plus the same date and place of death is more meaningful than a matching surname by itself. Useful comparison points include: * full registered name of the deceased * date of death * place of death * age or date-of-birth information when available in the source record * residence or address information when relevant * death certificate or civil registration reference * burial or transfer-related supporting references when part of the local process These comparison points should come from the LGU's actual records and approved process. They are not a new nationwide burial-permit form. ## Why Is a Matching Name Alone Not Enough? Names are useful search signals, but they are not reliable proof of duplication on their own. Two different people may share the same name. One person may also appear under a shortened name, a middle initial, different spacing, a typographical variation, or an encoding difference. This is where civil registrar record matching should use multiple facts. If the names are similar but the dates or places of death are different, the applications may describe different people. If the names vary slightly but the death-event details and source references align, the applications deserve closer review. A system-generated similarity result should therefore help prioritize records for review. It should not become an automatic legal finding. ## How Should Supporting Record References Be Used? Reference numbers often provide stronger evidence than free-text names. Staff should compare the death certificate reference, the existing permit number, and other authorized supporting references used by the LGU. If two applications cite the same death record but differ in typed names or applicant details, the reviewer should investigate whether both concern the same burial event. Different references still require source-record review before classification. ## How Should Applicant Differences Affect the Review? Different applicants do not automatically mean different burial events. Relatives, representatives, or other authorized persons may submit records in accordance with an LGU's local procedure. Applicant information is a supporting signal. The key question is whether the applications concern the same deceased person and burial event. The same applicant may also submit records for different deceased persons, so applicant identity should never be the sole basis for the duplicate rule. ## How Should Existing Permit Status Affect the Decision? The status of an earlier record helps staff understand what action is safe. A second application that matches an already approved or issued permit deserves a different review from two drafts submitted close together. The review screen should show whether the earlier application is draft, under review, approved, issued, returned, canceled, or otherwise classified under the LGU's actual workflow. These labels are operational examples, not mandatory national status names. If an earlier permit has already been issued, staff should avoid creating a second approval merely because a later application passed a completeness check. The reviewer should first determine why the new submission exists. ## What Should a Duplicate Application Review Decide? The review should end with a clear classification. The reviewer should determine whether the applications describe the same event, different events, or an unresolved situation requiring more evidence. A practical decision set might include: * not a duplicate, proceed with normal review * potential duplicate, hold for additional verification * same event, follow the LGU's authorized duplicate-handling procedure * insufficient information, return for clarification or supporting evidence These are recommended decision categories. The LGU should use statuses that fit its lawful process and existing records design. ## What Should Happen When Staff Cannot Confirm a Duplicate? Uncertainty should produce a controlled hold or additional verification, not an invented answer. Keep both applications intact while the reviewer checks missing evidence. The record should identify what remains unresolved and what evidence is needed next. This keeps the decision traceable and avoids repeating the same comparison without context. ## What Should the Duplicate-Review Record Contain? The review record should explain how the decision was reached. Useful elements include: * new application reference * possible matching application or permit reference * fields that matched exactly * fields that differed * source documents or records checked * reviewer * review date * decision * reason or notes * next authorized action This record supports civil registrar record matching by showing which facts mattered. It also helps later reviewers understand why a similar application was allowed to proceed or was held. ## How Should Duplicate Burial Permit Application Detection Treat a Potential Match? A potential match should change the workflow state, not destroy the application. The system might place the application in a review queue, display the matched records side by side, restrict final approval until review finishes, and preserve the final decision in the audit history. OpenCRVS provides one international technical example. Its deduplication workflow flags possible duplicate civil-registration declarations, sends them to a reviewer, presents matched records for comparison, and records whether the reviewer marks the declaration as duplicate or not duplicate. This is a useful design reference, not a Philippine legal requirement. The same principle applies to pre-approval screening: technology identifies potential matches, while an authorized person makes the decision in accordance with the LGU's applicable rules. ## What Should the System Administrator Configure? The administrator should configure search fields, permissions, reviewer roles, decision reasons, notifications, and audit history only after the Civil Registrar office approves the workflow. No Philippine source reviewed for this guide establishes a single national threshold for burial-permit duplicates. Configuration access should also remain separate from permit authority. ## Which Test Cases Should LGUs Run Before Go-Live? Testing should cover cases that challenge both exact matching and near matching. A useful set includes: * same registered name, same date and place of death, same source reference * same death event but shortened first name in one application * same surname but different date and place of death * same death-certificate reference with different applicant names * two applications submitted minutes apart for the same event * one application matching an already issued permit * similar names with different source references * potential match returned for more evidence These cases test the burial permit duplicate check without assuming every similarity is a duplicate. They also test whether duplicate burial permit application detection gives the reviewer enough evidence for a defensible decision. ## What Example Shows a Safe Pre-Approval Match Review? Example: One application lists the deceased as “Maria L. Santos.” A second application submitted later lists “Maria Lourdes Santos.” Both show the same date and place of death and the same death-certificate reference, but the applicant names differ. The system flags the records as a possible match. Staff do not reject the second application immediately. An authorized reviewer compares the death record, application references, supporting documents, existing permit status, and submission history. The reviewer determines whether both applications describe the same burial event and records the reason for the decision. This scenario illustrates pre-approval duplicate application review. It does not establish a universal rule that name variation plus a matching date always means duplication. ## What Mistakes Should Civil Registrar Staff Avoid? * Do not reject an application because the name alone looks similar. * Do not merge or delete applications before the authorized review is complete. * Do not treat applicant identity as proof that two burial events are the same. * Do not invent a national similarity percentage or duplicate threshold. * Do not hide conflicting fields from the reviewer. * Do not overwrite the original application when a possible match is found. * Do not let the system administrator make the legal permit decision. * Do not reuse a monthly delay-review workflow for duplicate detection. ## Frequently Asked Questions ### Should two applications with the same deceased person's name be treated as duplicates? No. Staff should compare other death-event facts and source references before deciding that the applications describe the same event. ### What fields are strongest for identifying a potential duplicate? Death-record references, date and place of death, and the full registered name provide strong comparison signals when the LGU holds those records. Staff should use combinations of facts rather than relying on a single field. ### Should a different applicant prevent a duplicate warning? No. Different people may submit records concerning the same deceased person. Applicant information is supporting context, not a final duplicate test. ### Should the system automatically reject a potential duplicate? No automatic rejection rule is supported by the Philippine sources reviewed for this guide. The safer design is to flag the possible match and route it to an authorized reviewer. ### What if the reviewer still cannot decide whether the applications match? Keep the applications intact, document the unresolved fields, and request or verify the additional evidence required under the LGU's current procedure. ### Does the workflow need automatic duplicate detection? No. The Philippine sources reviewed do not require automatic deduplication. An LGU may use search and comparison controls, but potential matches should still follow the authorized review process. ## What Is the Practical Takeaway? Effective duplicate burial permit application detection should identify possible matches before approval without turning similarity into an automatic rejection. Compare authoritative death-event facts, supporting references, applicant context, submission history, and permit status. Let an authorized reviewer classify the match, keep unresolved applications intact, and preserve the reason for the final decision. LGUs reviewing how Civil Registrar records, permissions, and approval workflows should connect in a digital environment can [schedule a GoLGU consultation](https://golgu.ph/get-demo) to discuss system requirements. ## Reference * [Philippine Statistics Authority, Act No. 3753](https://psa.gov.ph/content/act-no-3753) * [Republic Act No. 12254, E-Governance Act](https://lawphil.net/statutes/repacts/ra2025/ra_12254_2025.html) * [OpenCRVS, Deduplication Product Specification](https://documentation.opencrvs.org/v1.8/product-specifications/support-functions/12.-deduplication) ## Disclaimer This guide provides operational workflow and planning guidance for Philippine local government Civil Registrar offices. It does not replace civil registration laws, Philippine Statistics Authority rules, local burial permit procedures, health requirements, legal advice, or other binding authorities. Duplicate-review fields, thresholds, reviewer roles, hold statuses, and final actions should follow the rules and procedures applicable to the specific LGU.