Digital IT Operations

Welcome to the GUS Digital Operations (IT) Support Portal. Here you can raise requests for all things Digital (IT) related. From requesting access to one of our websites through to support with the performance of your site, UX/UI reviews, change and feature requests. Compliance reviews and even new Website Development.

For governance and process all documentation can be found here: https://gus.sharepoint.com/sites/WebsiteGovernance/SitePages/governance.aspx

What can we help you with?

Project Request

Please ensure you add as much information and context as possible. The more clearly the problem, context, journeys, and desired outcome are described, the faster teams can move from discussion to delivery. When briefing a project, assume the delivery team does not share your context.

A clear brief transfers knowledge from the stakeholder’s perspective to the delivery team so they can:
• Understand the problem
• Design the right solution
• Deliver efficiently.

You can also find our guides to writing a successful brief here: https://gus.sharepoint.com/sites/WebsiteGovernance/SitePages/governance.aspx

Required fields are marked with an asterisk

Email confirmation to(required)

Project Title(required)

Please enter the name of your project

Business Owner(required)

Please enter the name of the business owner (Who is accountable for this request and able to make decisions if trade‑offs are required?)

Business Context(required)

Provide the background to this request: the current situation, drivers or issues prompting it, and the impact on users or the business if not addressed.

Problem Statement(required)

Clearly describe the specific problem or issue being experienced today. Focus on what is not working or causing friction, rather than the solution you want.

Current User Journeys(required)

Describe how the process works today for each key user (for example, customers, internal teams, or partners). Include where friction, delays, or workarounds occur.

Desired Outcome(required)

Describe what should be different once this work is complete. Focus on the change in behaviour, experience, or decision‑making for users or the business — not the solution itself.

Scope(required)

Define what this request should include and, where helpful, what it should not include. Be clear about boundaries so expectations are aligned from the start.

Out of Scope(required)

List anything that is explicitly not included in this request. Call out assumptions or related items that might be expected but are not part of this work.

Systems Involved(required)

List any systems, platforms, or tools currently involved in this process, or likely to be affected by this request (for example CMS, CRM, analytics, third‑party tools).

Success Measures(required)

How will we know this work has been successful? Include any metrics, indicators, or observable changes where possible.

Dependencies/Constraints(required)

List any known dependencies, deadlines, approvals, compliance considerations, or external factors that could affect delivery.

Deadline(required)

e.g. 30/May/26

Deadline for this project (please note depending on requirements and solution, this may not always be feasible)

Timing Considerations(required)

Are there any timing considerations that make this request important now? (For example, regulatory deadlines, peak periods, or dependency on other work.)

Supporting Materials

Drag and drop files, paste screenshots, or browse

Attach any screenshots, data, examples, or links that help illustrate the problem or current process.