Cost calculator for deceased repatriation

How is a confirmed route selected?

The first searchable field contains only collection points for which at least one confirmed record exists. Free text cannot create another route. Once a city is selected, the second field is restricted to destinations released for that collection point. The component therefore cannot construct a price from two arbitrary place names.

When both values are present, the exact internal pair is checked. Only a matching confirmed record can display an amount. Indicative price means that the published starting figure still requires a fixed quotation for the circumstances of the case; it is not an automatic final invoice.

What appears in the result, and what is deliberately excluded?

The result presents the confirmed amount, the approved timescale for a routine case, the stated included services and an optional wooden coffin from €320. It does not expose internal distance, driving-time or named-crossing data. None of those values is needed to identify the confirmed record or explain the public price.

Where no record is approved, the calculator shows no average, distance formula or value taken from a neighbouring route. That absence is deliberate. A traceable individual enquiry is more reliable than an apparently precise number without an approved basis.

How are the chosen places passed to the enquiry form?

The send-details button copies only the visible collection and destination labels into their matching form fields and moves the page to the form. It does not generate a person’s name, telephone number or note. The user enters those details and can inspect every field before submission.

The contact form asks for the location of the deceased, destination, callback number and an optional message. Its privacy information identifies the controller, purpose, legal basis, retention and individual rights. The calculator is not a medical record and should not be used for unnecessary clinical detail.

Which information is stored in the shareable page link?

After a selection, technical location slugs are written to the URL fragment so the combination can be reopened or shared. The fragment is not designed to contain the deceased person’s name, telephone number, cause of death or a free-text message.

Data minimisation here has a practical meaning: two location identifiers are needed for selection, and a callback additionally needs the number deliberately entered into the form. Other information is not placed in the address pre-emptively. On a shared device, the route selection can be cleared before leaving.

How are anti-spam protection and analytics separated?

Technical anti-spam protection examines signals associated with automated submissions. Cloudflare documents how Turnstile performs that role, while the site privacy notice identifies the service actually used. Google documents Consent Mode for adapting tag behaviour to a visitor’s consent choice.

An analytics event may measure use of the calculator without sending the deceased person’s name, a callback number or the note as an event parameter. Route selection remains functionally separate from submitting personal information. The privacy information next to the form applies when an enquiry is sent.

How can the calculator’s data flow be audited?

At page load, the component receives approved location slugs and confirmed records from the build. Search only filters that supplied list; it neither calls an external pricing service nor creates a city from free text. Choosing a collection point derives the destination options from exact matching entries.

A result appears only when origin and destination belong to the same record. The amount, routine timescale and approved inclusions are not calculated from browser parameters. If somebody edits the URL fragment, the component validates the slugs again and rejects values absent from the supplied lists.

Moving to the form inserts only readable place names. An enquiry is created only when the user submits the form with a callback number. These two actions remain technically and substantively separate, so a route check can occur without unnecessary personal case details.

How can the calculator be used without a mouse or JavaScript?

The searchable controls use labelled inputs and a keyboard-operable option list. Focus, arrow keys, Enter and Escape support selection, while result changes appear in a designated live region.

Without JavaScript, a static alternative lists confirmed routes where records exist and provides a direct contact method. The fallback must not display an unconfirmed estimate either.

Which controls prevent an incorrect price from appearing?

Before release, verify that every visible pair has a confirmed price record, both places exist in the controlled lists and currency formatting is correct. One test deliberately edits the URL slugs; unknown values must produce no result. Another confirms that a selected collection point exposes only destinations actually approved for it.

Compare the result wording with the public data source. Unconfirmed entries must not reach HTML, structured data or the non-JavaScript fallback. If confirmation is withdrawn, the following build should remove that choice automatically.

Test transfer to the form as a separate action. Both places must reach the correct inputs without replacing a telephone number or message. Keyboard operation, focus order and mobile layout are release requirements because an accurate figure has limited value when it cannot be selected and queried safely.

Sources and review date