Compliance Coordinator
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Job title: COMPLIANCE COORDINATOR (but we don't repeat as heading). Provide location, salary, schedule maybe as metadata in a short
or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include location, salary, schedule in a paragraph.
We need sections: maybe "About the role", "Responsibilities", "Requirements", "Benefits". Possibly "Qualifications" and "Skills" if content.
Let's extract content.
From posting:
- Development details: description of location and environment. Could be "About the role" or maybe "About the development". But we need sections: "About the role" is typical. Could combine development details as part of role description.
- Role Expectations: description of what success looks like, bullet points.
- How You'll Spend Most Of Your Time: list of duties.
- Who This Role Is For: personal attributes.
- Experience That Helps: experience.
- What We Offer: benefits list.
- About Rendall & Rittner: company description.
- How We Hire: hiring process.
We need to decide which sections to include.
We must not create sections with filler like "Pay" unless posting actually states them. Pay is stated: £32,000 - £35,000. So we can include Pay section.
Schedule: Monday - Friday 0900 - 1730. So we can include Schedule section.
Benefits: listed under "What We Offer". So Benefits section.
Responsibilities: we have "Role Expectations", "How You'll Spend Most Of Your Time", maybe combine.
Requirements/Qualifications/Skills: we have "Who This Role Is For" (attributes), "Experience That Helps" (experience). Could map to Requirements or Qualifications.
We need to avoid duplication.
We'll produce sections: About the role (maybe includes development details and role expectations), Responsibilities (duties), Requirements (experience and personal attributes), Benefits, Pay, Schedule.
We must ensure we only include sections with real content.
Let's extract content for each.
About the role: Could include development details description and role expectations summary. But we need to preserve all substantive information; we cannot summarize away detail. However we can keep details in prose or lists.
We need to decide: maybe better to have separate sections: "About the development" not a standard heading; but we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those headings.
Thus "About the role" can contain development details and role expectations.
Responsibilities: list of duties (How You'll Spend Most Of Your Time) plus maybe role expectations tasks.
Requirements: personal attributes (Who This Role Is For) plus experience that helps.
Qualifications: maybe not needed if we don't have specific qualifications like degrees; we could omit.
Skills: maybe not needed.
Benefits: list from What We Offer.
Pay: salary.
Schedule: working hours.
We must not repeat job title as heading.
We must not include boilerplate like "INTERESTED? Apply with your CV." etc. Remove application instructions.
Also remove "How We Hire" maybe not needed as it's process; could be omitted as not required heading. But we might include as part of About the role? Probably better to omit as not in allowed headings and not required.
We must preserve all substantive information; if we omit "How We Hire" we lose that info. But maybe we can incorporate into About the role as a short paragraph? The instruction: "Prefer a few substantive sections over many thin ones." So we could include a section "About the role" that includes hiring process? But hiring process is not about the role; it's about recruitment. Might be considered boilerplate? It's not EEO but still procedural. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "How We Hire" is not exactly those, but could be considered application instructions? It's about the hiring process. Might be considered part of application instructions? Safer to omit? But we need to preserve ALL substantive information; does "How We Hire" count as substantive? It's about the process, not the job. Might be considered not essential to the job description. However the instruction says preserve ALL substantive information; but also says remove application instructions. "How We Hire" could be considered application instructions. So we can drop it.
Similarly "About Rendall & Rittner" is company description; could be considered substantive about employer. Might be okay to include in About the role? Not exactly role but could be included as part of About the role? Might be okay to include as a paragraph under About the role.
We need to decide.
Let's extract substantive content:
Development details: description of location, environment, amenities.
Role Expectations: bullet list of success criteria.
How You'll Spend Most Of Your Time: bullet list of duties.
Who This Role Is For: bullet list of personal attributes.
Experience That Helps: bullet list of relevant experience.
What We Offer: bullet list of benefits.
Pay: salary range.
Schedule: Monday-Friday 0900-1730.
We can produce sections:
About the role
Development details: Set on the River Thames beside Wandsworth Park, this landmark collection of nine contemporary residential buildings offers a calm, premium environment to work in every day. You’ll support a vibrant community of residents who enjoy beautifully landscaped grounds, two onsite gyms, a swimming pool, secure parking and even a dedicated Thames Clipper pier for river travel. With Wandsworth Town and East Putney stations close by, the setting blends riverside serenity with great city connectivity and a well-staffed, service-driven atmosphere.
Role expectations: You will be the go-to person for coordinating statutory and best-practice compliance across the development, keeping certifications, inspections and remedial actions on track and accurately recorded. Most days you’ll liaise with contractors and onsite teams, schedule works, update compliance trackers and ensure documentation is complete, current and audit-ready. You’ll also surface risks early, communicate clearly with stakeholders and support a culture of safety and assurance.
But we need to preserve all substantive information; we can't lose details like "What Success Looks Like" bullet points. So we should include those as a list under Responsibilities maybe.
Better: About the role includes development details and general description. Responsibilities includes the success criteria and daily tasks.
Let's extract success criteria bullet points:
- All statutory inspections and routine tests are scheduled ahead of time, completed on time and evidenced without gaps.
- Compliance documentation is meticulously maintained, version-controlled and instantly retrievable for audits.
- Actions from risk assessments and inspections are tracked through to closure, with clear ownership and timescales.
- Contractors are well-briefed, inducted and monitored, with permits, RAMS and insurance validated before works begin.
- Resident and stakeholder communications are timely, clear and proactive, reducing queries and escalations.
- Accurate compliance reporting is delivered to management on time, highlighting trends, risks and recommendations.
These are responsibilities/expectations.
How You'll Spend Most Of Your Time bullet points:
- Managing the compliance calendar for lifts, fire safety, water hygiene, electrical testing and other statutory checks.
- Coordinating contractor visits, verifying RAMS, insurance and permits to work, and arranging access with onsite teams.
- Maintaining digital records, certificates and logs to ensure full audit readiness and traceability.
- Tracking remedial actions from audits and risk assessments, chasing updates and closing out works.
- Producing regular compliance reports and dashboards for property managers and senior stakeholders.
- Responding to queries from residents and colleagues, providing clear information and next steps.
These are duties.
Who This Role Is For bullet points:
- You are highly organised, detail-focused and comfortable managing multiple deadlines without losing accuracy.
- You communicate confidently with contractors, residents and colleagues, adapting your style to the audience.
- You take ownership, spot risks early and follow through until issues are resolved.
- You are calm under pressure and use sound judgement to prioritise what matters most.
- You enjoy improving processes and leveraging systems to make compliance clear, simple and consistent.
Experience That Helps bullet points:
- Coordinating compliance, H&S or facilities tasks within residential or mixed-use developments.
- Hands-on experience managing action logs from fire, water or general H&S inspections.
- Using property or compliance systems to schedule, track and report (e.g. CAFM, document management tools).
- Working with contractors, reviewing RAMS/permits and arranging site access safely.
- Preparing reports or dashboards that turn technical information into clear updates.
Benefits bullet points:
- 20 days holiday plus bank holidays
- Enrolment into the Rendall & Rittner pension scheme
- Employee assistance programme supporting family, health, money and work
- Employee referral scheme
- Team uniform* subject to development
- Fully funded training and development opportunities
- Access to discounts across travel, retail, fitness and entertainment
Pay: £32,000 - £35,000
Schedule: Monday - Friday 0900 - 1730
Now we need to output HTML fragment with sections.
We must not repeat job title as heading. So no COMPLIANCE COORDINATOR
.
We need to decide which sections to include.
We have content for:
- About the role (development details + role overview)
- Responsibilities (success criteria + daily tasks)
- Requirements (personal attributes + experience) maybe we split into Requirements and Experience? But we only have headings: Requirements, Qualifications, Skills. We could put personal attributes under Requirements, experience under Qualifications? Or combine.
Better: Use Requirements for personal attributes and experience combined. Or we could have Requirements for personal attributes, Qualifications for experience. But we need to avoid thin sections. Perhaps combine into Requirements.
Thus:
About the role
Development details...
Role overview: You will be the go-to person...
Responsibilities
- All statutory inspections...
...
- Managing the compliance calendar...
...
But we have two sets of bullet points; we could combine into one list under Responsibilities containing all bullet points (both success criteria and daily tasks). That would preserve all info.
Similarly, Requirements: combine personal attributes and experience.
Thus:
Requirements
- You are highly organised...
...
- Coordinating compliance, H&S or facilities tasks...
...
Benefits: list.
Pay: £32,000 - £35,000
maybe as Pay
then .
Schedule:
Schedule
Monday - Friday 0900 - 1730
We must not create sections with filler like "commensurate with experience". We have actual content.
Now we need to ensure we don't include any boilerplate like "INTERESTED? Apply with your CV." etc. Also remove "About Rendall & R
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Job title: COMPLIANCE COORDINATOR (but we don't repeat as heading). Provide location, salary, schedule maybe as metadata in a short
or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include location, salary, schedule in a paragraph. We need sections: maybe "About the role", "Responsibilities", "Requirements", "Benefits". Possibly "Qualifications" and "Skills" if content. Let's extract content. From posting: - Development details: description of location and environment. Could be "About the role" or maybe "About the development". But we need sections: "About the role" is typical. Could combine development details as part of role description. - Role Expectations: description of what success looks like, bullet points. - How You'll Spend Most Of Your Time: list of duties. - Who This Role Is For: personal attributes. - Experience That Helps: experience. - What We Offer: benefits list. - About Rendall & Rittner: company description. - How We Hire: hiring process. We need to decide which sections to include. We must not create sections with filler like "Pay" unless posting actually states them. Pay is stated: £32,000 - £35,000. So we can include Pay section. Schedule: Monday - Friday 0900 - 1730. So we can include Schedule section. Benefits: listed under "What We Offer". So Benefits section. Responsibilities: we have "Role Expectations", "How You'll Spend Most Of Your Time", maybe combine. Requirements/Qualifications/Skills: we have "Who This Role Is For" (attributes), "Experience That Helps" (experience). Could map to Requirements or Qualifications. We need to avoid duplication. We'll produce sections: About the role (maybe includes development details and role expectations), Responsibilities (duties), Requirements (experience and personal attributes), Benefits, Pay, Schedule. We must ensure we only include sections with real content. Let's extract content for each. About the role: Could include development details description and role expectations summary. But we need to preserve all substantive information; we cannot summarize away detail. However we can keep details in prose or lists. We need to decide: maybe better to have separate sections: "About the development" not a standard heading; but we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those headings. Thus "About the role" can contain development details and role expectations. Responsibilities: list of duties (How You'll Spend Most Of Your Time) plus maybe role expectations tasks. Requirements: personal attributes (Who This Role Is For) plus experience that helps. Qualifications: maybe not needed if we don't have specific qualifications like degrees; we could omit. Skills: maybe not needed. Benefits: list from What We Offer. Pay: salary. Schedule: working hours. We must not repeat job title as heading. We must not include boilerplate like "INTERESTED? Apply with your CV." etc. Remove application instructions. Also remove "How We Hire" maybe not needed as it's process; could be omitted as not required heading. But we might include as part of About the role? Probably better to omit as not in allowed headings and not required. We must preserve all substantive information; if we omit "How We Hire" we lose that info. But maybe we can incorporate into About the role as a short paragraph? The instruction: "Prefer a few substantive sections over many thin ones." So we could include a section "About the role" that includes hiring process? But hiring process is not about the role; it's about recruitment. Might be considered boilerplate? It's not EEO but still procedural. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "How We Hire" is not exactly those, but could be considered application instructions? It's about the hiring process. Might be considered part of application instructions? Safer to omit? But we need to preserve ALL substantive information; does "How We Hire" count as substantive? It's about the process, not the job. Might be considered not essential to the job description. However the instruction says preserve ALL substantive information; but also says remove application instructions. "How We Hire" could be considered application instructions. So we can drop it. Similarly "About Rendall & Rittner" is company description; could be considered substantive about employer. Might be okay to include in About the role? Not exactly role but could be included as part of About the role? Might be okay to include as a paragraph under About the role. We need to decide. Let's extract substantive content: Development details: description of location, environment, amenities. Role Expectations: bullet list of success criteria. How You'll Spend Most Of Your Time: bullet list of duties. Who This Role Is For: bullet list of personal attributes. Experience That Helps: bullet list of relevant experience. What We Offer: bullet list of benefits. Pay: salary range. Schedule: Monday-Friday 0900-1730. We can produce sections:
About the role
Development details: Set on the River Thames beside Wandsworth Park, this landmark collection of nine contemporary residential buildings offers a calm, premium environment to work in every day. You’ll support a vibrant community of residents who enjoy beautifully landscaped grounds, two onsite gyms, a swimming pool, secure parking and even a dedicated Thames Clipper pier for river travel. With Wandsworth Town and East Putney stations close by, the setting blends riverside serenity with great city connectivity and a well-staffed, service-driven atmosphere.
Role expectations: You will be the go-to person for coordinating statutory and best-practice compliance across the development, keeping certifications, inspections and remedial actions on track and accurately recorded. Most days you’ll liaise with contractors and onsite teams, schedule works, update compliance trackers and ensure documentation is complete, current and audit-ready. You’ll also surface risks early, communicate clearly with stakeholders and support a culture of safety and assurance.
But we need to preserve all substantive information; we can't lose details like "What Success Looks Like" bullet points. So we should include those as a list under Responsibilities maybe. Better: About the role includes development details and general description. Responsibilities includes the success criteria and daily tasks. Let's extract success criteria bullet points: - All statutory inspections and routine tests are scheduled ahead of time, completed on time and evidenced without gaps. - Compliance documentation is meticulously maintained, version-controlled and instantly retrievable for audits. - Actions from risk assessments and inspections are tracked through to closure, with clear ownership and timescales. - Contractors are well-briefed, inducted and monitored, with permits, RAMS and insurance validated before works begin. - Resident and stakeholder communications are timely, clear and proactive, reducing queries and escalations. - Accurate compliance reporting is delivered to management on time, highlighting trends, risks and recommendations. These are responsibilities/expectations. How You'll Spend Most Of Your Time bullet points: - Managing the compliance calendar for lifts, fire safety, water hygiene, electrical testing and other statutory checks. - Coordinating contractor visits, verifying RAMS, insurance and permits to work, and arranging access with onsite teams. - Maintaining digital records, certificates and logs to ensure full audit readiness and traceability. - Tracking remedial actions from audits and risk assessments, chasing updates and closing out works. - Producing regular compliance reports and dashboards for property managers and senior stakeholders. - Responding to queries from residents and colleagues, providing clear information and next steps. These are duties. Who This Role Is For bullet points: - You are highly organised, detail-focused and comfortable managing multiple deadlines without losing accuracy. - You communicate confidently with contractors, residents and colleagues, adapting your style to the audience. - You take ownership, spot risks early and follow through until issues are resolved. - You are calm under pressure and use sound judgement to prioritise what matters most. - You enjoy improving processes and leveraging systems to make compliance clear, simple and consistent. Experience That Helps bullet points: - Coordinating compliance, H&S or facilities tasks within residential or mixed-use developments. - Hands-on experience managing action logs from fire, water or general H&S inspections. - Using property or compliance systems to schedule, track and report (e.g. CAFM, document management tools). - Working with contractors, reviewing RAMS/permits and arranging site access safely. - Preparing reports or dashboards that turn technical information into clear updates. Benefits bullet points: - 20 days holiday plus bank holidays - Enrolment into the Rendall & Rittner pension scheme - Employee assistance programme supporting family, health, money and work - Employee referral scheme - Team uniform* subject to development - Fully funded training and development opportunities - Access to discounts across travel, retail, fitness and entertainment Pay: £32,000 - £35,000 Schedule: Monday - Friday 0900 - 1730 Now we need to output HTML fragment with sections. We must not repeat job title as heading. So noCOMPLIANCE COORDINATOR
. We need to decide which sections to include. We have content for: - About the role (development details + role overview) - Responsibilities (success criteria + daily tasks) - Requirements (personal attributes + experience) maybe we split into Requirements and Experience? But we only have headings: Requirements, Qualifications, Skills. We could put personal attributes under Requirements, experience under Qualifications? Or combine. Better: Use Requirements for personal attributes and experience combined. Or we could have Requirements for personal attributes, Qualifications for experience. But we need to avoid thin sections. Perhaps combine into Requirements. Thus:About the role
Development details...
Role overview: You will be the go-to person...
Responsibilities
- All statutory inspections... ...
- Managing the compliance calendar... ...
Requirements
- You are highly organised... ...
- Coordinating compliance, H&S or facilities tasks... ...
£32,000 - £35,000
maybe asPay
then. Schedule:
Schedule
Monday - Friday 0900 - 1730
We must not create sections with filler like "commensurate with experience". We have actual content. Now we need to ensure we don't include any boilerplate like "INTERESTED? Apply with your CV." etc. Also remove "About Rendall & R