A meet the team page on a charity or nonprofit website does one job for a funder: it shows who runs the organisation and who holds it to account. Funders doing due diligence check it to verify who is in charge, what their backgrounds are, and whether the governance structure is visible and credible.

Many organisations have no team page, a page with first names only, or a static page that needs developer help whenever staff change. A content type in your CMS solves all three.

The Content Model

Field Type Notes
Full name Text, required First and last name
Role Text, required Job title or governance role, such as Chair of Trustees
Biography Long text Two to four paragraphs: background, experience, role here
Photo Image Professional headshot, with alt text
Category Option Staff, trustee or advisor
Display order Number Puts leadership first without relying on alphabetical sorting
LinkedIn Link, optional For senior staff and trustees who want one visible
Email Email, optional Staff who should be contactable through the site, never trustees' personal addresses
Active On/off Turns a profile off without deleting the record

Make alt text part of the editorial routine. It is WCAG 2.2 Success Criterion 1.1.1 Non-text Content, Level A. For a headshot, the alt text is the person's name. Do not add the role: it is already in the text beside the photo.

For the wider structure, see CMS architecture for nonprofit content teams.

What the Pages Show

Give each person a page with their photo, name, role and biography, linking back to the full listing and to your governance section. A funder who finds a trustee profile should be one click from the annual report.

The listing has three sections: leadership, staff and trustees, each filtered by category and sorted by display order.

The Trustee or Board Section

Separate trustees visually from staff, because funders are specifically looking for governance leadership.

Then link the section to the independent record. The Charity Commission's register shows a charity's trustees, work and finances, and since April 2020 every trustee's name has been displayed there unless a dispensation has been granted. It covers England and Wales. Elsewhere, link whichever public record lists your board.

Governance

When someone leaves. Switch the profile off, not delete it, and take it off the published site the same day. The governance policy should say who does this. See Website Governance During a Leadership Transition.

Lawful basis. A name on the public register does not carry its permission across to your website. Publishing someone's photograph, name and biography is your processing of their personal data, and it needs one of the lawful bases under Article 6 of the UK GDPR. Record it before the page goes live, cover profiles in your privacy notice, and decide in advance what happens when someone asks to be removed.

Photographs. A consistent style (same background, cropping and lighting) signals institutional seriousness, and a mixed set undermines it. On commissioning them, see ethical nonprofit photography.

For the broader framework, see How to Create a Website Governance Policy.

On Webflow? The platform-specific steps are in Platform Notes.

Next Step

Funders who check who runs you will check what you achieved next, so build the impact reports section they can verify.