BUS 799 Module 6 Capstone Recommendations Example

Reviewed by Douglas Renshaw, MBA Aspen University Updated October 2026

This BUS 799 Module 6 sample paper turns capstone findings at Keystone Electric, a composite electrical subcontractor, into five recommendations that target the 21 days needed to cut receivables from 71 to 50. Aspen's MBA capstone asks for recommendations and a rollout plan in Module 6. A table ties each recommendation to the stage it addresses, the expected days recovered and a named owner: billing by the fifth day of each period with applications started for the managers, a document checklist for each customer, signed change orders before change work, faster closeout for retainage and a collections routine. The estimates come from the findings. On two pilot jobs, the gap before billing shrank from 11 days to 4 and none of the four applications bounced back. An implementation schedule follows, then a control plan drawn from Linderman's account of Six Sigma, what the plan leaves aside and risks.

CourseBUS 799 Graduate Capstone
ModuleModule 6
Paper typeCapstone recommendations
LengthAbout 1,010 words, 6 pages
FormatAPA 7 student paper
SchoolAspen University
ProgramMBA
UpdatedOctober 2026

Free sample paper for BUS 799 Module 6

1

Twenty-One Days Back: Five Recommendations, a Pilot, and a Control Plan for Faster Collections

Student Name

Master of Business Administration Program, Aspen University

BUS 799: Graduate Capstone

Instructor Name

Month Day, Year

What this page is doingThe title states the target in days and the three parts of the section, which tells the owners what they are being asked to approve. APA 7 student title page; the company and figures are composite.
2

Twenty-One Days Back: Five Recommendations, a Pilot, and a Control Plan for Faster Collections

The current-state analysis showed that Keystone Electric, a composite electrical subcontractor, loses about 19 of its 71 receivable days to its own billing practices, with several more recoverable through faster closeout and complete submissions. This section presents five recommendations, estimates the days each should recover, reports early results from a two-project pilot, sets out the implementation schedule, and describes how the gains will be sustained.

What this page is doingThe introduction connects the recommendations to the findings and previews the section's structure.
3

Recommendations

Table 1 lists the recommendations with the stage each addresses, the expected reduction in days, and the person responsible.

RecommendationStage addressedExpected days recoveredOwner
1. Billing cutoff: quantities due two business days after period end, application submitted by day five, with billing staff pre-filling from the schedule of valuesBilling lag, 12 days8Controller
2. Customer-specific document checklist, with lien waivers requested at the start of each period rather than at submissionRejections, 3.5 days; review, 18 days4.5Billing lead
3. No change work without a signed change order or written directive, and a weekly review of the open change logUnsigned change orders, 3.5 days2.5Operations manager
4. Closeout package started when a project reaches 75 percent completeRetainage, 12 days4Project managers
5. Collections calls when payment is five days past due, and enrollment of customers in electronic paymentPayment after approval, 22 days2Accounts receivable clerk
Total21
What this page is doingEach recommendation is tied to a measured stage, an estimated effect and a named owner, so the plan adds up to the target and is accountable.
4

Why These Estimates

The estimates are grounded in the findings. A day-five submission would reduce average billing lag from 12 days to about 4, recovering 8. Complete applications, the largest customer's accounts payable specialist explained, are approved in the first review batch rather than waiting about two weeks for the next, so reducing rejections should shorten review time as well as removing rejection delays, for about 4.5 days combined. The change order rule addresses the third most common cause of late invoices. Starting closeout early should release retainage sooner, though the estimate of 4 days is conservative because general contractors control final release. Collections follow-up offers the smallest gain, since payment after approval depends largely on general contractors' own receipts. Two-thirds of the target comes from the first two recommendations, which are entirely within Keystone's control.

What this page is doingEach estimate is justified from the findings, uncertainty is acknowledged, and the highlighted sentence shows where confidence in the plan is highest.
5

Pilot Results

Recommendations 1 and 2 were piloted on two projects for two billing cycles. On those projects, the billing lag fell from an average of 11 days in the prior six months to 4 days, and all four applications submitted were approved without rejection, compared with roughly one in four rejected historically for these projects. Project managers reported that confirming pre-filled quantities took about 30 minutes, compared with two to three hours of assembling applications before. The pilot is small and short, so it shows feasibility rather than proving the full effect, but it met its prediction and produced the early win the change plan needed.

What this page is doingPilot results are reported with their baseline and honest limits, and they are connected to the change plan's need for early wins.
6

Implementation Schedule

Months one and two: complete the pilot, finalize the checklist for each of the five largest customers, and train project managers and billing staff. Months three and four: apply the billing cutoff and checklist to all active projects, beginning with the largest general contractor, which accounts for 38 percent of revenue and the most rejections. Month four: introduce the change order rule, with a short training session for field foremen. Months five through twelve: begin closeout packages on each project as it reaches 75 percent completion, and phase in the collections routine and electronic payment enrollment. The owners will review progress monthly.

What this page is doingThe schedule sequences changes by ease and impact, starting where the data showed the greatest concentration of problems.
7

Control Plan

Linderman et al. (2003) emphasized that Six Sigma's results depend on specific goals pursued through structured methods; the control phase keeps those goals visible after the project ends. Keystone will adopt a one-page monthly dashboard showing days sales outstanding and each of its six components, the share of applications submitted by day five, the rejection rate, the value of unsigned change orders, and retainage older than 90 days. Each measure will have an owner and a target. If days sales outstanding rises above 55 for two consecutive months, the controller will convene the change group to find the cause. To anchor the changes in routine, as Kotter (1995) urged, the billing cutoff will be written into project manager job expectations and discussed in performance reviews.

What this page is doingThe control plan specifies measures, owners, a trigger for action and a way to anchor the change, closing the DMAIC cycle.
8

