When a difficulty appears in a digital public service, acting calmly does not mean accepting an incomprehensible answer. A five-step plan helps protect rights, request support, and turn a specific incident into a verifiable improvement.
Step one: describe the problem#
Start with a description another person can understand: which procedure was attempted, on what date, using which device, what message appeared, and what outcome was expected. Separating facts from assumptions reduces unhelpful arguments. Retain the case number, a screenshot, and the channel used. This short log makes it possible to resume the issue accurately even when the support worker changes or several days have passed.
Start with a description another person can understand: which procedure was attempted, on what date, using which device, what message appeared, and what outcome was expected.
The second step is to retain a real route of access. If the website fails, request a telephone channel, an in-person appointment, office support, or an alternative format. Digitalisation should expand possibilities, not turn an application into a barrier. Ask who is responsible for the service and which support route is accessible. When there is urgency, state the deadline and ask for written confirmation of the incident so delay is not unfairly assigned to the user.
Gathering evidence does not require technical expertise. A dated screenshot, the wording of a notice, submitted documents, and a chronological note are usually enough. Do not share passwords or unnecessary personal data. Explain what each item demonstrates and remove sensitive information before sending an image through an insecure channel. Evidence turns an impression of failure into an issue the public body can investigate, correct, and communicate.
The request should be specific: a plain-language explanation, a correction, an alternative channel, access to the file, or information about an automated criterion. Ask for a response date and registration reference. If the reply does not resolve the matter, review available appeal or complaint routes. A firm, respectful tone helps keep attention on the solution, but clarity about the right and next step matters more than perfect wording.
Finally, check whether the measure worked for the person and for people who will arrive later. Confirm that the link is accessible, the deadline remains available, the decision gives reasons, and promised support exists. Safely share the incident with associations, libraries, or support teams when it may prevent similar harm. Improving a public service includes acknowledging the failure, explaining the change, and leaving a simple way to verify it.
Step two: protect access#
Start with a description another person can understand: which procedure was attempted, on what date, using which device, what message appeared, and what outcome was expected. Separating facts from assumptions reduces unhelpful arguments. Retain the case number, a screenshot, and the channel used. This short log makes it possible to resume the issue accurately even when the support worker changes or several days have passed.
The second step is to retain a real route of access. If the website fails, request a telephone channel, an in-person appointment, office support, or an alternative format. Digitalisation should expand possibilities, not turn an application into a barrier. Ask who is responsible for the service and which support route is accessible. When there is urgency, state the deadline and ask for written confirmation of the incident so delay is not unfairly assigned to the user.
Gathering evidence does not require technical expertise. A dated screenshot, the wording of a notice, submitted documents, and a chronological note are usually enough. Do not share passwords or unnecessary personal data. Explain what each item demonstrates and remove sensitive information before sending an image through an insecure channel. Evidence turns an impression of failure into an issue the public body can investigate, correct, and communicate.
The request should be specific: a plain-language explanation, a correction, an alternative channel, access to the file, or information about an automated criterion. Ask for a response date and registration reference. If the reply does not resolve the matter, review available appeal or complaint routes. A firm, respectful tone helps keep attention on the solution, but clarity about the right and next step matters more than perfect wording.
Finally, check whether the measure worked for the person and for people who will arrive later. Confirm that the link is accessible, the deadline remains available, the decision gives reasons, and promised support exists. Safely share the incident with associations, libraries, or support teams when it may prevent similar harm. Improving a public service includes acknowledging the failure, explaining the change, and leaving a simple way to verify it.
Step three: gather evidence#
Start with a description another person can understand: which procedure was attempted, on what date, using which device, what message appeared, and what outcome was expected. Separating facts from assumptions reduces unhelpful arguments. Retain the case number, a screenshot, and the channel used. This short log makes it possible to resume the issue accurately even when the support worker changes or several days have passed.
The second step is to retain a real route of access. If the website fails, request a telephone channel, an in-person appointment, office support, or an alternative format. Digitalisation should expand possibilities, not turn an application into a barrier. Ask who is responsible for the service and which support route is accessible. When there is urgency, state the deadline and ask for written confirmation of the incident so delay is not unfairly assigned to the user.
Gathering evidence does not require technical expertise. A dated screenshot, the wording of a notice, submitted documents, and a chronological note are usually enough. Do not share passwords or unnecessary personal data. Explain what each item demonstrates and remove sensitive information before sending an image through an insecure channel. Evidence turns an impression of failure into an issue the public body can investigate, correct, and communicate.
The request should be specific: a plain-language explanation, a correction, an alternative channel, access to the file, or information about an automated criterion. Ask for a response date and registration reference. If the reply does not resolve the matter, review available appeal or complaint routes. A firm, respectful tone helps keep attention on the solution, but clarity about the right and next step matters more than perfect wording.
Finally, check whether the measure worked for the person and for people who will arrive later. Confirm that the link is accessible, the deadline remains available, the decision gives reasons, and promised support exists. Safely share the incident with associations, libraries, or support teams when it may prevent similar harm. Improving a public service includes acknowledging the failure, explaining the change, and leaving a simple way to verify it.
Step four: request a response#
Start with a description another person can understand: which procedure was attempted, on what date, using which device, what message appeared, and what outcome was expected. Separating facts from assumptions reduces unhelpful arguments. Retain the case number, a screenshot, and the channel used. This short log makes it possible to resume the issue accurately even when the support worker changes or several days have passed.
The second step is to retain a real route of access. If the website fails, request a telephone channel, an in-person appointment, office support, or an alternative format. Digitalisation should expand possibilities, not turn an application into a barrier. Ask who is responsible for the service and which support route is accessible. When there is urgency, state the deadline and ask for written confirmation of the incident so delay is not unfairly assigned to the user.
Gathering evidence does not require technical expertise. A dated screenshot, the wording of a notice, submitted documents, and a chronological note are usually enough. Do not share passwords or unnecessary personal data. Explain what each item demonstrates and remove sensitive information before sending an image through an insecure channel. Evidence turns an impression of failure into an issue the public body can investigate, correct, and communicate.
The request should be specific: a plain-language explanation, a correction, an alternative channel, access to the file, or information about an automated criterion. Ask for a response date and registration reference. If the reply does not resolve the matter, review available appeal or complaint routes. A firm, respectful tone helps keep attention on the solution, but clarity about the right and next step matters more than perfect wording.
Finally, check whether the measure worked for the person and for people who will arrive later. Confirm that the link is accessible, the deadline remains available, the decision gives reasons, and promised support exists. Safely share the incident with associations, libraries, or support teams when it may prevent similar harm. Improving a public service includes acknowledging the failure, explaining the change, and leaving a simple way to verify it.
Step five: review and improve#
Start with a description another person can understand: which procedure was attempted, on what date, using which device, what message appeared, and what outcome was expected. Separating facts from assumptions reduces unhelpful arguments. Retain the case number, a screenshot, and the channel used. This short log makes it possible to resume the issue accurately even when the support worker changes or several days have passed.
The second step is to retain a real route of access. If the website fails, request a telephone channel, an in-person appointment, office support, or an alternative format. Digitalisation should expand possibilities, not turn an application into a barrier. Ask who is responsible for the service and which support route is accessible. When there is urgency, state the deadline and ask for written confirmation of the incident so delay is not unfairly assigned to the user.
Gathering evidence does not require technical expertise. A dated screenshot, the wording of a notice, submitted documents, and a chronological note are usually enough. Do not share passwords or unnecessary personal data. Explain what each item demonstrates and remove sensitive information before sending an image through an insecure channel. Evidence turns an impression of failure into an issue the public body can investigate, correct, and communicate.
The request should be specific: a plain-language explanation, a correction, an alternative channel, access to the file, or information about an automated criterion. Ask for a response date and registration reference. If the reply does not resolve the matter, review available appeal or complaint routes. A firm, respectful tone helps keep attention on the solution, but clarity about the right and next step matters more than perfect wording.
Finally, check whether the measure worked for the person and for people who will arrive later. Confirm that the link is accessible, the deadline remains available, the decision gives reasons, and promised support exists. Safely share the incident with associations, libraries, or support teams when it may prevent similar harm. Improving a public service includes acknowledging the failure, explaining the change, and leaving a simple way to verify it.
What to avoid#
Start with a description another person can understand: which procedure was attempted, on what date, using which device, what message appeared, and what outcome was expected. Separating facts from assumptions reduces unhelpful arguments. Retain the case number, a screenshot, and the channel used. This short log makes it possible to resume the issue accurately even when the support worker changes or several days have passed.
The second step is to retain a real route of access. If the website fails, request a telephone channel, an in-person appointment, office support, or an alternative format. Digitalisation should expand possibilities, not turn an application into a barrier. Ask who is responsible for the service and which support route is accessible. When there is urgency, state the deadline and ask for written confirmation of the incident so delay is not unfairly assigned to the user.
Gathering evidence does not require technical expertise. A dated screenshot, the wording of a notice, submitted documents, and a chronological note are usually enough. Do not share passwords or unnecessary personal data. Explain what each item demonstrates and remove sensitive information before sending an image through an insecure channel. Evidence turns an impression of failure into an issue the public body can investigate, correct, and communicate.
The request should be specific: a plain-language explanation, a correction, an alternative channel, access to the file, or information about an automated criterion. Ask for a response date and registration reference. If the reply does not resolve the matter, review available appeal or complaint routes. A firm, respectful tone helps keep attention on the solution, but clarity about the right and next step matters more than perfect wording.
Finally, check whether the measure worked for the person and for people who will arrive later. Confirm that the link is accessible, the deadline remains available, the decision gives reasons, and promised support exists. Safely share the incident with associations, libraries, or support teams when it may prevent similar harm. Improving a public service includes acknowledging the failure, explaining the change, and leaving a simple way to verify it.
Accessibility from the start#
Start with a description another person can understand: which procedure was attempted, on what date, using which device, what message appeared, and what outcome was expected. Separating facts from assumptions reduces unhelpful arguments. Retain the case number, a screenshot, and the channel used. This short log makes it possible to resume the issue accurately even when the support worker changes or several days have passed.
The second step is to retain a real route of access. If the website fails, request a telephone channel, an in-person appointment, office support, or an alternative format. Digitalisation should expand possibilities, not turn an application into a barrier. Ask who is responsible for the service and which support route is accessible. When there is urgency, state the deadline and ask for written confirmation of the incident so delay is not unfairly assigned to the user.
Gathering evidence does not require technical expertise. A dated screenshot, the wording of a notice, submitted documents, and a chronological note are usually enough. Do not share passwords or unnecessary personal data. Explain what each item demonstrates and remove sensitive information before sending an image through an insecure channel. Evidence turns an impression of failure into an issue the public body can investigate, correct, and communicate.
The request should be specific: a plain-language explanation, a correction, an alternative channel, access to the file, or information about an automated criterion. Ask for a response date and registration reference. If the reply does not resolve the matter, review available appeal or complaint routes. A firm, respectful tone helps keep attention on the solution, but clarity about the right and next step matters more than perfect wording.
Finally, check whether the measure worked for the person and for people who will arrive later. Confirm that the link is accessible, the deadline remains available, the decision gives reasons, and promised support exists. Safely share the incident with associations, libraries, or support teams when it may prevent similar harm. Improving a public service includes acknowledging the failure, explaining the change, and leaving a simple way to verify it.
Personal data and proportionality#
Start with a description another person can understand: which procedure was attempted, on what date, using which device, what message appeared, and what outcome was expected. Separating facts from assumptions reduces unhelpful arguments. Retain the case number, a screenshot, and the channel used. This short log makes it possible to resume the issue accurately even when the support worker changes or several days have passed.
The second step is to retain a real route of access. If the website fails, request a telephone channel, an in-person appointment, office support, or an alternative format. Digitalisation should expand possibilities, not turn an application into a barrier. Ask who is responsible for the service and which support route is accessible. When there is urgency, state the deadline and ask for written confirmation of the incident so delay is not unfairly assigned to the user.
Gathering evidence does not require technical expertise. A dated screenshot, the wording of a notice, submitted documents, and a chronological note are usually enough. Do not share passwords or unnecessary personal data. Explain what each item demonstrates and remove sensitive information before sending an image through an insecure channel. Evidence turns an impression of failure into an issue the public body can investigate, correct, and communicate.
The request should be specific: a plain-language explanation, a correction, an alternative channel, access to the file, or information about an automated criterion. Ask for a response date and registration reference. If the reply does not resolve the matter, review available appeal or complaint routes. A firm, respectful tone helps keep attention on the solution, but clarity about the right and next step matters more than perfect wording.
Finally, check whether the measure worked for the person and for people who will arrive later. Confirm that the link is accessible, the deadline remains available, the decision gives reasons, and promised support exists. Safely share the incident with associations, libraries, or support teams when it may prevent similar harm. Improving a public service includes acknowledging the failure, explaining the change, and leaving a simple way to verify it.
Explainable automated decisions#
Start with a description another person can understand: which procedure was attempted, on what date, using which device, what message appeared, and what outcome was expected. Separating facts from assumptions reduces unhelpful arguments. Retain the case number, a screenshot, and the channel used. This short log makes it possible to resume the issue accurately even when the support worker changes or several days have passed.
The second step is to retain a real route of access. If the website fails, request a telephone channel, an in-person appointment, office support, or an alternative format. Digitalisation should expand possibilities, not turn an application into a barrier. Ask who is responsible for the service and which support route is accessible. When there is urgency, state the deadline and ask for written confirmation of the incident so delay is not unfairly assigned to the user.
Gathering evidence does not require technical expertise. A dated screenshot, the wording of a notice, submitted documents, and a chronological note are usually enough. Do not share passwords or unnecessary personal data. Explain what each item demonstrates and remove sensitive information before sending an image through an insecure channel. Evidence turns an impression of failure into an issue the public body can investigate, correct, and communicate.
The request should be specific: a plain-language explanation, a correction, an alternative channel, access to the file, or information about an automated criterion. Ask for a response date and registration reference. If the reply does not resolve the matter, review available appeal or complaint routes. A firm, respectful tone helps keep attention on the solution, but clarity about the right and next step matters more than perfect wording.
Finally, check whether the measure worked for the person and for people who will arrive later. Confirm that the link is accessible, the deadline remains available, the decision gives reasons, and promised support exists. Safely share the incident with associations, libraries, or support teams when it may prevent similar harm. Improving a public service includes acknowledging the failure, explaining the change, and leaving a simple way to verify it.
Deadlines notices and alternatives#
Start with a description another person can understand: which procedure was attempted, on what date, using which device, what message appeared, and what outcome was expected. Separating facts from assumptions reduces unhelpful arguments. Retain the case number, a screenshot, and the channel used. This short log makes it possible to resume the issue accurately even when the support worker changes or several days have passed.
The second step is to retain a real route of access. If the website fails, request a telephone channel, an in-person appointment, office support, or an alternative format. Digitalisation should expand possibilities, not turn an application into a barrier. Ask who is responsible for the service and which support route is accessible. When there is urgency, state the deadline and ask for written confirmation of the incident so delay is not unfairly assigned to the user.
Gathering evidence does not require technical expertise. A dated screenshot, the wording of a notice, submitted documents, and a chronological note are usually enough. Do not share passwords or unnecessary personal data. Explain what each item demonstrates and remove sensitive information before sending an image through an insecure channel. Evidence turns an impression of failure into an issue the public body can investigate, correct, and communicate.
The request should be specific: a plain-language explanation, a correction, an alternative channel, access to the file, or information about an automated criterion. Ask for a response date and registration reference. If the reply does not resolve the matter, review available appeal or complaint routes. A firm, respectful tone helps keep attention on the solution, but clarity about the right and next step matters more than perfect wording.
Finally, check whether the measure worked for the person and for people who will arrive later. Confirm that the link is accessible, the deadline remains available, the decision gives reasons, and promised support exists. Safely share the incident with associations, libraries, or support teams when it may prevent similar harm. Improving a public service includes acknowledging the failure, explaining the change, and leaving a simple way to verify it.
Coordinate support without replacing#
Start with a description another person can understand: which procedure was attempted, on what date, using which device, what message appeared, and what outcome was expected. Separating facts from assumptions reduces unhelpful arguments. Retain the case number, a screenshot, and the channel used. This short log makes it possible to resume the issue accurately even when the support worker changes or several days have passed.
The second step is to retain a real route of access. If the website fails, request a telephone channel, an in-person appointment, office support, or an alternative format. Digitalisation should expand possibilities, not turn an application into a barrier. Ask who is responsible for the service and which support route is accessible. When there is urgency, state the deadline and ask for written confirmation of the incident so delay is not unfairly assigned to the user.
Gathering evidence does not require technical expertise. A dated screenshot, the wording of a notice, submitted documents, and a chronological note are usually enough. Do not share passwords or unnecessary personal data. Explain what each item demonstrates and remove sensitive information before sending an image through an insecure channel. Evidence turns an impression of failure into an issue the public body can investigate, correct, and communicate.
The request should be specific: a plain-language explanation, a correction, an alternative channel, access to the file, or information about an automated criterion. Ask for a response date and registration reference. If the reply does not resolve the matter, review available appeal or complaint routes. A firm, respectful tone helps keep attention on the solution, but clarity about the right and next step matters more than perfect wording.
Finally, check whether the measure worked for the person and for people who will arrive later. Confirm that the link is accessible, the deadline remains available, the decision gives reasons, and promised support exists. Safely share the incident with associations, libraries, or support teams when it may prevent similar harm. Improving a public service includes acknowledging the failure, explaining the change, and leaving a simple way to verify it.
Concrete cases#
Case 1. Leila could not attach a certificate from her phone. She recorded the error, requested an appointment, and submitted the document by an alternative route; the body extended the deadline. Case 2. Oscar received an automated refusal without reasons. He requested an explanation, provided additional information, and obtained human review. Case 3. An association tested a portal with screen readers, documented unlabelled buttons, and the council published a correction and checking date.
Short checking list#
Start with a description another person can understand: which procedure was attempted, on what date, using which device, what message appeared, and what outcome was expected. Separating facts from assumptions reduces unhelpful arguments. Retain the case number, a screenshot, and the channel used. This short log makes it possible to resume the issue accurately even when the support worker changes or several days have passed.
The second step is to retain a real route of access. If the website fails, request a telephone channel, an in-person appointment, office support, or an alternative format. Digitalisation should expand possibilities, not turn an application into a barrier. Ask who is responsible for the service and which support route is accessible. When there is urgency, state the deadline and ask for written confirmation of the incident so delay is not unfairly assigned to the user.
Gathering evidence does not require technical expertise. A dated screenshot, the wording of a notice, submitted documents, and a chronological note are usually enough. Do not share passwords or unnecessary personal data. Explain what each item demonstrates and remove sensitive information before sending an image through an insecure channel. Evidence turns an impression of failure into an issue the public body can investigate, correct, and communicate.
The request should be specific: a plain-language explanation, a correction, an alternative channel, access to the file, or information about an automated criterion. Ask for a response date and registration reference. If the reply does not resolve the matter, review available appeal or complaint routes. A firm, respectful tone helps keep attention on the solution, but clarity about the right and next step matters more than perfect wording.
Finally, check whether the measure worked for the person and for people who will arrive later. Confirm that the link is accessible, the deadline remains available, the decision gives reasons, and promised support exists. Safely share the incident with associations, libraries, or support teams when it may prevent similar harm. Improving a public service includes acknowledging the failure, explaining the change, and leaving a simple way to verify it.
Sources and next step#
Consult the Spanish Data Protection Agency, the Ministry for Digital Transformation and Public Administration, the Spanish Ombudsman, the Royal Board on Disability, and the competent authority. Always verify deadlines, appeals, and requirements on the relevant official website.
