Staff hours, access and named roles are argued inside the method in the DBAX 9102C Week 8 section, which prices each demand and names the fallback if support is withdrawn. Searches like "dbax 9102c week 8 assignment example", "dbax9102c week 8 sample" and "dbax 9102c week 8 example" land here.
What a finished DBAX 9102C Week 8 feasibility section looks like
Three to four pages inside the method chapter. A demand table sits at its center: twelve account managers for one sixty-minute interview each, two service team leads for a ninety-minute records walkthrough, a CRM extract of renewal histories approved by the compliance officer, and one operations manager as the named contact. Timing appears beside every row, with the peak renewal months excluded because account managers cannot spare an hour then. A paragraph on access follows, drawing on Buchanan, Boddy and McCalman's account of getting in, getting on, getting out and getting back, which treats access as renegotiated throughout a study rather than granted once. A contingency section closes the section: if the extract is refused, the study falls back to renewal records the service leads can summarize, and the section states what that fallback loses.
How a DBAX 9102C Week 8 example is structured
The section opens with a two-sentence restatement of the design, since feasibility only means something relative to what the method needs. The demand table comes next and does most of the arguing, with each row stating role, time, timing and approver. A timing paragraph explains the calendar, why the study avoids the renewal peak and how the schedule shifts as a result. The access paragraph then describes how agreement was obtained, who holds it, and when it will be reconfirmed, since the operations manager who agreed may not be the person who approves the extract. Risks follow in order of likelihood, each paired with a fallback and the evidence that fallback would sacrifice. A short final paragraph states the minimum the study needs to answer its question at all, below which the author would stop and redesign rather than continue with a study too thin to answer anything.
Demands by role, hour and month
Twelve account managers, sixty minutes each, outside the renewal peak. Two team leads, ninety minutes. One extract, one approver. Stating demands this plainly lets the client price the study in staff time, which is how the business will judge it.
The calendar the business runs on
Peak renewal months are closed to interviews. The section shows how the schedule bends around them and what the delay costs the stage timeline, so the constraint appears as a design fact rather than an excuse.
Access as an ongoing agreement
The operations manager agreed; the compliance officer approves extracts. Buchanan, Boddy and McCalman's view that access is renegotiated throughout a study shapes a plan to reconfirm at each stage, with dates.
Fallbacks with their costs
If the extract is refused, team leads summarize renewal patterns instead. The section says what that loses: account-level timing and any link between departures and specific lost renewals. Each fallback is priced in evidence.
The floor below which the study stops
Eight interviews and some form of renewal record are the minimum. Below that, the study cannot answer its question, and the section commits to redesign rather than proceeding on too little.
Where marks go in DBAX 9102C Week 8
Specificity is the first test. A feasibility section saying that access has been secured and participants are available tells a reader nothing; one naming roles, hours, months and approvers can be checked, which is how markers approach it. The calendar paragraph earns credit when it shows the business's rhythm shaping the schedule. Access is weighed for realism, since agreement from one manager rarely covers every data source, and a section that treats one yes as permanent draws skepticism. The contingency section counts heavily: fallbacks that state what they lose show the author understands the design, while fallbacks presented as equivalent substitutes do not. The stopping floor is credited separately in many sections. Graders also notice when no risk appears at all, since no study inside a working brokerage runs without one.
Get a DBAX 9102C Week 8 example written to your instructions
If the client has agreed to anything yet, list it by role alongside the Week 8 prompt, rubric and design. A feasibility section with demand table, calendar, fallbacks and stopping floor arrives within 24-48h, and the first is free. Roles and months carry the argument, so no staff member is ever named in the draft or needs to be named in the request.
DBAX 9102C Week 8 questions, answered
How precise should time estimates be?
Precise enough that the client could approve them: minutes per interview, hours per walkthrough, the number of people. Ranges are fine where genuinely uncertain, such as sixty to seventy-five minutes, but open-ended requests, such as some time from the service team, invite refusal later. Precise demands also help your committee judge whether the evidence planned can actually be collected in the time the client grants.
Does the client need to sign anything before this section is written?
Programs differ. Many require a documented agreement with the organization before data collection and ethics approval, and the feasibility section describes that agreement without reproducing it. At this stage, the section may rest on verbal agreement, provided it says so. Your institution's review board will expect the formal agreement later, and the section should name when it will be obtained.
What if the fallback would change the research question?
Then it is not a fallback but a redesign, and the section should say so. A true fallback answers the same question with weaker evidence. If losing the CRM extract means the study can no longer link departures to lost renewals, the question itself has to narrow, and the section names that narrowed question in advance so the change is planned rather than improvised.