If you’re staring at the clock at 2:00 AM, feeling the weight of a rejected chapter and wondering why your advisor balked, you’re not alone. A quick Google search for “King's College London doctoral prospectus rubric breakdown for” often yields the missing piece of the puzzle that keeps many dissertations stuck. Below is a step‑by‑step, rubric‑oriented playbook that will turn that late‑night panic into a clear, actionable path toward a 100 % pass. Follow the roadmap exactly: 1) Clarify the rubric, 2) Align your prospectus components, 3) Verify statistical and qualitative rigor, 4) Polish the APA 7 presentation, and 5) Run a final rubric‑check before submission.
Theoretical Foundation & Academic Criteria
Doctoral prospectuses at King’s College London and comparable institutions such as Walden, GCU, Capella, and WGU are anchored in three pillars: conceptual clarity, methodological soundness, and scholarly contribution. The rubric typically follows the UK “prospectus approval” checklist, demanding a detailed research problem, a literature review that identifies gaps, a justified methodological design (including Hayes PROCESS macro or SEM for mediation/moderation), and a clear data‑analysis plan that meets SPSS assumptions (normality, multicollinearity, homoscedasticity). NVivo 14 coding must demonstrate a transparent, replicable coding tree, while all writing must adhere to APA 7 style. The rubric’s thresholds are binary: each criterion must be met in full; partial compliance results in a zero for that sub‑section. Thus, the key to a 100 % score is not merely completeness but precision in meeting every listed standard.
Practical Execution Matrix & Comparison Table
| Component / Rubric Criterion | Common Student Error / Pitfall | High‑Scoring Correction / Example |
|---|---|---|
| Research Problem Definition | Vague problem statement with no explicit gap. | State the problem, cite three recent studies, and highlight the specific theoretical or empirical gap your work will fill. |
| Statistical Assumption Checks | Assumptions left unchecked; SPSS output misinterpreted. | Report Shapiro–Wilk for normality (p > .05), tolerance values for multicollinearity (≤ 0.10), and Breusch–Pagan for homoscedasticity (p > .05). Include the relevant SPSS tables in the appendix. |
| NVivo Coding Transparency | Unstructured coding tree, no memo or audit trail. | Provide a screenshot of the final coding tree, link to a written memo explaining code derivation, and include an audit trail table showing code revisions. |
Step‑by‑Step Implementation Protocol
- Draft the Problem Statement. Begin with a one‑sentence statement, then expand into a paragraph that situates your research within the current literature, explicitly stating the gap.
- Construct the Literature Review. Use a synthesis matrix (see table above) to map key authors, theories, methods, and findings. Highlight contradictions or omissions that justify your study.
- Design the Methodology. Choose Hayes PROCESS macro for mediation/moderation. Specify model number, variables, and hypotheses. Justify sample size with a power analysis (e.g., G*Power, α = 0.05, 1‑β = 0.80).
- Collect & Clean Data. Run descriptive statistics. Check normality (Shapiro–Wilk), linearity, homoscedasticity (Breusch–Pagan), and multicollinearity (Variance Inflation Factor). Document any data transformations.
- Execute the PROCESS Analysis. Run the macro in SPSS, record the output, and translate the key statistics (β, t, p, confidence intervals) into APA 7 tables and narrative.
- Qualitative Coding with NVivo 14. Import transcripts, create a codebook, code iteratively, and generate word frequency charts. Export the coding tree and audit trail.
- Write the Prospectus. Follow APA 7 formatting: title page, abstract, headings (H1–H3), in‑text citations, reference list, tables, figures, appendices. Use consistent heading levels and pagination.
- Run the Rubric Self‑Check. Create a checklist mirroring the rubric. For each criterion, tick “Yes” only if you can provide the required evidence (e.g., a screenshot of the coding tree or a SPSS output table).
- Peer Review. Have a colleague or mentor review the prospectus against the rubric; note any missing items.
- Final Proofread & Submission. Check for AI‑detector flags by running the document through Turnitin and a separate AI‑detection tool. Revise any flagged passages, ensuring they reflect original scholarship.
What Faculty Committees & Rubrics Look For
Committees scrutinize the prospectus against a fixed rubric that assigns 100 % when every criterion is fulfilled in full. Key thresholds include:
- Synthesis Matrix Completeness. Every cited study must appear in the matrix with at least one identified gap.
- Methodological Rigor. The chosen PROCESS model must be justified, the sample size must meet power requirements, and all SPSS assumption checks must be reported.
- Qualitative Transparency. NVivo coding must be reproducible; the audit trail must show code evolution.
- Plagiarism & AI Detection. The document must score below 10 % similarity on Turnitin and must not flag AI‑generated content. Rephrase any high‑similarity passages and cite all sources.
- APA 7 Compliance. Title page, abstract, headings, reference list, and in‑text citations must match the 7th edition guidelines.
Missing any of these elements triggers a zero for that subsection, which can bring the overall score below the passing threshold. Therefore, treat the rubric as a checklist that must be ticked in full before you click “Submit.”
Frequently Asked Questions
My SPSS output shows a violation of normality—can I still use PROCESS?
PROCESS assumes normality for the error terms. If Shapiro–Wilk indicates non‑normality (p < .05), apply a transformation (log, square‑root) or use bootstrapping (5,000 resamples) to mitigate the violation. Report the transformation and the bootstrapped confidence intervals in the results section.
How do I prove that my NVivo coding is rigorous enough for the rubric?
Provide a screenshot of the final