“Please complete your preparation.” Your client receives the reminder on Thursday. On Wednesday, they had already asked your consultant which part of the organisation the questions refer to. They are waiting for an answer.
This example is invented. The client has something to contribute, but cannot take the next step yet. Another reminder repeats the request without resolving the obstacle. For a consultancy offering a digital service under its own brand, this is a useful place to look beyond the questionnaire: does the communication reflect what is actually happening in the engagement?
Follow the next action
In our example, a consultancy asks a client to prepare for a workshop about a business process. The initial request sets out the information needed and an agreed date. If that preparation is still outstanding, a reminder may be useful.
Then the client asks whether the questions cover one site or the whole organisation. At this point, the next action belongs to the consultant. A suitable application could make the clarification visible to the team and pause the routine request for the client to finish this preparation. It would still show the unresolved work; pausing a reminder would not mean marking the task complete.
After the consultant clarifies the scope, the client can continue. If the clarification changes what can reasonably be prepared by the agreed date, the two sides should settle a new date. The application could then use that agreement for any later reminder.
These are proposed behaviours for this fictional service. A question should not silently cancel every deadline or suppress an urgent message. Here, we are considering routine workshop preparation, not incident reporting or professional warning duties.
Ask for the part that is still missing
Suppose the scope has now been clarified and the client has provided most of the preparation. One point remains: the function that coordinates the process during an interruption. A useful reminder could read:
“Before our workshop, please add the function responsible for coordination at the selected site by Tuesday. The other preparation answers have been received. You can open the remaining question in the portal. If you cannot identify the function, contact our team through the help option.”
The wording and date belong to the example. They show the remaining action, acknowledge what has already arrived and leave a route for help. The request does not ask the client to start again or imply that a routine preparation date is an emergency.
The GOV.UK Service Manual recommends messages that meet a user need and make the required action and timing clear. It also cautions against including sensitive information. In a consulting service, a reminder can point to the relevant work in the portal without copying confidential assessment details into an email. [1]
Keep a phone clarification connected
The client might call rather than use the portal's question field. That conversation should count. In the proposed journey, the consultant records the agreed scope and date against the preparation, so the next message uses the same understanding.
This does not require recording the call or copying every conversation into the application. A concise note of the relevant agreement may be enough. The client should be able to see the resulting next step. If the note is wrong, there needs to be a way to correct it.
GOV.UK's service standard recommends coordinating the online and offline channels that users need. Applying that idea here means a conversation with the consultant should not leave the client facing an unrelated instruction in the portal. [2]
Distinguish the message from the work
A delivery status tells you about the message. It does not establish that the preparation is complete. GOV.UK Notify, for example, explicitly says that its “Delivered” email status does not tell the sender whether someone opened or read the message. Other services have their own status definitions. [3]
If delivery fails, the consultancy needs a way to notice and resolve the contact problem. Repeatedly sending the same request is not evidence that the client has refused to respond. Equally, a successful delivery should not move an assessment into professional review.
Once the client submits the preparation, the proposed service confirms receipt and explains that the consultancy now takes over. Routine requests to complete that same preparation should stop. A later request for clarification can still be sent, but it should identify the new question. The Home Office's email pattern distinguishes actions for the recipient from actions for the service and advises against implying urgency where none exists. [4]
Turn the exchange into a usable service
Browserbite designs, develops and tests custom software around your consultancy's work. You explain the preparation, the points that require your judgement and the commitments you make to clients. We translate that into the interaction between the portal, your team's work and its messages.
For this example, we would test the journey through unanswered preparation, a clarification by phone, an agreed change of date and a completed submission. The purpose is to check that each message still asks for a relevant action. You would not need to design the sending rules or diagnose delivery systems yourself.
An existing task tool and a well-run shared inbox may already support this exchange. Custom software is worth exploring when keeping requests, clarifications and follow-up work connected is a recurring part of your service. Bring that exchange to a conversation with Browserbite. Together, we can establish whether a tailored application would make it clearer.
Sources and scope
[1] GOV.UK Service Manual: Planning and writing text messages and emails. Published 2017; current guidance accessed for this article.
[2] GOV.UK Service Standard, point 3: Provide a joined up experience across all channels. Updated 16 December 2025.
[3] GOV.UK Notify: Message status — emails. A product-specific explanation of delivery status.
[4] Home Office Design System: Send users an email. Guidance on next steps, support and urgency.
Sources checked on 5 October 2026. These UK public-service sources inform design choices; they do not establish legal duties for DACH consultancies or measured business benefits. The example is fictional and describes a proposed journey, not an existing standard product.