Every section placed where the funder's announcement puts it, resubmission changes carried through and the sharing plan added: the full proposal example that completes PHLT 8046 in Week 11. Searches like "phlt 8046 week 11 assignment example", "phlt8046 week 11 sample" and "phlt 8046 week 11 example" land here.
What a finished PHLT 8046 Week 11 full proposal looks like
The application begins with a project summary and a short narrative on public health relevance, then the one-page specific aims, revised after Week 10. The research strategy follows in its three parts, significance, innovation and approach, with innovation drafted fresh this week and arguing what a sham-controlled design adds to earlier filtration research. The human subjects section, inclusion plan and data and safety monitoring arrangement come next, drawn from Week 9. A data management and sharing plan, written to NIH's policy, describes which de-identified data will be deposited, where, and on what schedule. Budget and justification sit alongside a biosketch for each key person, a facilities and resources statement for the composite institution, and letters from the health system and the information exchange. A cover memo lists the checks run before submission.
How a PHLT 8046 Week 11 example is structured
Ordering by the announcement rather than by the course calendar is the point of the week, since reviewers expect to find sections where the funder told them to look. The research strategy keeps the standard three-part division so significance, innovation and approach can be scored in sequence. Innovation is new here because earlier weeks built everything else, and placing it between significance and approach makes it argue from the gap toward the design. The protections material stays in one block so a reviewer attentive to participant safety reads it continuously. The sharing plan sits where the application instructions require and is cross-referenced from the approach. Letters of support are chosen for what they commit, access to records and exchange data, rather than for general endorsement. The cover memo is internal; it documents the consistency checks made across sections, particularly on aims wording.
Summary and relevance
A project summary and a plain-language relevance statement, both rewritten last so they describe the application as revised.
Aims to approach
The revised aims page, then significance, a new innovation argument, and the approach carrying Week 10's changes through every aim.
Protections in one block
Human subjects, inclusion and monitoring, taken from Week 9 with the sham-arm guidance updated to match the revised approach.
The sharing plan
Which de-identified data are deposited, in what kind of repository, on what schedule and under what access terms, written to NIH's policy.
People, place, letters
Biosketches, facilities and resources, and commitment letters from the two data partners, each naming what it provides.
A consistency memo
An internal checklist, not submitted, recording where aims wording, sample figures and timelines were compared across sections.
Where marks go in PHLT 8046 Week 11
Coherence across sections decides this grade more than the quality of any one part. A panel member who meets Aim 3 as confirmatory on the aims page and exploratory in the approach, or finds the budget still paying for the version the resubmission dropped, stops trusting the rest. Compliance with the announcement comes next, and a missing sharing plan or absent letter counts as a structural fault. The new innovation section is read for substance, since claiming novelty without saying what differs from prior work earns little. Readiness for submission is sometimes graded too, including whether the author knows the application moves through Grants.gov and depends on the institution's SAM.gov registration being active. Applications assembled by pasting earlier weeks together, seams and repeated background showing, read as a folder of assignments rather than one request.
Get a PHLT 8046 Week 11 example written to your instructions
Share the sections you have written so far with the final application prompt and its rubric, and an assembled proposal in your announcement's order is ready in 24-48h, the first without charge. The institution, data partners and study in this example are all invented; your application assembles the proposal your own course feedback has shaped.
PHLT 8046 Week 11 questions, answered
Does a class proposal need a data management and sharing plan?
If the course models an NIH application, generally yes, since NIH's policy expects one for research generating scientific data. The plan describes what data will be shared, how, when and with what restrictions. The example writes it briefly and cross-references the approach. Where your announcement comes from a different funder, that funder's own data requirements take the place of this one.
How do Grants.gov and SAM.gov differ?
Grants.gov is the system through which many federal applications are submitted. SAM.gov is where an organization registers to do business with the federal government, and an active registration is a precondition for applying. Neither is typically used for a class submission, but your rubric may ask for awareness of both. The example's cover memo mentions each in a line.
What usually changes when earlier weeks are put together?
Mostly the seams. Assembly exposes contradictions, repeated background and shifts in terminology, and fixing those is most of the work; wholesale rewriting is rare. The example logs each edit in its consistency memo. If feedback on an earlier week has not yet been applied, applying it before you assemble usually saves a second full pass through the document.