DBA 960 Topic 4 fieldwork departure log example

Dissertation II Grand Canyon University Free custom sample in 24 to 48h

This DBA 960 Topic 4 sample paper logs four departures from an approved protocol in the first two months of a composite commercial insurer's study of how underwriters use a new risk-scoring tool. It was prepared for GCU DBA 960, Dissertation II, catalog code DBA-960, a course in the Grand Canyon University DBA. A pilot question heard as an audit is rewritten and approved, as Kallio and colleagues advise piloting. Interviews move to video after a reorganization, four participants decline recording, and the vendor changes how scores display. Lincoln and Guba's audit trail frames the log, and a re-interview the candidate declined is recorded too.

CourseDBA 960 Dissertation II
TopicTopic 4
Paper typeFieldwork departure log
LengthAbout 970 words, 2 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramDBA
UpdatedOctober 2026

Free sample paper for DBA 960 Topic 4

1

Four Departures in Two Months: A Fieldwork Log for a Study of How Underwriters Use a New Risk-Scoring Tool

[Author Name]

College of Doctoral Studies, Grand Canyon University

DBA-960: Dissertation II

Topic 4 Fieldwork Departure Log

[Instructor Name]

[Date]

The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.

What this page is doingThe title states what the log records. The candidate and the insurer are composites; the sources are real. Dates are illustrative.
2

Four Departures in Two Months: A Fieldwork Log for a Study of How Underwriters Use a New Risk-Scoring Tool

Why Keep a Departure Log

A doctoral candidate who manages an underwriting team at a composite commercial insurer is interviewing underwriters about how they use a new risk-scoring tool, a model that rates each submission and suggests a price range. Within two months of starting fieldwork, the study had departed from its approved protocol four times. None of the departures was improper, but each changed the data in some way, and a dissertation that reported the protocol as approved, without the departures, would misdescribe what was actually done. Lincoln and Guba (1985) argued that the dependability of qualitative research rests on an audit trail that lets others follow the decisions made during the study. This log is part of that trail. Each entry is dated, explains the cause and states which data it touches.

The Log

The entries are summarized in the table and explained below.

Table 1

Fieldwork Departure Log, Illustrative

DateDepartureCauseApprovalData affected
Day 5Interview question rewrittenPilot showed question heard as an auditAmendment approved before main interviewsAll main interviews; pilot data excluded
Day 26Interviews moved from meeting rooms to videoOffice reorganization closed meeting spaceMinor change, notified to review boardInterviews 6 onward; nonverbal data reduced
Days 18 to 47Field notes replace recordings for some interviewsFour participants declined recordingAllowed under approved consent optionsFour interviews lack verbatim quotes
Day 40Tool display changed by vendorVendor update altered how scores are shownNot a protocol change; recorded for analysisInterviews 9 onward describe a different version

Entry One: The Pilot

The first entry comes from the pilot. Two underwriters from an office outside the sample tried the interview guide. One question, how often do you override the score, was heard by both as an audit of their judgment; one answered defensively, and the other asked whether the answers would go to management. Kallio et al. (2016) recommended piloting semi-structured interview guides so that misread questions surface before the main fieldwork, and this pilot did its job. The question was rewritten to ask about a recent case, tell me about a submission where you and the score disagreed, which invites a story rather than a self-assessment. Because the change altered an approved instrument, the amendment was submitted to the review board and approved before the main interviews began, as the regulations require for changes to approved research (Protection of human subjects, 2018). Pilot interviews are excluded from the analysis.

Entry Two: Video Interviews

About a month into fieldwork, an office reorganization closed the meeting rooms where interviews had been held. Interviews from the sixth onward moved to video calls, with participants choosing a private location. The review board was notified as a minor change, since the consent form already allowed remote interviews. The effect on the data is modest but real: video reduces what an interviewer notices of hesitation and posture, and some participants joined from shared spaces where they may have spoken more guardedly. The analysis will compare themes from in-person and video interviews and note any differences.

Entry Three: Declined Recording

Four participants declined to be recorded, an option the approved consent form allowed. For those interviews, the candidate took field notes during the conversation and wrote fuller notes within two hours. These interviews lack verbatim quotations, so findings that rest on them will be reported as paraphrase, and the candidate will check whether refusals cluster among particular groups. Three of the four were senior underwriters, which may itself be informative about how the tool is perceived among those with the most discretion to lose.

Entry Four: The Tool Changed

Six weeks into fieldwork, the vendor updated the tool so that scores are shown with a confidence band and the three factors that most influenced each score. This was not a protocol change, but it is the most consequential entry for interpretation. Participants interviewed before the update were describing a tool that gave a single number; those interviewed afterward were describing one that explained itself. The analysis will treat the two groups separately before comparing them, and the update may turn out to be one of the study's findings: whether explanation changes how underwriters use a score.

What the Departures Have in Common

Read together, the four entries show that the study's setting is less stable than the protocol assumed. Questions that looked neutral on paper carried weight in an office where underwriters' discretion was already being measured. Physical space changed with a reorganization nobody in the study controlled. Participants exercised options the consent form gave them. And the object of study itself changed partway through. None of these could have been fully anticipated, which is why the log exists: the protocol described the study as planned, and the log describes it as done.

