PMO Administrator
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job description.
We have:
- Job Summary: description of role. Could be "About the role" maybe. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map "Job Summary" to "About the role". Provide About the role
then
About the role
thenwith the summary text. - "Why you should join our Team": could be "Benefits"? But it's more about why join. Could be "Benefits" if they mention benefits like opportunity to provide admin support, impact, etc. Not explicit benefits like salary, health, etc. Might be better as "About the role" or maybe "Responsibilities"? Actually "Why you should join our Team" is more like selling points, could be considered "Benefits". But we should only include Benefits if posting actually states them. It does state: "With over 100 projects, totally over £80M in progress at any one time, the PMO administrator role is a key support to this busy team, offering administration, governance and assurance. In our team, you’ll have the opportunity to provide administrative support to projects that will have a real impact on the provision and quality of care we deliver at Leeds Teaching Hospitals, supporting the health of people within our community." That's more about role impact, not typical benefits like pension, holiday. Could still be considered Benefits but ambiguous. Safer to treat as "About the role" or maybe "Responsibilities"? Actually responsibilities are listed later? Not explicit bullet list. There's "What You Will Bring To The Role": that's requirements/qualifications/skills. So we can map that to "Requirements" or "Skills". The list includes commitments etc. Those are more like personal attributes/skills. Could be "Skills". We'll decide. We also have "About Leeds Teaching Hospital NHS Trust" with values and priorities. That could be "About the role"? Actually it's about the trust. Could be a separate section like "About the Trust". But not in allowed headings list. We could incorporate into "About the role" or drop? The instruction: Prefer a few substantive sections over many thin ones. We could combine trust info into "About the role" or maybe omit if not directly about role. But we must preserve ALL substantive information; cannot drop. So we need to include it somewhere. Could create a section "About the Trust" but not allowed heading. However we could use
About the role
and include both role summary and trust info within that. That would preserve info. We also have "Shortlisting Date", "Interview Date", contact info. Those are metadata; we should fold minor metadata into a short
or drop it. Probably include a short
at top with contact and dates. We must not include boilerplate like cookie/navigation/legal/EEO etc. There's a sponsorship eligibility paragraph about Skilled Worker sponsorship. That's substantive? It's about eligibility; we should preserve. Could be part of "Requirements" maybe. But it's not a requirement per se, it's a note. Could include in a
under "Requirements" or separate? Since we cannot create new headings, we could add a
after the sections. We must not repeat job title as heading. Not include Job ID. We must not create Pay/Schedule/Benefits sections unless posting actually states them. No pay or schedule mentioned. Benefits not explicit; we might not create Benefits section. So we will have sections: About the role (h3), Requirements/Skills (h3). Possibly Responsibilities? The job summary includes responsibilities; we could treat that as About the role. Could also have Responsibilities section if we extract duties. The posting includes: "provide project administrative and secretarial support", "provide professional comprehensive administrative assistance supporting senior members", "develop an understanding of B&E and/or other projects", "support projects across the Directorate and wider Trust". That's responsibilities. Could make a Responsibilities section. But we already have About the role; we could split. However we need to avoid thin sections. Might be okay to have About the role (summary) and Responsibilities (list) and Requirements/Skills (list). That's three sections. Let's extract responsibilities as bullet list. From Job Summary: - Provide project administrative and secretarial support to Leeds Teaching Hospitals NHS Trust (LTHT) and particularly the Building & Engineering (B&E) capital programme and PMO. - Provide professional comprehensive administrative assistance supporting senior members of the B&E capital team in the delivery of the investment plans and other LTHT Projects as may be directed from time-to-time. - Develop an understanding of B&E and/or other projects where they are providing support. - Support projects across the Directorate and the wider Trust as may be directed from time-to-time. Also from "Why you should join our Team": maybe not responsibilities. We'll make
- for each. Now Requirements/Skills: from "What You Will Bring To The Role": list of commitments: - A commitment to delivering a professional administrative and project support service. - A commitment to maintain a positive and professional attitude at all times. - A commitment and willingness to support colleagues. - Self-motivated and the ability to be flexible with regard to working practices, workload; and working hours. - A commitment to continually maintaining and improve the quality of services. - A commitment to working and positively contributing to a team environment. - A commitment to attend and participate in all mandatory training and to your own professional development and learning as identified through the staff appraisal process. We can turn each into
- .
Also sponsorship eligibility note: "To comply with UK Government regulations on Skilled Worker sponsorship, Leeds Teaching Hospital NHS Trust is unable to provide sponsorship to applicants who do not meet the eligibility criteria or the salary threshold concessions set out under the Skilled Worker visa route. Please take this into consideration before submitting your application. Full guidance on these concessions, including details of who may qualify, can be found here. We reserve the right to close this advert early if we receive a high number of suitable applications."
We could put that in a
after sections, maybe as a note. Contact info: "For questions about this job, contact: Name: Tim Watts Position: Head of PMO Email: Timothy.Watts2@nhs.net Shortlisting Date: w/c 5th October 2026 Interview Date: w/c 12th October 2026". We'll put in a
at top. Now we need to output only HTML fragment, no /, no markdown. Let's craft:
Contact: Tim Watts, Head of PMO, Timothy.Watts2@nhs.net. Shortlisting: w/c 5th October 2026. Interview: w/c 12th October 2026.
ThenAbout the role
withcontaining job summary? Actually we might put job summary in About the role. But we also have Responsibilities separate. Let's decide: About the role could be a brief overview; Responsibilities list duties. We'll put overview in About the role: "Working within a multi-disciplined project-based environment, the post holder shall provide project administrative and secretarial support to the Leeds Teaching Hospitals NHS Trust (LTHT) and particularly the Building & Engineering (B&E) capital programme and PMO. The post holder will provide professional comprehensive administrative assistance supporting senior members of the B&E capital team in the delivery of the investment plans and other LTHT Projects as may be directed from time-to-time. It is expected that the Project Administrator shall develop an understanding of B&E and/or other projects where they are providing support. The B&E capital programme reflects the Trust’s vision the delivery of patient focussed services in a modern and fit-for-purpose world-class healthcare setting. It includes investment in the Leeds General Infirmary and St James’s University Hospital sites as well as the Trust’s other community hospitals. The programme is delivered by the Trust’s capital team which is responsible for delivering and supporting a wide range of small, medium, and large capital and service-based Projects. The Project Administrator shall be expected to support projects across the Directorate and the wider Trust as may be directed from time-to-time." That's a lot but okay. Then
Responsibilities
with- ... maybe we can condense but we need to preserve all substantive info; we already included many in About the role; but we might duplicate. To avoid duplication, we could keep About the role short and put details in Responsibilities. However we must preserve all info; duplication is okay as long as we don't invent or summarize away detail. Duplication is not prohibited but might be redundant. Better to split: About the role: brief overview (maybe one or two sentences). Responsibilities: detailed list. Let's craft About the role: "The Project Administrator provides project administrative and secretarial support to the Leeds Teaching Hospitals NHS Trust, focusing on the Building & Engineering capital programme and PMO, assisting senior team members in delivering investment plans and other projects, and developing an understanding of B&E and related projects." That captures core.
Then Responsibilities list the specific duties.
Let's extract duties from the longer summary:
- Provide project administrative and secretarial support to Leeds Teaching Hospitals NHS Trust (LTHT) and particularly the Building & Engineering (B&E) capital programme and PMO.
- Provide professional comprehensive administrative assistance supporting senior members of the B&E capital team in the delivery of the investment plans and other LTHT Projects as may be directed from time-to-time.
- Develop an understanding of B&E and/or other projects where they are providing support.
- Support projects across the Directorate and the wider Trust as may be directed from time-to-time.
We could also include that the B&E capital programme reflects Trust's vision etc. That's more about context, maybe not a duty. We'll keep in About the role.
Now Requirements/Skills section: we can call it "Requirements" or "Skills". Use
Requirements
with- each commitment.
Now after that, a
for sponsorship eligibility note and maybe note about early closure. Let's craft. Check for any other substantive info: "Please see the attached job description for further information about this vacancy." That's a reference to attachment; we can drop as it's not substantive. Now ensure we don't include any boilerplate like EEO etc. There's none. Now output HTML. Let's write:
Contact: Tim Watts, Head of PMO, Timothy.Watts2@nhs.net. Shortlisting: w/c 5th October 2026. Interview: w/c 12th October 2026.
About the role
The Project Administrator provides project administrative and secretarial support to Leeds Teaching Hospitals NHS Trust, focusing on the Building & Engineering capital programme and PMO, assisting senior team members in delivering investment plans and other projects, and developing an understanding of B&E and related projects.
Responsibilities
- Provide project administrative and secretarial support to Leeds Teaching Hospitals NHS Trust (LTHT) and particularly the Building & Engineering (B&E) capital programme and PMO.
- Provide professional comprehensive administrative assistance supporting senior members of the B&E capital team in the delivery of the investment plans and other LTHT Projects as may be directed from time-to-time.
- Develop an understanding of B&E and/or other projects where they are providing support.
- Support projects across the Directorate and the wider Trust as may be directed from time-to-time.
Requirements
- A commitment to delivering a professional administrative and project support service.
- A commitment to maintain a positive and professional attitude at all times.
- each commitment.
Now after that, a
- ... maybe we can condense but we need to preserve all substantive info; we already included many in About the role; but we might duplicate. To avoid duplication, we could keep About the role short and put details in Responsibilities. However we must preserve all info; duplication is okay as long as we don't invent or summarize away detail. Duplication is not prohibited but might be redundant. Better to split: About the role: brief overview (maybe one or two sentences). Responsibilities: detailed list. Let's craft About the role: "The Project Administrator provides project administrative and secretarial support to the Leeds Teaching Hospitals NHS Trust, focusing on the Building & Engineering capital programme and PMO, assisting senior team members in delivering investment plans and other projects, and developing an understanding of B&E and related projects." That captures core.
Then Responsibilities list the specific duties.
Let's extract duties from the longer summary:
- Provide project administrative and secretarial support to Leeds Teaching Hospitals NHS Trust (LTHT) and particularly the Building & Engineering (B&E) capital programme and PMO.
- Provide professional comprehensive administrative assistance supporting senior members of the B&E capital team in the delivery of the investment plans and other LTHT Projects as may be directed from time-to-time.
- Develop an understanding of B&E and/or other projects where they are providing support.
- Support projects across the Directorate and the wider Trust as may be directed from time-to-time.
We could also include that the B&E capital programme reflects Trust's vision etc. That's more about context, maybe not a duty. We'll keep in About the role.
Now Requirements/Skills section: we can call it "Requirements" or "Skills". Use