| Course | DBAX 9104 Business Research Project Stage 4 |
|---|---|
| Week | Week 2 |
| Paper type | Whole-document read |
| Length | About 900 words, 6 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Doctor of Business Administration (DBA) |
| Updated | October 2026 |
Free sample paper for DBAX 9104 Week 2
Twelve Places Where My Chapters Disagree: A Whole-Document Read of a Survey Study on Supplier-Relationship Practices and On-Time Delivery Among Small Food Manufacturers, Drafted Over Four Terms
Student Name
Walden University
DBAX 9104: Business Research Project Stage 4
Instructor Name
Month Day, Year
Twelve Places Where My Chapters Disagree: A Whole-Document Read of a Survey Study on Supplier-Relationship Practices and On-Time Delivery Among Small Food Manufacturers, Drafted Over Four Terms
Why a Whole-Document Read
My study surveyed owners and operations managers at small food manufacturers about three supplier-relationship practices, regular performance feedback, joint planning and information sharing, and related them to the share of customer orders shipped on time. I drafted it over four terms. Each chapter was revised when it was written and read closely by my chair at the time, but the chapters were never read together until this week. Contradictions in a long study rarely sit within one chapter. They sit between a sentence written in the first term and one written in the fourth, after the study had changed in ways the earlier sentence never caught up with.
How the Read Was Done
I read the full document in one sitting, chapters in order, with three running lists beside the text: every claim verb used about the relationship between practices and delivery, every count of firms or responses, and every definition of the three practices. Whenever an entry on a list disagreed with an earlier one, I logged it with both locations. Booth et al. (2016) recommend reading a research report as a single argument whose claims must stay stable from start to finish, and the lists turned that advice into something I could check.
The Log
Table 1
Contradictions Found in the Whole-Document Read
| No. | Locations | Wording at each | Kind | Version that stands | Repair | |
|---|---|---|---|---|---|
| 1 | Ch. 1 purpose; Ch. 4 results | "determine whether practices predict on-time delivery"; "practices were associated with on-time delivery" | Claim verb | Association | Purpose reworded to "examine the relationship" | |
| 2 | Ch. 1 significance; Ch. 5 conclusion | "improve delivery performance"; "relate to delivery performance" | Claim verb | Ch. 5 | Significance reworded | |
| 3 | Ch. 3 sample; Ch. 4 results | 164 responses; 141 analyzed | Count | 141, with exclusions stated | Ch. 3 adds the 23 incomplete surveys removed | |
| 4 | Abstract; Ch. 4 | 152 firms; 141 firms | Count | 141 | Abstract corrected | |
| 5 | Ch. 2 review; Ch. 3 measures | Collaboration as joint decision making; scale items on information sharing | Definition | Ch. 3 measure | Ch. 2 adds that the study measured one part of collaboration | |
| 6 | Ch. 1 definitions; Ch. 3 | On-time as shipped by promised date; on-time as delivered by requested date | Definition | Ch. 3, as surveyed | Ch. 1 definition replaced | |
| 7 | Ch. 3 procedure | "will be distributed"; "will be analyzed" | Tense | Past | Procedure rewritten in past tense | |
| 8 | Ch. 1 scope; Ch. 4 | Manufacturers with 20 to 250 employees; included firms with 12 to 300 | Scope | Ch. 1 scope binding | Eight firms outside range excluded and results rerun | |
| 9 | Ch. 2; Ch. 5 | Prahinski and Benton (2004) cited for feedback raising performance; cited for communication strategy | Source use | Ch. 2 accurate | Ch. 5 sentence narrowed | |
| 10 | Ch. 3 alpha; Ch. 4 table | .81; .78 | Count | .78, final data | Ch. 3 updated | |
| 11 | Ch. 1 question; Ch. 5 | Three practices; four practices discussed | Scope | Three | Fourth practice moved to future research | |
| 12 | Ch. 4 text; Ch. 4 table | "strongest predictor"; second largest coefficient | Count | Table | Text corrected | |
Locations refer to the chapter and section of the draft read on the date of this log.
Four Kinds of Contradiction
The twelve entries fall into four kinds. Claim verbs drifted because chapter one was written when I still imagined a predictive design; by the analysis chapter I was reporting associations from a cross-sectional survey, which is all the data allow. Counts drifted because exclusions were made after chapter three was approved and the method text was never updated. Definitions drifted because chapter two described supplier collaboration broadly, drawing on work where it includes joint decision making and shared goals (Simatupang & Sridharan, 2005), while my survey measured information sharing alone. Scope drifted in two directions: some firms outside the size range slipped into the analysis, and a fourth practice appeared in the conclusion though the question named three.
Which Version Stands
I did not assume the newest chapter wins. For most claim verbs and counts the later version is correct, because it reflects what was actually done. But the scope statement in chapter one is binding, since it is what my committee approved. Where the analysis included firms outside the stated size range, the repair was to exclude them and rerun the results, not to widen the scope after the fact. The Publication Manual asks authors to report methods as conducted and to keep terms consistent across a manuscript (American Psychological Association, 2020), and both principles point to the same repairs here.
What the Rerun Changed
Excluding eight firms outside the size range left 133 cases. The associations kept their direction and remained distinguishable from zero, and the ranking of the three practices did not change. The coefficient for joint planning fell slightly. That result is now reported, with a sentence explaining why the sample shrank.
What the Read Did Not Find
The read found no contradiction in the research question itself, which appears in the same words in every chapter. It also found no cited source missing from the reference list. Those checks matter less than the twelve entries, but recording them tells my chair what was checked and came out clean, so the next reader does not have to check it again.
References
American Psychological Association. (2020). Publication manual of the American Psychological Association (7th ed.). https://doi.org/10.1037/0000165-000
Booth, W. C., Colomb, G. G., Williams, J. M., Bizup, J., & FitzGerald, W. T. (2016). The craft of research (4th ed.). University of Chicago Press.
Prahinski, C., & Benton, W. C. (2004). Supplier evaluations: Communication strategies to improve supplier performance. Journal of Operations Management, 22(1), 39-62. https://doi.org/10.1016/j.jom.2003.12.005
Simatupang, T. M., & Sridharan, R. (2005). An integrative framework for supply chain collaboration. International Journal of Logistics Management, 16(2), 257-274. https://doi.org/10.1108/09574090510634548
Reading the DBAX 9104 Week 2 instructions
Week 2 asks you to read your full draft in one sitting, in chapter order, as one continuous argument, not a stack of separate sections. Keep running lists of the things most likely to drift between chapters: the verbs you use about your main relationship or finding, every count of participants or cases, and the definitions of key constructs. Log each place where two parts disagree, giving both locations, the wording at each, the kind of contradiction, which version stands and how you repaired it. Explain your rule for deciding which version stands, noting that the newest chapter is not always correct. Report any reanalysis a repair required. A table carrying the log is expected, with prose that groups the entries and explains their causes.
Inside the DBAX 9104 Week 2 example
A short opening explains why contradictions sit between chapters, followed by a description of how the read was done with three running lists. The log table holds twelve rows, from the purpose statement's "determine whether practices predict" to a strongest-predictor claim the coefficient table did not support. Prose then sorts the entries: claim verbs drifted because the first chapter imagined a predictive design, counts drifted because exclusions came after the method chapter was approved, a definition drew on broad collaboration literature while the survey measured information sharing, and scope slipped in both directions. A section explains why the approved scope binds even when the analysis is newer. Dropping eight firms left 133 cases with the same pattern. A last section records what the read checked and found clean.
Reading the DBAX 9104 Week 2 rubric
Credit goes to contradictions found between distant chapters. A log of typing errors and citation formats shows proofreading, and it earns little here; a log that catches a claim verb changing across three terms or a sample count that never matched shows the document was read as one argument. The column stating which version stands carries analytic weight, and a stated rule for choosing earns more than assuming the latest draft wins. Instructors look hard at sample counts, since a mismatch between described and analyzed samples undermines everything downstream. Reanalysis prompted by the read is strong evidence of seriousness. Grouping entries by cause shows the writer understands why drift happens and where else it may hide. Clean checks, reported briefly, round out a convincing log.
Common DBAX 9104 Week 2 mistakes, and how to avoid them
The read only works if you resist fixing things as you go, which breaks your attention to the whole. Keep a notepad or second screen for the lists and record every verb, count and definition you meet, then compare at the end of each chapter. Search your file for words such as predict, effect, impact, cause and influence and check each against your design. Compare the sample size in your abstract, method and results. Read your literature review's definition of each construct next to the items you actually used. When chapters disagree, ask which version your committee approved and which reflects what was done. A tutor can sit through a read of your chapters with you and help keep the log.
Get a DBAX 9104 Week 2 example written to your instructions
Send the Week 2 prompt and rubric, and sketch the study briefly: its design, its chapters and roughly when each was drafted. A contradiction log with its sorted entries returns within 24-48h; the first is free. The log is built on a comparable study, so your own chapters stay with you while its entries model the disagreements a read turns up.
More DBAX 9104 papers and DBA samples
- DBAX 9104 Week 1: Conclusion Match Discussion
- DBAX 9104 Week 3: Opening Chapter Rewrite
- DBAX 9104 Week 4: Findings Restatement
- DBAX 9104 Week 5: Interpretation Draft
- DBAX 9104 Week 6: Limitations Section
- DBAX 9104 Week 7: Conclusion Sizing Paper
- DBAX 9104 Week 8: Contribution Sentence Drafts
- DBAX 9104 Week 9: One-Page Summary
- DBAX 9104 Week 10: Defense Rehearsal
- DBAX 9104 Week 11: Final Assembly Record
- DBAX 9103C Week 2: Work Account
- DBAX 9103 Week 2: Research Procedure Account
- DBAX 9102C Week 2: Neighboring Sector Search
- DBAX 9102 Week 2: Literature Search Protocol
DBAX 9104 Week 2 questions, answered
Where can I find a free DBAX 9104 Week 2 sample paper?
The full Week 2 read, with its twelve-row log and the explanation of each kind of contradiction, appears on this page free of charge.
What kinds of contradictions does the DBAX 9104 Week 2 log find?
Claim verbs, counts, definitions and scope, plus a method chapter still written in future tense.
Which chapter wins when two disagree?
Usually the one describing what was actually done, but the approved scope statement binds even when a later chapter departs from it.
Why was the analysis rerun?
Eight firms outside the approved size range had entered the analysis, so they were excluded and the results recomputed with 133 cases.
Is a whole-document read the same as proofreading?
No. Proofreading finds slips within sentences; this read finds disagreements between chapters written at different times.