Assistant Commissioners Court Coordinator
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those headings if applicable. However we can also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those exact headings when we have content. But we can also have other headings? Probably we should stick to those headings where appropriate. Let's map content:
- About the role: we have description about the district and what you will do. Could combine "About Harris County Flood Control District" and "What you will do". So we can put under About the role
a paragraph(s) describing mission, jurisdiction, and duties.
- Responsibilities: we have "Essential Functions and Duties" with subpoints. So we can put under Responsibilities
a - list.
- Requirements: we have Education, Experience, Licensure, Knowledge Skills, and Abilities. Also note about documentation. So
Requirements
with .
- Qualifications/Skills: maybe combine with Requirements? But we have separate "Knowledge Skills, and Abilities". Could put under Skills
or Qualifications
. The instruction list includes Qualifications and Skills as possible headings. We could split: Requirements for education/experience/licensure, Skills for KSAs. But we can also combine. However they said prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section? But they gave examples of headings; we can choose to use Requirements and Skills separately if we have content. Let's see: we have Education, Experience, Licensure under Requirements. Then Knowledge Skills, and Abilities under a separate heading. Also Preferences. So we could have:
Requirements
(education, experience, licensure)
Skills
(knowledge, skills, abilities)
Preferences
(preferred education, experience, etc.)
We also have General Information: Position Type, Salary, Location, Physical Demands etc. That could be split into Pay, Schedule, Benefits? But we have no benefits or pay specifics (salary: To be discussed at interview). That's not specific, so we should NOT create Pay or Benefits sections because they are not specific (they say "To be discussed at interview" which is vague). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states "Salary: To be discussed at interview" which is not a specific amount, so we should not create Pay section. Schedule: Position Type, Salary: Regular | Full-Time. That indicates schedule: Full-Time. That's specific enough? It says Regular | Full-Time. That is a schedule. So we could create a Schedule
with content "Regular, Full-Time". However they said prefer few substantive sections over many thin ones. But schedule is a specific piece. Could also include under General Information as a paragraph. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. Schedule is specific: Full-Time. So we can include Schedule.
Location: we have location address. Could be part of General Information but we could put under a Location
but not in the list of allowed headings. The allowed headings list does not include Location. But we could still use for other headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Likely we can use other headings as needed, but they gave examples of typical sections. Safer to stick to those headings; we can embed location in a paragraph under About the role or under a generic
. But we need to preserve all substantive information. We could put location in a
after About the role.
Physical Demands etc: could be omitted? It's substantive but not fitting headings. Could be placed under a
maybe under a section like "Working Conditions". Not in list. Might be okay to include as a
after Schedule.
We must remove boilerplate: EEO link, accommodation phone, criminal history check, etc. Also remove "If you need special services..." etc. Also remove "NOTE: Qualifying education..." etc? That is part of requirements; we should keep it? It's a note about documentation; it's substantive but maybe we can keep as part of Requirements. It's not boilerplate. Keep.
Also remove "Preferred Education:" etc under Preferences.
We must not repeat job title as heading.
We must not put Job ID/requisition numbers as headings (none present).
We must output only HTML fragment.
Let's craft:
About the role
The Harris County Flood Control District reduces flood risk in Harris County, the third most populated U.S. county (over 4.7 million residents, including Houston, the nation’s fourth largest city). The District manages about 1,500 channels totaling nearly 2,500 miles, more than 60 regional stormwater detention basins (>10,000 acres), and several wetlands mitigation banks.
The Assistant Commissioners Court Coordinator supports the coordination and administration of Commissioners’ Court agendas, ensuring information, records, and agenda materials are organized, accurate, accessible, and processed efficiently. Duties include coordinating documents and deadlines, assisting with records retrieval and public information requests, and providing operational support to the Commissioners Court Coordinator and Public Information Officer as needed.
Responsibilities
- Support preparation of the Commissioners Court agenda and Request for Court Action (RCA) workflow: documenting court requests, retrieving historical records, gathering supporting documentation.
- Maintain and organize approved agenda RCA’s and record final agenda actions in internal District systems.
- Act as backup for the Agenda Team, supporting agenda and RCA workflow processes.
- Research, compile, and organize agenda information to assist in preparing Commissioners Court agenda briefings and facilitate discussion.
- Attend and handle RCA and CC Briefing meetings with Executive staff as needed.
- Coordinate with the Office of County Administration for agenda‑related questions, clarification, and assistance.
- Work with other personnel to address court‑related questions or concerns.
- Cross‑train in Commissioners Court agenda and open records processes to provide backup coverage during staff absences or increased workload.
- Assist the Public Information Officer and Records Team by processing Public Information Act requests and related records management activities.
- Assist with records retrieval, document organization, and filing of responsive records.
- Maintain records in the Harris County enterprise GovQA system and other applicable document management systems.
- Perform general administrative and records‑related duties to support Public Information and Records functions.
- Attend seminars, conference workshops, and other training programs.
- Assume additional responsibilities as required to meet the District's evolving demands.
Requirements
- High school diploma or G.E.D. equivalent from an accredited educational institution.
- Experience preparing agenda packets, coordinating agenda submissions, and managing agenda‑related documentation.
- Valid Class "C" Texas Driver’s License.
Skills
- Excellent organizational, analytical, and time‑management skills.
- Strong written and verbal communication skills with attention to detail.
- Proficient in using databases, spreadsheets, and digital document management tools.
- Skilled in handling sensitive information with a high degree of discretion.
- Knowledge of the Texas Public Information Act and related compliance requirements.
- Familiarity with legal and governmental documentation standards.
- Ability to work independently and collaboratively across departments.
Preferences
- Preferred Education: Bachelor’s degree in Public Administration, Business Administration, Communication, Legal Studies, or a related field from an accredited college or university.
- Preferred Experience: Minimum of five (5) years of progressive experience in records management, governmental operations, or a related administrative or legal field.
- Preferred: Experience with enterprise records tracking databases or workflow automation tools.
- Preferred: Knowledge of Commissioners Court agenda, Request for Court Action (RCA) processes, and related documentation requirements.
Schedule
Regular, Full‑Time.
Location: Executive Support Services, 9900 Northwest Freeway, Houston, TX 77092.
Physical demands: occasional stooping, bending, reaching, lifting, and carrying items up to 11 lb, occasional lifting up to 20 lb; occasional sorting, filing, shelving, handling of files, documents, books, file drawers, and related equipment; prolonged sitting; occasional ascending/descending stairs; occasional driving of a vehicle with automatic controls. Work performed indoors in a normal office environment with acceptable lighting, temperature, air conditioning, and noise levels.
We must ensure we didn't include any boilerplate like EEO, accommodation, criminal history check, drug screen note, etc. We removed those. Also removed "If you need special services..." etc. Also removed "This position is subject to a criminal history check." etc. Also removed "Due to a high volume of applications..." etc. Also removed "NOTE: Qualifying education, experience, knowledge, and skills must be documented on your job application." Actually that note is part of requirements; we might keep it? It's not boilerplate; it's an instruction to applicants. It's substantive. Should we keep? It says: "NOTE: Qualifying education, experience, knowledge, and skills must be documented on your job application. You may attach a resume to the application as supporting documentation but ONLY information stated on the application will be used for consideration. 'See Resume' will not be accepted for qualifications." This is important for applicants. We should keep it. Where to place? Could be under Requirements as a paragraph after the list. Let's add a after the Requirements list.
Similarly, we might keep "Preferred Education:" etc under Preferences; we already have.
We also need to keep "General Information Position Type, Salary: Regular | Full-Time Salary: To be discussed at interview Location: ..." We already captured Schedule and Location. Salary: To be discussed at interview - we should not create Pay section because not specific. We could mention salary in a paragraph under About the role or Schedule? But instruction says do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It does state Salary: To be discussed at interview, which is a statement but not specific. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them, albeit vague. Should we create a Pay section? It says "never create Pay/Schedule/Benefits sections
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those exact headings when we have content. But we can also have other headings? Probably we should stick to those headings where appropriate. Let's map content:
- About the role: we have description about the district and what you will do. Could combine "About Harris County Flood Control District" and "What you will do". So we can put under About the role
a paragraph(s) describing mission, jurisdiction, and duties.
- Responsibilities: we have "Essential Functions and Duties" with subpoints. So we can put under Responsibilities
a - list.
- Requirements: we have Education, Experience, Licensure, Knowledge Skills, and Abilities. Also note about documentation. So
Requirements
with .
- Qualifications/Skills: maybe combine with Requirements? But we have separate "Knowledge Skills, and Abilities". Could put under Skills
or Qualifications
. The instruction list includes Qualifications and Skills as possible headings. We could split: Requirements for education/experience/licensure, Skills for KSAs. But we can also combine. However they said prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section? But they gave examples of headings; we can choose to use Requirements and Skills separately if we have content. Let's see: we have Education, Experience, Licensure under Requirements. Then Knowledge Skills, and Abilities under a separate heading. Also Preferences. So we could have:
Requirements
(education, experience, licensure)
Skills
(knowledge, skills, abilities)
Preferences
(preferred education, experience, etc.)
We also have General Information: Position Type, Salary, Location, Physical Demands etc. That could be split into Pay, Schedule, Benefits? But we have no benefits or pay specifics (salary: To be discussed at interview). That's not specific, so we should NOT create Pay or Benefits sections because they are not specific (they say "To be discussed at interview" which is vague). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states "Salary: To be discussed at interview" which is not a specific amount, so we should not create Pay section. Schedule: Position Type, Salary: Regular | Full-Time. That indicates schedule: Full-Time. That's specific enough? It says Regular | Full-Time. That is a schedule. So we could create a Schedule
with content "Regular, Full-Time". However they said prefer few substantive sections over many thin ones. But schedule is a specific piece. Could also include under General Information as a paragraph. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. Schedule is specific: Full-Time. So we can include Schedule.
Location: we have location address. Could be part of General Information but we could put under a Location
but not in the list of allowed headings. The allowed headings list does not include Location. But we could still use for other headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Likely we can use other headings as needed, but they gave examples of typical sections. Safer to stick to those headings; we can embed location in a paragraph under About the role or under a generic
. But we need to preserve all substantive information. We could put location in a
after About the role.
Physical Demands etc: could be omitted? It's substantive but not fitting headings. Could be placed under a
maybe under a section like "Working Conditions". Not in list. Might be okay to include as a
after Schedule.
We must remove boilerplate: EEO link, accommodation phone, criminal history check, etc. Also remove "If you need special services..." etc. Also remove "NOTE: Qualifying education..." etc? That is part of requirements; we should keep it? It's a note about documentation; it's substantive but maybe we can keep as part of Requirements. It's not boilerplate. Keep.
Also remove "Preferred Education:" etc under Preferences.
We must not repeat job title as heading.
We must not put Job ID/requisition numbers as headings (none present).
We must output only HTML fragment.
Let's craft:
About the role
The Harris County Flood Control District reduces flood risk in Harris County, the third most populated U.S. county (over 4.7 million residents, including Houston, the nation’s fourth largest city). The District manages about 1,500 channels totaling nearly 2,500 miles, more than 60 regional stormwater detention basins (>10,000 acres), and several wetlands mitigation banks.
The Assistant Commissioners Court Coordinator supports the coordination and administration of Commissioners’ Court agendas, ensuring information, records, and agenda materials are organized, accurate, accessible, and processed efficiently. Duties include coordinating documents and deadlines, assisting with records retrieval and public information requests, and providing operational support to the Commissioners Court Coordinator and Public Information Officer as needed.
Responsibilities
- Support preparation of the Commissioners Court agenda and Request for Court Action (RCA) workflow: documenting court requests, retrieving historical records, gathering supporting documentation.
- Maintain and organize approved agenda RCA’s and record final agenda actions in internal District systems.
- Act as backup for the Agenda Team, supporting agenda and RCA workflow processes.
- Research, compile, and organize agenda information to assist in preparing Commissioners Court agenda briefings and facilitate discussion.
- Attend and handle RCA and CC Briefing meetings with Executive staff as needed.
- Coordinate with the Office of County Administration for agenda‑related questions, clarification, and assistance.
- Work with other personnel to address court‑related questions or concerns.
- Cross‑train in Commissioners Court agenda and open records processes to provide backup coverage during staff absences or increased workload.
- Assist the Public Information Officer and Records Team by processing Public Information Act requests and related records management activities.
- Assist with records retrieval, document organization, and filing of responsive records.
- Maintain records in the Harris County enterprise GovQA system and other applicable document management systems.
- Perform general administrative and records‑related duties to support Public Information and Records functions.
- Attend seminars, conference workshops, and other training programs.
- Assume additional responsibilities as required to meet the District's evolving demands.
Requirements
- High school diploma or G.E.D. equivalent from an accredited educational institution.
- Experience preparing agenda packets, coordinating agenda submissions, and managing agenda‑related documentation.
- Valid Class "C" Texas Driver’s License.
Skills
- Excellent organizational, analytical, and time‑management skills.
- Strong written and verbal communication skills with attention to detail.
- Proficient in using databases, spreadsheets, and digital document management tools.
- Skilled in handling sensitive information with a high degree of discretion.
- Knowledge of the Texas Public Information Act and related compliance requirements.
- Familiarity with legal and governmental documentation standards.
- Ability to work independently and collaboratively across departments.
Preferences
- Preferred Education: Bachelor’s degree in Public Administration, Business Administration, Communication, Legal Studies, or a related field from an accredited college or university.
- Preferred Experience: Minimum of five (5) years of progressive experience in records management, governmental operations, or a related administrative or legal field.
- Preferred: Experience with enterprise records tracking databases or workflow automation tools.
- Preferred: Knowledge of Commissioners Court agenda, Request for Court Action (RCA) processes, and related documentation requirements.
Schedule
Regular, Full‑Time.
Location: Executive Support Services, 9900 Northwest Freeway, Houston, TX 77092.
Physical demands: occasional stooping, bending, reaching, lifting, and carrying items up to 11 lb, occasional lifting up to 20 lb; occasional sorting, filing, shelving, handling of files, documents, books, file drawers, and related equipment; prolonged sitting; occasional ascending/descending stairs; occasional driving of a vehicle with automatic controls. Work performed indoors in a normal office environment with acceptable lighting, temperature, air conditioning, and noise levels.
We must ensure we didn't include any boilerplate like EEO, accommodation, criminal history check, drug screen note, etc. We removed those. Also removed "If you need special services..." etc. Also removed "This position is subject to a criminal history check." etc. Also removed "Due to a high volume of applications..." etc. Also removed "NOTE: Qualifying education, experience, knowledge, and skills must be documented on your job application." Actually that note is part of requirements; we might keep it? It's not boilerplate; it's an instruction to applicants. It's substantive. Should we keep? It says: "NOTE: Qualifying education, experience, knowledge, and skills must be documented on your job application. You may attach a resume to the application as supporting documentation but ONLY information stated on the application will be used for consideration. 'See Resume' will not be accepted for qualifications." This is important for applicants. We should keep it. Where to place? Could be under Requirements as a paragraph after the list. Let's add a after the Requirements list.
Similarly, we might keep "Preferred Education:" etc under Preferences; we already have.
We also need to keep "General Information Position Type, Salary: Regular | Full-Time Salary: To be discussed at interview Location: ..." We already captured Schedule and Location. Salary: To be discussed at interview - we should not create Pay section because not specific. We could mention salary in a paragraph under About the role or Schedule? But instruction says do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It does state Salary: To be discussed at interview, which is a statement but not specific. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them, albeit vague. Should we create a Pay section? It says "never create Pay/Schedule/Benefits sections
Requirements
with- .
- Qualifications/Skills: maybe combine with Requirements? But we have separate "Knowledge Skills, and Abilities". Could put under
- Support preparation of the Commissioners Court agenda and Request for Court Action (RCA) workflow: documenting court requests, retrieving historical records, gathering supporting documentation.
- Maintain and organize approved agenda RCA’s and record final agenda actions in internal District systems.
- Act as backup for the Agenda Team, supporting agenda and RCA workflow processes.
- Research, compile, and organize agenda information to assist in preparing Commissioners Court agenda briefings and facilitate discussion.
- Attend and handle RCA and CC Briefing meetings with Executive staff as needed.
- Coordinate with the Office of County Administration for agenda‑related questions, clarification, and assistance.
- Work with other personnel to address court‑related questions or concerns.
- Cross‑train in Commissioners Court agenda and open records processes to provide backup coverage during staff absences or increased workload.
- Assist the Public Information Officer and Records Team by processing Public Information Act requests and related records management activities.
- Assist with records retrieval, document organization, and filing of responsive records.
- Maintain records in the Harris County enterprise GovQA system and other applicable document management systems.
- Perform general administrative and records‑related duties to support Public Information and Records functions.
- Attend seminars, conference workshops, and other training programs.
- Assume additional responsibilities as required to meet the District's evolving demands.
- High school diploma or G.E.D. equivalent from an accredited educational institution.
- Experience preparing agenda packets, coordinating agenda submissions, and managing agenda‑related documentation.
- Valid Class "C" Texas Driver’s License.
- Excellent organizational, analytical, and time‑management skills.
- Strong written and verbal communication skills with attention to detail.
- Proficient in using databases, spreadsheets, and digital document management tools.
- Skilled in handling sensitive information with a high degree of discretion.
- Knowledge of the Texas Public Information Act and related compliance requirements.
- Familiarity with legal and governmental documentation standards.
- Ability to work independently and collaboratively across departments.
- Preferred Education: Bachelor’s degree in Public Administration, Business Administration, Communication, Legal Studies, or a related field from an accredited college or university.
- Preferred Experience: Minimum of five (5) years of progressive experience in records management, governmental operations, or a related administrative or legal field.
- Preferred: Experience with enterprise records tracking databases or workflow automation tools.
- Preferred: Knowledge of Commissioners Court agenda, Request for Court Action (RCA) processes, and related documentation requirements.
Skills
orQualifications
. The instruction list includes Qualifications and Skills as possible headings. We could split: Requirements for education/experience/licensure, Skills for KSAs. But we can also combine. However they said prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section? But they gave examples of headings; we can choose to use Requirements and Skills separately if we have content. Let's see: we have Education, Experience, Licensure under Requirements. Then Knowledge Skills, and Abilities under a separate heading. Also Preferences. So we could have:Requirements
(education, experience, licensure)Skills
(knowledge, skills, abilities)Preferences
(preferred education, experience, etc.) We also have General Information: Position Type, Salary, Location, Physical Demands etc. That could be split into Pay, Schedule, Benefits? But we have no benefits or pay specifics (salary: To be discussed at interview). That's not specific, so we should NOT create Pay or Benefits sections because they are not specific (they say "To be discussed at interview" which is vague). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states "Salary: To be discussed at interview" which is not a specific amount, so we should not create Pay section. Schedule: Position Type, Salary: Regular | Full-Time. That indicates schedule: Full-Time. That's specific enough? It says Regular | Full-Time. That is a schedule. So we could create aSchedule
with content "Regular, Full-Time". However they said prefer few substantive sections over many thin ones. But schedule is a specific piece. Could also include under General Information as a paragraph. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. Schedule is specific: Full-Time. So we can include Schedule. Location: we have location address. Could be part of General Information but we could put under aLocation
but not in the list of allowed headings. The allowed headings list does not include Location. But we could still use for other headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Likely we can use other headings as needed, but they gave examples of typical sections. Safer to stick to those headings; we can embed location in a paragraph under About the role or under a generic
. But we need to preserve all substantive information. We could put location in a
after About the role. Physical Demands etc: could be omitted? It's substantive but not fitting headings. Could be placed under a
maybe under a section like "Working Conditions". Not in list. Might be okay to include as a
after Schedule. We must remove boilerplate: EEO link, accommodation phone, criminal history check, etc. Also remove "If you need special services..." etc. Also remove "NOTE: Qualifying education..." etc? That is part of requirements; we should keep it? It's a note about documentation; it's substantive but maybe we can keep as part of Requirements. It's not boilerplate. Keep. Also remove "Preferred Education:" etc under Preferences. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings (none present). We must output only HTML fragment. Let's craft:
About the role
The Harris County Flood Control District reduces flood risk in Harris County, the third most populated U.S. county (over 4.7 million residents, including Houston, the nation’s fourth largest city). The District manages about 1,500 channels totaling nearly 2,500 miles, more than 60 regional stormwater detention basins (>10,000 acres), and several wetlands mitigation banks.
The Assistant Commissioners Court Coordinator supports the coordination and administration of Commissioners’ Court agendas, ensuring information, records, and agenda materials are organized, accurate, accessible, and processed efficiently. Duties include coordinating documents and deadlines, assisting with records retrieval and public information requests, and providing operational support to the Commissioners Court Coordinator and Public Information Officer as needed.
Responsibilities
Requirements
Skills
Preferences
Schedule
Regular, Full‑Time.
Location: Executive Support Services, 9900 Northwest Freeway, Houston, TX 77092.
Physical demands: occasional stooping, bending, reaching, lifting, and carrying items up to 11 lb, occasional lifting up to 20 lb; occasional sorting, filing, shelving, handling of files, documents, books, file drawers, and related equipment; prolonged sitting; occasional ascending/descending stairs; occasional driving of a vehicle with automatic controls. Work performed indoors in a normal office environment with acceptable lighting, temperature, air conditioning, and noise levels.
We must ensure we didn't include any boilerplate like EEO, accommodation, criminal history check, drug screen note, etc. We removed those. Also removed "If you need special services..." etc. Also removed "This position is subject to a criminal history check." etc. Also removed "Due to a high volume of applications..." etc. Also removed "NOTE: Qualifying education, experience, knowledge, and skills must be documented on your job application." Actually that note is part of requirements; we might keep it? It's not boilerplate; it's an instruction to applicants. It's substantive. Should we keep? It says: "NOTE: Qualifying education, experience, knowledge, and skills must be documented on your job application. You may attach a resume to the application as supporting documentation but ONLY information stated on the application will be used for consideration. 'See Resume' will not be accepted for qualifications." This is important for applicants. We should keep it. Where to place? Could be under Requirements as a paragraph after the list. Let's add aafter the Requirements list. Similarly, we might keep "Preferred Education:" etc under Preferences; we already have. We also need to keep "General Information Position Type, Salary: Regular | Full-Time Salary: To be discussed at interview Location: ..." We already captured Schedule and Location. Salary: To be discussed at interview - we should not create Pay section because not specific. We could mention salary in a paragraph under About the role or Schedule? But instruction says do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It does state Salary: To be discussed at interview, which is a statement but not specific. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them, albeit vague. Should we create a Pay section? It says "never create Pay/Schedule/Benefits sections