DBA-960 · Topic 4

DBA-960 Topic 4 fieldwork departure log example

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

A composite commercial insurer's underwriting manager began interviewing underwriters about a new risk-scoring tool, and within two months the study had left its approved protocol four times. This finished DBA-960 Topic 4 fieldwork departure log example records each departure on the date it happened, with its cause and its cost. Midpoint topics in DBA 960 commonly keep such a record, and the pilot is where this one starts.

What this page holds

A finished DBA-960 Topic 4 fieldwork departure log example, dating four departures from an insurer study's approved protocol, from a pilot-driven question change to a mid-study software update. Searches like "dba 960 topic 4 assignment example", "dba960 topic 4 sample" and "dba-960 topic 4 example" land here.

What a finished DBA-960 Topic 4 fieldwork departure log looks like

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.

How a DBA-960 Topic 4 example is structured

The log is presented in four parts. A brief preface explains that departures are recorded when they occur because a record kept afterward cannot show what was known at the time. Next comes the table, with columns for date, departure, cause, who authorized it, amendment status, data affected and consequence for the analysis. A third part expands each entry into a paragraph, and the pilot entry also shows the original question beside its revision letting the change and its reason be read together. The fourth part draws the entries together for the analysis to come: interviews after the display change are grouped separately, note-based interviews are flagged wherever they are quoted, and the question change is traced so that no comparison runs across the two versions of the guide. The log stays open until the last interview closes.

The pilot as the first entry

Testing the guide with underwriters outside the sample exposed a question heard as an audit, and the log records the revision and its approval before fieldwork began.

Recorded on the day it happened

Each departure carries the date it occurred and the date it was logged, so a reader can confirm the record was kept during collection rather than rebuilt later.

Notes where recording was declined

Participants who refused recording are interviewed from field notes, and every later quotation from those interviews is flagged as paraphrase rather than transcript.

A software update splits the data

After the vendor changed how the score displays, interviews describe a different tool, so the analysis groups them separately instead of treating all accounts as one.

Consequences carried into analysis

The final section converts each entry into an instruction for the analysis chapter, which keeps the departures from being acknowledged once and then forgotten.

Where marks go in DBA-960 Topic 4

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.

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.