Four outputs, each with its receiver and a tolerance, are set out in a returns center's GB560 Unit 2 process requirements memo, which also flags two that conflict. Searches like "gb 560 unit 2 assignment example", "gb560 unit 2 sample" and "gb560 unit 2 example" land here.
What a finished GB560 Unit 2 process requirements memo looks like
Three pages, give or take, centered on a requirements table. The heading addresses the operations director and gives the subject as the returns process's required outputs. The table has four rows. A refund posted to the shopper's original payment within three business days of dock receipt for 95 percent of returns, correct to the cent for 99.5 percent. A-grade units available to sell within 48 hours, also for 95 percent. Vendor defect claims assembled for finance within ten days. Units priced above 400 dollars checked by loss prevention before any refund posts. Each row names the receiver, the measure, the tolerance and how it would be counted. A conflict section explains that the first and fourth rows cannot both be met by one sequence, and asks the director to rank them.
How a GB560 Unit 2 example is structured
The memo moves from output to receiver to tolerance, and never to solutions. Purpose comes first: agree what the process must produce before measuring how it currently performs. Next comes the table, each row written so that it could be tested with data: a stated measure, a threshold, the population it applies to and the source of the count. A short paragraph below the table explains where each tolerance came from, whether a published refund promise, the planner's replenishment cycle or the vendor agreement's claim window. The conflict section then isolates the tension between fast refunds and loss checks on high-value units. The memo closes by listing what it deliberately leaves out, such as speed targets for grading, because no receiver has asked for them, and it requests a decision by a named date.
Outputs, not activities
Each requirement describes something a receiver gets, a posted refund or a sellable unit, rather than a task the returns staff perform during a shift.
A tolerance on every row
Ninety-five percent within three business days, 99.5 percent to the cent, 48 hours to stock and ten days for claims give every output a threshold.
Where each figure came from
The website's refund promise, the planner's replenishment cycle and the vendor agreement's claim window are cited as the sources of the three time limits.
Two rows that collide
Checking every unit above 400 dollars before refunding slows the refund row, and the memo asks the director to rank the two by a set date.
What is left out, and why
Grading speed and dock throughput are omitted because no receiver needs them, a choice the memo states outright rather than leaving to inference.
Where marks go in GB560 Unit 2
Requirements that describe activities, receive returns promptly or process refunds efficiently, are the weakness graders flag first here, since none of them can be counted. A tolerance missing from any row leaves that requirement open to whatever the writer later wants it to mean. Memos that jump to a redesign before the requirements are settled answer the wrong unit. Sources for the thresholds matter in most sections: a three-day refund limit with no origin looks invented. Conflicts left unstated suggest the writer never tested the requirements against each other, and they tend to surface later as design problems. Business memo form counts here as well, so a heading that names no reader, or a subject line announcing only a topic, costs presentation marks.
Get a GB560 Unit 2 example written to your instructions
Send the process your section follows through the term, whatever you know about its receivers, and the Unit 2 prompt with its rubric. Expect a memo with outputs named, a tolerance and source for each, and any conflicts between requirements set out for a decision. Initial custom samples are free and typically ready in 24-48h.
GB560 Unit 2 questions, answered
How exact should a tolerance be?
Exact enough that two people counting the same data would reach the same verdict. A refund within three business days of dock receipt, for 95 percent of returns, meets that test; refunds processed quickly does not. The sample states the measure, the threshold, the population and the source for each row, which is usually what the rubric means by measurable.
What if nobody has written the requirements down?
That is common, and the memo then reconstructs them from evidence: published promises to customers, service agreements with vendors, and what downstream teams actually complain about. The sample's inventory requirement came from the planner's replenishment cycle rather than from any document. Stating where each figure came from keeps a reconstructed requirement credible to the manager reading it.
Should the memo recommend which conflicting requirement wins?
It can suggest a ranking, but the decision usually belongs to the manager the memo addresses. The sample lays out the tradeoff between fast refunds and loss checks on expensive units, estimates what each costs, and asks the director to decide by a date. Some prompts want the writer's recommendation stated; the custom version follows yours.