Charity Website Crisis Signposting: How to Add Safe Emergency and Safeguarding Information

Start with the boundary: what this guide is and is not

This guide is for small charities, peer support groups, community services, and volunteer-led organisations that want to make their website safer for people who may arrive in distress. It focuses on website wording, page structure, forms, automated replies, and internal ownership.

It does not tell you how to run an emergency service, make clinical decisions, investigate safeguarding concerns, or replace your organisation’s safeguarding policy. Your website can help people find the right route quickly, but it cannot make an unmonitored inbox safe for urgent disclosures.

A safe crisis signposting approach has three jobs: make the emergency boundary visible, route people to appropriate urgent help when needed, and explain what your organisation can and cannot respond to through normal website channels.

Why crisis signposting matters and where risk appears on a small charity website

For this guide, the practical planning assumption is that a distressed visitor may not land neatly on the page you expect. They might arrive through a search result, a shared link, a referral form, a footer link, or an old page. They may also use the quickest channel they can see, even if that channel is not monitored often.

That creates risk when ordinary website copy sounds more responsive than the organisation can safely be. Phrases such as “contact us if you need urgent help” or “tell us what happened” may feel kind, but they can accidentally suggest that the organisation is ready to receive and act on urgent information.

Start by auditing the pages and channels where someone could look for help or submit sensitive information. The aim is not to fill every page with alarming messages. It is to place short, clear boundaries at the moments where misunderstanding is most likely.

Write a clear crisis signposting box or banner

A crisis signposting box should be visible, calm, and bounded. It should not over-explain, diagnose, or ask the person to prove that their situation is serious. Its purpose is to move someone towards the right route before they use a slow or unsuitable channel.

Use wording your organisation can stand behind operationally. If you do not monitor messages outside office hours, say so. If volunteers cannot provide crisis support, say so. If the right emergency number or crisis support route depends on location, use a placeholder until your organisation has verified the correct local wording.

Create or improve a safeguarding information page

A safeguarding page should answer practical questions without making the visitor work through your full internal policy. People need to know what the page is for, what types of concerns it covers, how to raise a concern, what to do if the concern is urgent, and what to do if the concern is about your organisation or a named contact.

Write the page for people outside your organisation as well as staff or volunteers. Avoid internal shorthand. If you name a role, explain what that role is. If you ask people to email a safeguarding contact, state when that inbox is monitored and what route to use when immediate action is needed.

The page should also include a brief privacy and information-handling statement. Do not promise absolute confidentiality if there are circumstances where information may need to be shared to protect someone from harm. Use wording approved by the people responsible for safeguarding and privacy in your organisation.

Make contact forms, referral forms, inboxes, and automated replies safer

Forms and inboxes are often where the highest-risk misunderstanding happens. A visitor may treat a general form as the fastest route to help, while the organisation may only check it weekly. Safer wording needs to appear before the form starts, not only after someone has submitted information.

Use a short pre-form warning to explain what the form is for, what it is not for, when messages are checked, and what to do instead if the situation is urgent. If the form is not designed for safeguarding concerns, say that clearly and link to the safeguarding route. If it can receive safeguarding concerns, make sure the route has appropriate access controls, monitoring, escalation, and ownership.

Automated replies should not create false reassurance. A confirmation email can say that the message has been received, but it should also repeat that the inbox is not monitored 24/7, give realistic response times, and signpost urgent help again.

Privacy matters here. Do not send credentials, private records, analytics exports, screenshots containing private information, or identifiable sensitive records. If staff or volunteers need help reviewing a form or workflow, use non-sensitive examples or manually written topic summaries instead.

Use plain language and calm design so people can act quickly

Crisis and safeguarding signposting is not only a wording task. Design affects whether someone can find the right route quickly, especially on a small screen or when they are distressed.

Keep the message direct and respectful. Do not use blame-based wording such as “Only contact us if this is a real emergency.” Do not hide urgent boundaries in a long privacy notice or at the bottom of a form. Do not use a dramatic colour palette that makes the page feel like an alarm unless your design system already uses strong colours for warnings.

Approval, maintenance, and volunteer workflow

Crisis and safeguarding wording should not be left to one website editor to invent alone. It needs human approval from the people who understand safeguarding, operations, privacy, and the actual capacity of the organisation.

Create a simple ownership record for each page or channel. Name who approves the wording, who checks the route still works, who updates monitoring hours, and who volunteers should escalate concerns to if a message arrives through the wrong channel.

For volunteer-led organisations, the workflow should be realistic. If nobody can check messages daily, the website should not suggest daily monitoring. If a named person may be unavailable, the safeguarding page should explain an alternative route or role-based contact rather than relying only on one individual.

Before-and-after wording examples and pre-publish checklist

Use the examples below as wording patterns, not as legally approved templates. Replace placeholders with locally verified routes, realistic response times, and approved safeguarding contacts.

Before publishing, test the journey as if the visitor lands directly on the contact page, referral form, safeguarding page, or an old deep link. The emergency boundary should still be visible before they submit anything sensitive.

Self-serve next step: copy the checklist into your website publishing process and ask the safeguarding, operational, privacy, and website owners to review it together. Chestnut Communities is not currently offering paid reviews, implementation, urgent support, or automatic AI replies.

Where crisis signposting may be needed on the website

Crisis signposting wording: risk-prone vs safer alternatives

Safeguarding information page content map

Form and inbox safety checklist

Pre-publish crisis and safeguarding signposting checklist

This guide is not legal, clinical, or emergency-response advice

Evidence note: verify routes locally

Reusable crisis signposting box

Frequently asked questions

Should a small charity put crisis signposting on every page?
Not always. A site-wide banner can be useful if many visitors may arrive in distress, but it is not the only option. At minimum, place crisis and emergency boundaries where someone may look for help or submit information: contact pages, referral forms, safeguarding pages, help pages, automated replies, and relevant footer links. The right pattern depends on your service, audience, and capacity, so agree it with your safeguarding and operational owners.

What if our organisation cannot monitor messages every day?
Say that clearly before people contact you. Use wording such as “This inbox is not monitored every day” or “We usually reply within [timeframe]” only if the timeframe is realistic. Then signpost urgent situations to appropriate emergency, crisis, or safeguarding routes. Do not use vague reassurance such as “we’ll get back to you soon” if a visitor could mistake it for active support.

Can we use a contact form for safeguarding concerns?
Only if the form and workflow are designed for that purpose. Check who receives the messages, how often they are monitored, how information is stored, who can access it, how urgent concerns are escalated, and what alternative route exists if the concern is about the organisation or named contact. A general website form is often unsuitable for detailed or urgent safeguarding disclosures unless those issues have been addressed and approved.

What should an automated reply say when someone contacts us?
An automated reply should confirm receipt without implying that a person has assessed the message. It should repeat monitoring limits, realistic response times, and urgent-help signposting. For example: “Thank you for contacting us. This inbox is monitored during [hours] and we usually reply within [timeframe]. We are not an emergency service. If you or someone else is in immediate danger, contact your local emergency number now. If your concern is urgent, do not wait for our reply.”

Who should approve crisis and safeguarding wording before it goes live?
Approval should involve the safeguarding lead or equivalent, an operational owner who knows the organisation’s real response capacity, the person responsible for privacy or information governance, and the website editor or communications owner. If your organisation has trustees, a committee, or a board with safeguarding responsibility, check whether they also need to approve the wording.