The City of Laredo Veterans Affairs Committee voted June 9 to accept a set of bylaws intended to formalize the panel’s membership, authority and procedures.
Ricardo Khano, who said he was tasked with drafting the rules, opened the discussion by urging committee members to hold themselves accountable: “We need to police ourselves. We need to hold ourselves accountable,” he said. Khano said the draft spells out the committee’s purpose and operational procedures and includes language to clarify membership eligibility.
During discussion, members focused on several practical details: the draft adds a provision for the mayor to appoint two city council liaisons to the committee and formally recognizes a city liaison officer to coordinate between the committee and city staff. Members debated meeting frequency (monthly versus quarterly), term lengths and whether previously appointed groups or individuals should be “grandfathered” if they fail to meet new paperwork or meeting-frequency requirements.
Jesus Rivas moved to accept the bylaws and asked that any recommended changes be submitted for consideration at the next meeting. “My motion is to accept the bylaws,” Rivas said. The motion was seconded, discussed, and approved by a voice vote; committee members did not enter a roll-call tally in the record and no effective date was recorded during the meeting.
Committee members said the approval is intended to bring more structure to how veterans organizations and government agencies interact and to prevent single individuals from asserting committee influence without representing an active organization. Several members said organizations that do not meet draft membership standards could be considered for removal or for reassignment of voting privileges once the bylaws take effect, and that any final changes could be proposed and adopted in subsequent meetings.
What’s next: the committee will accept suggested edits and is expected to revisit the draft at its next meeting; the record does not specify an implementation or effective date, and committee members discussed possible future dates (for example, an August 1 implementation was mentioned as one option).