Start with who writes it
The what-to-do-now section is the part of an emergency dental page that tells a frightened person what to do in the next ten minutes. Knocked-out tooth, abscess, broken crown, lost filling.
It is clinical content. Every word of it must be written and approved by a clinician at your practice, and reviewed by them on a schedule. A web agency must never draft it, adapt it from another practice's site, or generate it. This post is about the structure that holds it, the workflow that keeps it current, and the technical work around it. The wording itself is not ours to supply, and you should be wary of anyone who offers to supply it.
If nobody at the practice has time to own the wording, leave the section out and point instead to the appropriate local urgent dental service and to the official NHS guidance for your nation. An empty section is a small loss. A wrong one is a serious problem.
Decide the scenarios with the clinical team
Ask the clinicians which situations actually arrive at your door, and take the four or five most common. In most practices the list looks like the one in the brief above, but yours may differ, and the list should reflect the emergencies your team really sees rather than a standard set copied from elsewhere.
Ask them also which scenarios should not be on the page at all, because the only correct answer is to seek urgent medical care. Facial swelling affecting breathing or swallowing, and significant trauma, are the usual examples. Those get a short, clinician-written line that sends the reader elsewhere immediately, placed above the rest.
The structure for each scenario
Every entry gets the same shape, which makes it quick to read on a phone at night and quick for a clinician to review:
- A plain heading naming the situation in the patient's words, not in clinical terms. "Knocked-out tooth", not "avulsed permanent tooth".
- A short block of what to do now, written by the clinician.
- A line saying how urgent it is and by when the patient should be seen, again from the clinician.
- The call button and the booking button, repeated inline.
Keep each entry to a few short paragraphs. Nobody reads a wall of text with a throbbing tooth.
Publish it as structured content, not as prose in a page builder
Hold each scenario as a record with fields: title, guidance body, urgency line, author, approved-by, approved date, review date. Render them into an accordion or a set of short sections on the page.
That structure buys you three things. The clinician can edit their own wording without touching layout. The page can display the reviewed date, which is a genuine trust signal. And the review date can drive an internal reminder so nothing quietly goes five years stale.
Show the provenance
Under the section, display the clinician's name and role, the date the guidance was last reviewed, and a line stating that the guidance is general information and does not replace an examination. Your clinician will want to phrase that last line themselves.
Naming a real, registered clinician as the author is worth more for trust than any design work on the page, and it also makes the review cycle somebody's actual job.
Set the review cycle and put it in the diary
Twelve months is a reasonable default and your clinical lead may want it sooner. Put the date in the same place the practice keeps its other recurring compliance tasks rather than in a website to-do list. Review it also whenever national guidance changes or the practice changes what it does.
Keep it fast
This section is often where an emergency page gets heavy: illustrations, a video, an embedded map per scenario. Resist all of it. Text and one small image at most, accordions that render their content in the HTML rather than fetching it on tap, and no third-party script anywhere near it.
The patient is on a phone on mobile data, and a guidance section that takes three seconds to appear has failed regardless of how good the words are.
Do not let it push the booking down
Order on the page: what you are and where, call button, hours, today's availability, the fee, unregistered patients, then the guidance. The guidance is genuinely useful and it is also read by people who will never book, so it sits below the blocks that convert rather than above them.
Accessibility and reading level
Short sentences. Real headings in order. Accordions built as buttons that work with a keyboard and announce their state. Adequate contrast, because a lot of this is read in the dark at arm's length. Ask the clinician to keep the language at the level they would use speaking to a patient, not the level of a case note.
What the web team is responsible for
The structure, the speed, the accessibility, the review reminders, the display of the approval metadata, and the discipline of refusing to write the words. That last one is the part that matters.
Where this sits
A properly owned guidance section, structured, dated and clinician-approved, is part of every emergency dentist website we build, and the same separation between our work and clinical wording runs through all the dental practice websites we make. Package details are on pricing. We build the frame. Your clinician writes what goes in it.