-
Email or online ticketing support
-
Yes, at extra cost
-
Support response times
-
Ticketing support provides a controlled, auditable route for engaging the Architecture Governance and Independent Assurance Service. All requests for architectural review, assurance, advice, and standards clarification are logged and managed through an approved service management system. This ensures transparency, consistency, and traceability in line with public-sector governance and audit requirements. Tickets are prioritised based on service criticality, risk, and delivery impact, with clear ownership and documented outcomes. The ticketing process supports evidence-based assurance, enables reporting to governance and audit bodies, and provides management information to inform continuous improvement of architectural standards and controls.
-
User can manage status and priority of support tickets
-
Yes
-
Online ticketing support accessibility
-
EN 301 549
-
Phone support
-
Yes
-
Phone support availability
-
9 to 5 (UK time), 7 days a week
-
Web chat support
-
Yes, at an extra cost
-
Web chat support availability
-
9 to 5 (UK time), 7 days a week
-
Web chat support accessibility standard
-
EN 301 549
-
Web chat accessibility testing
-
Testing a web chat solution against requires a combination of automated testing, manual review, and assistive-technology validation. Testing should cover the full user journey, including opening the chat, sending and receiving messages, notifications, and closing the session.
Automated accessibility tools should be used to identify baseline issues aligned to World Wide Web Consortium WCAG 2.2 AA, such as missing labels, colour contrast failures, focus order problems, and incorrect ARIA usage. These tools provide initial coverage but cannot detect all issues.
Manual testing must confirm full keyboard operability, ensuring the chat interface can be used without a mouse. Focus must move logically, remain visible, and not be trapped. Dynamic updates, such as new messages or agent status changes, should be announced correctly to screen readers using appropriate ARIA live regions.
Assistive-technology testing should be performed using screen readers (e.g. NVDA, JAWS, VoiceOver), screen magnification, and speech recognition to validate real-world usability. Time limits, session expiry warnings, and error messages must be accessible and adjustable where required, chat transcripts, file attachments, and supporting help content must be tested for accessibility. All findings should be documented as audit evidence, with remediation actions tracked to closure to demonstrate compliance with EN 301 549
-
Support levels
-
Level 1 – Advisory & Triage Support
Provides a single point of contact for architectural enquiries, standards clarification, and initial triage of assurance requests. Supports early engagement and rapid responses to low-risk queries via a managed ticketing system during core business hours.
Level 2 – Design Review & Assurance Support
Provides structured architecture reviews and independent assurance for defined initiatives or changes. Assesses compliance with agreed principles, standards, security, data, and regulatory requirements. Findings and recommendations are documented with clear traceability.
Level 3 – Deep / High-Risk Assurance
Provides enhanced assurance for high-risk, business-critical, or regulatory-sensitive initiatives. May include multi-stage reviews, senior stakeholder engagement, and alignment with formal governance bodies.
Level 4 – Executive & Audit Support
Provides senior architectural input to executive forums and audit activities, including independent assurance statements, risk summaries, and support for regulatory scrutiny.
Service Characteristics
Risk-based prioritisation, defined response targets, audit-ready evidence, and alignment with Agile delivery models.
-
AI chatbot
-
No