DBAX 9103 Week 2 Research Procedure Account Example

Business Research Project Stage 3 Walden University Free custom sample in 24 to 48h

This DBAX 9103 Week 2 procedure account example rewrites a plan from the future tense into the past, recording what was actually done with data for a study of caregiver retention. Walden DBAX 9103 treats the shift in tense as more than grammar, so the account describes the home care agency, its 612 hires over 24 months and four data sources with who held them and when they arrived. It reports how records were linked by employee number and where links failed, including three paper onboarding records and 14 caregivers whose check-in logs vanished in a system replacement. A coding rule for check-ins was tested by two readers on 200 entries. Appelbaum and colleagues set the reproducibility standard, Bauer and colleagues justify studying every hire and Newman guides missing logs. The past tense here is what lets a Doctor of Business Administration (DBA) committee repeat the work.

CourseDBAX 9103 Business Research Project Stage 3
WeekWeek 2
Paper typeProcedure account
LengthAbout 770 words, 5 pages
FormatAPA 7 student paper
SchoolWalden University
ProgramDoctor of Business Administration (DBA)
UpdatedOctober 2026

Free sample paper for DBAX 9103 Week 2

1

From "Will Be Collected" to "Was Collected": A Procedure Account for a Study of Caregiver Retention, Recording in the Past Tense What Was Actually Done With Hiring, Onboarding and Check-In Records at a Home Care Agency

Student Name

Walden University

DBAX 9103: Business Research Project Stage 3

Instructor Name

Month Day, Year

What this page is doingThe title contrasts the tense of a plan with the tense of an account, because the shift exposes what changed.
2

From "Will Be Collected" to "Was Collected": A Procedure Account for a Study of Caregiver Retention, Recording in the Past Tense What Was Actually Done With Hiring, Onboarding and Check-In Records at a Home Care Agency

Plans and Accounts

Plans are written in the future tense and procedure accounts in the past, and the difference is more than grammar. A plan says what will happen if everything goes as expected. An account says what happened, including the parts that did not. Appelbaum et al. (2018) recommend that reports describe procedures fully enough for someone else to carry them out again, which a plan cannot do because it was written before the work met reality. This account describes how data were obtained, linked and checked for a study asking whether newly hired caregivers at a Kansas City home care agency stay longer when supervisors contact them early and when onboarding is finished on time.

What this page is doingThe account explains why past tense matters, because writing what was done exposes every place it differed from what was planned.
3

Setting and Population

The agency employs about 900 caregivers who provide personal care and companionship in clients' homes. Caregivers work alone at client homes and are supervised by field supervisors, each responsible for about forty caregivers. The study population was every caregiver hired over a 24-month period, a total of 612 hires.

What Was Obtained

Table 1

Data Sources as Obtained

SourceHeld byContentObtainedFormat |
Hiring listHuman resourcesHire date, separation date, pay rate, prior caregiving experience, rehire flagMonth 1 of fieldworkSpreadsheet export |
Onboarding recordsTraining coordinatorCompletion dates for six online modulesMonth 1Learning system report |
Check-in logsScheduling officeSupervisor contacts with each caregiver, with date, mode and noteMonth 2, after a delayScheduling system export |
Travel recordsScheduling officeMiles between client visitsMonth 2Scheduling system export |

All files were stripped of names by the agency's data analyst before transfer; caregivers were identified only by an employee number.

How Records Were Linked

The four files were linked by employee number. All 612 hires appeared in the hiring list. Onboarding records matched 609; the three unmatched caregivers had completed onboarding on paper during a system migration, and the training coordinator supplied their dates from paper logs. Check-in logs matched 598; the 14 caregivers without logs had been hired during a two-month period when the scheduling system was being replaced and supervisors recorded contacts in personal notebooks that were not kept. Travel records matched all 612.

What this page is doingThe account names each link and its failure rate, since unlinked records are part of what happened.
4

How Check-Ins Were Identified

The check-in log recorded every contact between a supervisor and a caregiver, including calls about schedule changes. The study defined a check-in as a contact about the caregiver's work, wellbeing or questions, excluding contacts solely about scheduling. Two readers, the agency's training coordinator and I, coded the note text of a random 200 entries independently and agreed on 186; disagreements were resolved by discussion and the rule was clarified. I then coded the remaining entries using the clarified rule.

How the Outcome Was Defined

Retention was defined as being employed by the agency 90 days after hire, taken from separation dates in the hiring list. Caregivers who transferred to the agency's sister company were treated as separated, since they left the role studied.

Why the Population Was Every Hire

Studying every hire, rather than a sample, avoided a selection decision the agency might have shaped. The training coordinator first offered a list of "typical" new caregivers; using it would have excluded people hired through a staffing partner, who tend to leave sooner. The full hiring list was requested instead. Bauer et al. (2007) found that newcomer outcomes vary with how people enter an organization, so leaving out one entry route could have distorted the result.

