How To Review a Draft Ordinance Before It Reaches First Reading
A draft ordinance should not reach First Reading as a raw idea.
By the time it appears on the agenda, the proposed measure does not need to be perfect. It does not need to have survived committee scrutiny. It does not need to answer every possible objection.
But it should already be clear enough to show what problem it seeks to address, what authority supports it, who will implement it, and what action the Sanggunian is being asked to consider.
Want a ready-to-use system for preparing legislative documents?
I created professional LGU templates designed to help local officials, legislative staff, and government offices prepare clearer, more organized, and more defensible legislative documents.
Individual templates cost ₱199 each. Get the complete toolkit for better value.
This is where pre-First Reading review matters.
The purpose of reviewing a draft ordinance before First Reading is not to prejudge the measure. It is not to bypass the committee. It is not to turn staff review into final approval.
The purpose is more basic:
to make sure the ordinance is ready to enter the legislative process without avoidable confusion.
In legislative work, a weak draft creates friction early. A confusing title leads to unclear referrals. A vague purpose makes committee discussion harder. An unsupported legal basis invites avoidable questions. An unclear implementing office creates problems after approval.
A cleaner draft creates a cleaner deliberation.
First Reading Begins Before the Session
First Reading is often treated as a formal step, and in many ways, it is. The title of the proposed ordinance is read or entered into the record, and the measure begins its formal journey through the Sanggunian.
But the quality of that moment is shaped before the session.
If the draft is unclear before First Reading, the body may already be forced to carry unnecessary confusion into the committee stage. The referral may still proceed, but the committee will have to spend time correcting matters that could have been flagged earlier.
That is not efficient legislative work.
A pre-First Reading review should therefore ask one practical question:
Is this draft clear enough to be formally introduced?
That question is modest, but important. It does not require final agreement. It requires readiness.
Start With the Title
The title is not decoration.
It is the first formal description of the proposed ordinance. It tells the Sanggunian, the public, the Secretariat, the committee, and future readers what the measure is about.
A weak title creates early ambiguity.
Before First Reading, check whether the title answers the following:
- What is the subject of the ordinance?
- What action is being proposed?
- Who or what will be affected?
- Is the title broad enough to cover the provisions?
- Is the title narrow enough to avoid sounding misleading?
A title should not promise more than the ordinance actually provides. It should also not be so vague that the reader cannot identify the subject of the measure.
For example, a title that says only “An Ordinance Promoting Public Welfare” is too broad. Almost every ordinance can claim to promote public welfare.
A better title identifies the concrete policy subject, the mechanism, and the local context.
The title should act as the first control point of the draft.
Identify the Legal Authority
A proposed ordinance should not rely on good intention alone.
Local legislation must still be anchored on legal authority. The Sanggunian exercises local legislative power, but that power must be used within the limits of law, jurisdiction, and public purpose.
This does not mean the draft must become overloaded with citations. It means the drafter should know what authority supports the measure.
Before First Reading, ask:
- What law, code, rule, policy, or mandate supports the proposed ordinance?
- Is the subject within the authority of the LGU?
- Is the Sanggunian the proper body to act on the matter?
- Does the draft appear to conflict with national law or existing local policy?
- Does the matter require consultation with a specific office, sector, or agency?
This is not about pretending to issue a legal opinion. That role belongs to the proper legal office.
The point is to avoid sending forward a draft that has no visible foundation.
A draft ordinance may be improved in committee, but it should not enter First Reading with its legal footing entirely unclear.
Review the Explanatory Basis
The explanatory basis of an ordinance may appear in the whereas clauses, explanatory note, introductory statement, committee background, or supporting documents.
Whatever the format, the function is the same.
It should explain why the ordinance is being proposed.
A strong explanatory basis usually shows:
- the public problem or policy gap;
- the affected sector or community;
- the existing condition that needs correction;
- the public value being pursued; and
- the reason local legislative action is necessary.
The common mistake is to write broad and noble statements without connecting them to a concrete local concern.
Words like “development,” “empowerment,” “welfare,” “protection,” and “governance” are useful, but they are not enough by themselves. They must be connected to the actual problem being addressed.
The draft should make the reader understand:
Why is this ordinance needed here, by this LGU, at this time?
If the answer is not visible, the draft may still be premature.
Need a draft ordinance reviewed before it moves forward?
I help local officials, legislative staff, and government offices review, polish, and structure draft ordinances, resolutions, committee reports, privilege speeches, and official documents before they enter or move through the legislative process.
Reduce avoidable confusion before the document reaches the floor.
Test the Operative Provisions
The operative provisions are where the ordinance does its work.
This is where the draft stops explaining and starts directing. It identifies duties, creates rules, establishes mechanisms, defines prohibitions, authorizes programs, imposes requirements, or assigns responsibility.
Before First Reading, review whether the operative provisions are understandable.
Ask:
- What exactly does the ordinance require, authorize, regulate, prohibit, or establish?
- Who is responsible for implementation?
- What office will lead?
- What offices will support?
- What process must be followed?
- What timeline applies, if any?
- What happens if the ordinance is not followed?
If the ordinance creates duties but does not identify the responsible office, implementation becomes vague.
If it imposes requirements without defining the affected persons or entities, enforcement becomes difficult.
If it creates a program without considering funding, staffing, or administrative capacity, the ordinance may look good on paper but fail in practice.
A draft ordinance should not merely sound important.
It should be administratively readable.
Check for Implementation Gaps
Many weak ordinances fail not because the intention is bad, but because implementation was not thought through.
A pre-First Reading review should therefore look for gaps between policy language and operational reality.
Some common implementation gaps include:
- no lead implementing office;
- no coordination mechanism;
- unclear funding source;
- unclear reporting requirement;
- unclear enforcement mechanism;
- unclear penalties or consequences;
- no transition period;
- no reference to existing programs or offices; and
- no practical way to monitor compliance.
These gaps do not always mean the ordinance should stop.
They mean the draft needs attention before it moves deeper into the process.
A good reviewer does not merely ask whether the provision sounds correct. A good reviewer asks whether the provision can actually be carried out.
Be Careful With Penalties
Penalty clauses require special care.
A penalty should not be inserted casually just to make the ordinance appear stronger. It must be appropriate, enforceable, and legally supportable.
Before First Reading, check whether the draft clearly identifies:
- what specific act is prohibited;
- who may be held liable;
- what penalty may apply;
- who will enforce the ordinance;
- what process will be followed; and
- whether the proposed penalty is within allowable limits.
If these matters are unclear, the penalty provision may create more risk than strength.
In local legislation, forceful language is not the same as enforceable language.
A penalty clause must be precise because it affects rights, duties, enforcement, and public accountability.
Check the Funding Language
A draft ordinance that requires implementation may also require resources.
This does not mean every ordinance must contain a detailed budget. But if the ordinance creates a program, requires personnel action, mandates procurement, establishes incentives, or directs recurring activities, funding must be considered.
Before First Reading, ask:
- Does the ordinance require funding?
- Is there an identified source of funds?
- Will implementation depend on annual appropriations?
- Does the ordinance create obligations that the LGU may not be ready to fund?
- Should the budget office, accounting office, treasurer, or concerned department be consulted?
Poor funding language can weaken even a well-intentioned ordinance.
A measure may have strong policy value, but if the funding mechanism is unclear, implementation may stall after approval.
The draft does not need to solve every budget issue before First Reading. But it should not ignore funding altogether when implementation obviously requires resources.
Match the Draft With the Proper Committee
First Reading usually leads to committee referral.
That is why a pre-First Reading review should also consider committee jurisdiction.
The title, subject matter, purpose, and operative provisions should make it reasonably clear which committee or committees should study the measure.
If the draft involves education, the education committee may be relevant. If it involves health, the health committee may be involved. If it affects appropriations, finance, rules, legal matters, public works, environment, cooperatives, civil service, or local governance, the proper committee alignment must be considered.
Some measures may require joint committee referral.
This is not a minor administrative detail.
A wrong or incomplete referral can delay the process, confuse responsibility, or require later correction.
The cleaner the subject matter, the easier the referral.
Separate Drafting Questions From Policy Questions
Not every issue in a draft ordinance is a drafting issue.
Some questions are policy questions. These belong to the author, sponsor, committee, or Sanggunian.
For example:
- Should the LGU adopt this policy?
- Should the penalty be strict or moderate?
- Should the program be mandatory or optional?
- Should the ordinance cover the entire province, city, municipality, or only a specific sector?
- Should implementation be immediate or phased?
These are not merely grammar questions. They involve judgment, politics, administration, budget, and public policy.
The reviewer should not pretend that a drafting edit can decide everything.
The better approach is to flag the issue clearly.
A useful comment may say:
This provision may require policy direction from the author or committee because it affects implementation scope, funding, and enforcement responsibility.
That kind of comment respects the limits of drafting support while still helping the process move forward.
Do Not Over-Polish a Draft Too Early
There is also a danger on the other side.
A draft can be over-polished too early.
Before First Reading, the goal is readiness, not final perfection. The ordinance may still be referred to committee. It may still be revised. It may still be subjected to hearings, consultations, legal review, budget review, technical comments, and amendments.
The reviewer should therefore avoid treating the draft as if it is already on final reading.
At this stage, focus on the essentials:
- Is the subject clear?
- Is the authority visible?
- Is the purpose understandable?
- Are the operative provisions readable?
- Are obvious implementation gaps flagged?
- Is the draft ready for committee study?
That is enough for pre-First Reading review.
The rest can be refined as the measure moves through the legislative process.
Create a Short Review Note
A pre-First Reading review does not always need a long memorandum.
Sometimes, a short review note is more useful.
The note may contain:
- Subject: What the ordinance is about.
- Purpose: What public concern it seeks to address.
- Legal or policy basis: What authority or policy supports it.
- Implementation points: Which offices, mechanisms, or resources may be involved.
- Issues for committee: What questions should be clarified during study.
- Recommended action: Whether the draft appears ready for First Reading and referral.
This creates a useful paper trail.
It helps the author, Secretariat, committee, and other concerned offices see what has already been checked and what still needs attention.
If the draft later becomes the subject of a committee hearing, the same review note can help convert discussion into a clearer committee report. This is where structured documentation matters, especially when moving from hearing notes to a decision-ready report.
For that stage, you may also read: How To Convert a Committee Hearing Into a Decision-Ready Committee Report .
Want a deeper understanding of legislative writing?
This guide explains the principles behind clear, defensible LGU documentation, including how legislative documents should be framed, structured, reviewed, and refined.
A Simple Pre-First Reading Checklist
For practical use, the review may follow this checklist:
- Title: Is the title clear, accurate, and aligned with the body of the ordinance?
- Purpose: Is the public concern clearly stated?
- Authority: Is the legal or policy basis visible?
- Scope: Who or what is covered by the ordinance?
- Definitions: Are important terms defined when necessary?
- Operative provisions: Are the duties, rules, or mechanisms clear?
- Implementing office: Is responsibility assigned?
- Funding: Is the funding implication considered?
- Penalties: Are prohibited acts and consequences clear?
- Committee referral: Is the proper committee or joint committee reasonably identifiable?
- Review issues: Are questions for committee study clearly flagged?
This checklist will not make the ordinance perfect.
But it can prevent avoidable confusion.
That matters because legislative work is cumulative. A vague title affects referral. A vague referral affects committee work. Weak committee work affects the report. A weak report affects deliberation. Weak deliberation affects the final record.
The earlier the draft is clarified, the cleaner the entire workflow becomes.
Final Thought
Reviewing a draft ordinance before First Reading is an act of discipline.
It does not replace the committee. It does not replace legal review. It does not replace public consultation. It does not replace the judgment of the Sanggunian.
But it protects the process from unnecessary disorder.
A draft ordinance should enter First Reading with enough clarity to be understood, referred, studied, and improved. That is the standard. Not perfection. Not premature approval. Just disciplined readiness.
In legislative work, the quality of the final ordinance often depends on the quality of the first review.
A cleaner draft creates a cleaner deliberation.
Before a proposed ordinance reaches First Reading, it should already have a clear title, visible authority, readable provisions, and a practical path for committee study.
If your office needs help reviewing, polishing, or preparing legislative documents, SPerience can help.
Request Legislative Drafting Support →
Toolkit | Reports | Resolutions | Guide