University department website content checklist
A department site has to explain programmes to applicants, list staff and research for peers and give students one place for the things they need. The delays come from central brand rules, staff profiles and who signs off each page.
Where to start
- Contact and brand. Brand rules and central approvals decide the design limits, and they take the longest to confirm.
- Programmes. Programme facts are copied from the catalogue and drive what applicants see, so they need an early check.
- People. Staff profiles come from many people, so start the requests early and use the directory as a base.
- Research. Research themes need group leads to write or approve, which takes weeks.
- News and events. The page depends on a named editor and a calendar source, which can be settled in a short meeting.
The checklist
Home
Applicants, current students and visiting researchers all land here, and a department homepage that tries to serve all three equally serves none of them.
- Department name and parent faculty Short text, requiredThe name exactly as the university's brand guide spells it, followed by the faculty or school it sits in, for example 'Department of Earth Sciences, Faculty of Science'.
- Two-sentence department summary Short text, requiredSay what the department teaches and researches, and one thing a prospective student would not find at another university. Avoid rankings unless you can cite the source.
- Hero photo Image upload, requiredA landscape photo of the building, a lab or a field site that the department owns the rights to. At least 2400 pixels wide, with no logo or text on it.
- Audience priority order Single choice, requiredChoose the visitor group the homepage should address first. The other groups sit in a clear second tier.Prospective undergraduatesProspective postgraduatesCurrent studentsResearchers and partners
- News feed or announcements source LinkThe address of the news page or feed the department already uses. Say who writes it and how often it updates.
Programmes
Applicants compare programmes across universities, so each programme needs its own page with entry rules, structure and a named contact.
- List of programmes offered Long text, requiredEach programme's official title, level, mode of study and duration. Copy them from the university catalogue so names match the application system.
- Programme descriptions File upload, requiredOne Word or PDF file per programme, or the catalogue entry if it is accurate. The designer rewrites the page text for the screen and checks facts with you.
- Entry requirements per programme Long text, requiredState the entry rule as the admissions office states it, with a link to the central page for the final word. Do not paraphrase grade or language requirements.
- Application deadlines Long text, requiredThe closing date for each intake, with the year. Ask admissions to confirm, since dates are set centrally and change each cycle.
- Study levels shown Multiple choice, requiredTick every level the department teaches so the menu shows the right sections.FoundationUndergraduateTaught mastersResearch degreesShort coursesDoctoral training programme
- Links to the central application pages LinkThe address of the university's apply page for each programme. Programme pages send applicants there, so test each link.
People
Staff directories are the biggest content job on a department site, and they stall because profiles belong to the academics, not the web team.
- Staff list with titles and roles File upload, requiredA spreadsheet with name, title, role, office and email. Export it from the staff database if one exists, and say who keeps it accurate.
- Staff profile source Single choice, requiredSay where profile text comes from. This decides whether the department site pulls it or the designer imports it once.University staff directoryResearch information systemWritten by each personWritten by the department office
- Profile photos Image uploadOne portrait per person, at least 1200 pixels on the short side, from the university photographer or supplied by the person. Name each file after the person.
- Agreement for staff profiles online Yes or no, requiredConfirm each person listed has agreed to have their profile published. The university's own rules may add requirements, so check them with the central web team.
- Head of department welcome Long textAbout 200 words from the head in their own voice. Give the date it was last reviewed so the designer can flag it later.
Research
Peers and funders judge a department by its research pages, and the usual fault is a list of themes with no outputs behind them.
- Research themes or groups Long text, requiredName each group, its lead, a two-sentence description and the people involved. Link to its own page if one exists.
- Recent publications source LinkThe address of the repository or research system that lists outputs. The site can embed or link to it, so say which you prefer.
- Funded projects to feature Long textProject name, funder, dates and principal investigator for three to six projects. Check each funder's wording rules for acknowledgements.
- Facilities and equipment Long textLabs, collections or instruments partners can book. Give a contact person and whether external users are allowed.
- Research photos or figures Image uploadImages of experiments, fieldwork or data visuals the department owns the rights to. Include a caption and credit for each.
News and events
Events and news show the department is active, and they go stale when no one has the job of adding to them.
- Event types to list Multiple choice, requiredTick the kinds of event the department runs so the page can filter by type.Open daysSeminarsPublic lecturesConferencesStudent society eventsWorkshops
- Events calendar source LinkThe calendar or booking system that already lists department events. Say if the university's central events page must also show them.
- Five recent news stories File uploadThe text and photos for five stories from the last year as Word files. They set the style the designer builds the news layout around.
- Who publishes news and events Short text, requiredName the person who adds and removes items after launch. If there is nobody, the page will be removed or the dates will be wrong.
Students
Current students visit weekly, and the page works only if every link points at the live source instead of a copy that ages.
- Key links for current students Long text, requiredThe timetable, handbook, module system, library and support service links, with the name each is known by. Check each one before sending.
- Student handbook File uploadThe current handbook as a PDF, with its academic year on the front page. Say if a newer version is due before launch.
- Student support contacts Long text, requiredThe people or offices a student writes to for advice, extensions and wellbeing, with role titles and a shared email for each.
- Student society and group links Long textNames and web addresses for societies linked to the department. Ask each society to confirm the page can be listed.
Contact and brand
Brand rules and central approval decide how much freedom the department has, so these items come first in any build.
- Department address and contacts Long text, requiredBuilding name, street address, reception hours and the department email. Add a room or floor for each office a visitor might look for.
- University brand guidelines File upload, requiredThe current guide as a PDF, covering logo use, colours and approved fonts. Ask the central communications office if the version you hold is the latest.
- Department logo or lockup files File upload, requiredVector files (SVG, EPS or PDF) supplied by central communications. The department should not recreate the university mark.
- Brand colours and fonts ColourThe hex codes and font names in the brand guide. If a department palette exists, name the file where it is defined.
- Central web team approval needed Yes or no, requiredSay whether the university's web team must approve the design, hosting or domain before launch. This changes the schedule.
- Accessibility statement and privacy notice Yes or no, requiredConfirm the university's standard statements will be linked in the footer. If the department needs its own, name who writes and approves it.
What clients get stuck on
Staff profiles owned by each academic
Profiles come from dozens of people with their own priorities. Ask the head to send one email setting a deadline, and import what exists from the directory first so nobody starts from blank.
Central brand approval
Find out in week one whether the central communications team must approve designs, and how long a review takes. A rejected layout in the last week costs more than a slow answer in the first.
Programme facts that change each year
Entry rules, fees and deadlines are set by admissions, and the department copies are often stale. Link to the central page for anything that changes and keep only descriptions on the department site.
Image rights for lab and field photos
Photos taken by students or earlier staff may not belong to the department. Ask who took each image and whether the university has a licence before building a page around it.
An unowned news section
Departments launch with a news page and stop updating it. Ask for a named editor and a rule for how often a story appears, or build the page without a dated feed.
Copy the checklist
Plain Markdown you can paste into a doc or an email.
# University department website content checklist
## Home
- [ ] Department name and parent faculty (Short text, required)
- [ ] Two-sentence department summary (Short text, required)
- [ ] Hero photo (Image upload, required)
- [ ] Audience priority order (Single choice, required)
- [ ] News feed or announcements source (Link)
## Programmes
- [ ] List of programmes offered (Long text, required)
- [ ] Programme descriptions (File upload, required)
- [ ] Entry requirements per programme (Long text, required)
- [ ] Application deadlines (Long text, required)
- [ ] Study levels shown (Multiple choice, required)
- [ ] Links to the central application pages (Link)
## People
- [ ] Staff list with titles and roles (File upload, required)
- [ ] Staff profile source (Single choice, required)
- [ ] Profile photos (Image upload)
- [ ] Agreement for staff profiles online (Yes or no, required)
- [ ] Head of department welcome (Long text)
## Research
- [ ] Research themes or groups (Long text, required)
- [ ] Recent publications source (Link)
- [ ] Funded projects to feature (Long text)
- [ ] Facilities and equipment (Long text)
- [ ] Research photos or figures (Image upload)
## News and events
- [ ] Event types to list (Multiple choice, required)
- [ ] Events calendar source (Link)
- [ ] Five recent news stories (File upload)
- [ ] Who publishes news and events (Short text, required)
## Students
- [ ] Key links for current students (Long text, required)
- [ ] Student handbook (File upload)
- [ ] Student support contacts (Long text, required)
- [ ] Student society and group links (Long text)
## Contact and brand
- [ ] Department address and contacts (Long text, required)
- [ ] University brand guidelines (File upload, required)
- [ ] Department logo or lockup files (File upload, required)
- [ ] Brand colours and fonts (Colour)
- [ ] Central web team approval needed (Yes or no, required)
- [ ] Accessibility statement and privacy notice (Yes or no, required)
Questions about this checklist
Do we need to follow the university's central brand guidelines?
Almost always yes, and often with a review step. Ask the central communications team for the current guide and whether the department may use its own colours before you start the design.
Should staff profiles be pulled from a central directory?
If a central system is accurate, pull from it so profiles update in one place. If it is incomplete, import once and agree who maintains each profile after launch.
Who should own the department website after launch?
A named person in the department office who can edit pages and chase academics. Without one, staff profiles and events age quickly, and applicants see the dates first.
Related checklists
School
A school site has to answer parents' questions on admissions, term dates, uniform and safeguarding without a phone call. Requests here cover public content and policy documents only, and never pupil information.
Alumni association
An alumni site has to keep graduates in touch with each other and the institution through events, news and giving, without exposing their personal data. The hard parts are the member directory, consent and approval from the university.
Museum
A museum site has to sell a visit with opening hours, ticket prices and what is on now, then let people explore the collection online. Image rights for objects and who approves each page are what hold most builds up.