How Step 4 Actually Works in the MRT Workbook
Step 4 is where most people lose points. It is the reconciliation phase, and the workbook treats it like a simple verification step when it is actually the step that catches every mistake you made in Steps 1 through 3. I spent two weeks last year dealing with a discrepancy in a logistics module where the numbers looked right on paper but the final tally refused to balance. The issue turned out to be that the workbook expects you to carry the adjusted variance from Step 3 forward with three decimal places, not two, and rounding early introduces a cascade error that shows up at Step 4. The method in step 4 requires you to cross-reference the calculated values against the provided benchmark table and flag any deviation above the tolerance threshold. You do not just confirm the answer matches. You document the difference, note whether it falls within the acceptable range defined in the workbook appendix, and write a one-line justification if it does not. The workbook answer key only shows the final number. It does not show the justification line, which is why students who skip that part lose partial credit even when their math is correct.
Examples Mrt Workbook Answers Step 4
Here is a realistic scenario from a recent cohort. The problem involved a maintenance scheduling module where three work orders had overlapping time windows. Step 1 asked for the total estimated hours. Step 2 required identifying the critical path. Step 3 was adjusting for shift handover downtime. Step 4 then asked for the reconciled schedule with variance notation. The provided answer shows a final adjusted total of 47.3 hours with a variance flag of +1.8. If you arrived at 47.3 but did not include the +1.8 notation, the automated grader marks it incomplete. I learned this the hard way after submitting the same numerical answer three times and getting different scores each time. The grading rubric weights the annotation at 30 percent of the step total. The number itself is only 70 percent. Another common case involves negative variance. When the actual resource consumption falls below the estimate, the workbook expects the variance to be recorded as a negative value in parentheses, not as a positive number with a "below estimate" label. I have seen people write (minus) or use a minus sign in the wrong column. The system reads those as data entry errors and zeroes out the entire step. Write it as (1.2) with the parentheses, placed in the designated variance field, and move on.
There is a counter-intuitive detail that the workbook never calls out directly. In certain scenarios, Step 4 requires you to ignore the smallest variance and focus on the largest single deviation. The instruction is buried in the methodology note on page 62 of the main text. If your step 3 produced five variance lines and one of them is more than double the others, the grader expects you to prioritize documenting that outlier first. The smaller variances get a summary line at the bottom instead of individual entries. I wasted about forty-five minutes on one assignment inputting every single variance in full detail when the rubric was looking for prioritized outlier documentation. Switching to the outlier-first format brought my score from 58 percent to 91 percent on that section alone. Here is a breakdown of how to approach a standard Step 4 problem without overcomplicating it. Pull your Step 3 output and place it next to the benchmark table. Compare each line item. Record the variance using the workbook's prescribed notation format. Flag anything outside the tolerance range. Add the outlier summary if needed. Double-check that your parentheses and decimal alignment match the example in the appendix exactly. Submit. The download link for the full answer key is located in the course resources section under the Materials tab. It is labeled MRT_Workbook_Answers_V3. You do not need it for Step 4 unless you are stuck on a specific anomaly case, because the key only covers the standard problems. The anomaly section in the workbook is intentionally unanswered so students can practice the exception handling logic. My workaround when I hit one of those was to create a small spreadsheet that mirrored the workbook's tolerance thresholds and ran a conditional formatting rule that highlighted any deviation beyond the specified range. This cut my checking time from about twenty minutes down to roughly three minutes per problem set.
Get the Full Details
Be aware that the workbook has a known limitation with mixed-unit problems. If your scenario combines hours and minutes with fractional day conversions, Step 4 can produce rounding mismatches depending on which cell your intermediate values are stored in. Excel and Google Sheets handle this differently, and the answer key assumes a specific rounding convention that is not stated in the instructions. The workaround is to convert everything to a single unit before you reach Step 3, then carry that single unit through to the final reconciliation. I switched to doing this after noticing my Step 4 results varied by up to 0.4 units depending on my spreadsheet software, which is enough to push a borderline variance into flagged territory. If you are working through this workbook and Step 4 is consistently eating your grade, the issue is rarely the arithmetic. It is almost always the documentation format, the tolerance notation, or the outlier prioritization rule. Fix those three things and your scores stabilize immediately. The workbook is straightforward once you stop treating it like a math test and start treating it like a compliance checklist. The answers are there. The catch is in the details between the numbers.
