Public Health Grant Writing is PUBH 6213, worth 3 credits in Walden's Master of Public Health. It teaches a document with an unusual reader: someone scoring your proposal against published criteria, at speed, alongside many others. Most of what the course grades is whether you wrote for that reader rather than for yourself.
What PUBH 6213 actually grades
Walden's description of the course sets out the ground it covers: the grant writing process and the funding sources behind research, practice and administrative or planning grants, finding those sources, and the techniques the writing itself requires. It names budgets, sustainability once the money ends, and the role of collaboration in bringing organizations and stakeholders together around shared ideas and resources. It also states that students are taken through the whole submission process, proposal development and reviewer evaluation included.
In practice the graded work builds a proposal in pieces across the term, then usually asks you to turn around and assess one. That reviewer exercise is worth more attention than students give it, because it is the course explaining its own grading logic out loud. Once you have scored somebody else's needs statement against criteria, the reason your own needs statement was marked down becomes obvious.
How we help in this course
Send the funding announcement or the scenario you were given along with the assignment prompt, and the section comes back written to those criteria rather than to a generic template. Because the deliverables in this course accumulate into one document, tell us what you have already submitted and the new section will match its scenario, its numbers and its organization details instead of contradicting them.
Every draft clears two reviews before it reaches you, one against the funder criteria and the rubric rows, one on citation accuracy and originality. The window is 24 to 48 hours, and free revisions run until the grade target is hit.
Weekly manuals for this course
Week by week manuals for PUBH 6213 publish separately, each one after its deliverable has been verified against a running section. Walden does not release syllabi publicly, so printing a fixed schedule of weekly tasks here would amount to making one up. Send whatever section is due through chat and it gets drafted regardless of whether its manual has appeared.
Proposal section due this week?
Send the prompt, the criteria and anything you have already submitted. First sample is on the house and comes back in the usual window.
Write for the reviewer, not the reader
Almost everything that separates a strong proposal from a competent one follows from a single fact: the person deciding is working through a scoring sheet, not reading for pleasure. They have a fixed set of criteria, a limited amount of time per application, and a need to locate each answer quickly. A proposal that makes them hunt for the answer loses points that a proposal saying the same thing in the expected place keeps.
The practical consequence is that structure is content here. Use the headings the announcement uses, in the order it uses them. If the criteria ask about significance, put a heading called significance rather than burying the argument inside your background section. Answer the question in the first sentence under each heading and elaborate afterwards, because a reviewer skimming for a judgment will find it and a reviewer reading a slow build might not.
The same logic explains why the reviewer exercise in this course is so useful. Score one proposal against criteria and you will feel how quickly generosity runs out when an answer is not where it should be. That experience changes your own drafting more than any amount of advice.
Where PUBH 6213 sits in the plan
Walden's requirements page puts this degree at 64 total quarter credits, and the curriculum runs across eight numbered quarter blocks with no semester edition beside it. This course sits at the end of that sequence, in the eighth block, taken in the same quarter as the field experience practicum. That timing is the single most important pacing fact on this page: you will be writing proposal sections in the same weeks that a practicum is making demands on your time, and this is a 3 credit course sharing a term with a 5 credit one.
The pairing is also an opportunity. A proposal needs a setting, a population and a plausible organization, and your practicum site hands you all three along with a real sense of what such a place can actually staff and afford. Where your prompt allows it, building the proposal around the setting you are already standing in produces stronger detail than an invented scenario ever will.
On dates, the university calendar lists the Summer 2027 quarter as running from May 31 to August 15. Walden does not publish a week count beside those spans, so the familiar figure is arithmetic rather than the university's own wording: 76 days works out to slightly less than eleven weeks. Weekly deadlines close at 10:59 p.m. Central, which is 11:59 p.m. Eastern, and Walden expects a post or a submission during the first week of the term.
How to actually write PUBH 6213: where to begin
Begin with the funding announcement rather than with your idea. Read the eligibility rules first and confirm your organization qualifies, because a strong proposal from an ineligible applicant scores nothing at all. Then find the review criteria, which are usually printed with their weights, and treat that list as the outline of the document. Anything the criteria do not ask about is a candidate for deletion no matter how interested you are in it.
Write the needs statement about the community, never about the organization. This is the most common reversal in the course and the easiest to fix once seen. Nobody funds an organization because it lacks money; they fund it because a population has a problem the applicant is positioned to address. Establish that problem with data specific to your service area, drawn from public sources such as census figures, state and county health reporting, or surveillance summaries. Then narrow: national statistics establish that a problem exists somewhere, while local figures establish that it exists where you are asking to work, and only the second kind earns the row.
Turn goals into objectives that could be checked by somebody who dislikes you. A goal can be broad, but an objective needs a number, a population, a direction and a deadline: raising second dose completion among enrolled children from a stated baseline to a stated target within eighteen months. The frequent error is writing activities where objectives belong. Holding six workshops is something you will do; a change in a measured outcome is something you promise. Reviewers score the promise.
Methods then explain how the objectives will be achieved, in enough operational detail that a reader can picture the work. Who does what, to whom, how often, starting when, with what evidence that this approach has worked before. A work plan or timeline table earns its space here. Evaluation follows directly and must connect back: for each objective, the indicator, the data source, who collects it and when, and how you would know the program failed. Proposals that describe evaluation only as measuring success are describing a plan that cannot report bad news.
The budget and its narrative come last and have to reconcile with everything above. Every line item should trace to an activity in the methods, and every activity of any size should appear somewhere in the budget. Read the two documents against each other before submitting, because a coordinator named in the methods but absent from the personnel lines is the kind of discrepancy reviewers catch immediately. Finish with sustainability, which is not a promise to look for more grants. It is a plan: which costs disappear when the project ends, which are absorbed into an existing budget, what partner has agreed to carry a function, and what the program will look like in year four at a smaller scale.
| Section | What goes in it | Common failure |
|---|---|---|
| Needs statement | Local data establishing the problem, who it affects, and why this applicant is placed to address it. | Framing the need as the organization's shortage of funding rather than the community's health problem. |
| Goals and objectives | Broad aims, then objectives carrying a baseline, a target, a population and a date. | Activities written in the objective slot, which leaves nothing measurable for evaluation to track. |
| Methods and work plan | Activities, staffing, sequence and timeline, with evidence supporting the approach chosen. | A description of intent rather than of operations, so no reader can tell what happens in month one. |
| Evaluation | An indicator per objective, the data source, collection timing, and who is responsible. | Only success measured, with no design capable of detecting that the program did not work. |
| Budget and narrative | Itemized costs with a justification tying each line to a specific activity in the methods. | Lump sums with no basis shown, or personnel appearing in one document and not the other. |
| Sustainability and partners | What continues after the award, who absorbs which cost, and the commitments already secured. | A promise to pursue future funding, which restates the problem rather than solving it. |
Discussion posts that earn the row
Discussion prompts in this course tend to hand you a funding scenario, a proposal excerpt, or a question about collaboration and ask for a judgment. Write the first post the way you would write a short section of the proposal: a clear position in the opening line, one piece of evidence or one criterion supporting it, and a concrete consequence for the applicant. Reviewer habits transfer well to this format, because both reward getting to the point.
Replies carry their own scoring row, and agreement adds nothing. Do something to the argument in front of you: name the criterion a classmate's approach would fail and say why, question whether their objective is measurable as written, or point out a cost their methods imply that their budget never mentions. Walden's policy on grading expects contributions that are substantive and on time, recommending you spread them across two to four days at minimum instead of posting everything at once. The university is explicit that posting expectations are not uniform, differing between courses and between weeks of the same course, so let the classroom instructions decide.
Sources, data and APA 7 in a proposal course
This course asks for two source types that behave differently, and treating them alike is a quiet way to lose credit. Data sources establish the need and belong to the place you are writing about, which is why census tables, state and county health reports and surveillance summaries do work that a journal article cannot. Evidence sources establish that your intervention has a reasonable chance of working, and those should be peer reviewed and recent, retrieved through the Walden Library rather than a general search.
Cite the funding announcement itself when you explain a decision, since showing the reader that a choice came from the criteria is exactly the discipline the course teaches. Give every statistic a year and a geography in the sentence that uses it. Reference formatting follows APA 7 unless the prompt directs otherwise, and where an assignment asks you to mirror a funder's format instead, the funder's instructions govern the document while APA still governs your citations. The Walden Writing Center templates settle the mechanics faster than guesswork.
The mistakes that cost points in PUBH 6213
- Building the needs statement around the applicant's finances instead of a documented community health problem.
- Objectives with no baseline, no target figure or no deadline, which makes the evaluation section impossible to write honestly.
- A budget that names staff or supplies the methods never mentioned, or methods requiring resources the budget never funded.
- Ignoring the announcement's own structure and headings, forcing a reviewer to search for answers the criteria asked for.
- National statistics used where local figures were needed, leaving the service area itself undocumented.
- Sustainability handled as an intention to seek further grants rather than a plan for specific costs and partners.
- Letters of support described in the text but never obtained or specified, so collaboration remains an assertion.
PUBH 6213 questions students actually ask
Does the funding opportunity have to be a real one?
Follow whatever your prompt says, but where the choice is yours a real announcement is almost always the better one. A genuine opportunity hands you eligibility rules, review criteria, a ceiling on the award and a page limit, and every one of those constraints gives your draft something to be shaped by. Invented funders tend to want exactly what the student already planned to write, which produces a proposal that never had to survive a real constraint. Print the announcement, keep it beside the draft, and cite it when you explain a decision.
How specific does the budget need to be?
Specific enough that a reviewer could reconstruct every number without needing to ask you about it. A personnel line should show a role, the fraction of time it is funded for, and the basis of the rate. Supplies should show unit cost and quantity rather than a single lump. The narrative beside the budget is where you justify each item by tying it to an activity in the methods, and that link is what the scoring row is really testing. Where an assignment gives a ceiling, come in under it and explain any figure that looks unusual rather than hoping it passes unnoticed.
What if I have never worked at a nonprofit?
It is not a disadvantage the rubric can see. Everything the proposal needs is either published or reasonable to specify: the community data comes from public sources, the intervention comes from the literature, and the organizational details are things you state as premises of your scenario. Choose a setting you can describe consistently, such as a county health department or a community clinic, and hold its size and staffing steady across every section. Coherence across the document is what reads as competence here, far more than any particular employment history.