UK Space Design Competition: win the contract, not just the idea

Editorial overview

The UK Space Design Competition places students inside an industry-style proposal rather than asking for an unconstrained vision of life in space. Large teams respond to a client request for a settlement somewhere in the solar system. They must interpret requirements, divide work across technical and management functions, integrate the design and present a case to experienced judges.

The contract framing is important. A spectacular idea can still fail if it ignores a requirement, conflicts with another subsystem or cannot be explained within the presentation. Regional and digital heats lead to a National Final at Imperial College London, where the format becomes larger but retains the same collaborative pressure. Selected national winners may then join the UK team for the international competition.

CompeteMap sees UKSDC as a strong fit for students who enjoy engineering decisions and fast team coordination more than months of physical construction. It accommodates structures, operations, automation, human factors, finance and presentation, so students do not need identical technical backgrounds. The challenge is making a large temporary team coherent. Good preparation focuses on requirements, interfaces and concise communication rather than pre-designing a favourite settlement.

Quick Facts

For current dates, eligibility and registration details, see the UK Space Design Competition page.

Read the brief as a contract

Turn every requirement into a traceable design response. Highlight quantities, operating conditions and mandatory functions. Create an interface table showing where structures, power, transport, life support and operations depend on one another.

Assign subsystem leads, but use regular integration reviews. A technically plausible power system is not useful if another group assumes a different capacity or location.

Present decisions, not a catalogue

The final presentation should prioritise the client's hardest concerns. Explain the requirement, chosen approach, trade-off and interface. Diagrams need readable labels and one purpose each.

Prepare for questions by identifying assumptions and risks. A team that can state what remains uncertain often appears more credible than one that claims every problem is solved.

Key Takeaways

• Treat the request for proposal as the source of truth.
• Manage interfaces between subsystems as actively as the subsystems themselves.
• Use the presentation to defend decisions and trade-offs, not list features.
• Check the CompeteMap and UKSDC pages for current heat and registration information.

Sources checked

• https://uksdc.org/
• https://uksdc.org/compete/
• https://uksdc.org/competition-overview-2/