Technical design reviews explained

The review ensures your solution is sustainable and fits within our digital environment.

The TDA provides the final technical sign-off your proposal needs before you move to the development or procurement stage.

1. Get support before you submit

We strongly encourage you to engage with the Enterprise Architecture team early in your project. You should do this before booking a TDA review.

Getting support upfront is the fastest way to speed up your overall project timeline. This initial, informal discussion is the best way to strengthen your proposal, quickly identify risks, and ensure your design is ready for a smooth TDA review.

Meet the team and get in touch

2. The TDA process

Before you can procure or implement your solution, the TDA must review it. The TDA's role is not to block progress, but to help projects succeed by:

• providing diverse expertise and technical perspective
• identifying risks and integration issues early
• strengthening proposals before implementation.

The TDA provides an open space for discussion, feedback and to share expertise. The emphasis is always on constructive feedback and support. 

3. Book and prepare your session

The TDA meets weekly. To ensure a productive discussion and get on the agenda, follow these steps.

Booking a session

When your proposal is ready for review, you will need to meet with the TDA to discuss it.

You must request a slot and ensure all materials are submitted eight days before your meeting.

To request a meeting, either:

• email tda-group@york.ac.uk
• post a request in the #tda Slack channel.
• view availability: check the TDA Google Calendar.

Once your meeting is confirmed a shared Google Drive folder will be created for your materials, and you'll be added to the calendar invite and the #tda Slack channel for updates.

Supporting document checklist

You must provide a supporting document eight days before your session. It should include:

• background and rationale for the proposal
• overview of the proposed solution
• integration details (eg SSO, links to other systems)
• any comparative solutions considered
• timeline and key deadlines.

Depending on the stage of your proposal, you may also need the following:

• Computing risk assessment (CRA)
• Data Protection Impact Assessment (DPIA).

If in doubt, the Enterprise Architecture can help guide you through these assessments.

4. During a session

Sessions last up to 60 minutes. Initial comments from TDA members are typically shared the Friday before.

The proposer walks the group through the design, leading a discussion with TDA members. Sessions typically finish 10 minutes early to confirm outcomes.

Possible outcomes:

• accept a design (final sign-off)
• request changes or further information (sometimes requiring resubmission)
• make recommendations for improvements
• reject a design proposal (in rare cases).

The TDA review is your final technical sign-off before your proposal moves into the development or procurement stage. You will be sent the meeting notes and they will be shared in the #tda Slack channel afterwards.