| Course | DBAX 8101 Business Research Project Mentoring |
|---|---|
| Week | Week 10 |
| Paper type | Revision log |
| Length | About 810 words, 5 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Doctor of Business Administration (DBA) |
| Updated | October 2026 |
Free sample paper for DBAX 8101 Week 10
Every Change, Its Date and the Objection Behind It: A Term's Revision Log for an Interview Study of How Rural Electric Cooperatives Explain Rate Increases to Their Members, Grouped Into Objection Threads
Student Name
Walden University
DBAX 8101: Business Research Project Mentoring
Instructor Name
Month Day, Year
Every Change, Its Date and the Objection Behind It: A Term's Revision Log for an Interview Study of How Rural Electric Cooperatives Explain Rate Increases to Their Members, Grouped Into Objection Threads
Why a Revision Log
By the tenth week, my draft has changed in dozens of places, and the reasons for most changes exist only in returned drafts and email threads. If a committee member later asks why the sample was narrowed or why a research question was reworded, I need to be able to answer. This log records every substantive change since the first draft, with its date and the objection that caused it, grouped into threads by objection. The study examines how rural electric cooperatives explain rate increases to their member-owners, through interviews with general managers and board members at nine cooperatives.
Summary of Objection Threads
Table 1
Objection Threads and How Many Rounds Each Took to Close
| Thread | Objection in one line | First raised | Rounds returned | Status | |
|---|---|---|---|---|
| 1 | The problem is about utilities generally, not cooperatives | Round 1 | 2 | Closed in round 3 | |
| 2 | Member ownership is mentioned but never used in the analysis | Round 1 | 3 | Closed in round 4 | |
| 3 | The sample mixes distribution and generation cooperatives | Round 2 | 1 | Closed in round 3 | |
| 4 | Interview questions lead participants toward expected answers | Round 2 | 0 | Closed in round 2 | |
| 5 | Literature on rate communication is mostly about investor-owned utilities | Round 2 | 2 | Open | |
| 6 | Research question 2 overlaps with research question 1 | Round 3 | 1 | Closed in round 4 | |
| 7 | Ethics: board members may be identifiable | Round 3 | 0 | Closed in round 3 | |
| 8 | Analysis plan does not say how documents will be used | Round 4 | 0 | Open | |
Composite study. Rounds returned counts the times an objection came back after a revision.
Selected Thread Detail
Thread 2 took the most rounds. In round one, my mentor noted that the draft mentioned member ownership in the introduction but never returned to it. I added a paragraph on cooperative governance to chapter two. In round two, the note returned: "Still not used." I added a sentence to the purpose. In round three: "Where does member ownership appear in your questions?" Only then did I add interview questions about how managers think about members as owners rather than customers, and a coding category for ownership language. The thread closed in round four. Looking back, each early revision added description of member ownership without making it part of the study's design. The pattern resembles what Kumar and Stracke (2007) describe: feedback that asks for a conceptual change can be answered with additions that leave the concept unused.
Thread 5 remains open. Most research on how utilities communicate rate increases concerns investor-owned utilities, whose customers do not own them. My mentor has asked twice whether the literature can support claims about cooperatives. My current position is that it cannot fully, and that the study's contribution is partly to fill that gap. I have added the few studies of cooperative governance I could find, including work on member participation in agricultural and electric cooperatives, but the thread will stay open until the mentor agrees the gap is stated honestly.
Changes Not Tied to Objections
Some changes were not prompted by mentor notes: a corrected statistic, two new sources found during the term and the removal of a section on rate design that I decided was outside the study's scope. These are listed separately so they are not mistaken for responses to objections.
What the Log Shows
The log shows that objections closed fastest when I changed the study's design rather than its description. Threads 3, 4 and 7 closed in one round because each required a concrete change, narrowing the sample, rewording questions or changing participant codes. Threads 1 and 2 took several rounds because I answered them with added text before making the design change they called for. Engaging with what a critique means, and not only with its surface, is what made students better scholarly writers in the study by Caffarella and Barnett (2000); the log is a record of when I did each.
Next Time
Starting over, I would start the log in the first week rather than reconstructing it in the tenth. Reconstruction took most of a weekend and depended on email searches that may have missed changes made during calls with my mentor. I would also note, for each response, whether it changed the design or only the text, since that distinction turned out to predict how quickly each objection closed.
The Log's Next Readers
The log will accompany the draft to the committee, letting members trace how earlier objections were resolved and which remain open. Kamler and Thomson (2014) treat the thesis as built through successive conversations around text; the log keeps a record of those conversations in one place.
References
Caffarella, R. S., & Barnett, B. G. (2000). Teaching doctoral students to become scholarly writers: The importance of giving and receiving critiques. Studies in Higher Education, 25(1), 39-52. https://doi.org/10.1080/030750700116000
Kamler, B., & Thomson, P. (2014). Helping doctoral students write: Pedagogies for supervision (2nd ed.). Routledge.
Kumar, V., & Stracke, E. (2007). An analysis of written feedback on a PhD thesis. Teaching in Higher Education, 12(4), 461-470. https://doi.org/10.1080/13562510701415433
Reading the DBAX 8101 Week 10 instructions
Week 10 asks you to log the substantive changes made to your draft over the term. Record each change with its date and the objection that caused it, and group changes into threads by objection. Summarize each thread: when it was first raised, how many times it returned and whether it is closed. Trace one long thread and one open thread in detail. List changes not tied to objections separately. Explain what the log shows about how objections close. Describe what you would do differently if you began again, and say how the log will be used with your committee so members can see which objections were resolved and which remain open.
How this DBAX 8101 Week 10 example is built
The log opens by explaining why reasons for changes need recording. A table summarizes eight objection threads with first round, rounds returned and status. A section traces the member-ownership thread through four rounds, citing Kumar and Stracke, and the open thread on literature about investor-owned utilities. A section lists changes not tied to objections. A section finds that design changes closed objections faster than added text, citing Caffarella and Barnett. A section describes starting the log earlier and noting design versus text changes. A closing section explains its use with the committee, citing Kamler and Thomson. Changes not prompted by notes are kept in their own short list, so the threads stay clean.
Reading the DBAX 8101 Week 10 rubric
Revision logs earn credit for completeness and for what they reveal. Recording each change with its date and objection is weighted heavily. Grouping into threads with counts of rounds shows patterns. Tracing a long thread and an open thread in detail demonstrates reflection. Separating unprompted changes keeps the record honest. Drawing a general lesson about how objections close shows learning. Planning to share the log with the committee shows professionalism. Logs that list changes without reasons, omit open threads or offer no reflection tend to receive lower marks. A summary table with short thread narratives is the expected format for this mentoring course. Closing with what the author would change next time, such as starting the log sooner, rounds out the document.
Common DBAX 8101 Week 10 mistakes, and how to avoid them
Gather every returned draft and email from your mentor this term. For each substantive change you made, write the date, what changed and which note caused it. Group the changes by the objection behind them. Count how many times each objection came back. Then look for a pattern: which objections closed quickly and which took several rounds, and why? Students often reconstruct the log from memory and miss changes. Others list changes without linking them to objections, which loses the point. Start your log now and keep it going. Sorting a term of emails into threads goes faster with help, and our writers can do the first sort.
Get a DBAX 8101 Week 10 example written to your instructions
Attach the Week 10 prompt and rubric, the notes you received this term, and a list of the larger changes you remember making. A threaded revision log with a summary table and a closing lesson comes back within 24-48h, and a first request is free. The cooperative study behind it is fictional; rebuilding your own record belongs to you.
More DBAX 8101 papers and DBA samples
- DBAX 8101 Week 1: Project Status Discussion Post
- DBAX 8101 Week 2: Doctoral Draft Map
- DBAX 8101 Week 3: Standing Objection Analysis
- DBAX 8101 Week 4: Targeted Framework Revision
- DBAX 8101 Week 5: Literature Source Check
- DBAX 8101 Week 6: Second Pass Revision
- DBAX 8101 Week 7: Study Alignment Check
- DBAX 8101 Week 8: Whole-Document Citation Pass
- DBAX 8101 Week 9: Plain-Language Study Summary
- DBAX 8101 Week 11: Project Handoff Note
- DBAX 8006 Week 10: Claim Audit Revision Pass
DBAX 8101 Week 10 questions, answered
Where can I find a free DBAX 8101 Week 10 sample paper?
The revision log is reproduced below and free to read.
How many objection threads does the DBAX 8101 Week 10 log track?
Eight, from the problem's focus to the analysis plan's use of documents.
Which thread took longest?
Member ownership, which closed after four rounds.
Why did it take so long?
Early responses described member ownership without building it into questions and coding.
What does the log show?
Objections closed fastest when the study's design changed rather than its text.