DBA 960 Topic 3 sensitivity exclusion log example

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

This DBA 960 Topic 3 sample paper records every item a composite aerospace components supplier withheld from its contracts manager's study of price escalation clauses, and what each gap removes. It forms part of GCU DBA 960, Dissertation II, catalog code DBA-960, a core course of Grand Canyon University's DBA. Prices return as an indexed series, clauses arrive with names and quantities redacted, the largest customer's agreements are refused and correspondence comes as legal summaries. Bell, Bryman and Harley explain why firms restrict access. Interviews carry what documents cannot, Yin frames generalization without the dominant customer, and a known-but-not-usable category marks what the job revealed.

CourseDBA 960 Dissertation II
TopicTopic 3
Paper typeSensitivity exclusion log
LengthAbout 950 words, 2 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramDBA
UpdatedOctober 2026

Free sample paper for DBA 960 Topic 3

1

What Came Back and What Each Gap Removes: A Sensitivity Exclusion Log for a Study of Price Escalation Clauses

[Author Name]

College of Doctoral Studies, Grand Canyon University

DBA-960: Dissertation II

Topic 3 Sensitivity Exclusion 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 the log's two columns that matter most. The candidate and the aerospace supplier are composites; the sources are real. Dates and items are illustrative.
2

What Came Back and What Each Gap Removes: A Sensitivity Exclusion Log for a Study of Price Escalation Clauses

The Study and Why a Log Is Needed

A doctoral candidate who works as a contracts manager at a composite aerospace components supplier is studying how price escalation clauses, the contract terms that adjust prices when material or labor costs change, are negotiated and applied in long-term supply agreements with aircraft manufacturers and their tier-one suppliers. The company agreed to support the study. When data requests went in, most of what made the clauses commercially interesting came back restricted. This is common in business research: Bell et al. (2019) noted that organizations often limit access to commercially sensitive material even after agreeing to a study. The candidate has kept a running log from the first data request, dated row by row, so that every exclusion is recorded when it happens, with what it costs the analysis. The log will be summarized in the methods chapter and reproduced in an appendix.

The Log

Each row records the item requested, what the company actually provided, the reason given, who made the decision and what the exclusion costs the analysis.

Table 1

Sensitivity Exclusion Log, Illustrative Entries

DateItem requestedProvidedReason givenDecided byCost to analysis
Month 1Customer-specific prices and margins, 2016 to 2024Indexed price series by customer, base year 100Margins commercially sensitiveChief financial officerCan trace when escalation triggered and direction of price movement, not size in dollars
Month 1Full text of escalation clauses in 14 agreementsClause text with customer names and quantities redactedConfidentiality obligations to customersGeneral counselCan compare clause design, not link design to customer size
Month 2Agreements with the largest customerRefusedContract forbids disclosure to third partiesGeneral counselLargest account excluded; findings speak to smaller relationships
Month 2Negotiation correspondenceSummaries prepared by legal, no emailsPrivilege and confidentialityGeneral counselProcess data second-hand; interviews must carry it
Month 3Cost index data used in clausesProvided in fullPublished indexesContracts teamNo cost

Reading the Indexed Series

The indexed price series is the most consequential compromise. With prices expressed as an index for each customer, the study can trace when escalation clauses triggered, how quickly prices adjusted after cost indexes moved and whether prices moved up and down symmetrically. It cannot say how much money the clauses moved or compare price levels across customers. The research questions concern how clauses are designed and applied, so the index preserves most of what the study needs. Questions about the financial impact of escalation, which the candidate had hoped to address in a secondary analysis, are dropped and will be named as a limitation.

The Largest Customer

The refusal of the largest customer's agreements is the most serious gap for generalization. That customer accounts for about 38 percent of the supplier's revenue and negotiates from a position the others do not share. Its exclusion means the findings describe escalation in relationships where the supplier has more bargaining room. Yin (2018) emphasized that case study findings generalize to theory rather than to populations, and the dissertation will frame its conclusions accordingly, stating that dominant-customer relationships may work differently and that this study cannot say how.

How the Interviews Carry What the Documents Cannot

With negotiation correspondence replaced by legal summaries, interviews must carry the account of how clauses were negotiated. The candidate will interview contracts, pricing and program staff on both sides of the agreements where customers permit, asking about the reasoning behind clause design rather than about specific prices. Because interviewees may refer to figures the company has restricted, the interview guide reminds them at the start not to name prices, margins or customer volumes, and any figures mentioned will be removed from transcripts before analysis. The interviews will also be used to test the indexed series: if an interviewee describes an escalation event, the candidate will check that it appears in the index at the time described.

What the Exclusions Do Not Change

Not every restriction weakens the study. The cost indexes referenced in the clauses were provided in full, so the analysis of how clauses link prices to published measures of metals, energy and labor costs is complete. The redacted clause texts preserve the mechanisms: trigger thresholds, adjustment formulas, caps, floors and review periods. The core research question, how escalation clauses are designed and applied in long-term aerospace supply agreements, can still be answered for the agreements provided, which cover eleven customers across commercial and defense programs. That breadth was the reason for studying several agreements rather than one, and it survives the restrictions largely intact.

