DBA 955 Topic 7 access feasibility plan example

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

This DBA 955 Topic 7 sample paper plans who can approve each kind of access for a study of how 1,400 field technicians at a composite telecommunications provider adopt a new dispatch app. It forms part of GCU DBA 955, Dissertation I, catalog code DBA-955, offered through Grand Canyon University's DBA. A table names the approver, scope and fallback for technician interviews, supervisor interviews, usage logs and rollout documents. The union is consulted before any invitation, and logs come aggregated through data governance. Following Coghlan and Brannick, job access is separated from research use, and Cunliffe and Alcadipani's politics of access shape written terms.

CourseDBA 955 Dissertation I
TopicTopic 7
Paper typeAccess feasibility plan
LengthAbout 1,010 words, 2 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramDBA
UpdatedOctober 2026

Free sample paper for DBA 955 Topic 7

1

Who Can Say Yes: An Access Feasibility Plan for Studying How Field Technicians Adopt a New Dispatch App

[Author Name]

College of Doctoral Studies, Grand Canyon University

DBA-955: Dissertation I

Topic 7 Access Feasibility Plan

[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 plan's central question. The candidate and the telecommunications provider are composites; the sources are real. The plan describes what permission documents must cover and does not draft them.
2

Who Can Say Yes: An Access Feasibility Plan for Studying How Field Technicians Adopt a New Dispatch App

The Study and Why Access Must Be Confirmed

A doctoral candidate who works as a service delivery manager at a composite telecommunications provider proposes to study how field technicians adopt a new dispatch app, rolled out over the past year across three regions with about 1,400 technicians. The study would combine interviews with technicians and dispatch supervisors, aggregated usage data from the app and internal documents from the rollout. The candidate works for the company and can see much of this material every day. That is precisely why access must be planned carefully: being able to see something in a job is not permission to use it in research. Bell et al. (2019) noted that gaining access is often a negotiated, ongoing process involving several gatekeepers, not a single permission granted once.

What the Study Needs and Who Can Approve It

Each kind of access is listed with the person who holds authority to approve it, which is rarely the candidate's own manager.

Table 1

Access Needs, Approving Authorities and Fallbacks

What the study needsWho can approve itWhat approval must coverIf refused
Interviews with techniciansVice president of field operations; local union representative consultedTime on or off shift, voluntary participation, no reporting to supervisorsRecruit through the union newsletter off shift, or narrow to supervisors
Interviews with dispatch supervisorsDirector of dispatchRelease time, confidentiality from senior managementReduce interviews; rely more on documents
Aggregated app usage logsData governance office, after legal reviewAggregation level, no individual identifiers, storage outside company systemsUse published adoption figures from rollout reports
Internal rollout documentsProgram director for the rolloutWhich documents, how they may be quotedLimit to documents already shared company-wide

Technician participation needs two kinds of agreement. The vice president of field operations controls technicians' time and can authorize interviews during shifts. But technicians are represented by a union, and a study inviting them to discuss a tool that may be used to measure their work will be read through that lens. A conversation with the local representative before any invitation goes out is not a formality; without it, technicians are likely to decline, and the union may object on their behalf.

The Data Governance Question

The app's usage logs record each technician's location, job times and actions. The candidate's login can reach summary reports of these logs, which the candidate uses to manage service delivery. For research, the data governance office must approve use, and legal review must confirm that the purpose is consistent with the notices technicians received when the app was introduced. The plan proposes that the governance office supply aggregated data, by region and week, with no individual identifiers, so that no technician's performance can be inferred from the research data.

Separating the Job From the Research

The plan distinguishes what the candidate may see as an employee from what the candidate may use as a researcher. Coghlan and Brannick (2014) described the dual roles insider researchers occupy and the need to negotiate both. In this study, the line is drawn explicitly. The candidate will not use individual technicians' records, even though the candidate's login reaches them. The candidate will not use performance reviews, disciplinary files or complaints, all of which pass through the candidate's role. The candidate will not use anything a technician says in an interview in any management decision. Each exclusion will be written into the approval documents and the consent form, so that participants know what the candidate has promised not to do.

The Politics of Access

Access is not only a matter of permissions. Cunliffe and Alcadipani (2016) showed how access in fieldwork is shaped by organizational politics, shifting relationships and the interests of gatekeepers, and how it can be withdrawn as circumstances change. Here, the rollout program director has a stake in the app's success and may welcome a study that confirms it but resist one that finds technicians working around it. The union may support a study that documents problems but resist one that seems to help management monitor its members. The plan responds by agreeing scope, publication terms and the right to report unfavorable findings with each gatekeeper in advance, in writing.

What the Permission Documents Must Cover

The plan does not draft the permission letters, which the university's review board and the company's legal office will shape, but it lists what each must cover. Each must name the data or people it concerns, the purpose, the period of access and how data will be stored and destroyed. Each must state whether the company may review findings before publication, and if so, that review is limited to checking for confidential information and does not extend to changing conclusions. Each must name the person at the company who can withdraw access and how much notice they must give. And the letter covering technicians must confirm that participation is voluntary and that no supervisor will be told who took part.

Sequence and Timing

Order matters, because some gatekeepers will ask what others have said. The plan approaches the union representative and the vice president of field operations first, in the same week, so neither learns of the study from the other. The data governance office follows once the purpose is agreed, since its legal review depends on a settled scope. The rollout program director comes last, with the scope already fixed. The plan allows ten weeks for all four approvals and treats any approval still missing at twelve weeks as a refusal for planning purposes.

If a Gatekeeper Refuses

The final column of the table states a fallback for every refusal. The study can survive the loss of usage logs or of internal documents, since interviews carry the core of the research question. It cannot survive the loss of technician interviews. If both the vice president and the union decline, the study would need to be redesigned around supervisors and documents, a weaker study that the candidate would discuss with the chair before proceeding.

References

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

Coghlan, D., & Brannick, T. (2014). Doing action research in your own organization (4th ed.). SAGE.

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

DBA 955 Topic 7 instructions, in plain terms

The Topic 7 assignment in DBA-955 asks doctoral students to plan access for research in a real organization. Strong plans list each kind of access the study needs and name who holds authority to approve it, which is often not the candidate's manager. Students should separate what they can see in their job from what they may use as researchers, list what permission documents must cover without drafting them and set a sequence and timeline for approaching gatekeepers. The plan should anticipate the politics of access and state a fallback for each refusal, including which refusal the study could not survive.

How this DBA 955 Topic 7 example is built

The finished plan is a table with a short argument around it, and it describes what the eventual permission documents must cover without drafting any of them. Each row names one thing the study needs: interviews with technicians, interviews with dispatch supervisors, aggregated app usage logs and internal rollout documents. Against each sits the person with authority to approve it, which is rarely the candidate's own manager. Technician participation needs the vice president of field operations and, because the technicians are represented by a union, a conversation with the local representative. The usage logs need the data governance office and legal review. The plan also separates what the candidate may see in his job from what he may use as a researcher, and lists the records he will not touch even though his login reaches them.

Where the marks sit in the DBA 955 Topic 7 rubric

Faculty reward access mapped to the people who can grant it. An Excellent plan tables each need with approver, scope and fallback, citing Bell, Bryman and Harley on negotiated access. Credit goes to consulting the union before inviting technicians and to aggregated logs approved by data governance. The rubric values separating job access from research use with Coghlan and Brannick, and Cunliffe and Alcadipani on gatekeeper interests. Strong plans list what permission documents must cover and sequence the approaches. Top marks go to naming the refusal the study cannot survive.

DBA 955 Topic 7 help: mistakes that cost marks

The weakest access plan leans on a friendly manager's spoken assurance, which lapses with that manager's next reassignment and was rarely theirs to give. A second loss is treating job access as research access, where the candidate plans to analyze records he can already open without asking whether he may use them for a dissertation. Plans listing one approver for the whole study usually miss that interviews, operational data and documents fall under different authorities. Omitting a gatekeeper the setting plainly has, such as a union, a legal office or a works council, reads as unfamiliarity with the organization the candidate claims to know. Plans with no fallback treat approval as certain. Where a plan describes permission documents as already drafted and signed at the proposal stage, a committee will ask to see them.

Get a DBA-955 Topic 7 example written to your instructions

Send the DBA-955 Topic 7 instructions and your classroom rubric. We write a custom structural example to them, showing access mapped to the people entitled to grant it, 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 site permission letters, your IRB application, committee correspondence and signatures stay yours.

More DBA 955 papers and DBA samples

DBA 955 Topic 7 questions, answered

Who should approve access to my own company?

Whoever holds authority over the specific data or people involved, which is rarely the manager who likes the study. Interviews with employees, operational records and internal documents often sit under different approvers, sometimes including legal, data governance or employee representatives. The example maps each source to its approver so the eventual permission covers exactly what the study will use and survives a change of contact.

Can I use data I already access in my job?

Not simply because you can reach it. Operational access is granted for your role, and using the same records for research usually needs separate approval from the organization and review through the university's process. The example lists the records the candidate can open at work and excludes them from the study unless their research use is approved, which is the question a committee will ask.

Will you draft my site permission letter?

No. Site permission letters, institutional review applications and committee correspondence are the candidate's own documents, and they carry signatures that must be genuine. The example on this page describes, at a structural level, what an access plan typically covers and how it connects to the method, using a composite telecommunications case. Your dissertation and every approval behind it remain yours.

Where can I find a free DBA 955 Topic 7 sample paper?

The structural example is shown here complete: why access must be confirmed, needs and approvers, data governance, job and research separated, document contents, sequence, politics and fallbacks. Post your DBA 955 Topic 7 prompt and get a free paper.

Why approach the union first in DBA 955 Topic 7?

Technicians will read a study of a tool that may measure their work through the union's view. Without the representative's support they are likely to decline, and the union may object for them.