Practice Manager, CVH

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Oregon Humane" (organization description) then "The Team", "The Position", "Eligible Benefits", "Essential Responsibilities" with subheadings (PERSONAL LEADERSHIP etc). Also "Primary Responsibilities" then "SUPERVISOR RESPONSIBILITY", "ACCOUNTABILITY", "Qualifications", "Work Environment Conditions & Physical Requirements", "Diversity, Equity & Inclusion", "Equal Employment Opportunity". We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also we must not repeat job title as heading (not present). We must not put Job ID/requisition numbers as headings. We need to include sections only when posting has real specific content. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we can also use other headings? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those standard headings, but we can also use other headings if they match content? The examples are just examples; they say use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map our content to those headings where appropriate. But we also have sections like "About Oregon Humane" (organization description) maybe map to "About the role"? Actually "About the role" is about the position, not organization. But we have "About Oregon Humane" describing organization. Could be considered "About the role"? Not exactly. However we could create a section "About the Organization" but instruction says use those examples; but not strict that we must only use those exact headings. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings as appropriate; we can also use other headings if needed? Probably safer to stick to those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we have many sections like "Eligible Benefits", "Essential Responsibilities", "Primary Responsibilities", "Qualifications", "Work Environment Conditions & Physical Requirements", "Diversity, Equity & Inclusion", "Equal Employment Opportunity". We need to decide which to keep. The instruction: "Prefer a few substantive sections over many thin ones." Also "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to combine similar content. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep all details but can group them under appropriate headings. We have: - About Oregon Humane (organization description) - The Team (description of team) - The Position (role description) - Eligible Benefits (list of benefits) - Essential Responsibilities (with subheadings: PERSONAL LEADERSHIP, TEAM LEADERSHIP & MANAGEMENT, LEARNING, INFLUENCE & REPRESENTATION) - Primary Responsibilities (detailed list) - SUPERVISOR RESPONSIBILITY (Supervises: Community Solutions Manager) - ACCOUNTABILITY (Reports Directly To: Hospital Administrator; Often Engages Directly With: ...) - Qualifications (Minimum Qualification & Transferable Skills) - Work Environment Conditions & Physical Requirements - Diversity, Equity & Inclusion - Equal Employment Opportunity (EEO) - this is boilerplate; we should remove EEO/equal-opportunity boilerplate. So drop that. Also there is a line about "We are interested in finding the best candidate..." within Qualifications; we keep. We need to remove duplicated lines, cookie/navigation/legal/EEO etc. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to output only HTML fragment. We need to decide sections: Perhaps we can have: - About the Organization (maybe use About the role? but we can use About the organization as heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but examples given. Safer to use those exact headings where applicable. Let's map: About the role: could contain description of the role (The Position, The Team, maybe About Oregon Humane? but that's about organization). However we could put About Oregon Humane under About the role? Not ideal. Responsibilities: could contain Essential Responsibilities + Primary Responsibilities + Supervisor Responsibility + Accountability. Requirements: could contain Qualifications. Skills: maybe not needed. Benefits: Eligible Benefits. Pay: not present, so omit. Schedule: not present, omit. We could also have a section "Work Environment" maybe not in list but could be under Requirements? But we could add a custom heading if needed. However instruction says prefer few substantive sections over many thin ones. So we could combine Work Environment into Requirements or Qualifications? It's not a qualification but work conditions. Could be under Requirements? Might be okay. Diversity, Equity & Inclusion: could be under Requirements? Or maybe a separate section but it's substantive. Could be its own section; but we need to decide if we want many sections. It's important content; we could include as a section "Diversity, Equity & Inclusion". The instruction didn't forbid that; they just gave examples. So we can use other headings as needed. Thus final sections:

  About the Organization

  (contains About Oregon Humane + The Team maybe)

  About the Role

  (contains The Position description)

  Responsibilities

  (contains Essential Responsibilities, Primary Responsibilities, Supervisor Responsibility, Accountability)

  Qualifications

  (contains Minimum Qualification & Transferable Skills)

  Benefits

  (Eligible Benefits)

  Work Environment

  (Work Environment Conditions & Physical Requirements)

  Diversity, Equity & Inclusion

  (the DEI paragraph) We must ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive information. Let's extract each piece. First, About Oregon Humane paragraph: "About Oregon Humane Founded in 1868, Oregon Humane is the Northwest's oldest and largest animal welfare organization with one of the highest adoption rates in the nation. We are working toward our vision of a world where all animals are treated with compassion, kindness, and respect. With campuses in Portland and Salem, Oregon Humane is an Oregon-based nonprofit that relies on donor support for its adoption, education, medical and humane law enforcement programs. Visit oregonhumane.org to learn more about how we’re creating an ecosystem where all of us – animals and humans – feel safe, valued and part of something bigger." We need to keep that as prose (

  ). The Team: "The Team This position is part of the Medical Services team within the Community Veterinary Hospital." That's a short sentence. Could be included under About the Organization or About the Role. We'll put under About the Organization after the org description. The Position: "The Position This role ensures the Community Veterinary Hospital (CVH) runs smoothly by balancing day-to-day operations with financial oversight. They review invoices, track revenue and expenses, and use data to spot trends and improve performance. The position also supports reporting, is responsible for accurate systems and processes, and implements policies and pricing updates. The Practice Manager collaborates with other CVH leaders, leading the process of developing and implementing standard operating procedures. In addition, they oversee client financial programs, ensure compliance, and lead and supports staff to create an efficient, positive, and mission-driven workplace." We'll put under About the Role. Now Responsibilities: we have Essential Responsibilities with subheadings PERSONAL LEADERSHIP, TEAM LEADERSHIP & MANAGEMENT, LEARNING, INFLUENCE & REPRESENTATION. Each has bullet-like sentences but not formatted as list. We need to convert to

  • for any list of duties/requirements/benefits. So we should treat each bullet as list item. Let's extract each: PERSONAL LEADERSHIP: - Consistently strives to exceed expectations; demonstrates flexibility, resilience, and the ability to maintain positive relationships and composure, even under difficult circumstances. - Maintains high ethical standards, including exhibiting behaviors and actions that embrace and align to our organization and customer service values, while treating all people with respect and dignity. - Demonstrates an awareness of your individual personal strengths and development needs, modeling non-defensive behavior and openness to feedback; builds a culture of feedback and learning. TEAM LEADERSHIP & MANAGEMENT: - Manage, support, and provide coaching feedback to team members, and create and sustain a work environment of mutual respect where team members strive to achieve excellence within their own team and embrace their role and responsibilities in advancing shared goals and priorities. - Manage day-to-day implementation and support for key activities including coordination with other teams implementing complementary activities. - Role model inclusive leadership, creating an environment where diverse viewpoints are welcomed and actively engaged LEARNING: - Contributes to regular dialogue and accountability with the leadership team and across the organization to review progress and course correct if necessary. - Utilizes data and insights to identify, understand and articulate the key inputs and metrics that tell the story of the organization/team strategy and its progress. - Builds appropriate feedback loops to measure if we are meeting key milestones and if the impact planned is being felt across the organization. INFLUENCE & REPRESENTATION: - Communicate effectively to executive and other stakeholder groups to ensure they are informed and able to actively engage. - Liaise with and maintain productive relationships with all stakeholders, including other departments, and donors; build mutually rewarding professional relationships inside Oregon Humane at all levels. - Leverage our best practices externally and grow Oregon Humane’ reputation as a leader in the animal welfare space. Note there may be missing punctuation; we keep as is. Primary Responsibilities: a long paragraph with many sentences separated by periods. We need to convert to list items. Let's break at each sentence that starts with a capital letter after a period. We'll produce list items. Primary Responsibilities text: "Champions the Community Veterinary Hospital's strategic vision by embedding financial growth, sustainability, and operational efficiency into day-to-day decision-making and long-term planning. Conducts and interprets regular recurring financial analyses, including a high volume of invoice reviews, audits for missed charges, and identification of revenue opportunities or risks. Monitor employee discounts for IRS compliance and work directly with clients and employees to resolve aged receivables. Analyze client compliance and hospital performance data, providing actionable insights to leadership and implementing improvements. Identifies opportunities for clarification of process, communication and/or recommended adjustments in pricing strategy to achieve compliance with recommended treatment plans, including the development of proposals and managing rollout to internal teams and clients. Produce and review monthly, quarterly, and annual reports; support leadership with KPI tracking, monthly board reporting, and grant-related data needs. Lead data management efforts, ensuring accuracy and integrity of all data within the Practice Information Management System (PIMS) and integrated platforms (e.g., AllyDVM). Collaborates with cross-functional partners to ensure accuracy of data in external platforms (SalesForce) and represents CVH on the cross-departmental Data Governance Committee. Responsible for the development, implementation, and continuous improvement of standard operating procedures (SOPs) for the CVH; ensuring team adherence through clear communication and training, including ownership