| Course | MHRM 6101 Foundations of Human Resource Management |
|---|---|
| Week | Week 7 |
| Paper type | HRIS brief |
| Length | About 610 words, 5 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | MS in Human Resource Management |
| Updated | October 2026 |
Free sample paper for MHRM 6101 Week 7
Twelve Questions Leadership Asked and What Kestrel's HR Records Can Answer: An HRIS Brief Sorting Each Into Answerable Now, Answerable if Entered and Not Held
Student Name
Walden University
MHRM 6101: Foundations of Human Resource Management
Instructor Name
Month Day, Year
Twelve Questions Leadership Asked and What Kestrel's HR Records Can Answer: An HRIS Brief Sorting Each Into Answerable Now, Answerable if Entered and Not Held
The Question That Started This
Last quarter the chief executive asked why the Obetz night shift keeps losing operators. HR at Kestrel, the logistics firm in this course's composite case, could report how many had left but not why, which shift they had worked longest or who had supervised them. This brief takes that failure as a prompt to test the system against every workforce question leadership has asked in the past year.
The Inventory
Table 1
Leadership's Questions and What the HR System Can Answer
| Question asked | Status | |
|---|---|
| Headcount by site and job | Answerable now | |
| Payroll cost by site | Answerable now | |
| Average pay versus posted range | Answerable now | |
| Hires by month | Answerable now | |
| Turnover rate by site | Answerable now | |
| Turnover by shift | Answerable if entered: shift field blank for 40 percent of hourly records | |
| Reasons for leaving | Answerable if entered: separation reason blank on 58 percent of last year's terminations | |
| Time to fill an operator role | Answerable if entered: requisition open dates not recorded | |
| Training completed before working alone | Answerable if entered: certifications kept in site spreadsheets | |
| Turnover by supervisor | Not held: no supervisor field | |
| Overtime hours by employee before leaving | Not held: timekeeping not linked to HR records | |
| Agency workers by site and week | Not held: tracked only in agency invoices | |
Composite organization; field completion from a January audit.
What the Inventory Shows
The finding is lopsided. Everything finance and payroll depend on is complete: pay, positions, hire dates. Everything that explains why people leave is missing or partial. Five of the twelve questions can be answered today, four could be answered if existing fields were filled consistently and three need data the system does not hold.
That pattern matches what Angrave et al. (2016) observed across many organizations: HR systems tend to be built around transactions such as paying people, not around the questions managers ask about them. Marler and Boudreau (2017) found in their review that HR analytics depends first on reliable, connected data, and that many firms attempt analysis before that foundation is in place.
Separation Reasons Come First
The separation reason field is the single most valuable fix. It already exists, it costs nothing to fill and it is blank on more than half of last year's departures because site clerks process terminations and the field is optional. Making it required, with a short list of reasons such as pay, schedule, supervisor, commute, health and other, would begin answering the night-shift question within a quarter. Pairing it with a brief exit conversation by HR rather than the site clerk would make the recorded reasons more honest. Once reasons and shifts are recorded, Kestrel can also compare its quit rate with the monthly figures for transportation and warehousing in the monthly JOLTS release (Bureau of Labor Statistics, 2026), which would show whether the night shift's losses are unusual for the industry or simply typical of it.
Recommendations, in Order of Cost
First, make shift and separation reason required fields and audit completion monthly. Second, add a supervisor field, which the vendor can configure without new licensing. Third, connect timekeeping to HR records, which requires a vendor project and should be priced separately. Agency headcount can be logged weekly by site clerks in the meantime.
Limits
The question list comes from leadership's requests over one year and may miss questions nobody thought to ask. Completion figures come from a single audit and may have changed since January.
References
Angrave, D., Charlwood, A., Kirkpatrick, I., Lawrence, M., & Stuart, M. (2016). HR and analytics: Why HR is set to fail the big data challenge. Human Resource Management Journal, 26(1), 1-11. https://doi.org/10.1111/1748-8583.12090
Bureau of Labor Statistics. (2026). Job openings and labor turnover survey. U.S. Department of Labor. https://www.bls.gov/jlt/
Marler, J. H., & Boudreau, J. W. (2017). An evidence-based review of HR analytics. International Journal of Human Resource Management, 28(1), 3-26. https://doi.org/10.1080/09585192.2016.1244699
What the MHRM 6101 Week 7 instructions ask for
Week 7 asks you to evaluate an HR information system against the needs of the people who use its data. Start with a real question the system failed to answer. Build an inventory of the questions leaders actually ask, and mark whether each can be answered now, could be answered if existing fields were filled or needs data the system does not hold. Explain what the pattern shows. Focus on the single fix that would matter most, and order your recommendations by cost. Note the limits of your inventory and how current your data is. A single inventory table usually carries the analysis, with brief sections of interpretation and recommendation after it.
Inside the MHRM 6101 Week 7 example
The brief opens with the chief executive's night-shift question and HR's partial answer. The inventory table lists twelve questions with their status and the specific gap behind each. A section interprets the result: five answerable, four fixable by data entry and three needing new data, with Angrave and colleagues and Marler and Boudreau explaining the pattern. The longest section argues for making separation reasons required, with a short list of reasons and an HR exit conversation, and mentions comparing results with the federal turnover survey. Recommendations follow in order of cost, and a limits paragraph notes the single audit. Each status entry names the exact field or source responsible, so the reader can see what a fix would involve.
MHRM 6101 Week 7 rubric: what earns full marks
HRIS briefs are graded on whether the evaluation starts from users' needs. Organizing by questions leaders ask, rather than by system modules, earns credit. The three-way classification separating data entry problems from system problems shows analytical clarity and is weighted heavily. Interpretation supported by research adds depth. Prioritizing one fix, with reasons, demonstrates judgment. Recommendations ordered by cost are practical for executive readers. Limits should be acknowledged. Briefs that describe system features without testing them against real questions, or that recommend a new system without considering cheaper fixes, receive fewer points. Specific completion figures, even from one audit, carry more weight than a general complaint about poor data.
Common MHRM 6101 Week 7 mistakes, and how to avoid them
Collect the workforce questions your leaders have asked in the past year, from emails, meetings or reports. For each, check whether your HR records can answer it today. If not, ask whether the field exists but is empty, or whether the data is not kept at all. Sort the questions into those three groups. Then look for the one gap that blocks the most important question, and ask what it would take to close it. Many briefs jump to buying new software when filling an existing field would help more. If you have a list of questions, send it to us and we can help sort it. Two or three pages are usually enough for this brief.
Get a MHRM 6101 Week 7 example written to your instructions
Include the prompt and the rubric, and describe the records system or data scenario your section gives; the brief works from those questions and fields. First custom sample free, 24 to 48 hours. Its half-empty records belong to a fictional firm, and no employee data from your organization is wanted or used.
More MHRM 6101 papers and MS in Human Resource Management samples
- MHRM 6101 Week 1: HR Belief Discussion Post
- MHRM 6101 Week 2: HR Function Role Brief
- MHRM 6101 Week 3: Peak-Season Shortfall Case Memo
- MHRM 6101 Week 4: Freight Dispatcher Job Analysis
- MHRM 6101 Week 5: Supervisor Staffing Memo
- MHRM 6101 Week 6: Internal Posting Policy Draft
- MHRM 6101 Week 8: Selection Ethics Memo
- MHRM 6101 Week 9: Reporting Line Peer Reply
- MHRM 6101 Week 10: HR Structure Memo
- MHRM 6101 Week 11: HR Position Paper
MHRM 6101 Week 7 questions, answered
Where can I find a free MHRM 6101 Week 7 sample paper?
Read the twelve-question HRIS brief below for free.
What question started the MHRM 6101 Week 7 brief?
Why the night shift at one site keeps losing operators, which the records could not answer.
How are the questions sorted?
Answerable now, answerable if existing fields were filled, and not held by the system.
Which fix does the brief prioritize?
Making the separation reason field required, since it is blank on 58 percent of terminations.
What is the most expensive recommendation?
Connecting timekeeping to HR records, which needs a vendor project priced separately.