Known but Not Usable

A final category in the log lists what the candidate knows from the job and may not cite. As contracts manager, the candidate has read the largest customer's agreements, attended negotiations and seen margin reports. None of that knowledge can appear in the dissertation, and the log records the categories, without content, so that the committee knows the boundary exists. The candidate will have the findings chapter read by a colleague outside the contracts function, who will flag any statement that appears to rest on unusable knowledge rather than on the data provided.

Why the Log Matters

Access that a company grants can narrow later as people and priorities change (Cunliffe & Alcadipani, 2016). A log kept as exclusions happen protects the study in three ways. It lets the committee judge what the study can and cannot claim. It protects the candidate from later suggestions that data were withheld or used without permission. And it gives future researchers an honest account of what this kind of study can obtain inside a company, which is itself a contribution.

References

Bell, E., Bryman, A., & Harley, B. (2019). Business research methods (5th ed.). Oxford University Press.

Cunliffe, A. L., & Alcadipani, R. (2016). The politics of access in fieldwork: Immersion, backstage dramas, and deception. Organizational Research Methods, 19(4), 535-561. https://doi.org/10.1177/1094428116639134

Yin, R. K. (2018). Case study research and applications: Design and methods (6th ed.). SAGE.

Reading the GCU DBA 960 Topic 3 instructions

Topic 3 in DBA-960 asks doctoral students to document data an organization withholds and what each exclusion costs. Strong logs are kept from the first request, with each dated row recording the item requested, what was provided, the reason, the decision maker and the cost to the analysis. Students should explain how compromises such as indexed or redacted data change what the study can claim, show how other sources carry what documents cannot and keep job knowledge apart from what the study is permitted to use from what they may use as data. The paper should state which exclusions do not weaken the study.

How this DBA 960 Topic 3 example is built

The finished log is a running table kept from the first data request, and each row is dated. Its columns record the item requested, what the company actually provided, the reason given, who made the decision and what the exclusion costs the analysis. Customer-specific prices and margins come back as an indexed series, so the study can trace when escalation clauses triggered and in which direction prices moved, but not by how much. Contract clauses arrive with customer names and quantities redacted. One customer's agreements are refused outright under a confidentiality obligation to that customer, and because it is the largest account, the log notes that findings will speak to smaller relationships. A final category, known but not usable, lists what the candidate knows from his job and may not cite.

Reading the DBA 960 Topic 3 rubric

Faculty reward exclusions recorded as they happen. An Excellent log tables requests, provisions, reasons, decision makers and costs from the first request, noting with Bell, Bryman and Harley that firms guard commercial data. Credit goes to reading the indexed price series for what it preserves and loses. The rubric values treating the refused largest customer as a limit on generalization, following Yin. Strong logs show interviews carrying negotiation history and name what the exclusions leave intact. Top marks go to a known-but-not-usable category checked by an outside reader.

Common DBA 960 Topic 3 mistakes, and how to avoid them

The weakest submissions mention confidentiality once in the limitations and never say what was withheld, leaving a reader with no way to judge how much of the picture is missing. A related loss comes from quietly analyzing indexed or aggregated figures as though they were the original data, which lets a claim about magnitude slip in where only direction survives. Insider candidates are marked down for drawing on what they know from their job when the company never released it, since that knowledge sits outside the permission and cannot be checked. Logs assembled at the end of collection, rather than kept as requests are answered, read as reconstruction and lack dates. Compensations presented as full substitutes overstate what interviews can recover. Papers that treat the refused customer as a minor gap miss that its absence changes whom the findings describe.

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

Send the DBA-960 Topic 3 instructions and your classroom rubric. We write a custom structural example to them, showing withheld material logged with its consequences, in 24 to 48 hours, and the first one is free. Your dissertation is your own work: chapters are never written 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 3 questions, answered

What if my company refuses to release key data?

Record the refusal, its reason and who made it, then state what the refusal removes from the claims your study can make. A refusal rarely ends a study, but hiding one weakens it badly. The example logs a refused customer and an indexed price series, narrowing the findings to smaller accounts and to the direction rather than the size of price changes.

Can I use what I know from my job in my dissertation?

Generally not as data, unless the organization has approved that use through the same permission that covers the rest of the study. Knowledge gained in your role was given to you for the job. The example lists such knowledge in its own category, known but not usable, so the committee can see the candidate recognized the boundary and kept to it.

Does this example contain any real company's contract data?

No. The supplier, its customers, the clauses and the indexed series are all composites invented for coursework, and no actual commercial information appears. What the example offers is the organization of a sensitivity log and the kinds of entry it holds. Your own data, the permissions that govern it and every chapter built on it remain your responsibility and your work.

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

The exclusion log is shown here complete: why a log is needed, the dated entries, the indexed series, the largest customer, how interviews fill gaps, what the exclusions leave intact, known but not usable and why the log matters. Send your DBA 960 Topic 3 prompt and a log follows free.

What does the indexed price series still allow in DBA 960 Topic 3?

It shows when escalation clauses triggered, how quickly prices followed cost indexes and whether prices moved symmetrically. It cannot show dollar amounts or compare price levels across customers.