A finished DBA-960 Topic 1 permission scope reconciliation example, comparing a grocery study's approved protocol, site letter and data agreement line by line and resolving four gaps before collection. Searches like "dba 960 topic 1 assignment example", "dba960 topic 1 sample" and "dba-960 topic 1 example" land here.
What a finished DBA-960 Topic 1 permission scope reconciliation looks like
The finished reconciliation is a comparison table with a short commentary, and it describes the permission documents rather than reproducing or drafting them. Down the left run the dimensions any permission has to settle: who signed and on what authority, which data, which period, which participants, what use and what publication. Across the top sit the three documents. The table exposes four gaps. The regional vice president who signed the site letter controls merchandising staff but not the finance system that holds promotional funding records. The letter mentions sales data in general while the protocol requests supplier-level extracts. Finance agreed to two fiscal years where the protocol names three. No document mentions publication at all. For each gap the commentary records the resolution sought, from whom, and whether collection waits for it.
How a DBA-960 Topic 1 example is structured
The reconciliation is arranged in five parts, beginning with the rule the candidate applies: nothing is gathered until every data source in the protocol is covered by a permission from someone entitled to give it. Next comes the comparison table, one row per dimension and one column per document. A third part discusses each gap in turn, explaining why it matters and what would follow if collection went ahead regardless. The fourth part records the resolution path for each gap, such as a confirmation from the chief financial officer's office, a protocol amendment through institutional review to match the two-year window, and explicit written agreement on publication. The last part is a dated status log showing which gaps are closed, which are pending and which data sources remain untouched until they close.
Six dimensions every permission must settle
Signatory authority, data, period, participants, use and publication form the rows, so each document is tested against the same questions rather than read on its own terms.
A signatory without authority over finance
The vice president's signature covers merchandising staff but not the finance system holding promotional funding records, which only the chief financial officer's office can release.
Two years agreed where three were approved
Finance will release a shorter window than the protocol names, and the reconciliation amends the protocol to match rather than collecting beyond what was granted.
Publication unmentioned in every document
None of the three documents addresses whether findings may be published, so explicit agreement is sought before collection instead of after an awkward result.
A dated log of what is closed
Each gap carries its status and the date it changed, so a committee can see that collection began only after the relevant permission was confirmed.
Where marks go in DBA-960 Topic 1
Reconciliations earn the least when they treat a signed site letter as settling everything, since a signature is only as broad as the signer's authority and grocery finance systems rarely belong to merchandising. Candidates also lose credit by resolving a mismatch in favor of the protocol, collecting three years because the university approved three when the organization released two. A frequent omission is publication, which none of the documents mention and which becomes contentious the moment findings disappoint the company. Some papers identify gaps accurately and then begin collection while resolutions are pending, which turns a careful document into a record of knowing risk. Tables comparing documents on data alone miss participants, period and use. A reconciliation with no dates, and no record of when each gap closed, cannot show the committee that collection actually waited.
Get a DBA-960 Topic 1 example written to your instructions
Send the DBA-960 Topic 1 instructions and your classroom rubric. We write a custom structural example to them, showing permissions reconciled against the approved protocol, in 24 to 48 hours, and the first one is free. A dissertation is the candidate's 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 1 questions, answered
What if my site permission does not match my IRB approval?
Resolve the difference before collecting anything. Usually that means either obtaining broader permission from someone entitled to give it or amending the approved protocol, via institutional review, to match what the organization released. Both routes appear in the composite grocery study, where the protocol is narrowed to the period finance agreed to release rather than collecting beyond it.
Who counts as an authorized signatory?
Someone whose position lets them bind the organization on the particular records or staff in question. Seniority alone does not qualify a signer when the records belong to another function. The example finds a merchandising vice president who could approve staff interviews but not the release of finance records, and it seeks confirmation from the office that actually controls those records.
Can collection start while one permission is still pending?
Only for data sources the confirmed permissions already cover, and many candidates wait regardless so the whole dataset is gathered under one consistent set of terms. The example leaves every source touched by an open gap alone until that gap closes, and dates each closure, so a committee reading the log later can see that nothing was gathered ahead of its authorization.