Added cost, design and scrut notes based on feedback from Powertrain (paula and patryk voice memo)

docs/competition/index.md

@@ -1,33 +1,28 @@
 # Competition
 
-Formula Trinity competes in [Formula Student UK](https://www.imeche.org/events/formula-student), teams are assessed across three main areas:
+Formula Trinity competes in [Formula Student UK](https://www.imeche.org/events/formula-student). It is an engineering competition as much as a racing competition: teams are assessed on the design, manufacture, cost and safety of the car as well as its on-track performance.
 
-- [Static Events](statics/index.md) - Design Judging, Cost and Manufacturing, and Business Presentation
-- [Scrutineering](scrut/index.md) - Technical inspections required before the car can compete on track
-- [Dynamic Events](dynamics/index.md) - Acceleration, Skid Pad, Sprint, and Endurance
+This section explains what happens at competition, how to prepare and what the team learned from FTX7. It is written primarily for the IC team and should be used alongside the current competition rules.
 
-This wiki is written primarily for the IC team. Business Presentation is just included in the points breakdown for context.
+## What You Will Find
 
-As you can see, FSUK is not just a racing competition, it is an engineering competition. A good chunk of points are awarded for the team’s technical knowledge, engineering decisions, design processes, cost awareness and ability to justify the car as a complete vehicle.
+- [**Static Events**](statics/index.md) — Engineering understanding and justification of the car.
+  - [Design Judging](statics/design/index.md) — Vehicle goals, design decisions, trade-offs and validation.
+  - [Cost & Manufacturing](statics/cost/index.md) — Cost-report submissions and the in-person judging process.
+- [**Scrutineering**](scrut/index.md) — Inspections the car must pass before going on track.
+  - [Technical](scrut/tech/index.md) — Rule compliance and preparation for inspection.
+  - [Safety](scrut/safety/index.md) — General hazards, component security and driver safety.
+  - [Chassis](scrut/chassis/index.md) — SES compliance, templates, clearances and weigh-in.
+- [**Dynamic Events**](dynamics/index.md) — Acceleration, Skid Pad, Sprint and Endurance/Efficiency.
 
-```mermaid
----
-config:
-  theme: base
-  themeVariables:
-    pie1: "#A52332"
-    pie2: "#5D626C"
+## Points Breakdown
 
-    pieStrokeColor: "#111318"
-    pieStrokeWidth: "2px"
-    pieSectionTextColor: "#FFFFFF"
-    pieLegendTextColor: "#D6D8DE"
-    pieTitleTextColor: "#F2F3F5"
----
-pie showData
-    "Static Events" : 400
-    "Dynamic Events" : 600
-```
+The 1,000 available points are split between:
+
+- **Static events:** 400 points
+- **Dynamic events:** 600 points
+
+Static events account for 40% of the total score, so documentation, engineering understanding and the team's ability to justify its work are a major part of the competition.
 
 ```mermaid
 ---
@@ -60,3 +55,9 @@ pie showData
     "Sprint" : 100
     "Endurance/Efficiency" : 350
 ```
+
+*Business Presentation and Lap Time Simulation are included in the chart for context, although they are not currently covered in detail by this wiki section.*
+
+---
+
+![FTX7 during scrutineering at FSUK](../assets/images/competition/scrut/ftx7_at_FSUK.jpg)

docs/competition/scrut/safety/index.md

@@ -16,6 +16,8 @@ Bring the complete set of driver equipment for inspection. At FSUK 2026, drivers
 
 - Check that loose items, wiring, hoses and other components are securely retained.
 - Check that the floor, bodywork, intake and fuel rail are securely supported.
+- Check that engine and powertrain mounts are aligned, correctly supported and use appropriate inserts, bearings and fastener retention.
+- Finish and secure the cooling, exhaust, control-cable and gear-shift routing, keeping them clear of hot or moving components.
 - Check bodywork for gaps, movement, rattling and sharp edges.
 - Trim cable ties flush and cover exposed fasteners in the cockpit, especially around the driver's legs.
 - Fit rule-compliant head-restraint padding anywhere the driver's helmet could contact the roll structure, insulation foam is **not** suitable.

docs/competition/statics/cost/judging/index.md

@@ -9,12 +9,14 @@ Up to **10 team members** can attend the session. The exact format and number of
 ## What to Bring
 
 - A printed copy of the CCBOM for reference during discussion.
-- A searchable copy (*using* `ctrl+F`) of the CCBOM on a laptop so selected components can be found quickly.
+- A searchable copy (*using* `ctrl+F`) of the CCBOM on a fully charged laptop so selected components can be found quickly.
 - Two full printed sets of drawings so multiple judges can inspect them at the same time.
 - Assembly drawings and fully dimensioned manufacturing drawings for the selected area.
 
 The drawings and CCBOM should work as a complete manufacturing package: together, they should contain enough info for someone outside the team to make and assemble the relevant components.
 
+Practise navigating both the printed and digital reports before competition. Everyone attending should know how to find the CCBOM assemblies, labour rates, fastener and material costs, process costs and supporting tables. A dedicated navigation practice prevents the team appearing unfamiliar with information that is already present.
+
 ---
 
 ## Judging Format
@@ -77,6 +79,8 @@ Topics included:
 
 The exact direction of the discussion will depend on the judging panel and the answers given by the team.
 
+Verify suggested costing factors against the current year's rules before changing the report. Be prepared to explain whether items such as machine depreciation, maintenance, utilities or workshop floor space are required, excluded, included elsewhere or added as a team assumption. A judge's industrial experience may inform a question without making that costing method a competition requirement.
+
 ---
 
 ## FTX7 Feedback

docs/competition/statics/cost/pre_comp_submissions/CCBOM.md

@@ -11,4 +11,6 @@ Sequence matters. Within each assembly, list materials, manufacturing operations
 - Include the processes used to join components and complete each assembly.
 - Check that quantities, materials and processes agree with the submitted drawings.
 - Confirm that cost and carbon data use consistent, justifiable assumptions.
+- Export and print the final report early enough to correct page numbering or formatting problems.
+- Check the printed copy for page order, cropped content, section boundaries and missing assembly operations.
 - Ask someone unfamiliar with the assembly to use the CCBOM and drawings to explain how it would be manufactured.

docs/competition/statics/design/pt.md

@@ -33,4 +33,27 @@ loose cables and unfinished gear shifting system.
 
 ## Team Debrief Notes
 
-**Add notes here:** Record verbal judging comments, questions asked, what evidence worked well, and what should be prepared earlier next year.
+**NOTE:** *These notes were recorded by team members immediately after judging. They summarise verbal comments and questions from the judges and should not be treated as official feedback.*
+
+### Presenting the Design
+
+- Begin with the overall powertrain concept, including the department goals and why the engine and system architecture were selected.
+- Use an engine comparison table to show the alternatives considered and the trade-offs behind the final choice.
+- Divide supporting material into clearly labelled subsystem sections and tab important pages so evidence can be found quickly.
+- Understand the known weaknesses of the design and raise important ones proactively. Explain why the original decision was made, what was sacrificed, and what would be changed with more time or funding.
+- Prioritise a clear engineering explanation over memorising every equation or value. Detailed figures should still be available in the supporting material when requested.
+- Prefer solutions that can be manufactured, integrated and tested in the available time. Complexity is only valuable when its benefit can be demonstrated.
+
+### Analysis and Validation
+
+- Be ready to justify intake-runner length, plenum volume, and exhaust lengths and diameters using calculations, simulation or testing.
+- State what each model can and cannot predict. Do not present simulation results with more accuracy than the assumptions and validation support.
+- Link detailed 3D analysis back to the earlier hand calculations or 1D model that drove the design decisions.
+- Develop the 1D engine model until it can support component sizing and the engine specification, then validate it against controlled test data.
+- Use a dyno or dedicated engine test rig where possible to separate engine, intake, exhaust and calibration faults.
+
+### Integration
+
+- Review cooling and exhaust routing early enough to resolve conflicts before the car is assembled.
+- Design engine mounts around achievable chassis tolerances. Use the actual engine as a manufacturing reference where practical and do not compensate for poor alignment with an unsuitable washer arrangement.
+- Justify fuel-tank foam, pump and pickup positions with evidence. Show how fuel supply is maintained during acceleration and cornering, while accounting for manufacturability and chassis clearance.

docs/competition/statics/design/timing_planning.md

@@ -36,4 +36,5 @@ workshop due to size.
 
 - Include validation activities in the project plan, particularly when introducing a new design or process.
 - Allocate enough time to act on test results rather than scheduling validation immediately before competition.
+- Set an internal powertrain completion target well before competition. The FTX7 debrief suggested approximately two months to allow time for integration, controlled testing, repairs and validation.
 - When the plan changes, record what changed, why it changed and what the team did in response.