How To Clarify a Position-Creation Ordinance Before It Becomes a Compliance Problem
A position-creation ordinance may look simple on paper. It creates positions, assigns salary grades, identifies the office where the positions will be placed, states the source of funds, and provides duties and responsibilities.
But in local legislation, personnel measures are never just about titles and salary grades. They sit at the intersection of legislative authority, civil service rules, budget discipline, plantilla structure, appointment process, and institutional accountability.
This is why a position-creation ordinance must be drafted with unusual precision.
A single unresolved phrase can create a compliance question later. A single unclear mechanism can affect qualification standards, appointment treatment, budget impact, incumbency, and the relationship between the elected official’s office and the permanent Secretariat.
Provincial Ordinance No. 531-2026 of the Province of La Union provides a useful case study. It creates fourteen Senior Administrative Assistant III positions with Salary Grade 15 and fourteen Administrative Aide VI positions with Salary Grade 6 under the plantilla of the Office of the Sangguniang Panlalawigan. It also recognizes the existing Private Secretary I positions, Salary Grade 11, and Administrative Aide III / Clerk I positions, Salary Grade 3, which are to be abolished upon vacancy.
This article is not about personalities.
It is about legislative precision.
This discussion is not a legal ruling on the validity of the ordinance. It is a drafting and compliance analysis focused on whether the text is clear, internally consistent, and implementation-ready.
The analysis is based only on the text of the ordinance as a legislative document and does not impute bad faith, irregularity, or improper motive to any author, sponsor, office, or approving authority.
If you are new to this kind of systems-based legislative review, you may also read my earlier article, Start Here: Legislative Systems and Workflow Guide.
The first question: is the measure creating, upgrading, reclassifying, or replacing positions?
The ordinance appears to pursue a legitimate staffing objective: to strengthen the support capacity of the offices of the Sangguniang Panlalawigan Members.
In substance, the movement appears to be this:
- Private Secretary I, Salary Grade 11, moving toward Senior Administrative Assistant III, Salary Grade 15;
- Administrative Aide III / Clerk I, Salary Grade 3, moving toward Administrative Aide VI, Salary Grade 6.
That is a significant improvement in staffing level.
The drafting issue, however, is whether the ordinance clearly treats this as:
- the creation of entirely new positions;
- the upgrading of existing positions;
- the reclassification of existing plantilla items;
- the conversion or replacement of existing items while old positions are phased out;
- the creation of replacement positions while old positions are abolished upon vacancy; or
- a combination of these mechanisms.
Those are not the same.
If the intention is to create additional positions, the ordinance must justify the additional personnel complement and funding requirement.
If the intention is to upgrade existing positions, the ordinance must address the treatment of incumbents, qualification standards, applicable classification rules, budgetary consequences, and plantilla adjustment.
If the intention is to reclassify existing positions, the ordinance must be especially careful. Reclassification, particularly where filled LGU positions are involved, raises restrictions under DBM rules and must not be used loosely as a generic term for salary-grade improvement.
If the intention is to convert or replace existing positions while old positions are abolished upon vacancy, the ordinance must state the transition mechanism clearly.
Without that clarification, the measure may be read in more than one way.
That is where implementation problems begin.
Need your ordinance draft to stand up to scrutiny?
I review and prepare ordinances, resolutions, committee reports, and legislative documents with clear structure, traceable logic, and defensible wording—so your measure holds up during review, implementation, and future reference.
Avoid ambiguity. Protect the institution.
“Creation” is not the same as “upgrading”
In legislative drafting, the word create carries weight.
To create a position means to establish a new plantilla item. It suggests that the position did not previously exist.
To upgrade a position means to elevate an existing position to a higher classification or salary grade, usually because the duties, responsibilities, or organizational needs have changed.
To reclassify a position means to change the position title, level, or classification based on the nature of the work and applicable standards.
To convert a position means to abolish an existing item and create the appropriate position in its place, usually when the existing vacant item no longer matches the required title, level, or work structure.
To abolish upon vacancy means the old position continues to exist until it becomes vacant.
These terms should not be treated as interchangeable.
DBM Budget Circular No. 2018-3 is instructive on this point. It treats reclassification, conversion, abolition, and creation as distinct personnel actions. It also warns against using reclassification language loosely. Where filled LGU positions are involved, reclassification is subject to specific restrictions under applicable DBM rules and Section 325(f) of Republic Act No. 7160. Where vacant regular positions require changes in position titles, the relevant mechanism may be conversion, which is effected by abolishing the old item and creating the appropriate position in its place. Read DBM Budget Circular No. 2018-3 →
This reinforces a practical drafting point:
A position-creation ordinance should clearly state whether it is creating new plantilla items, converting vacant items, replacing old positions, or establishing a transition mechanism for positions to be abolished upon vacancy.
A measure that says it is creating new positions while also saying older positions will be abolished only upon vacancy creates a transition question:
Will the old and new positions coexist for a period of time?
If yes, that should be expressly justified and funded.
If no, the ordinance should be drafted using the mechanism that accurately reflects the intended personnel action, whether that is creation, conversion, abolition, replacement, or another legally supportable route.
The text must match the intended administrative action.
Want a ready-to-use system for reviewing legislative documents?
I created professional LGU templates designed to help you prepare clearer, more defensible resolutions, committee reports, and legislative documents.
Individual templates cost ₱199 each (₱398 total). Get both for ₱349.
Local legislative power exists, but it must be exercised with structure
The Local Government Code of 1991 recognizes the authority of local government units to design and implement their own organizational structure and staffing pattern, subject to minimum standards and guidelines prescribed by the Civil Service Commission.
The Sangguniang Panlalawigan also has authority over positions, salaries, wages, allowances, and other emoluments of officials and employees paid wholly or mainly from provincial funds.
That power is real.
But it is not free-floating.
It must operate within civil service rules, budget limitations, plantilla standards, and proper position classification.
A personnel ordinance must therefore answer not only what position do we want? but also what legal and administrative mechanism are we using?
For reference, the Civil Service Commission issued the 2022 Guidelines and Standards in the Establishment of Organizational Structures and Staffing Patterns in Local Government Units.
DBM issuances also support this discipline. The DBM Manual on Position Classification and Compensation provides that LGU positions are classified based on duties and responsibilities, and that LGUs are guided by the Index of Occupational Services, Position Titles, and Salary Grades and by class specifications when classifying positions. Read DBM Manual on Position Classification and Compensation, Chapter 9 →
Local Budget Memorandum No. 90 likewise reminds LGUs that positions should be allocated to their proper position titles and salary grades in accordance with the IOS-LGU and that LGUs should conform with CSC MC No. 12, s. 2022. Read DBM Local Budget Memorandum No. 90 →
This means that a local ordinance should not treat position titles, salary grades, duties, and appointment treatment as separate drafting details. They must align.
A legislative measure without structure is vulnerable.
Even a valid policy objective can become difficult to implement when the text does not clearly state the legal mechanism, transition rule, funding basis, and institutional safeguards.
The danger of mixing confidential logic with career-service duties
Another issue arises when an ordinance classifies positions as primarily confidential while assigning duties that are largely technical, administrative, legislative, or clerical.
This matters because the phrase primarily confidential is not merely descriptive. It has legal consequences.
The Civil Service Commission has issued guidelines on determining positions in LGUs as primarily confidential. These guidelines are intended to distinguish positions that genuinely require close intimacy and trust from positions that are ordinary career-service positions in substance.
For reference, see CSC Memorandum Circular No. 12, s. 2011 on the determination of positions in LGUs as primarily confidential.
In the ordinance being discussed, the Senior Administrative Assistant III functions include legislative research, drafting resolutions and ordinances, preparing privilege speeches and policy briefs, assisting in committee meetings and hearings, proofreading agenda and journals, preparing minutes, tracking referrals, and coordinating with the SP Secretariat.
The Administrative Aide VI functions include records management, document routing, encoding, clerical work, frontline assistance, logistical support, and preparation or processing of financial documents.
These may be necessary functions.
But they also raise a classification question.
If the positions are primarily confidential, the ordinance should explain why the nature of the work requires that classification.
If the positions are career or technical support positions, the ordinance should avoid overstating confidential status.
The safe drafting principle is simple:
A position’s classification should follow its actual duties.
This principle is not only a civil service issue. It is also a DBM classification issue. If the duties are technical, administrative, legislative, clerical, or records-related, the position title and salary grade should be tested against the appropriate position classification standards and IOS-LGU references.
Coterminous status should not be used as shorthand for qualification-standard exemption
Another technical point is the difference among coterminous status, primarily confidential status, and qualification standards.
Coterminous status generally refers to the duration or tenure of the appointment. It may be tied to the tenure of the appointing authority, the head of office, the lifespan of an agency, a project, or a specific period.
Primarily confidential status refers to the nature of the position. It is concerned with whether the duties require close intimacy and personal trust between the appointee and the official served.
Qualification standards refer to education, training, experience, eligibility, competency, and other requirements attached to a position.
These concepts are related, but they are not identical.
Under the 2025 Omnibus Rules on Appointments and Other Human Resource Actions, appointees to primarily confidential or personal staff positions are generally exempt from qualification requirements, except where the position is governed by specific legal qualifications or involves the practice of a regulated profession requiring the appropriate license.
This is why a position-creation ordinance should be careful in its wording.
If the ordinance treats the positions as primarily confidential, it should clearly justify why the actual duties require that classification.
If the ordinance requires appointees to meet prescribed qualification standards, it should clarify whether those standards are mandatory legal or CSC-approved requirements, preferred internal qualifications, or requirements arising from law or professional regulation.
The ordinance should avoid saying one thing in the explanatory portion and another thing in the operative section.
If one part of the ordinance suggests exemption from qualification standards while another part requires full compliance with prescribed qualification standards, the text creates an internal conflict.
The safe drafting principle is simple:
A position’s tenure classification, confidential character, and qualification-standard treatment should be stated consistently.
The ordinance should not leave HR, the appointing authority, or the Civil Service Commission to reconcile conflicting language later.
Want to quickly spot common legislative writing errors?
A visual framework can help you identify inconsistencies in structure, wording, legal basis, classification, and implementation logic.
The “next-in-rank” clause should be used carefully
The phrase next-in-rank also requires caution.
Next-in-rank language belongs to a career progression and promotion framework. It makes sense when a lower position is part of an established career path toward a higher position.
But when positions are coterminous or primarily confidential, next-in-rank language becomes more delicate.
Confidential and coterminous appointments are not ordinary career ladder appointments. They are tied to tenure, trust, confidence, or the appointing and recommending authority.
If an ordinance says Administrative Aide VI, Salary Grade 6, is next-in-rank to Senior Administrative Assistant III, Salary Grade 15, it should explain the basis for that relationship.
That is a wide salary grade gap.
If the intention is to establish a real promotion path, then the position classification, qualification standards, and appointment rules must support it.
If the intention is merely to identify office hierarchy, the ordinance should use different wording.
The DBM Manual on Position Classification and Compensation also treats salary grade as tied to the level of difficulty and responsibility of work. This supports the need to explain wide gaps in salary grade, especially when the text appears to imply a career relationship between two positions.
A safer formulation may be:
The Administrative Aide VI shall provide administrative and clerical support to the concerned office and shall assist the Senior Administrative Assistant III in the performance of support functions, without prejudice to applicable civil service rules on appointment and promotion.
That avoids importing promotion concepts where they may not properly apply.
Funding clauses must do more than say “chargeable against Personnel Services”
A position-creation ordinance is also a budget measure.
It creates recurring obligations.
That means the funding section should do more than say salaries and benefits shall be charged against Personnel Services.
A strong funding clause should answer several questions:
- What is the total annual cost of the new or upgraded positions?
- What salary step is being used?
- Are mandatory benefits included?
- Is the amount covered by the annual budget or a supplemental budget?
- Is there certification of fund availability?
- Will the LGU remain within the statutory Personnel Services limitation?
- What is the fiscal effect of abolishing old positions only upon vacancy?
DBM Local Budget Circular No. 145 reinforces this point by providing guidelines on the implementation of Personnel Services limitation on local government budgets and the determination of waived PS items. Its worksheets require attention to total annual PS budget, income base, PS limitation, benefits, contributions, and additional allowable PS budget or excess over the PS limitation. Read DBM Local Budget Circular No. 145 →
DBM Local Budget Circular No. 165 is also relevant because it provides that the salary of a new hire shall correspond to Step 1 of the salary grade allocation of the position in the salary schedule adopted by the LGU. This is why the salary-step question should not be left to assumption when a personnel measure creates new or replacement positions. Read DBM Local Budget Circular No. 165 →
This is why a thin funding clause is risky.
It may appear sufficient at first glance, but it can leave unanswered questions during implementation, budget review, appointment processing, or audit.
This connects with a broader documentation problem I discussed in How To Diagnose and Fix Payroll Friction in Job Order Workflows: when funding, process ownership, and documentation are unclear, friction becomes predictable.
Transition clauses protect the plantilla from confusion
If the intention is to move from Private Secretary I, SG 11, to Senior Administrative Assistant III, SG 15, and from Administrative Aide III / Clerk I, SG 3, to Administrative Aide VI, SG 6, then the ordinance should contain a clear transition clause.
That clause should answer:
- Are the new positions additional or replacement positions?
- What happens to current incumbents?
- Will incumbents be automatically appointed, considered, evaluated, or left in their current positions until vacancy?
- Will the existing positions be abolished immediately, upon vacancy, or upon assumption into the new positions?
- Will there be no impairment of vested rights?
- Will the plantilla reflect both old and new positions during the transition?
- How will the Province fund the overlap, if any?
This is not a minor drafting detail.
It determines whether the ordinance is financially and administratively coherent.
DBM Budget Circular No. 2018-3 makes this more concrete because it distinguishes reclassification from conversion. Item 4.9 provides that reclassification does not apply to vacant regular positions that require changes in position titles; instead, conversion is effected by abolishing the old items and creating the appropriate positions in their stead. This means that when a vacant position needs a different title because the work or organizational need has changed, the appropriate mechanism may not be casual wording about “upgrading.” It may require abolition of the old item and creation of the proper item in its place, subject to applicable rules. Read DBM Budget Circular No. 2018-3, Item 4.9 →
The same circular also states that reclassification of filled positions in local government units is prohibited in view of Section 325(f) of Republic Act No. 7160, which is why LGU personnel ordinances should avoid using reclassification language loosely.
Without a transition clause, the measure can be read as both an upgrade and an expansion. That is exactly the kind of ambiguity that legislative drafting should avoid.
Institutional duties must not blur Secretariat authority
Staff assigned to individual members of the Sangguniang Panlalawigan may validly assist in legislative work.
They may conduct research. They may prepare drafts. They may assist in committee documentation. They may coordinate with stakeholders. They may monitor referrals. They may prepare briefing materials.
But the ordinance should be careful when assigning duties involving official agenda, journals, minutes, committee documentation, and institutional records.
Those functions touch the authority of the SP Secretariat and the Office of the Secretary to the Sangguniang Panlalawigan.
The staff of an individual member may assist.
The Secretariat should retain institutional custody and control.
The committee should retain deliberative authority.
The SP Secretary should retain official records responsibility.
A simple saving phrase can prevent confusion:
in coordination with, and without prejudice to the official functions and records custody of, the Office of the Secretary to the Sangguniang Panlalawigan.
That kind of phrase protects the institution.
The same logic applies to committee documentation. A hearing may produce information, but the record must still be converted into a defensible report. I explained this process in 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—not just the format.
The repealing clause should not overclaim
Another overlooked technical issue is the repealing clause.
Some ordinances still use broad language stating that all laws, decrees, executive orders, rules, and regulations inconsistent with the ordinance are repealed, amended, or modified.
That language is too broad for a provincial ordinance.
A provincial ordinance cannot repeal national laws, presidential decrees, executive orders, CSC rules, DBM issuances, or national implementing rules.
It can only repeal or modify local ordinances, resolutions, rules, or issuances within the authority of the province.
This point becomes more important when the ordinance concerns personnel, salary grades, and plantilla structure because DBM and CSC issuances operate within the national framework for position classification, compensation, appointment, and staffing standards.
A cleaner clause would say:
All provincial ordinances, resolutions, rules, issuances, or parts thereof inconsistent with this Ordinance are hereby repealed, amended, or modified accordingly, subject to applicable national laws, rules, and regulations.
That is more accurate.
It respects hierarchy.
It avoids legislative overreach.
The real issue is alignment
The weakness of a position-creation ordinance is not always the policy objective.
The policy objective may be valid.
Legislative offices need competent staff. Board Members need technical assistance. Committee work requires research. Constituency service requires coordination. Documentation work requires discipline. Public offices cannot function on titles alone.
The real issue is alignment.
- The title must align with the body.
- The explanatory note must align with the operative provisions.
- The classification must align with the duties.
- The appointment rule must align with qualification standard treatment.
- The salary grade must align with the appropriate position classification standard.
- The funding clause must align with budget reality.
- The transition clause must align with plantilla consequences.
- The Secretariat support functions must align with institutional authority.
- The local ordinance must align with applicable CSC and DBM issuances.
When these do not align, the ordinance may still look complete, but implementation becomes vulnerable.
In another article, I discussed how precise observation protects the legislative record. The same principle applies here: the clearer the text, the fewer assumptions future implementers must make. Read: How To Protect the Legislative Record Through Precise Observation.
A simple test for position-creation ordinances
Before a position-creation ordinance is finalized, the drafter should ask these eleven questions.
- What exact positions are being created, upgraded, reclassified, converted, or replaced?
- Are the positions career, coterminous, primarily confidential, or personal staff?
- Do the duties justify the classification?
- Are the position titles and salary grades aligned with the IOS-LGU and applicable DBM classification standards?
- Do qualification standards apply or not?
- Who is the appointing authority?
- Who recommends the appointment?
- What is the total funding requirement?
- Is there certification of fund availability and compliance with Personnel Services limits?
- What happens to existing positions and incumbents?
- Does the ordinance preserve the institutional authority of the office responsible for official records and documentation?
If the ordinance cannot answer these questions clearly, it is not yet implementation-ready.
Precision is not obstruction
In government, technical clarification is sometimes misunderstood as opposition.
It should not be.
Clarifying a personnel ordinance is not an attack on its policy objective. It is a way of protecting the ordinance from avoidable defects.
Precision protects the author.
Precision protects the approving body.
Precision protects the appointing authority.
Precision protects HR.
Precision protects the budget office.
Precision protects the employees.
Precision protects the institution.
A position-creation ordinance creates more than jobs. It creates a continuing administrative structure.
That structure must be legally defensible, financially supported, and operationally clear.
In legislative writing, the question is not only:
Can we create this position?
The better question is:
Can this position survive review, implementation, audit, and future transition without confusion?
That is where legislative drafting becomes more than wording.
It becomes institutional protection.
Next Action Steps
For any LGU office preparing or reviewing a position-creation ordinance, the practical move is to require a compliance matrix before final approval.
The matrix should show:
- position title;
- salary grade;
- salary step assumption;
- nature of appointment;
- civil service classification;
- qualification standard treatment;
- duties and responsibilities;
- appointing authority;
- recommending authority;
- funding source;
- annual cost;
- effect on Personnel Services limitation;
- effect on existing plantilla items;
- effect on incumbents;
- whether the action is creation, reclassification, conversion, upgrading, or replacement; and
- applicable CSC, DBM, and Local Government Code basis.
This does not need to be complicated.
But it must be written.
Because once a measure reaches implementation, verbal assumptions no longer protect the institution.
Only the text does.
Mastering this kind of review does not just improve one document. It positions you as someone who can see the system behind the text. That is how legislative writing becomes leverage.
Legislative precision is not cosmetic—it is protection.
A clear ordinance can mean the difference between smooth implementation and avoidable compliance confusion.
If your draft still leaves classification, funding, transition, or institutional authority unclear, the risk is already in the text.