What the Plan Does Not Address

The recommendations deliberately leave aside the largest single component, the 22 days between approval and payment, beyond a modest collections routine. That time depends on general contractors' payment terms and on whether owners have paid them, and construction payment research identifies the financial strength of other parties as central to payment problems (Ramachandra & Rotimi, 2015). Keystone can influence it only over the longer term, through choices the owners make before signing work: checking a general contractor's payment history and financial condition during bidding, negotiating payment terms and retainage rates, and in some cases declining work from customers who pay slowly. The capstone recommends that the owners add a short payment-history review to the bid decision, but treats contract strategy as outside the project's scope, as set in the proposal. Naming this gap matters because the owners should not expect the plan to fix a problem it was not designed to fix.

What this page is doingExplicitly naming what the plan leaves out, with evidence for why, keeps expectations honest and points to a longer-term decision for the owners.
9

Risks

The main risks are project managers reverting to late billing during busy periods, general contractors resisting the change order rule on fast-moving jobs, and the largest customer changing its documentation requirements. The dashboard will reveal the first risk quickly. For the second, the rule allows a written directive by email when a signed change order is impractical. For the third, the billing lead will review each customer's requirements quarterly.

What this page is doingRisks are specific to the recommendations and each has a response.
10

Conclusion

Five recommendations, each tied to a measured stage and a named owner, together target the 21 days Keystone needs to reach 50. The first two, a billing cutoff and a document checklist, account for most of the expected gain and have already worked on two pilot projects. A monthly dashboard with clear triggers will keep the gains in place. The next section estimates the financial return of the plan.

What this page is doingThe conclusion summarizes the plan, the evidence from the pilot and the handoff to the financial justification.
11

References

Kotter, J. P. (1995). Leading change: Why transformation efforts fail. Harvard Business Review, 73(2), 59-67.

Linderman, K., Schroeder, R. G., Zaheer, S., & Choo, A. S. (2003). Six Sigma: A goal-theoretic perspective. Journal of Operations Management, 21(2), 193-203. https://doi.org/10.1016/S0272-6963(02)00087-6

Ramachandra, T., & Rotimi, J. O. B. (2015). Causes of payment problems in the New Zealand construction industry. Construction Economics and Building, 15(1), 43-55. https://doi.org/10.5130/ajceb.v15i1.4214

What the BUS 799 Module 6 instructions ask for

Module 6 of Aspen's BUS 799 usually asks for recommendations and an implementation plan based on your findings. Tie each recommendation to a specific finding and stage. Estimate its effect and explain the basis. Name an owner for each. Pilot the most important changes if possible and report results. Give an implementation schedule by month. Set a control plan so gains last, with measures, triggers and owners. Say what the plan does not address and why. Name risks with responses. Keep the organization composite, and make sure the expected gains add up to the target, since owners will check whether the plan actually closes the gap.

How the BUS 799 Module 6 example is put together

The introduction restates the gap between 71 and 50 days. A table lists the five recommendations with stages, expected days and owners. The estimates section explains how each figure comes from the findings, such as reducing billing lag from 12 to about 4 days. The pilot section reports results on two projects over two billing cycles. The schedule section phases the cutoff and checklist first, then the change order rule, closeout and collections. The control section sets a one-page monthly dashboard and a trigger when days outstanding stay above 55. The scope section explains why the 22 days after approval are left mostly aside. The risks section covers project managers slipping back and customer pushback, and the conclusion summarizes the plan.

BUS 799 Module 6 rubric: what earns full marks

Recommendation papers in BUS 799 earn the most credit for recommendations tied to findings, grounded estimates, named owners, pilot evidence, a realistic schedule and a control plan. This example earns marks by piloting the two largest recommendations before asking for full adoption, which gives graders evidence rather than projection. Linderman and colleagues' 2003 article supports the control phase and the use of specific goals. The estimates rest on the measured stages from the findings, and the plan states plainly that the largest component depends on customers' payment terms. That honesty about scope shows judgment. A dashboard with a trigger and an owner shows the student expects gains to fade without control.

BUS 799 Module 6 help from the desk

Recommendation papers often list ideas without linking them to findings. Tie each to a stage. Another common gap is estimates with no basis; explain the arithmetic. Students also skip owners. Name one person per recommendation. Pilot if you can. Phase the schedule. Set a control plan with a trigger. Say what you are not addressing. Name risks. Check that gains add up to the target. Keep the organization composite. Avoid recommending software as the whole answer; tools help only when the habit changes too. Finally, report pilot results honestly even when small, since two projects over two cycles are evidence of direction, not proof of the full effect.

Write yours, or have the desk draft it

This paper is an original model document written by our desk, not a submitted student paper and not an official Aspen University document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.

More BUS 799 and MBA sample papers

BUS 799 Module 6 questions, answered

What does BUS 799 Module 6 usually ask for?

Work in this part of a graduate business capstone typically asks for recommendations and an implementation plan based on your findings. Aspen does not publish module deliverables, so your classroom's instructions govern.

How do I make capstone recommendations credible?

Tie each recommendation to a specific finding, estimate its effect with reasoning, name an owner and a start date, and test the most important ones on a small scale if possible.

What is a control plan?

The final phase of a DMAIC project, which defines the measures, owners, targets and triggers that keep an improvement in place after the project team moves on.

Where can I find a free BUS 799 Module 6 sample paper?

The full BUS 799 Module 6 paper is above, five recommendations, a pilot and a control plan to cut a contractor's receivables from 71 to 50 days.

What does the BUS 799 Module 6 plan leave out?

The 22 days between approval and payment, which depend on customers' terms and finances. The plan suggests checking a general contractor's payment history at bid time instead.