How Should Planning Offices Verify the Project Value Used in a Zoning Fee Calculation?
Planning offices should verify the project value before a zoning fee calculation by tracing the amount to the current application and supporting cost document, checking that the figure covers the same project scope being assessed, confirming that no newer revision has replaced it, and recording who accepted the value for assessment. At a minimum, the system should capture and require the following fields: source document type, source document reference or file, document revision or version, stated project value, project scope covered, application reference, assessment reference, name or identifier of the responsible verifier, and verification date. This zoning fee project value verification step matters because some local locational-clearance schedules use project cost bands or percentages. A connected set of planning and development workflow records can keep the source value, application, assessment, and later payment reference tied to one transaction.
The software should calculate from an approved input, not decide what the project is worth. Philippine local government units (LGUs) may use different local ordinances, Citizen’s Charters, fee schedules, and documentary requirements. Planning staff therefore need to verify the value under their own current rules before relying on an automated amount.
Why does the project value need verification before a zoning fee is calculated?
A formula can work exactly as configured and still produce the wrong assessment when the input value is wrong, incomplete, outdated, or taken from a different version of the project. The first control is therefore not a mathematical recheck. It is a source check.
Official LGU examples show why this matters. The City of San Fernando, La Union publishes locational-clearance fees that vary by project type and project-cost band. Its schedule uses different thresholds for single residential structures, apartments or townhouses, dormitories, institutional projects, commercial or industrial projects, and special uses. Kabankalan City also publishes sample computations in which the stated project cost directly changes the resulting locational-clearance amount.
Those examples are local, not national fee tables for every LGU. They demonstrate the operational risk: when the applicable local schedule uses project cost, the zoning fee calculation input must come from the correct record before any automated computation can be trusted.
Which document should be treated as the source of the project value?
The source depends on the LGU’s current service requirements. Planning staff should begin with the documents identified by the LGU’s Citizen’s Charter, ordinance, approved fee basis, and application process.
For example, the Municipal Planning and Development Coordinator’s Office of Polanco lists a Bill of Materials or Project Cost Estimate among its locational-clearance requirements. Malolos City’s Citizen’s Charter lists a Bill of Materials signed and sealed by a licensed professional among its locational-clearance requirements. These examples show why project cost estimate verification may begin from a defined supporting document.
A practical project cost estimate verification record should identify the application, source document, document date or revision, stated amount, project scope, responsible verifier, and verification date.
Do not create a new documentary requirement merely because it seems useful. Republic Act No. 11032 requires LGUs to publish service requirements and fees in the Citizen’s Charter. Staff should follow the approved requirements rather than add informal evidence.
How should staff confirm that the value belongs to the same zoning application?
Match the source document to the exact application before copying or accepting the amount. The project location, owner or applicant reference, project type, drawing or plan set, and transaction number should be consistent with the planning record.
This prevents a common record problem: a valid cost estimate from one version, phase, building, or property being used in another assessment. The value may be genuine, but it is not the correct value for that transaction.
The locational clearance project cost should also match the scope currently under review. If the application covers a new building, the supporting amount should correspond to that project. If the application concerns an alteration or expansion and the applicable local rule assesses only the affected area or cost, staff should follow that local rule and verify that the source value covers the same affected scope.
What should happen when the applicant submits a revised project cost?
A revised amount should create a new record event instead of silently replacing the earlier value. Planning staff should preserve the previous figure, identify the new document, record the reason for the revision when available, and show which value became active for assessment.
In GoLGU, each project value revision should trigger an update workflow that logs the new document, links it clearly to the current application and specific assessment, and marks the effective status of all submitted values. The system should maintain a chronological revision history that records the date and time of each submission, the source document details, and the user or staff member making the change. All previous values and their supporting documents remain accessible and are never overwritten or deleted. GoLGU should display revision history in an audit-friendly view, showing which value was active at each step, who confirmed or accepted each revision, and the reason or context for any changes if provided. When viewing an assessment, users should be able to see the progression of project values, jump to the corresponding source files, and confirm which input drove the automated calculation for any particular result. This approach supports transparent, traceable, and auditable zoning fee workflows.
This is especially important when the revised amount crosses a fee band. A change from one project-cost range to another may legitimately change the fee under a local schedule. The key question is not whether the new amount creates a higher or lower charge. The question is whether the revised value is supported by the current application record and accepted under the office’s procedure.
The planning fee assessment history should make the sequence understandable:
Original project value received
Initial source document identified
Revised value submitted or confirmed
Previous value marked as superseded for the current assessment, without deleting it
New source linked to the application
Assessment recalculated from the active value
This creates a traceable planning fee assessment without turning the system into the authority that decides which applicant value is legally acceptable.
How should staff handle a value that does not match the project scope?
Stop the assessment and resolve the mismatch before calculation. Do not adjust the number merely to make it fit the expected fee band.
Suppose a commercial building application covers the full proposed structure, but the submitted cost document appears to cover only one construction phase. If the local process requires the value for the full project being assessed, the figure may be incomplete. Conversely, an alteration application may contain a whole-building value even though the applicable local schedule refers to the affected area or cost only.
Staff should record the mismatch, identify the missing or conflicting information, and route the application according to the LGU’s approved procedure. The office responsible for the zoning or locational-clearance evaluation should decide what evidence is sufficient under the current local rules.
In GoLGU, the system should automatically flag any detected project value mismatches, such as discrepancies between the project scope and the submitted amount or conflicting information between multiple documents. When a mismatch is identified, GoLGU should log the event with details of the issue, associated application, and relevant user actions. The system should then escalate or route the flagged application to the designated planning staff or authorized reviewer based on the LGU’s defined workflow. Automated notifications can prompt responsible personnel to review and resolve the conflict, helping ensure compliance with standard procedures and creating an audit trail for all mismatches or exceptions.
How can staff verify the calculation input without repeating the whole fee formula?
The goal of this article is narrower than a full calculation regression test. Planning staff are checking whether the value entering the calculation is defensible and current.
Before the system calculates, confirm:
the correct application is open
the correct project type or fee category is selected under the local rule
the active project value comes from the required source
the value covers the correct project scope
the latest accepted revision is being used
the amount is stored in the correct unit and field
the verifier and verification date are recorded
After those checks, the application can proceed to the configured fee calculation. Separate testing should be used when the LGU needs to prove that a new or revised formula itself behaves correctly across thresholds, exceptions, rounding, or effective dates.
What does a practical zoning fee project value verification scenario look like?
Consider a fictional LGU processing a commercial locational-clearance application. The first submitted cost estimate states ₱1.9 million. Before the assessment is finalized, the applicant submits a revised signed cost document showing ₱2.2 million because additional work was added to the project scope.
The planning evaluator does not manually change the amount in the fee field and discard the first document. The evaluator links the revised document to the same application, confirms that it covers the updated project scope, marks the earlier value as superseded for the active assessment, and records the accepted amount and verification date.
If the LGU’s current schedule places ₱1.9 million and ₱2.2 million in different fee treatments, the automated result may change. That change is explainable because the record shows which source value drove the calculation. The scenario demonstrates zoning fee project value verification; it does not establish a national fee amount or require another LGU to use the same bands.
What should the digital record preserve for later review?
The digital record should let an authorized reviewer reconstruct why a particular value was used without searching through unrelated folders or messages. Preserve the application reference, active project value, source document, revision history, project scope, fee category or service type, verifier, verification date, calculated amount, and later correction history.
Republic Act No. 12254, the E-Governance Act, covers LGUs and promotes integrated digital government services. It does not prescribe a zoning-fee project-value form. For this workflow, the useful principle is record continuity: the source value and the resulting government transaction should remain traceable within the LGU’s approved digital process.
GoLGU publicly describes Planning & Development functions that include computerized evaluation, auto-calculation of payments, and zoning-clearance and development-permit applications. Those functions can support the record flow, but the LGU’s current ordinance, Citizen’s Charter, fee schedule, and authorized personnel still determine the proper source value and applicable charge.
How does GoLGU fit into project value verification?
For this workflow, GoLGU’s role is to support connected planning records and configured assessment processing. The system can help keep the application, source documents, evaluation, payment calculation, status, and transaction history in one managed process. It should not be described as deciding the lawful project value or replacing the professional and administrative review required by the LGU.
Before configuring the workflow, the planning office should identify the accepted source for the locational clearance project cost, the user role that verifies it, how revisions are handled, and which value becomes active for calculation. Those decisions come from the LGU’s own approved procedure.
To support clear permissions and workflow configuration, map GoLGU user roles to specific actions in the verification process. For example, the 'Applicant' submits the project value and supporting documents. The 'Evaluator' reviews the submission for completeness and matches the project scope. The 'Verifier' checks the accuracy of the source document, confirms the project value against requirements, and formally accepts or flags the amount. If a revision is submitted, the 'Evaluator' or 'Assessment Approver' logs the new document and records the reason for the change. An 'Administrator' or 'Records Officer' maintains the revision history and ensures all relevant information is accessible for later review. This approach helps analysts configure user permissions and approval steps effectively within GoLGU or similar systems.
Teams that want to map this verification point into their planning workflow can request a GoLGU workflow consultation. Bring one current locational-clearance process, the project-value source document, and one example where the amount changed before assessment.
Sample Configuration Scenario:
For example, in GoLGU, the project value verification workflow can be set up with the following configuration:
Field Configuration:
Project Value Source Document Type (e.g., Bill of Materials, Cost Estimate)
Source Document Reference or File Upload
Document Revision or Version Number
Stated Project Value (numeric field)
Covered Project Scope (text or dropdown)
Application Reference Number
Assessment Reference Number
Verifier Name or Staff Identifier
Verification Date
Workflow States:
Applicant submits the project value and source document.
Evaluator checks for completeness and matches the project scope to the application.
Verifier confirms the accuracy, checks compliance, and accepts or flags the value.
If a revised value is submitted, the workflow logs the new document, preserves the previous input in the revision history, and marks the active value.
Assessment Approver or Reviewer finalizes the project value for calculation, and the fee is recalculated as needed.
The system maintains an auditable log showing who performed each step, document versioning, and any notes on the change.
This setup enables staff to trace each project value entry, maintain revision control, and preserve a clear audit trail for all workflow actions.
Frequently Asked Questions
Is the applicant’s declared project value always enough for zoning fee calculation?
No. Use the source required by the LGU’s current process. If the approved procedure requires a bill of materials, project cost estimate, or another record, verify that source before assessment.
Should the system automatically use the newest project value it receives?
Not without a defined workflow. A new amount should be linked to the application, checked against the project scope, and accepted by the responsible role before it becomes the active zoning fee calculation input.
What if two documents show different project costs?
Do not choose the convenient number or average the amounts. Identify which documents are current, determine what each value covers, and route the conflict to the authorized planning role under the LGU’s procedure.
Can planning staff use the building permit project cost instead?
Only when the applicable zoning process recognizes that source or the LGU’s approved workflow requires the comparison. Do not substitute a value from another government record without confirming that it represents the input required for the zoning charge.
Does a revised project value require deleting the old assessment input?
No. Preserve the earlier value and its source in the history, then identify the accepted replacement and recalculate from the active value. This keeps later review understandable.
Does GoLGU determine which project value is legally correct?
No. GoLGU can support connected records and configured calculations. The LGU’s current rules, source documents, authorized evaluators, and applicable fee schedule control the assessment basis.
Conclusion
Reliable zoning fees begin with a reliable value. Planning staff should trace the project amount to the correct application and supporting source, confirm that it covers the same project scope, preserve revisions, resolve conflicting figures, and record who accepted the active value before calculation. This zoning fee project value verification creates a clear link between the source document and the resulting assessment without turning software into the authority for the project value.
References
Republic Act No. 11032, Ease of Doing Business and Efficient Government Service Delivery Act of 2018
City of San Fernando, La Union Citizen’s Charter: Locational Clearance/Zoning Compliance Certificate
Municipality of Polanco, Office of the MPDC: Locational Clearance Requirements
Kabankalan City Planning and Development Office Citizen’s Charter
Disclaimer
This guide provides general operational information for Philippine LGUs. Each planning office should confirm its current zoning ordinance, Citizen’s Charter, fee schedule, documentary requirements, delegated authority, and applicable legal and audit rules before changing a zoning assessment process.