How Missing Logs Were Handled at This Stage

The 14 caregivers without check-in logs were not imputed or dropped at the point of obtaining data; they were flagged and carried forward so the decision could be made deliberately during preparation. Newman (2014) recommends recording the pattern and reason for missing data before choosing a method, since the reason determines which methods are defensible. Here the reason was a system change unrelated to the caregivers themselves, which the preparation note uses to justify its choice.

Approvals and Consent

The university's review board approved the study as research using existing records. The agency's chief executive signed a data use agreement. Because no caregiver was contacted, individual consent was waived.

What This Account Does Not Yet Cover

Exclusions, coding decisions and analysis choices are recorded in the deviation record and data preparation note that follow. This account covers only how the data came to exist in the form analyzed.

References

Appelbaum, M., Cooper, H., Kline, R. B., Mayo-Wilson, E., Nezu, A. M., & Rao, S. M. (2018). Journal article reporting standards for quantitative research in psychology: The APA Publications and Communications Board task force report. American Psychologist, 73(1), 3-25. https://doi.org/10.1037/amp0000191

Bauer, T. N., Bodner, T., Erdogan, B., Truxillo, D. M., & Tucker, J. S. (2007). Newcomer adjustment during organizational socialization: A meta-analytic review of antecedents, outcomes, and methods. Journal of Applied Psychology, 92(3), 707-721. https://doi.org/10.1037/0021-9010.92.3.707

Newman, D. A. (2014). Missing data: Five practical guidelines. Organizational Research Methods, 17(4), 372-411. https://doi.org/10.1177/1094428114548590

DBAX 9103 Week 2 instructions, in plain terms

Week 2 asks you to write a procedure account of how your data were obtained and prepared for analysis, in the past tense. Explain why an account differs from a plan. Describe the setting and population. Present each data source in a table with who held it, what it contained, when you obtained it and in what form. Describe how records were linked and report every link that failed, with the reason and what you did. Explain how any key variable was identified or coded, including a reliability check if judgment was involved. Define the outcome. Report approvals and consent. State what the account does not cover and where those details appear.

How the DBAX 9103 Week 2 example is put together

The account opens by contrasting plans and accounts, citing Appelbaum and colleagues. A section describes the agency and its 612 hires. A table lists four sources with holders, contents, timing and format. A section reports linkage: three onboarding records recovered from paper and 14 check-in logs lost in a system change. A section explains the check-in coding rule and two readers' agreement on 186 of 200 entries. A section defines retention and the handling of transfers. A section explains studying every hire rather than a suggested list, citing Bauer and colleagues, and carrying missing logs forward, citing Newman. A section records approvals and waived consent. The table notes that names were removed before transfer, so readers know what the researcher could see.

Reading the DBAX 9103 Week 2 rubric

Faculty look for an account another researcher could follow to obtain the same data. A table of sources with holders and timing carries the most weight. Reporting every failed link, with its reason, shows honesty. A coding rule tested by two readers shows rigor. A clear outcome definition, including edge cases such as transfers, demonstrates care. Explaining why the full population was used shows attention to selection. Recording approvals shows ethical compliance. Accounts that restate the proposal in past tense without reporting what changed, omit failed links or leave coding rules vague receive lower marks. Stating when each file arrived, including delays, helps a reader judge whether timing affected the data. Approval details, kept brief, close the account properly.

Common DBAX 9103 Week 2 mistakes, and how to avoid them

Start from your proposal's method section and change every "will" to what actually happened, then look at each sentence you cannot change honestly. Those sentences are where your study departed from its plan. Record who gave you each file and when, because delays and partial files matter. Count matched and unmatched records at every link. If any variable depended on judgment, have someone else code a sample and report agreement. Many students write procedure accounts that read like polished plans, hiding the messy parts a reader most needs. Others bury the account in appendices. Write it plainly and early. Our writers can help you turn a plan into an honest account.

Get a DBAX 9103 Week 2 example written to your instructions

Attach the Week 2 prompt and its rubric, and describe your study's design in a few lines: who was approached, how, and over what period. A dated procedure account with its flow figure comes back in 24-48h, free for a first request. Dates and counts inside it belong to an invented survey, so what happened in your own fieldwork stays in your own notes.

More DBAX 9103 papers and DBA samples

DBAX 9103 Week 2 questions, answered

Where can I find a free DBAX 9103 Week 2 sample paper?

The procedure account, including its sources table, is reproduced below without a fee.

How many caregivers were hired in the DBAX 9103 Week 2 study?

612 over 24 months.

Why were 14 check-in logs missing?

They were lost when the scheduling system was replaced.

How was the check-in coding rule tested?

Two readers coded 200 entries independently and agreed on 186.

How were transfers to a sister company treated?

As separations, since they left the role studied.