Hi folks,

The Cost Report and Design Brief are both due this week for FSAE Michigan May, so I imagine you're feeling the pressure. Here's some advice that I would have liked as a competitor for managing these document submissions and to remind myself what's *actually* important:

For both events:

1. FSAEOnline experiences high load on Cost Report night and I sincerely recommend submitting at least 12 hours earlier than the deadline.
2. Did you *actually* read the guidance on FSAEonline for these documents in the rules and in Series Resources? Go read them again.
3. Do you *actually* know what the file types required, the length requirements, etc for these submissions? Go check them again.
4. Verify you have completed all workflows for all submissions and that they have been *actually* submitted. Starting a workflow is not enough, it must be *completed* before the deadline.
5. Are you *actually* using the correct templates for everything? Verify the version you are working with.

For Cost:

1. Read the Cost Supplement.
2. Read the Cost Module Guide.
3. Read the Check Cost Report Tool document.
4. Did you *actually* check the report for Obsolete Materials? Duplicating old cars and editing them introduces Obsolete items in the reports. See #3
5. Add Item Requests for Materials, etc take time to be processed and should be submitted asap.
6. Correct and Complete is best, but Complete is better than Correct.

For Design:

1. Read the 2024 Design Scoring Rubric.
2. Read the Three View Drawing Excellence Criteria.
3. Does your Design Briefing *actually* answer the questions presented in the rubric?
4. For each section, the following areas are expected to be addressed.
   Design
   Build
   Validation
   Does your section *actually* hit all of these points?
5. Has someone else not on your team or sub-team *actually* read and understood your ppt content?
6. Have you *actually* checked your grammar and spelling?
7. Does the content *actually* reflect what you've built or what you *wanted* to build?
8. Does the content *actually* show what testing (both component as well as system/vehicle testing) has been done and will be done, or what you *wanted* to do?
9. Is that screenshot or image *actually* relevant and adds value to the PowerPoint slide?

Best of luck, see you all soon.