If you're about to start commissioning a medical website for your practice or clinic, know this up front: most of the trouble starts with vague contract clauses, not with the design. So before you sign, get these in writing: the basic information, the feature scope, who signs off on what, the scheduling prerequisites, who owns which accounts, and the handover tests. This checklist is the same list I go through as a project manager before every medical project kicks off.
What information should you prepare before commissioning a medical website?
Before commissioning a medical website, gather your list of doctors and services, their working schedules, and your booking and cancellation rules. You also need clear contact details and branches, a named person who approves content, and the details of your practice management software. Then write the essential features, whether you need online payment, who owns the domain and who signs off on handover into a one-page brief.
A brief is a short document that captures the project's needs in plain language. My suggestion: next to each item, note who supplies the information and who approves it, and how. Why do I insist on names? Because an item without an owner usually stays empty until the final week.
Brief item | Information owner | How it's approved |
|---|---|---|
List of doctors and services | Practice manager | Each doctor signs off on their own entry |
Schedules and booking and cancellation rules | Receptionist | Approved by the practice manager |
Contact details, address and branches | Practice manager | Checked against the practice's signage and letterhead |
Practice software | Receptionist or IT lead | Software name and a contact for its support team |
Domain owner and handover approver | Practice manager | Name and role of both in the brief |
Don't confuse the documents needed to design a medical website with the documents a payment gateway or SMS provider might ask for. For the design itself, three things are usually enough: professional information you're happy to publish, permission to use the images, and the name of the person authorised to give approvals. Gateway and SMS requirements vary from provider to provider, so ask each one separately.
An initial estimate for a medical website doesn't need any real patient data either. If someone asks for it, ask why before you do anything else.
Which features are essential, and which can wait for a later phase?
The rule is simple. A feature is essential if the practice can't operate on launch day without it. Everything else can safely move to a later phase. For each feature, write down three things: whether it's needed on day one, what a passing acceptance test looks like, and what stays outside the contract.
Take a hypothetical practice with two doctors. Its table might look something like this:
Feature | Launch day | Testable output | Outside the contract |
|---|---|---|---|
Doctor profiles | Required | A page for each doctor with specialty and schedule | Writing specialist copy, unless agreed separately |
Appointment booking | Required | A booking made on a phone appears in the receptionist's panel | Booking for a branch that hasn't opened yet |
Online payment | Depends on the booking model | Successful and failed payments leave the appointment in the right status | Automatic refunds |
Online medical records | Usually not | — | The whole feature; a separate project |
When you're commissioning a medical website, this table is what heads off the familiar “I thought that was included” argument. You may need online medical records one day. They're still better handled as a separate project with their own estimate.
Choose one of the two booking models now, too. With an “appointment request”, the patient only sends a request and the receptionist confirms it later. With a “confirmed booking”, the system takes the slot the moment the patient books. Your SMS wording and on-screen messages must match your model. Under the first model, for example, “Your appointment is confirmed” misleads the patient, because nobody has confirmed anything yet.
For integrations with the practice software, payment gateway and SMS provider, ask for costs on three separate lines: setup, subscription and usage. We cover budgeting in detail in medical booking website costs and the maintenance budget. Here we're only drawing the contract boundary. If you're still unsure about the features themselves, our medical website design guide, from search to appointment will be more useful.
Who prepares and approves the doctors' content?
The doctor approves the accuracy of the medical content. The receptionist checks the operational rules. The agency is responsible for entering and displaying the agreed content correctly. In other words, the agency doesn't edit medical copy for clinical accuracy. Its job is to put that exact copy on the site, complete and correct.
When commissioning a medical website, fill in this checklist with people's names, not a generic “the practice”. When an approval stalls, you need to know who to call:
Bio text: written by the doctor or practice manager; approved by the doctor.
List of services: prepared by the practice manager; the doctor confirms the service names are accurate.
Approved images: supplied by the practice manager, who keeps written permission for each photo.
Schedules: prepared by the receptionist; approved by the practice manager.
Cancellation and rescheduling rules: proposed by the receptionist; approved by the practice manager and the doctor.
Entry and display on the site: done by the agency; reviewed by the receptionist or practice manager.
Then turn this list into an appendix to the medical website contract. Keep each item's delivery date and approved version in the project's working file. That file pays for itself later, because it settles “which version was final?” on the spot.
Write down the rule for changes after approval, too. Fixing a typo takes a few minutes. Adding a new doctor or service means a new page, a new schedule and new booking rules. Don't lump the two together in the contract.
Drop one common assumption as well: a patient's photo or story isn't automatically publishable. Think of before-and-after treatment photos, or a patient's own account of their treatment. Publishing them depends on valid patient consent and on checking the relevant professional rules. Until both are settled, leave their spot in the design empty.
What does the medical website timeline depend on?
Coding speed matters less than three other things: content readiness, how fast approvals come back, and access to outside systems. That's why you should write each stage of the project with an entry condition and an output. A single end date with no prerequisites won't hold.
Stage | Entry condition | Output |
|---|---|---|
Brief and scope | Meeting with the practice manager and doctors | Approved brief and feature list |
Visual design | Approved brief and sample content | Approved design for the main pages and the booking flow |
Build | Approved design and final content | A test version of the site (staging) |
Integrations | Test access to the practice software, gateway and SMS | Integrated booking and payment on the test version |
Acceptance testing | Complete build and dummy data | Signed acceptance record |
Launch | Written handover approval and completed training | Live site and a monitoring plan for the first few days |
Track four dependencies separately: content, design approval, test access to the practice software, and activation of payment and SMS. Give each one an owner, and note how a delay would affect the schedule. A delay caused by an outside supplier isn't necessarily the agency's delay. The agency should still flag it early, though, not at the handover meeting.
Say the design is approved, but the practice software's support team still hasn't provided test access. You can review the look and the booking flow. Integrated booking, however, isn't ready for final acceptance. This is exactly where I'm strict in progress reports. Until someone has actually tested the integration, the report shouldn't show that line as “done”.
A delivery date without written prerequisites is a hope, not a plan.
After you've placed the order, re-estimate time and cost every time the scope changes. No fixed timeframe fits every practice. If an agency gives you a firm date before seeing your brief, ask what assumptions that date rests on.
Ownership of the domain, code and access in a medical website contract
When commissioning a medical website, don't treat handing over a password as transferring ownership. Anyone with access to an account can change its password. The real owner is set by the registered details and the recovery email. Picture a domain whose recovery email belongs to an employee who later leaves the practice. Getting that domain back becomes a real headache. Register the domain under the agreed owner's details, and give the recovery email to the practice's authorised representative.
Then list every account and note four things for each:
Account name: domain, hosting, SMS, payment gateway and the site's admin panel.
Owner: the person or organisation the account is registered to.
Access level: who is a full admin and who is only an editor.
Renewal owner: who tracks the renewal date and pays for it.
For the code, separate three categories in the medical website contract. First, the code the agency writes for you and hands over. Second, components you only have a licence to use, such as a ready-made theme or plugin. Third, services that belong to outside suppliers, like the practice software or the SMS platform.
The point of this split is simple. If the practice ever switches agencies, it should know exactly what it keeps. Include regular backups and at least one restore test in the contract as well. A backup you've never tried restoring is just an assumption. After handover, remove the agency's unnecessary access and keep only what support requires.
For general clauses like payment, termination and dispute resolution, read our guide to writing a professional website design contract. This section is no substitute for legal advice, though. Agree the final wording with the practice's legal adviser.
What are the acceptance criteria for booking, payment and practice integration?
“The site is up” isn't an acceptance criterion. Acceptance criteria for a medical website are a list of test scenarios. Each scenario has a written expected result and the signature of the person who approves handover. That's why the first question I usually ask on any medical website project is this: what happens if the patient's internet drops in the middle of a payment?
Build your acceptance form with these columns. Here's a sample row:
Scenario | Precondition | Expected result | Actual result | Test evidence | Status | Approved by |
|---|---|---|---|---|---|---|
Two patients try to book the last slot at the same time | One free slot; confirmed booking model | Only one is confirmed; the other sees a “fully booked” message | Filled in after the test | Screenshot and panel log | Pass or fail | Name and date |
Then add at least these scenarios to the form:
Booking: a normal booking, and two people going for the last slot at the same moment. Under the confirmed booking model, only one appointment should be confirmed.
Payment: successful, failed, and an interrupted return from the gateway. That last case means the patient paid at the gateway but the page never came back to the site. An unclear status needs a follow-up path and must not create a duplicate appointment or payment.
Cancellation and rescheduling: test both against the agreed refund rule. If automatic refunds aren't in the contract, don't assume you're getting them.
Practice integration: decide which system is the source of truth for availability, meaning which one wins when the site and the practice software disagree. Simulate a connection outage. Once the connection is back, the system mustn't create duplicate records.
Mobile and roles: run the tests with dummy data, on a phone, and using the receptionist's account. Check that each role sees only the patient information it needs.
Accessibility: the site should be usable by everyone, including someone who only uses a keyboard. Fill in the booking form once without a mouse.
For a fuller list, the web accessibility resources and the web application security testing guide are reliable references. You don't have to run them all yourself. Ask the agency which ones they've tested and where they recorded the results.
A site's real test comes in the busy, broken moments, not on a quiet day.
Sort test results into two groups: blocking defects, like a duplicate appointment, and minor issues, like a misplaced button. Final handover only means something once the main tests pass and the handover approver signs off in writing. Minor issues don't need to hold up handover. Record them in the acceptance record with a deadline for fixing them.
What should front-desk training and the launch plan deliver?
The output of training is a skill you can see, not a signature on an attendance sheet. The receptionist or front-desk lead should be able to create an appointment, move it and block out a day off, all without the agency's help. If they do those three things in front of you, the training has worked.
Alongside that skill, make sure you receive these deliverables:
A short guide to daily operations, a page or two long, written in the receptionist's language rather than a developer's.
An escalation path for payment or integration errors: who to contact, through which channel, and with what information.
A separate account for the receptionist's stand-in, with suitable access rather than full access. Otherwise, the day the receptionist is on leave, their password starts getting passed around.
For launch day, settle three things in advance: who monitors the site, how confused patients get answers, and how to temporarily switch off a faulty booking flow. Switching booking off should be simple enough for the practice manager to do. Picture the first morning: confirmation texts aren't arriving and the practice phone won't stop ringing.
If your new medical website replaces an existing system, actually test the backup and the way back (rollback) before you switch over. A rollback lets you return quickly to the previous setup if the new system has problems. The most sensitive point is the appointments patients make during the transition. Then, in the first days after launch, reconcile the site's appointments with the practice's records so no availability mismatch stays hidden.
What evidence should you ask for when choosing a medical website design company?
Instead of screenshots, ask each company for a live demo: booking, capacity management, and handling an uncertain payment. An uncertain payment is one where nobody can yet tell whether it went through. A screenshot only shows the look. A live demo shows whether the team has thought about the hard moments.
Ask for these three documents too:
A blank template of their handover record.
How they log and track bugs during the testing period.
Their list of prerequisites for integrating with practice software.
You don't need to see other clients' patient data for any of this. Blank templates are enough. In fact, if an agency shows you real data, that's a red flag in itself. Someone who shows you other people's patient data may show yours to someone else tomorrow.
Before you finalise the order, compare proposals only against a shared brief and a shared list of scenarios. Big gaps between estimates sometimes come down to one bidder leaving out practice integration or training. Without a common baseline, the cheapest proposal may simply be the most incomplete. Ask every bidder this question as well: “If the practice software supplier doesn't grant access, which parts can you still deliver, and what stays open?”
Some questions about the team and how they work aren't specific to medical websites. For those, see key questions for evaluating a web design company.
نمونهکارهای ما در همین زمینه
Medical site
SMS gateway and payment gateway fees are separate and listed before we start. Clinical copy, where needed, is written for review by the practitioner.
Where support ends and new development begins: your estimate request pack
Support means fixing behaviour that doesn't match the accepted criteria. Any new request is new development. When commissioning a medical website, most disputes after handover happen right at this boundary. It's best to write the boundary into the contract with examples:
Request | Support | New development |
|---|---|---|
Duplicate appointment or a wrong message sent to a patient | Yes | — |
Behaviour that contradicts the acceptance criteria and wasn't caught in testing | Yes | — |
Changing the cancellation rule or booking model | — | Yes |
Adding a new branch | — | Yes |
Connecting to a different payment gateway or SMS provider | — | Yes |
Put these in the contract: when support starts and how long it lasts, response hours, the channel for logging requests, and the severity levels for errors. Keep in mind that response time isn't fix time. “We respond within a few hours” means someone has seen your message, not that the problem is solved.
Outages at the gateway, the SMS provider or the practice software are sometimes outside the agency's control. Even so, someone needs to chase them and keep the practice informed. Put that person's name in the contract.
Now put together your estimate request pack. It's essentially the output of this checklist:
A one-page brief with an owner and an approval method for each item.
A list of essential features and later-phase features.
A responsibility table for the doctor, the receptionist and the agency.
Integration prerequisites: the name of the practice software and of the gateway and SMS providers.
An acceptance form with the main booking, payment and cancellation scenarios.
Don't include passwords or patient data in this pack.
Ask every agency you speak to about your medical website to break down their estimate. You need four lines: core cost, assumptions, out-of-scope items and recurring costs. Assumptions matter most. An estimate that doesn't state its assumptions comes back later as “that wasn't included”.
Your next step is simple. This week, sit down with the practice manager and the receptionist, write the one-page brief, and put a name next to each item. The rest of the checklist builds on that single page. If it's right, the rest of commissioning a medical website goes much more smoothly.
If your pack is ready, send it for review through Niasa's medical website design services. At Niasa, we first go through the pack with you and ask about any open questions and integration prerequisites. Only then do we give an estimate. That's why we don't quote a firm price or timeline before that review.
فهرست امکانات ضروری، قواعد رزرو و مشخصات نرمافزار مطب را برای بررسی محدوده و درخواست برآورد به نیاسا ارسال کنید.
Frequently asked
5Can I commission a medical website before the content is ready?
You can start the needs assessment and scope definition. Content delivery, though, needs a named owner and a deadline. Placeholder content is fine for reviewing the design, not for final publishing approval.
When does the medical website timeline start?
The contract should define the start point. Signing it doesn't always mean the prerequisites are in place. Receiving content, design approval and integration access can each set when different parts of the work begin.
Is integration with practice software included in every contract?
No. Standalone booking and integrated booking are two different scopes. Agree on the system's name, technical access, the data exchanged and who pays for the integration before anyone commits.
Who should approve handover of a medical website?
The client's authorised representative approves contractual acceptance. The front-desk lead should check day-to-day booking operations. Approving how the site looks doesn't prove the practice's operations work.
Is every change after handover covered by support?
No. The baseline is the agreed scope and acceptance criteria. A delivered feature that breaks is different from a request for a new feature. Put the handling terms for each in writing.








