Writing a full proposal is not a course assignment — it is a months-long effort with a real deadline attached to somebody’s salary. But the two fragments that decide most proposals are each about a page, and both are learnable in isolation. The project summary is what a programme officer reads to decide which panel sees it. Broader impacts is the section engineers routinely treat as an afterthought and reviewers routinely score hardest, because a vague broader impacts section is the clearest available signal that the rest was written in a hurry.
The NSF PAPPG — Chapter II for what the project summary must contain and the Intellectual Merit / Broader Impacts headings it requires. A live DOE funding opportunity announcement if your work is DOE-aligned, since the format differs.
None.
Work against a real, currently-open call. Named, with its deadline. A generic proposal teaches nothing, because every constraint that makes proposal writing hard comes from the call.
Your gap statement from Literature review and gap-finding is the raw material for the intellectual merit paragraph. If it does not fit, the gap was not specific enough — go back to it.
PDF, within the call’s stated page limits.
This replaces your writing entry for the week you do it. Submit it to that week’s WW assignment in Canvas — the same one you would have submitted anyway. It is not an extra piece of work on top of the log.
You do not submit anything to the milestone yet. When all four skills in M6 are done, submit the M6 — Stewardship assignment, which is just an index saying which week each one went in.