A finished DBA-960 Topic 3 sensitivity exclusion log example, recording what an aerospace supplier released, redacted or refused and stating what each exclusion removes from the study's claims. Searches like "dba 960 topic 3 assignment example", "dba960 topic 3 sample" and "dba-960 topic 3 example" land here.
What a finished DBA-960 Topic 3 sensitivity exclusion log looks like
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.
How a DBA-960 Topic 3 example is structured
The log sits inside a short methods note arranged in five parts. The note begins by explaining that commercial confidentiality is expected in this sector and that the log exists so readers can judge what is missing rather than guess. The second part defines the release categories used throughout: provided, redacted, aggregated, refused and known but not usable. A third part is the log itself, with one row per request and a date for every change in status. The fourth part draws the consequences together, stating for each category which claims the analysis can still make and which it must abandon. The last part describes the compensations adopted, such as asking about escalation practice in interviews where documents are silent, and marks each one as partial so no reader mistakes a workaround for the data it replaces.
Release categories defined before use
Provided, redacted, aggregated, refused and known but not usable are defined before the first row, which keeps every entry meaning the same thing to every reader.
An indexed series in place of prices
Indexed figures show when escalation clauses triggered and which way prices moved, and the log states plainly that magnitude has left the study.
The largest customer refused outright
One account's contracts are withheld under its own confidentiality terms, and the log records that the findings will describe smaller customer relationships only.
Knowledge from the job set apart
What the candidate knows from managing these contracts is listed as off limits, since knowledge gained in the role was never released for research.
Compensations marked as partial
Interview questions about escalation practice fill some gaps the documents leave, and each compensation is labeled partial so it is not mistaken for the missing data.
Where marks go in DBA-960 Topic 3
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.
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.