| Course | MT497 Bachelor's Capstone in Organizational Management |
|---|---|
| Unit | Unit 10 |
| Paper type | Consulting report |
| Length | About 1,270 words, 7 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | BS in Business Administration |
| Updated | October 2026 |
Free sample paper for MT497 Unit 10
Approve a Six-Week Pilot: An MT497 Unit 10 Consulting Report to Caldwell Run's Director and Board
[Student Name]
Purdue University Global
MT497: Bachelor's Capstone in Organizational Management
Unit 10 Consulting Report
[Instructor Name]
[Date]
Caldwell Run, its staff, board and every figure are composite; the sources cited are real.
Summary for the Board
Decision requested: approve a six-week pilot of three changes to how dogs move from the kennel to adoption, with a review at the end of week six.
Why: dogs now stay an average of 19 days, up from 11 two years ago, and seven were returned in the last quarter for behavior their adopters had not been told about. In every one of those seven cases the shelter had written down the behavior before the adoption. The information existed; it never reached the counselor choosing the new home.
What changes: behavior notes move from a separate spreadsheet into the shelter software, where every desk can see them and a dog cannot be listed without them; a fifteen-minute morning meeting of three leads decides when each dog is ready; and the two department managers review dog length of stay and returns together every week.
Cost: staff time only, about one hour of training per person and fifteen minutes a day for three people. No new positions.
How the board will know: four figures reported weekly, with targets at week six of 16 days average stay, no more than two behavior returns, behavior notes on 95 percent of listings, and 70 percent of staff able to say who makes the readiness call.
The Engagement
The study ran over one term with the director's written permission. It examined dogs only, from intake to the thirty days after adoption. Fifteen staff and two volunteers were interviewed, 31 of 38 invited staff answered an anonymous survey, two years of shelter records were reviewed and two weekday mornings were observed. The author works weekend shifts as an adoption counselor, so a second interviewer spoke with adoption staff, and the author interviewed nobody from their own shift. Details of every method are in the appendices.
What the Study Found
The findings are organized under the seven headings of the framework used for the diagnosis (Waterman et al., 1980), described here in plain terms.
The board's goal. Two years ago the board committed the shelter to sending nine dogs in ten out alive. Staff in both departments are proud of it, and it has increased the pace and the stakes of every placement.
How the teams are organized. The two teams answer to separate managers, and intake surges wiped out half of those managers' monthly meetings last year. Below manager level, no one from the two teams can settle together that a dog should go up for adoption.
Where information lives. Kennel and behavior staff write behavior notes promptly, most within a day of an assessment, but into a spreadsheet the adoption computers cannot open. The software used to post a dog for adoption never prompts for behavior information before listing.
How leaders work. Both managers are respected and hard-working. Each spends most of the day in their own department, and staff take problems to their own manager rather than across.
The people. Kennel attendant turnover is high, about 52 percent last year, and departing staff cite workload and the emotional weight of shelter work. New attendants still write detailed notes.
What staff do well. Notes are specific and useful, and counselors read them carefully when they can find them. Training is not the gap.
What staff believe. Nearly all staff in both departments hold two values: finding every adoptable dog a home, and giving every adopter an honest account of the dog. Most also feel the shelter rewards placements more than honesty with adopters.
Staff described their frustration truthfully; the cause simply sat somewhere other than where they looked.
Returning the Presenting Problem
Leadership asked for help because adoption and animal care did not seem to communicate. That description fits what staff on both sides feel, and it should not be dismissed. But the evidence places the cause in arrangements rather than in people. When the board raised the placement goal, the work of the two teams became more tightly linked, and nothing was added to link them: the notes stayed in a separate file, listing stayed a one-department decision, and the managers' meeting stayed monthly. Both teams have been doing their part well, and the handoff between them has been left to chance. Schein (1999) describes the consultant's task as helping a client see its situation more clearly, not assigning blame, and the report offers this finding in that spirit.
The Three Changes
Notes inside each dog's record. Kennel leads and the behavior coordinator enter notes in the software's existing behavior field, and a dog cannot be marked available until it is complete. The spreadsheet becomes read-only and is retired after the pilot.
A morning decision. At 9:30 each weekday, the kennel lead, behavior coordinator and adoption lead meet for fifteen minutes. Each has a defined decision: assessment complete, dog physically ready, dog listable. If anyone objects, the dog waits a day; a repeat objection is settled by the managers.
One number for two managers. A weekly thirty-minute review of length of stay and thirty-day returns replaces the monthly meeting, so each manager answers for the whole path, not half of it.
A communication workshop, the remedy first requested, is held in reserve. The study found skills and working relationships largely sound, so a workshop now would improve what already works. It can be revisited if friction continues after the pilot.
Managing the Change
Every group gives something up. Counselors no longer list dogs alone, yet they still choose the family each dog goes home with. Kennel leads gain a daily meeting during a busy hour, which is protected on the schedule. Volunteers fear the behavior field will label favorite dogs, so it will include a line for positive notes and volunteers will join one meeting a week. The two managers will introduce the pilot together at every shift change, so no team hears about it second-hand, and a short weekly note will report the four figures and one problem being fixed.
Changes Since Earlier Work
Two changes since the midpoint of the study are flagged. After a classmate pointed out that five of the first seven interviews came from the author's own team, three kennel interviews were added and the behavior spreadsheet's edit history was examined, which moved the diagnosis from late note writing to notes that could not be seen. And the shared weekly measure now includes thirty-day returns as well as length of stay, so that faster placement is never rewarded at the cost of honesty with adopters.
Limits
The survey had 31 responses and no earlier baseline, so it shows the present only. Two invited kennel attendants declined interviews, leaving the kennel side's evidence thinner. The author works adoption shifts, and although the key finding rests on records and a test of computer access rather than on interviews, readers should weigh that role. Finally, the report makes no claim that the shelter has adopted or will adopt any recommendation; it asks only for a pilot and a review.
Appendices
Appendix A holds the interview guide, Appendix B the survey, Appendix C anonymized summaries of survey results for groups of five or more, Appendix D the 7S evidence matrix, and Appendix E the consent script. Block (2011) recommends that a consultant's report leave the client with everything needed to check its conclusions, and the appendices are assembled for that purpose.
References
Block, P. (2011). Flawless consulting: A guide to getting your expertise used (3rd ed.). Pfeiffer.
Schein, E. H. (1999). Process consultation revisited: Building the helping relationship. Addison-Wesley.
Waterman, R. H., Jr., Peters, T. J., & Phillips, J. R. (1980). Structure is not organization. Business Horizons, 23(3), 14-26. https://doi.org/10.1016/0007-6813(80)90027-0
MT497 Unit 10 instructions, in plain terms
The final MT497 unit asks you to deliver diagnosis and intervention to leadership as one report. Open with an executive summary that requests a specific decision and gives its reason, cost and the measures leadership will see. Describe the engagement briefly, including methods and your own role. Present findings in plain language organized by your model, keeping technical vocabulary to headings and appendices. Return the presenting problem respectfully, explaining what it got right and where the cause actually lies. Condense the intervention and change plan rather than repeating them, and flag changes made since earlier units. State limits before the appendices. Write for leaders who may read only the first page, and do not claim the organization has adopted anything.
Inside the MT497 Unit 10 example
The report begins with a board summary covering the decision, the reason, the three changes, staff time cost and four week six targets. A short engagement section describes scope, interviews, survey, records, observation and the second interviewer. Findings run under seven plain headings, from the board's goal to what staff believe, with a highlighted line that frustration was described truthfully while the cause sat elsewhere. A section returns the presenting problem without blame, citing Schein. The three changes and the held workshop are condensed, followed by a paragraph on managing each group's loss. Changes since the seminar are flagged, limits are named, and the appendices are listed with Block's advice on leaving the client able to check the conclusions.
Where the points sit in the MT497 Unit 10 rubric
Coherence across the whole engagement usually carries the most weight: evidence leading to a diagnosis, a diagnosis leading to a change aimed at the level it identified, and a change plan with measures. Reports that paste earlier units together, repeating contradictions or abandoned claims, tend to lose credit throughout. An executive summary that requests a specific decision is expected, and writing for leadership rather than for the instructor shows professional judgment. Plain language earns credit where model vocabulary would obscure the argument. Respectful handling of the presenting problem matters, since a report that blames a team rarely gets implemented. Flagged revisions, stated limits and complete appendices, with APA references, round out what instructors look for.
MT497 Unit 10 help from the desk
The most damaging weakness is a report that reads like a course portfolio, with each unit's paper pasted in order and the decision hidden near the end. Another is model jargon throughout, which leaves a board unable to follow the argument. Students sometimes overclaim, writing that the organization has adopted the changes when it has only heard about them. Limits are often dropped from the final version for fear they weaken it, though they usually strengthen trust. Inconsistent figures between the summary and the body are common and easy to catch. Before submitting, hand your first page alone to a friend and ask whether it tells a director what to decide, then check every number on that page against the sections that follow.
Get an MT497 Unit 10 example written to your instructions
Assembling the report your organization's leadership will read? Send the units you have written so far, any comments your instructor made, and the Unit 10 report requirements with the rubric. We write it in leadership's language, keep every individual unidentifiable, frame the decision clearly and state its limits; there is no fee for a first request, and it is ready in 24-48h. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More MT497 papers and BS in Business Administration samples
- MT497 Unit 1: Complaint Diagnosis Board Post
- MT497 Unit 2: Access and Scope Proposal
- MT497 Unit 3: Coordination and Shelter Strain Review
- MT497 Unit 4: 7S Diagnostic Model Rationale
- MT497 Unit 5: 7S Data Collection Plan
- MT497 Unit 6: Lopsided Evidence Seminar Reflection
- MT497 Unit 7: 7S Organizational Diagnosis
- MT497 Unit 8: Systems Intervention Design
- MT497 Unit 9: Pilot Change Management Plan
- MT494 Unit 10: Weekday Group Events Marketing Plan
- MT483 Unit 10: Investment Policy Proposal
- LI410 Unit 10: Leadership Development Plan
- MT482 Unit 10: Equity Valuation Recommendation Report
MT497 Unit 10 questions, answered
Who is the audience for the Unit 10 report?
Typically the organization's leadership, even though your instructor grades it. Write so a director or board member could understand it without course background: plain language, a clear decision on the first page and model terminology kept to a minimum. Your instructor will look for evidence that you can communicate with a real client.
Should I share the report with the organization?
That depends on your agreement with them and your instructor's guidance. Many students offer leadership a copy as thanks for access. If you do, check that nothing could identify an interviewee, and make clear the recommendations are yours rather than decisions the organization has made. A short cover note explaining the report's purpose can help.
How much of the earlier units should the report repeat?
Condense rather than repeat. The report should carry the essential evidence, diagnosis, intervention and change plan in a form leadership can read quickly, with full instruments and detailed tables in appendices. Note where you revised earlier conclusions, since that shows the engagement developed over the term. Leadership rarely reads appendices, so the body must stand alone.
Where can I find a free MT497 Unit 10 sample paper?
The full MT497 Unit 10 consulting report is on this page, asking a composite animal shelter's board to approve a six-week pilot and presenting findings in plain language.
Does the MT497 Unit 10 sample claim the shelter adopted the changes?
No. It requests approval for a pilot with a review at week six and states that it makes no claim about what the shelter has adopted or will adopt.