| Course | GB892 Doctoral Project III: Data Analysis |
|---|---|
| Unit | Unit 3 |
| Paper type | Codebook |
| Length | About 860 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | MBA |
| Updated | October 2026 |
Free sample paper for GB892 Unit 3
Nine Codes Tied to Nine Fields: A Unit 3 Codebook for Interviews in a Dock Appointment Study
[Student Name]
Purdue University Global
GB892: Doctoral Project III: Data Analysis
Unit 3 Codebook
[Instructor Name]
[Date]
Haverly Logistics, its interviews and every anchor excerpt are composite and illustrative; the excerpts are invented to show the method, and the sources cited are real.
Preface
The codebook will be applied to seventeen interviews with dock supervisors and carrier dispatchers about why trucks wait at Haverly's centers. The unit of coding is one speaker turn: everything a participant says between two questions from the interviewer. The codebook was drafted before coding began, following the structure DeCuir-Gunby et al. (2011) recommend: each code has a name, a definition, criteria for when to apply it and when not to, and an example. Two features are added for this study. Each code has a note about whether supervisors or dispatchers are likely to raise it, and each code that describes something the yard system records is linked to the field that records it, so that the qualitative and quantitative strands can later be compared directly.
The Nine Codes
1. Crew-slot mismatch. *Definition:* the participant describes a truck arriving at its appointment time but no unloading crew being available at the door. *Include when:* the account names staffing, breaks or shift changes as the reason a booked truck waited. *Exclude when:* the truck was unbooked or early, which other codes cover. *Speaker note:* mostly supervisors. *Linked field:* door-assigned time minus appointment time, for booked visits. *Anchor, invented:* "The portal gives the truck a nine o'clock slot, but my second crew doesn't start until ten."
2. Early arrival. *Definition:* the participant describes trucks arriving well before their appointment. *Include when:* early arrival is named as a cause of waiting or as a carrier strategy. *Exclude when:* the account concerns unbooked walk-up trucks. *Speaker note:* both groups, with different reasons. *Linked field:* arrival offset, gate-in minus appointment time. *Anchor, invented:* "If I'm early I might get a door before the guy booked ahead of me."
3. Floor-loaded duration. *Definition:* the participant describes freight loaded loose on the trailer floor rather than on pallets, taking longer to unload. *Include when:* unload time or door occupancy is attributed to floor-loaded freight. *Linked field:* load type. *Speaker note:* mostly supervisors.
4. Paperwork hold. *Definition:* the participant describes a truck held after unloading because documents were missing or wrong. *Linked field:* unload complete to gate-out interval. *Speaker note:* both.
5. Walk-up handling. *Definition:* the participant describes how trucks without appointments are treated since the portal began. *Linked field:* booking status. *Speaker note:* mostly dispatchers.
6. Duplicate or placeholder bookings. *Definition:* the participant describes carriers booking slots they may not use, or booking several slots for one load. *Linked field:* bookings without a matching gate-in. *Speaker note:* both.
7. Detention dispute. *Definition:* the participant describes disagreement over whether a wait triggers detention charges. *Linked field:* none, since detention is not recorded by visit, a gap noted for the integration unit.
8. Portal working as intended. *Definition:* the participant describes the portal reducing waits or smoothing arrivals. *Include when:* a specific example is given. *Linked field:* dwell for booked, on-time visits.
9. Residual. *Definition:* any account of a cause of waiting that no other code fits. *Use:* reviewed regularly to see whether a new code is needed.
Application Rules
A turn may receive more than one code when the participant names more than one cause, such as an early arrival that then met a crew shortage. A turn receives no code if it concerns something other than waiting. The residual code is reviewed after every four transcripts; if three or more residual excerpts describe the same cause, a new code is drafted, defined and applied to all transcripts coded so far. Every change to the codebook is dated and recorded with its reason.
The Second-Reader Check
A second reader, a doctoral colleague without logistics experience, will independently code three transcripts chosen to include both supervisors and dispatchers. Disagreements will be discussed and resolved, and any definition that produced repeated disagreement will be revised. The purpose is not to compute a reliability coefficient, which some approaches to qualitative analysis question, but to test whether the definitions are clear enough for someone else to apply. Braun and Clarke (2006) note that themes are constructed by the analyst rather than found in the data, and a second reader helps show that the codes underneath them are not idiosyncratic.
A code tied to a yard field makes a testable claim: if supervisors say early trucks wait longest, the arrival-offset field can show whether they do.
What the Codebook Leaves Open
The codebook does not yet say how codes will group into themes; that is the work of thematic analysis in Unit 7. Nor does it decide whether the interview accounts and the yard data agree; that comparison, laid out as a joint display of the kind Guetterman et al. (2015) describe, waits for the results chapter. What it does is make the comparison possible by naming, for each code, the field that would confirm or contradict it.
References
Braun, V., & Clarke, V. (2006). Using thematic analysis in psychology. Qualitative Research in Psychology, 3(2), 77-101. https://doi.org/10.1191/1478088706qp063oa
DeCuir-Gunby, J. T., Marshall, P. L., & McCulloch, A. W. (2011). Developing and using a codebook for the analysis of interview data: An example from a professional development research project. Field Methods, 23(2), 136-155. https://doi.org/10.1177/1525822X10388468
Guetterman, T. C., Fetters, M. D., & Creswell, J. W. (2015). Integrating quantitative and qualitative results in health science mixed methods research through joint displays. Annals of Family Medicine, 13(6), 554-561. https://doi.org/10.1370/afm.1865
Reading the GB 892 Unit 3 instructions
The third GB892 assignment asks you to build the codebook you will apply to your qualitative data. State the approach, the number and kind of interviews and the unit of coding. Then define each code with a name, a definition, criteria for when to apply it and when not to, and an example, labeling invented examples as such. If your study is mixed methods, link each code to the quantitative field that could confirm or contradict it, and note codes with no such field. Include a residual code and a rule for when it triggers a new code. Set rules for double coding and for recording changes. Describe a check by a second reader and its purpose. Close with what the codebook leaves for later analysis. About seven pages with one table row per code is a common format for this assignment in the course.
How the GB 892 Unit 3 example is put together
The preface describes seventeen interviews with supervisors and dispatchers, coded by speaker turn, and follows DeCuir-Gunby and colleagues' code structure. Nine codes follow: crew-slot mismatch, early arrival, floor-loaded duration, paperwork hold, walk-up handling, duplicate bookings, detention dispute, the portal working as intended and a residual code. Each has a definition, rules, a speaker note and a linked field, with detention disputes flagged as having none. A margin note explains why the codebook includes positive accounts. Application rules allow double coding and review the residual code every four transcripts. A second reader checks three transcripts, consistent with Braun and Clarke's view of constructed themes, and the closing section points to Guetterman and colleagues' joint displays.
Where the points sit in the GB892 Unit 3 rubric
GB892 instructors grade the codebook on clarity and readiness for use. Each code earns credit when its definition and rules are precise enough for another person to apply. Inclusion and exclusion criteria are weighted because they prevent overlap. Invented examples should be labeled. In mixed methods studies, linking codes to quantitative fields is highly valued because it makes integration testable. A residual code with a rule for creating new codes shows the codebook can adapt without drifting. Double-coding rules and a dated change record show discipline. A second-reader check explained by its purpose, rather than as a reliability ritual, shows methodological awareness. Cite the codebook and thematic analysis sources in APA 7.
GB892 Unit 3 help from the desk
Many GB892 codebooks list code names with one-line definitions, which leaves coders to guess when a code applies. Others omit exclusion criteria, so codes overlap. Students often build codes only for problems, missing accounts of what works. Mixed methods studies frequently fail to link codes to the quantitative data they will later be compared with. Residual codes are absent, or new codes are added without a rule. Second-reader checks are described without a purpose. Define every code fully, add inclusion and exclusion rules, label invented examples, link codes to fields, include positive and residual codes, set rules for changes and double coding and explain the second-reader check. Bring your interview guide, and our team can draft a codebook with you.
Get a GB892 Unit 3 example written to your instructions
Tell us who you interviewed and what your guide asked, and include the Unit 3 prompt with its rubric. Your sample codebook comes back with definitions, boundary rules and anchors written for your participants, plus a note on where each code meets your other data if the design has a second strand. The first one is free; allow 24-48h. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More GB892 papers and MBA samples
- GB892 Unit 1: Discussion Board Post
- GB892 Unit 2: Data Preparation Record
- GB892 Unit 4: Assumption Check Summary
- GB892 Unit 5: Descriptive Results Table
- GB892 Unit 6: Seminar Reflection
- GB892 Unit 7: Thematic Analysis
- GB892 Unit 8: Inferential Results Write-up
- GB892 Unit 9: Departure Log
- GB892 Unit 10: Results Chapter Draft
- GB891 Unit 3: Review Board Application
- GB500 Unit 3: Marketing Mix Application
- GB890 Unit 3: Search Documentation
- GB512 Unit 3: Routine Business Memo
GB892 Unit 3 questions, answered
Should a codebook be finished before coding starts?
A working version should be, with definitions and boundary rules settled enough that coding can begin consistently. Most codebooks change as transcripts reveal cases nobody anticipated, and that is expected. What sections look for is a record of each change, dated and explained, so a reader can see how the final codes differ from the starting set.
Why link interview codes to quantitative fields?
In a mixed methods project the link shows in advance where the two strands can be compared, which strengthens the later integration. It must stop at naming the field. A codebook that predicts what the comparison will find has decided the answer before coding, and a committee will read that as confirmation bias rather than planning.
Is inter-coder agreement required at this stage?
Not always. Some sections ask for an agreement statistic, others for an account of how a second reader's disagreements were resolved, and some qualitative traditions reject agreement figures entirely. The codebook should say which approach the project takes and why. Your instructions and your chosen method decide which of those applies to your paper.
Where can I find a free GB892 Unit 3 sample paper?
This page carries a full GB892 Unit 3 codebook for interviews in a dock appointment study, with nine codes each tied to a yard system field.
Why link interview codes to quantitative fields?
Linking each code to a data field turns an interview claim into something the records can test, such as whether trucks described as arriving early actually wait longer.