A Departure Not Taken

The log also records one departure the candidate considered and rejected. After the vendor update, the candidate's manager suggested re-interviewing early participants about the new display. That would have produced cleaner comparisons, but it would have meant asking people to participate twice without having consented to it, and it would have drawn on the candidate's managerial relationship with some of them. The suggestion was declined, and the log records why, so that the committee can see the choice and its reasoning.

What the Log Commits To

Each entry will appear in the methods chapter, with the table reproduced in an appendix. Findings will be reported with the version of the tool and the interview mode noted where they matter. And the log will be kept until the last interview, since departures in the remaining fieldwork are likely, and an entry written on the day is more reliable than one reconstructed at the end.

References

Kallio, H., Pietilä, A.-M., Johnson, M., & Kangasniemi, M. (2016). Systematic methodological review: Developing a framework for a qualitative semi-structured interview guide. Journal of Advanced Nursing, 72(12), 2954-2965. https://doi.org/10.1111/jan.13031

Lincoln, Y. S., & Guba, E. G. (1985). Naturalistic inquiry. SAGE.

Protection of human subjects, 45 C.F.R. pt. 46 (2018).

The DBA-960 Topic 4 assignment instructions

Topic 4 in DBA-960 asks doctoral students to keep a dated record of departures from their approved protocol during fieldwork. Strong logs record each departure on the day it occurs, with its cause, whether it needed approval and which data it touches. Students should explain the effect of each departure on the data, including changes to the object of study itself, and state how the analysis will handle it. The log should also record departures considered and rejected, read the entries together for what they reveal about the setting and commit to continuing the record until fieldwork ends.

Inside the DBA 960 Topic 4 example

The finished log is a dated table with a paragraph of commentary under each entry. The first entry comes from the pilot. Two underwriters from an office outside the sample tried the interview guide, and one question about how often they override the score was heard as an audit of their judgment; it was rewritten to ask about a recent case, and the amendment was approved before the main interviews began. The second entry records a reorganization that moved interviews from meeting rooms to video. The third notes that several participants declined recording, so field notes replace transcripts for those interviews. The fourth marks the date the vendor changed how the score is displayed, which means later participants were describing a different version of the tool. Each entry states which data it touches.

Reading the DBA 960 Topic 4 rubric

Faculty reward an audit trail kept on the day. An Excellent log tables four dated departures with cause, approval and data affected, after Lincoln and Guba on dependability. Credit goes to the pilot rewrite approved before main interviews, as Kallio and colleagues advise and the federal rule requires. The rubric values comparing video and in-person themes, marking field-note interviews as paraphrase and separating interviews before and after the vendor update. Strong logs read the entries together. Top marks go to recording a rejected re-interview and why.

DBA 960 Topic 4 help: mistakes that cost marks

A log written up after collection ends draws the heaviest deductions, because it reads as narrative and cannot show what the candidate knew when each change was made. Many papers record departures without dates or without the approval each needed, which leaves a committee unable to tell a disclosed amendment from an unapproved change. The pilot is often omitted, although revisions it prompts are departures from the guide the proposal described. Candidates who note that recording was declined but then quote those interviews as if verbatim convert paraphrase into testimony. A change in the tool being studied, such as a software update partway through, is frequently missed because it happened outside the research, and it quietly splits the data in two. Entries describing what changed without saying what it does to the analysis leave the record decorative.

Get a DBA-960 Topic 4 example written to your instructions

Send the DBA-960 Topic 4 instructions and your classroom rubric. We write a custom structural example to them, showing protocol departures logged with dates and consequences, in 24 to 48 hours, and the first one is free. Your dissertation is your own work: we never write chapters for a reader, and your IRB application, site permission letters, committee correspondence and signatures remain yours.

More DBA 960 papers and DBA samples

DBA 960 Topic 4 questions, answered

Why log protocol departures as they happen?

Because a record made afterward can only reconstruct, and reconstruction tends to smooth over what was uncertain at the time. A dated entry shows what the candidate knew when a change was made, who approved it and which data it touched. Committees treat that record as evidence about the conduct of the study, while a retrospective account reads as explanation.

Does a pilot change count as a departure?

It counts as a change to the instrument the proposal described, and it belongs in the record even when it was approved before the main collection. The example logs the rewritten override question beside the original, with the reason and the approval, which shows that the interviews used the revised guide and why the revision was needed.

What if participants refuse to be recorded?

Respect the refusal, take careful field notes and record the change in the log. Notes are not transcripts, so quotations drawn from those interviews should be marked as paraphrase wherever they appear. The example flags every such passage, which keeps the analysis honest about the difference between what a participant said and what the researcher wrote down afterward.

Where can I find a free DBA 960 Topic 4 sample paper?

The departure log is printed here in full: why keep it, the dated table, the pilot, video interviews, declined recording, the changed tool, what the departures share, a departure not taken and the commitments. Share your DBA 960 Topic 4 prompt for a free log.

Why treat interviews before and after the vendor update separately in DBA 960 Topic 4?

Earlier participants described a tool giving a single number, later ones a tool that explained its score. Comparing them separately may show whether explanation changes how underwriters use scores.