Business and Project Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it.
We need to decide which sections to include. We have substantive content for About the role (summary), Responsibilities (duties), Requirements (minimum qualifications), Qualifications (desirable qualifications), Skills (proficiency in MS Office etc), Pay, Schedule. Benefits not present, so omit.
We must not create sections with filler like "not specified". So only include if we have content.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tasks, systems, etc.
We need to format duties as
- . For responsibilities we can list bullet points derived from the summary. Must not lose detail.
Similarly for requirements (minimum qualifications) we can list bullet points.
Qualifications (desirable) bullet list.
Skills bullet list (proficiency in MS Word, Excel, Teams, Outlook essential; also maybe knowledge of other tools? Those are in desirable qualifications; but we could still list them under Skills if they are skills. However we might keep Skills separate for proficiency in MS Office etc. The desirable qualifications include many technical knowledges; we could put them under Qualifications (desirable) or Skills. The instruction says use sections as exemplified; we can decide.
Better to have:
About the role
Provide business administration and project management for the UVM Office of Primary Care (OPC) and Area Health Education Centers (AHEC) Program. ... (the summary)
Responsibilities
- Financial management duties: financial analysis and planning, budget development and fiscal year-end processes, reconciliation, and reporting; accounts payable and receivables (PeopleSoft); fulfilling federal, state, and foundation grants financial and activity reporting requirements; assist with budget development and creation of funding proposals in UVM grant applications; facilitate processes related to personnel management (new hires, effort certification, and salary distributions).
- Serve as the point person for OPC and AHEC on PeopleSoft matters, facilities and space, and technology/COMTS matters.
- Coordinate complex, multidisciplinary health workforce and medical education initiatives, in partnership with Program Director and AHEC faculty; contribute to development of project processes and documentation; support recruitment and enrollment into programs; track grant-required deliverables and program timeline; funder reporting; stakeholder engagement.
- Collaborate with office leadership and grant principal investigators.
- Work closely with UVM Sponsored Project Administration (SPA), Accounting and Procurement Services, and the regional AHECs.
- Reports to OPC/AHEC Program Director.
But note we already included some of that in About the role; we risk duplication. However the instruction says preserve ALL substantive information; we can have both About the role (summary) and Responsibilities (detailed list). That's okay as long as we don't repeat same sentences verbatim? Might be okay but could be considered duplication. However we could combine About the role as a brief overview and Responsibilities as detailed list. That seems fine.
Now Requirements (minimum qualifications) bullet list:
- Bachelor’s degree and two to four years of related experience required or an equivalent combination of education and experience.
- Effective financial management and communication skills.
- Ability to effectively respond to a wide variety of individuals and their varying needs including UVM, the regional AHECs, and the public.
- Demonstrated ability to attend to detail.
- Effective time-management skills and ability to prioritize effectively to meet deadlines; ability to manage multiple projects simultaneously.
- Ability to take initiative and ability to work independently as well as collaboratively within a team.
- Ability to use discretion regarding disclosure/dissemination/security of confidential/sensitive information.
- Proficiency in Microsoft Word, Excel, Teams, and Outlook is essential.
- A commitment to continuous quality and process improvement.
Now Qualifications (desirable) bullet list:
- Experience in higher education and grant-funded organizations highly desirable.
- PMP certification.
- Knowledge of Microsoft Access, SharePoint, project management software, Concur, PeopleSoft, UVM financial systems, and fund accounting are highly desirable.
- An understanding of education financing/student loan programs.
Now Skills: Could be overlapping with Requirements (proficiency in MS Office). But we could keep Skills separate for proficiency in MS Word, Excel, Teams, Outlook essential. However that is already in Requirements. To avoid duplication, maybe we omit Skills section and keep proficiency under Requirements. But the instruction says we can have Skills section; but we need to avoid filler. If we already covered it under Requirements, we could still have Skills but would duplicate. Better to not duplicate. So we can omit Skills section.
Pay: Pay
Anticipated Pay Range $60,000 - $70,000
Schedule: Schedule
Eligible for a hybrid schedule with option to split time between campus and elsewhere, per university telecommuting policy.
We might also include location and other info as a short p under About the role or separate section like "Position Details". But we have no heading for that; we could add a short p after About the role containing location and funding info. However we must not create a heading unless we have real content for that section. We could add a after About the role containing: Position is partially funded by grants. Located in Burlington, Vermont, United States. That's fine.
We need to ensure we don't include boilerplate like "Our Common Ground Statement", "Supplemental Questions", "Documents Needed to Apply", etc.
Now output only HTML fragment.
Let's craft.
Check for any missing substantive info: "Position reports to OPC/AHEC Program Director." Already in responsibilities.
"Position is partially funded by grants" we added.
"Background Check required for this position FLSA Exempt Union Position Yes, UVMSU" This is substantive? It's about background check, FLSA exempt, union position. Should we include? It's not in the specified sections but could be placed in a short p under About the role or maybe a separate section like "Other Information". However we don't have a heading for Other Information in the list; but we could add a
after schedule? The instruction says we can include sections only when posting has real, specific content for it. It didn't forbid adding a generic paragraph outside sections. It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. It doesn't forbid having
outside headings. So we can add a paragraph for miscellaneous info like background check, FLSA exempt, union position.
But we must
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. We need to decide which sections to include. We have substantive content for About the role (summary), Responsibilities (duties), Requirements (minimum qualifications), Qualifications (desirable qualifications), Skills (proficiency in MS Office etc), Pay, Schedule. Benefits not present, so omit. We must not create sections with filler like "not specified". So only include if we have content. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tasks, systems, etc. We need to format duties as
- . For responsibilities we can list bullet points derived from the summary. Must not lose detail.
Similarly for requirements (minimum qualifications) we can list bullet points.
Qualifications (desirable) bullet list.
Skills bullet list (proficiency in MS Word, Excel, Teams, Outlook essential; also maybe knowledge of other tools? Those are in desirable qualifications; but we could still list them under Skills if they are skills. However we might keep Skills separate for proficiency in MS Office etc. The desirable qualifications include many technical knowledges; we could put them under Qualifications (desirable) or Skills. The instruction says use sections as exemplified; we can decide.
Better to have:
About the role
Provide business administration and project management for the UVM Office of Primary Care (OPC) and Area Health Education Centers (AHEC) Program. ... (the summary)
Responsibilities
- Financial management duties: financial analysis and planning, budget development and fiscal year-end processes, reconciliation, and reporting; accounts payable and receivables (PeopleSoft); fulfilling federal, state, and foundation grants financial and activity reporting requirements; assist with budget development and creation of funding proposals in UVM grant applications; facilitate processes related to personnel management (new hires, effort certification, and salary distributions).
- Serve as the point person for OPC and AHEC on PeopleSoft matters, facilities and space, and technology/COMTS matters.
- Coordinate complex, multidisciplinary health workforce and medical education initiatives, in partnership with Program Director and AHEC faculty; contribute to development of project processes and documentation; support recruitment and enrollment into programs; track grant-required deliverables and program timeline; funder reporting; stakeholder engagement.
- Collaborate with office leadership and grant principal investigators.
- Work closely with UVM Sponsored Project Administration (SPA), Accounting and Procurement Services, and the regional AHECs.
- Reports to OPC/AHEC Program Director.
Pay
Anticipated Pay Range $60,000 - $70,000
Schedule:Schedule
Eligible for a hybrid schedule with option to split time between campus and elsewhere, per university telecommuting policy.
We might also include location and other info as a short p under About the role or separate section like "Position Details". But we have no heading for that; we could add a short p after About the role containing location and funding info. However we must not create a heading unless we have real content for that section. We could add aafter About the role containing: Position is partially funded by grants. Located in Burlington, Vermont, United States. That's fine. We need to ensure we don't include boilerplate like "Our Common Ground Statement", "Supplemental Questions", "Documents Needed to Apply", etc. Now output only HTML fragment. Let's craft. Check for any missing substantive info: "Position reports to OPC/AHEC Program Director." Already in responsibilities. "Position is partially funded by grants" we added. "Background Check required for this position FLSA Exempt Union Position Yes, UVMSU" This is substantive? It's about background check, FLSA exempt, union position. Should we include? It's not in the specified sections but could be placed in a short p under About the role or maybe a separate section like "Other Information". However we don't have a heading for Other Information in the list; but we could add a
after schedule? The instruction says we can include sections only when posting has real, specific content for it. It didn't forbid adding a generic paragraph outside sections. It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
- for any list of duties/requirements/benefits, and
for prose. It doesn't forbid having
outside headings. So we can add a paragraph for miscellaneous info like background check, FLSA exempt, union position. But we must