Write the problem without a board name
“Build something with ESP32” names a tool, not a problem. “Show when a model tank reaches a selected level” describes an observable outcome. The second statement helps you decide which sensor, controller and output are needed.
Define the smallest credible demonstration
Separate the essential function from optional improvements. A local indication might demonstrate the problem before a mobile app or dashboard exists. Create a version that can be tested early and expanded only if the base is reliable.
Plan for evidence and explanation
For each requirement, write an expected result and a way to observe it. Include an invalid-input or disconnected-sensor case, not only a successful demonstration. Keep records of failures and the changes that resolved them.
Match scope to your team
Consider available equipment, component lead times, existing programming experience and college review dates. Assign work so everyone understands the whole system as well as their contribution. Your report should describe what you actually built and measured.