C227 Research Proposals, catalog number EDUC 5114, is the two-CU closing course of the School of Education research sequence. It asks for one thing and asks for it carefully: a well organised research proposal, written so that its sections correspond to the sections of the research report the study would eventually produce. That correspondence is the point. A proposal is a report written in advance, with results left blank, and the whole document is judged on whether it would survive being turned into that report without rewriting.
What a proposal is for, and why organisation is the skill
By the time you reach EDUC 5114 you have the material. C224 gave you the tradition and the measurement vocabulary. C225 produced the problem, the reviewed literature and the question. C226 produced the design, the instruments, the analysis plan and the validity work. C227 does not ask for new content. It asks whether you can assemble what you have into a document that a reader who was not present for any of it would find complete, internally consistent and worth approving.
That reframing matters because it changes what counts as an error. In a proposal, an unsupported claim is not merely weak; it is a hole in a plan someone is being asked to authorise. A vague timeline is not sloppy writing; it is a reason to withhold approval. Proposals are read by people deciding whether to let something happen, and the assessed version behaves the same way.
Alignment is the specific quality being scored, and it runs in a chain: problem to question, question to design, design to instruments, instruments to analysis, analysis back to question. Break any link and the whole document loses credibility even when each section is individually competent. The commonest break is between question and analysis, because those two sections are written furthest apart in time and nobody rereads them side by side. Read them side by side.
The second scored quality is the mapping to a report. A proposal describes what will be done; a report describes what was done and what was found. Sections correspond one to one apart from the results, which is why a well built proposal converts with a change of tense and the addition of findings. Writing your proposal as an essay about your intentions produces something no report will ever come out of.
Turning scored aspects into a section plan
Scored detail for any WGU course lives in your Course of Study rather than the public catalog, so open the rubric and count aspects before drafting. Each aspect is scored on its own against a three-point scale, and a score of 2 in every aspect is what passes a task. Nothing averages, and in a document assembled from four courses of prior work that is a mercy and a trap at once: strong inherited sections do not carry a section you assembled carelessly.
Where your version is assessed by submitted work, take the aspect list as the table of contents, using the rubric's own nouns. In a proposal this is easier than in most courses, because proposals are supposed to have visible section headings. Use that convention rather than fighting it.
The word budget, worked. Suppose your rubric shows seven scored aspects and the directions ask for roughly 2,100 words. Reserve 150 words for a purpose statement and 120 for a closing significance section, leaving about 1,830 for the scored body. Seven into 1,830 is 261 words per aspect. Then reallocate on purpose. The literature section usually needs about 450 because it is carrying a synthesis you already wrote, and the participants section is complete at roughly 130. The analysis plan wants around 320 because it has to name the procedure and connect it back to the question. Take the surplus from wherever the rubric only asks you to state rather than to justify.
One structural rule for proposals specifically. Every section should be written so that it could be lifted out and read alone by someone who knows the field but not your project. A section that only makes sense because of the paragraph above it will not survive the conversion into a report, and evaluators reading aspect by aspect are effectively reading each section alone.
A proposal structure that maps onto a report
Where the task directions supply their own arrangement, that arrangement governs. Where they do not, this order is the standard correspondence, with the right-hand column showing what each section becomes in the eventual report.
| Proposal section | What belongs in it | What it becomes in the report |
|---|---|---|
| Title and purpose | What is being studied, with whom, and to what end, in a few precise sentences | The same, with tense changed |
| Problem statement | The educational problem, its setting, and the evidence that it exists | Unchanged; the reason the study happened |
| Literature review | Synthesised findings, agreements, conflicts and the gap the study addresses | Unchanged, sometimes with sources added |
| Research question | The question verbatim, plus any hypotheses or sub-questions | Unchanged; results are reported against it |
| Method | Design, participants, sampling, instruments, procedure and timeline | Rewritten in past tense with what actually happened |
| Analysis plan | What will be done with the data, matched to data type and to the question | Becomes the analysis section, with output added |
| Validity and ethics | Named threats with answers, consent, anonymity and researcher role | Becomes limitations, with anything unexpected added |
| Significance | Who benefits from the answer, and what changes if the result goes either way | Becomes discussion and implications |
| References | Every source cited, in the required style | Unchanged apart from additions |
| Results | Absent by definition; the analysis plan stands in its place | The one genuinely new section in the report |
Write the significance section as if the result could go either way. Proposals that argue their intervention will work read as advocacy, and a reader whose job is to approve research is trained to be wary of it. A study worth running is worth running because both answers are informative.
Evidence craft in a document about the future
Proposals are written in a tense that makes sloppiness invisible to the writer. Nothing has happened yet, so nothing can be checked, and unsupported statements slip through easily.
- Support every claim about the problem with evidence, whether that is school data you can describe without identifying anyone, or published research.
- Support every methodological choice with a methods source, so that design decisions read as informed rather than as preferences.
- Keep tense consistent. Method and analysis are what will be done. Literature is what has been found. Mixed tense inside one section is the fastest signal of a document assembled from pieces.
- State the timeline in weeks with what happens in each, because a timeline that cannot be scheduled cannot be approved.
- De-identify pupils, colleagues and the school throughout, and say that you have done so where ethics is discussed.
- Match citations to your required style and reconcile the reference list against the text, which matters more here because the list is assembled from three earlier courses.
One test finds most of the remaining problems. Read only your question and only your analysis plan, in that order, with nothing else visible. If the analysis would not produce an answer to that question, something upstream needs fixing, and finding it now is far cheaper than finding it in a capstone.
What separates Competent from a submission sent back
Because aspects are scored independently, a returned proposal is usually one inconsistency rather than a weak plan.
- Every scored aspect has its own labelled section in the rubric's own wording.
- The research question appears in identical wording everywhere it is used.
- Every element the analysis needs is collected somewhere in the method, and nothing is collected that the analysis never touches.
- Threats to validity are named individually with answers attached, and the researcher's dual role is addressed.
- Each section could be read alone and still make sense.
- The reference list and the in-text citations reconcile exactly, with no orphans in either direction.
Performance assessment work at WGU can be revised and resubmitted with no grade penalty, so a return costs time rather than standing. In a six-month flat-rate term that time is the whole budget, and C227 usually sits at the end of a sequence students are trying to close before the term does. A proposal returned twice for internal inconsistency is the difference between finishing the sequence and carrying it forward.
Where a proctored objective assessment accompanies this course in your plan, the boundary is absolute. Proctored exams are yours to sit. We prepare only: alignment audits, section-mapping practice, and an honest readiness call. We do not sit assessments, we are never present during one, and we never ask for portal credentials.
Five mistakes that cost time in C227
- Pasting earlier coursework in without reconciling it. The literature from C225 and the design from C226 were written weeks apart. Left unreconciled, they contradict each other in small, visible ways.
- Writing the proposal as an essay. Continuous prose with no labelled sections cannot map onto a report and forces the evaluator to hunt for every aspect.
- Arguing that the intervention will work. A proposal justifies asking the question, not the answer. Advocacy reads as bias to the reader deciding whether to approve it.
- Leaving the timeline vague. Over the term is not a schedule. Weeks, with what happens in each, is what makes a plan reviewable.
- Skipping the final alignment read. Question against analysis, side by side, catches more returns than any other single check in this course.
How support works on this course
Send the rubric from your Course of Study, the task directions and whatever you produced in C225 and C226. Work comes back as an assembled proposal with the alignment chain audited end to end, sections labelled to match the rubric and mapped to their report counterparts, tense made consistent, the reference list reconciled, and every claim about the problem supported. The walkthrough points out where the earlier courses disagreed with each other, because that is almost always where the returns would have come from.
If the whole sequence is being run inside one term, this is the course where that decision pays off or costs you. A proposal built from material that was written with this document in view assembles in days. One built from four unrelated submissions takes a rewrite.
Questions students ask about C227
Is C227 the same course as EDUC 5114?
Can I reuse my work from C225 and C226 in the proposal?
Will you sit a proctored assessment for me?
Assembling the proposal that closes the sequence?
Send your Course of Study rubric, the task directions and your earlier coursework. You get an assembled proposal with the alignment chain audited from problem to analysis.
Where C227 sits in WGU's programs
The July 2026 catalog places this code in 1 current WGU program. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.