Warehouse Process Design and WMS Execution

Introduction

A warehouse is not merely a building in which inventory is stored. It is an operating system that converts inbound supply into reliable outbound service. Warehouse Management Systems (WMS) provide the transaction control, data visibility, decision rules and task coordination needed to execute this conversion. Transportation Management Systems (TMS) extend control beyond the warehouse by planning, tendering, monitoring and settling transportation movements. The quality of a WMS implementation therefore depends less on software features alone than on the quality of the processes, master data, rules and governance embedded in the system.

Warehouse process design determines how physical work and information work are connected. A receiving transaction should create an accurate inventory record; a put-away task should direct stock to a suitable location; a replenishment task should prevent picking shortages; and dispatch confirmation should provide a reliable handoff to the carrier and TMS. Poorly designed processes generate hidden queues, inventory inaccuracies, unnecessary travel, congestion, avoidable touches and service failures.

This chapter examines the design and execution of receiving, inspection, put-away, replenishment, storage, picking, packing, staging, dispatch, cross-docking, returns and cycle-counting processes. Particular attention is given to rules, task interleaving and exception management.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Design an end-to-end warehouse process architecture and distinguish physical, information and control flows.
2. Configure appropriate WMS rules for receiving, slotting, put-away, replenishment, picking, packing and dispatch.
3. Explain task interleaving and evaluate its operational benefits and risks.
4. Design cross-docking, returns and cycle-counting processes.
5. Develop performance measures and exception-management controls.
6. Assess the relationship between WMS execution, TMS planning, governance, data quality and managerial decision-making.

1. The Warehouse as a Controlled Flow System

A WMS coordinates three interacting flows:

• Material flow: goods, containers, pallets, totes and parcels moving through the facility.
• Information flow: advance shipping notices, purchase orders, sales orders, inventory records, status messages and shipment documentation.
• Decision flow: rules and priorities that determine what should be done, by whom, where and when.

The basic process chain is:

Inbound planning → receiving → inspection → put-away or cross-dock → storage → replenishment → picking → packing → staging → dispatch → inventory and transport confirmation.

This chain is not always linear. Returns may enter from the customer side, urgent orders may bypass normal waves, and cross-docked products may move directly from receiving to outbound staging. Process design must therefore define both the normal route and authorized alternatives.

A useful design principle is one physical event, one accountable system event. When a pallet is received, the WMS should record what was received, when, against which document, in what condition and under whose authority. When a carton is loaded, the system should record the shipment, carrier, vehicle or load, operator and time. This traceability supports inventory accuracy, customer service, financial control and regulatory compliance.

1.1 Process states and inventory ownership

The WMS should distinguish operational states such as expected, received, under inspection, available, allocated, picked, packed, staged, loaded, damaged, quarantined and returned. Treating all physically present stock as available stock is a major control failure. Inventory status should represent both physical condition and business usability.

Ownership is equally important. Vendor-owned, customer-owned, bonded, consignment and company-owned inventory may occupy the same building but require different accounting, access and release rules. Location, lot, serial number, status and ownership are therefore core dimensions of inventory identity.

1.2 Master data as a process prerequisite

Execution rules depend on reliable master data. Important fields include item dimensions and weight, unit-of-measure hierarchy, barcode standards, storage constraints, lot and serial requirements, shelf life, hazardous-material classification, temperature requirements, replenishment parameters, supplier and customer identifiers, carrier services and location capacities.

If a case is recorded as 12 eaches but physically contains 10, the resulting errors propagate through receiving, picking, replenishment, inventory valuation and transport planning. Data governance should include ownership, validation, version control, periodic review and a process for correcting errors without destroying audit history.

2. Receiving and Inspection Design

Receiving begins before the truck arrives. Appointment scheduling, advance shipping notices (ASNs), dock planning and expected-receipt records allow the WMS to prepare labor and space. An ASN normally includes supplier, shipment, purchase order, item, quantity, packaging, lot or serial information and estimated arrival.

At the dock, the receiving process should establish:

1. the identity of the vehicle and shipment;
2. the physical condition of the load;
3. the quantity and unit of measure received;
4. discrepancies against the expected receipt;
5. quality, regulatory or documentation status; and
6. the next authorized disposition.

A robust receiving sequence is:

Appointment and ASN validation → dock assignment → unload → scan or count → discrepancy recording → inspection decision → labeling and license-plate creation → put-away, quarantine or cross-dock.

A license plate is a system identity for a pallet, carton, tote or other handling unit. It permits the WMS to control a group of items as a unit while retaining item, lot, serial and quantity detail.

Inspection strategies

Inspection may be performed through:

• Blind receiving, in which the operator counts without seeing the expected quantity, reducing confirmation bias.
• Directed sampling, where a statistically or contractually defined sample is inspected.
• 100 percent inspection, used for high-risk, regulated, fragile or high-value items.
• Exception inspection, where only damaged, unexpected or suspicious goods are examined.

The appropriate method depends on risk, supplier performance, product characteristics, legal requirements and the cost of inspection. A WMS should support quarantine locations and blocked inventory statuses rather than forcing uncertain goods into available stock.

Receiving discrepancies may include overages, shortages, substitutions, damage, incorrect lot dates, unapproved packaging and missing documentation. The system should distinguish a physical discrepancy from an administrative discrepancy. For example, a supplier may ship the correct quantity under an incorrect purchase-order line. Resolution may involve approval, rejection, supplier claim, adjustment or rework.

3. Put-Away, Slotting and Storage

Put-away is the assignment and movement of received inventory to a storage or processing location. A WMS put-away rule generally considers item characteristics, location capacity, compatibility, velocity, order demand, ownership, lot controls, temperature, hazardous-material restrictions and travel distance.

Common put-away strategies include:

• Fixed location: each SKU has a designated location. This simplifies recognition but can waste space.
• Random or dynamic location: the system assigns any suitable location. This improves utilization but requires accurate scanning and location control.
• Class-based storage: fast movers are placed near picking and dispatch areas, while slow movers are stored farther away.
• Dedicated environmental storage: items are assigned according to temperature, security, hazard or regulatory requirements.
• Demand-directed put-away: goods needed for urgent or imminent orders receive priority locations.

Location suitability is a constraint problem. A candidate location must satisfy requirements such as size, weight capacity, item compatibility, access method and status. The best location is not necessarily the nearest empty location; it is the best feasible location under current and anticipated demand.

Slotting is the strategic assignment of products to locations. A basic slotting analysis examines demand frequency, units per order, cube, weight, handling characteristics, co-pick relationships and replenishment burden. Fast movers may be placed at ergonomic waist-to-shoulder levels, but velocity alone is insufficient. A bulky slow mover may consume more capacity and handling effort than a small fast mover.

Storage design should distinguish reserve storage from forward pick storage. Reserve locations hold larger quantities; forward locations support efficient picking. The WMS must maintain a relationship between the two and trigger replenishment before the forward location becomes unavailable.

4. Replenishment and Inventory Availability

Replenishment moves inventory from reserve or another source location to a forward pick location. It may be:

• Min–max replenishment: triggered when stock falls below a minimum and replenished toward a maximum.
• Demand-based replenishment: created from allocated or released orders.
• Top-off replenishment: performed during low-activity periods to restore forward locations.
• Emergency replenishment: created when a picker encounters insufficient stock.
• Opportunistic replenishment: performed when a worker passes a suitable location with available stock.

For a simple min–max policy, the replenishment quantity can be represented as:

where Q_r is the replenishment quantity in the defined unit of measure, M is the target maximum quantity and P is the projected quantity in the forward location. The equation assumes that capacity, reserve availability, unit conversions and allocations have already been considered. In practice, the WMS may cap Q_r by location capacity, pallet or case multiples, and available reserve stock.

Projected quantity should not be confused with physical quantity. A useful operational representation is:

where O is on-hand quantity in the forward location, I is confirmed inbound replenishment, A is allocated or committed quantity, and R is reserved or blocked quantity. The exact definition must be standardized because different systems treat allocations and reservations differently.

Replenishment rules should protect picking continuity without creating excessive travel or congestion. A WMS can prioritize by order due time, shortage risk, wave priority, route or customer service level. It should also prevent two operators from being assigned the same stock unless the system supports controlled parallel execution.

5. Picking, Task Interleaving and Work Release

Picking is often the largest source of warehouse labor and travel. The WMS may select among discrete, batch, zone, cluster, wave, cart, pallet and goods-to-person methods.

• Discrete picking: one order at a time; simple and traceable but potentially travel-intensive.
• Batch picking: several orders are picked together and later sorted; efficient for common items.
• Zone picking: each worker serves a zone; orders move between zones or are consolidated.
• Cluster picking: one trip serves multiple orders using separately identified containers.
• Wave picking: work is released in planned groups according to cut-off times, routes or capacity.
• Waveless or continuous release: tasks are released dynamically as capacity and priorities change.

The correct method depends on order profile, SKU count, order-line density, service requirements, equipment, labor skills and physical layout. A method that minimizes walking may increase sorting, consolidation or verification work.

Task interleaving

Task interleaving assigns a logically compatible next task to a worker who would otherwise travel empty. For example, a forklift operator delivering a pallet to a forward pick area may receive a put-away or retrieval task near the return path. The WMS evaluates worker skill, equipment, location, task priority, safety restrictions and timing.

Interleaving can reduce empty travel, but it should not be treated as an automatic optimization. Excessive switching may increase cognitive load, delay urgent work or cause equipment conflicts. Interleaving rules should therefore include:

• compatibility between equipment and task;
• maximum travel or detour limits;
• priority and due-time constraints;
• congestion and aisle restrictions;
• worker authorization and training;
• product and handling-unit compatibility; and
• rules for abandoning or escalating a task.

Picking accuracy and verification

Accuracy controls include scan validation, check digits, weight verification, image recognition, pick-to-light, voice direction and independent audit. Technology does not replace process discipline. Barcodes must be readable, locations must be correctly labeled, unit-of-measure conversions must be controlled and exception paths must be easy to use.

A picker should not be forced to confirm a quantity that was not physically found. Short picks require a defined workflow: recount, search, check adjacent locations, inspect inventory status, trigger replenishment or substitution if authorized, and report the final disposition.

6. Packing, Staging and Dispatch

Packing transforms picked goods into a shipment that can survive handling and can be identified throughout transportation. The WMS or an integrated packing system should determine packaging type, combine eligible order lines, verify contents, print labels and capture weight and dimensions where required.

Packing design should address:

• product protection and sustainability;
• cartonization and dimensional constraints;
• dangerous-goods or regulatory documentation;
• customer-specific labeling;
• serial or lot traceability;
• shipment consolidation; and
• integration with carrier systems and the TMS.

Cartonization is not merely a packaging decision. It affects freight cost, trailer utilization, handling risk, dimensional-weight charges and customer experience. The system should use validated packaging dimensions and product compatibility rules rather than relying on informal operator judgment alone.

Staging is the controlled accumulation of completed shipments before loading. Staging lanes may be organized by route, carrier, departure time, customer, temperature regime or load sequence. A staging location should have a clear status and capacity control. Staging is not a permanent storage area; prolonged dwell usually indicates an upstream or transportation planning problem.

Dispatch control should verify that the correct shipment is loaded onto the correct vehicle or transport unit. Typical controls include scan-to-load, load sequencing, seal capture, departure confirmation, manifest generation and electronic proof of handoff. The WMS should transmit shipment status and relevant load information to the TMS, while the TMS returns carrier, route, appointment and execution information. Interfaces require clear ownership of fields and status definitions.

7. Cross-Docking

Cross-docking minimizes or eliminates storage by moving eligible inbound goods directly to outbound staging. It is appropriate when demand, timing, product identity and transport coordination are sufficiently reliable.

Types include:

• Pre-distribution cross-docking: destination and allocation are known before receipt.
• Post-distribution cross-docking: allocation is determined after receipt using current demand.
• Opportunistic cross-docking: inbound goods are matched to an urgent or existing shortage.
• Flow-through handling: goods move through a facility with minimal dwell and handling.

Cross-docking requires accurate ASNs, synchronized appointments, reliable labeling, outbound capacity and a clear exception route. If an outbound order is delayed, the system must decide whether goods remain staged, move to temporary storage, are reallocated or are held in a controlled exception area. Cross-docking should not be used to conceal poor inventory planning or unreliable suppliers.

8. Returns and Reverse Logistics

Returns are operationally complex because the physical product may be reusable, repairable, resalable, recyclable, counterfeit, damaged or unsafe. A returns process should begin with authorization and classification rather than simply placing returned goods into general inventory.

A controlled returns sequence is:

Return authorization → receipt and identification → condition assessment → quarantine or disposition decision → refurbishment, restock, repair, recycle, supplier return or disposal → financial and inventory settlement.

Disposition codes should be specific enough to support analysis. “Damaged” may need to distinguish transport damage, customer handling, manufacturing defect, packaging failure and unknown cause. Serial and lot capture may be essential for warranty, recall and regulatory purposes.

Returns also create financial questions: refund eligibility, credit timing, restocking fees, ownership transfer and liability. The WMS, order-management system, customer-service platform and financial system must agree on status transitions. Ethical practice requires transparent customer communication and safe handling of products that may be contaminated, recalled or otherwise unsuitable for resale.

9. Cycle Counting and Inventory Control

Cycle counting replaces or supplements dependence on a single annual physical inventory. The WMS schedules counts, freezes or controls movement, records results and routes discrepancies for investigation.

A common policy is to count high-value or high-risk items more frequently than low-value items. However, classification should consider not only monetary value but also demand, service criticality, shrinkage history, regulatory exposure, serial control and operational volatility.

The inventory record accuracy for a defined population can be expressed as:

where N_c is the number of counted records meeting the organization’s accuracy tolerance and N_t is the total number of records counted. The tolerance must be specified; an item may be considered accurate only if the quantity difference is zero, or within a formally approved percentage or unit threshold. Record accuracy and quantity accuracy are therefore not identical measures.

A basic quantity variance is:

where Q_p is the physical quantity counted and Q_s is the system quantity. A positive variance indicates more physical stock than recorded; a negative variance indicates less. The calculation assumes consistent item identity, location, ownership and unit of measure.

Effective cycle counting is investigative. Repeated variances may indicate receiving errors, picking confirmation problems, unit-of-measure defects, unrecorded damage, unauthorized movement, theft or master-data failure. Adjusting the system without identifying causes improves the number temporarily but weakens control.

10. Exception Management and Control Architecture

Normal flows receive substantial attention during system design, but operational performance is often determined by exceptions. Examples include damaged goods, missing stock, unreadable labels, unexpected receipts, short picks, blocked locations, failed interfaces, late carriers, duplicate shipments and unsafe conditions.

An effective exception process defines:

1. the trigger and its severity;
2. the immediate containment action;
3. the responsible role;
4. the permitted decisions;
5. the information to be recorded;
6. escalation time and authority;
7. financial or customer impact; and
8. the corrective and preventive action.

Exceptions should be visible through dashboards and queues rather than hidden in informal messages. Severity can be based on safety, legal exposure, customer impact, value, service deadline and recurrence. A warehouse may use different workflows for a one-unit short pick and a suspected product recall.

Control design should balance automation and human judgment. Rules are valuable for repeatable decisions, but ambiguous, high-risk or novel situations require authorized review. Overrides should be logged with user, reason, timestamp and resulting disposition. This protects both operational integrity and employee fairness.

11. Performance Measurement

Warehouse metrics should connect activity to outcomes. Useful measures include:

Metrics must have definitions, scopes, data sources, time windows and owners. For example, “dock-to-stock time” should specify whether the clock ends at physical put-away, system availability or quality release. A productivity metric that rewards speed while ignoring errors can produce harmful behavior.

12. Illustrative Case: NorthStar Medical Distribution

Background

NorthStar Medical Distribution supplies hospitals from a regional facility. It handles temperature-sensitive products, serialized devices and ordinary medical consumables. The company experienced late shipments, frequent replenishment emergencies and inventory discrepancies. Its WMS had been installed, but many decisions were still made through spreadsheets and informal supervisor instructions.

Problem

Receiving operators placed inspected and uninspected goods in the same general area. Pickers reported shortages through radio messages. Forward pick locations were replenished only after a shortage occurred. Staging lanes were organized by personal preference, and the TMS often received shipment confirmation after the carrier had departed.

Analysis

The principal problem was not a lack of software functionality. It was weak process governance. Inventory states were ambiguous, master data for case quantities was incomplete, and there were no service-level priorities for replenishment. The facility also measured labor hours but not dock-to-stock time, short-pick causes or staging dwell.

Approach

NorthStar redesigned the process as follows:

• ASNs became mandatory for controlled suppliers.
• Receiving created license plates and separated available, quarantine and damaged statuses.
• Put-away rules incorporated temperature, security and compatibility constraints.
• Forward locations received min–max parameters based on demand and capacity.
• Replenishment priorities were linked to released orders and carrier cut-offs.
• Scan-based short-pick exceptions replaced radio-only reporting.
• Staging lanes were assigned by route and departure time.
• A load-confirmation interface sent verified shipment data to the TMS before departure.
• Cycle-count frequency was increased for serialized and high-value products.
• Supervisors reviewed exception aging daily and conducted root-cause analysis weekly.

Outcome

In the first operating period, NorthStar reduced emergency replenishments and improved shipment visibility. More importantly, management could distinguish supplier discrepancies, receiving errors, picking errors and system-interface failures. The improvement was therefore not attributed to one algorithm; it resulted from aligned process states, master data, work rules, accountability and measurement.

Learning points

1. A WMS cannot compensate for undefined process ownership.
2. Inventory status is a control mechanism, not a descriptive label.
3. Exceptions must be captured at the point of work.
4. WMS–TMS integration should confirm physical events, not merely transmit planned data.
5. Metrics become useful only when their definitions and corrective actions are explicit.

13. Implementation, Governance and Contemporary Developments

WMS process implementation should proceed through process mapping, requirements definition, rule design, master-data cleansing, configuration, integration testing, simulation, user acceptance testing, training, cutover and stabilization. Testing should include normal flows, peak volumes, partial receipts, damaged goods, failed interfaces, unit-of-measure conversions, canceled orders and recovery after equipment or network failure.

Contemporary systems increasingly use mobile scanning, voice interfaces, computer vision, autonomous mobile robots, real-time location systems and machine-learning forecasts. These technologies can improve visibility and decision support, but they introduce governance requirements. Organizations should assess cybersecurity, data privacy, model explainability, worker surveillance, algorithmic bias, safety certification and fallback procedures.

Artificial intelligence may help predict congestion, identify anomalous inventory movements, recommend slotting changes or prioritize labor. It should not be allowed to override safety, regulatory or customer-specific constraints without controlled authorization. Human accountability remains necessary for hazardous materials, recalls, ethical employment decisions and material financial adjustments.

Regulatory requirements vary by jurisdiction and product category. Relevant concerns may include traceability, customs and bonded inventory, dangerous goods, food or pharmaceutical controls, worker safety, data protection and records retention. The governing principle is that system convenience must not weaken legal or ethical control.

Chapter Summary

Warehouse process design integrates physical handling, information capture and decision rules. Receiving establishes identity, quantity, condition and ownership; inspection separates usable inventory from quarantined or damaged stock. Put-away and slotting determine how space, travel and accessibility are balanced. Replenishment protects forward-pick availability, while picking methods and task interleaving coordinate labor and equipment.

Packing, staging and dispatch connect warehouse execution to carrier and TMS processes. Cross-docking can reduce dwell when inbound and outbound flows are synchronized. Returns require controlled authorization, condition assessment and disposition. Cycle counting provides continuous inventory control, but variance adjustment should be accompanied by root-cause analysis. Across all processes, exception management, master-data governance, measurable definitions and accountable overrides are essential. Technology and AI can enhance execution, but they do not replace sound process design, human responsibility or regulatory compliance.

Key Terms

Advance Shipping Notice (ASN): Electronic or structured information describing an expected inbound shipment.

Available inventory: Stock released for allocation or operational use under defined rules.

Cycle counting: Scheduled counting of selected inventory records throughout the year.

Cross-docking: Movement of eligible inbound goods to outbound flow with little or no storage.

Exception management: Identification, containment, resolution and analysis of deviations from normal process.

Forward pick location: Location positioned for efficient order picking.

Inventory Record Accuracy (IRA): Measure of agreement between physical inventory and system records under a defined tolerance.

License plate: System identifier for a pallet, carton, tote or other handling unit.

Master data: Relatively stable data describing items, locations, units, partners, constraints and rules.

Min–max replenishment: Policy that triggers replenishment below a minimum toward a target maximum.

Order allocation: Assignment of available inventory to specific demand.

Put-away: Movement and system placement of received goods into an authorized location.

Quarantine: Controlled status or location for inventory awaiting inspection or disposition.

Reserve storage: Storage holding inventory that supports forward-pick locations.

Slotting: Assignment of products to storage or picking locations.

Staging: Temporary, controlled accumulation of completed shipments before loading.

Task interleaving: Assignment of different compatible tasks to reduce empty travel.

Unit of measure: Defined quantity basis, such as each, inner pack, case or pallet.

WMS: Warehouse Management System that controls inventory, locations, tasks and warehouse transactions.

TMS: Transportation Management System that plans, executes, monitors and often settles transportation activity.

Review Questions

Short Answer Questions

1. What are the three flows coordinated by a WMS?
2. Why should quarantined inventory be represented separately from available inventory?
3. Define task interleaving and identify one potential disadvantage.
4. What is the purpose of a license plate in warehouse execution?
5. Why is root-cause analysis important after a cycle-count variance?

Long Answer Questions

1. Explain how receiving, inspection, put-away and inventory-status controls should be integrated in a WMS.
2. Compare fixed, dynamic, class-based and demand-directed put-away strategies.
3. Evaluate the advantages and limitations of discrete, batch, zone, cluster and wave picking.
4. Design a cross-docking process, including prerequisites and exception paths.
5. Discuss how WMS–TMS integration affects staging, dispatch, shipment visibility and accountability.

Analytical / Application Questions

1. A forward pick location has a target maximum of 120 cases, 35 cases on hand, 20 cases allocated and 15 cases in confirmed inbound replenishment. Using the projected-quantity definition in this chapter, calculate the replenishment quantity before considering capacity or reserve constraints.
2. A warehouse reports high labor productivity but declining shipping accuracy and increasing short picks. Diagnose possible incentive, master-data, process and control failures, and recommend a measurement redesign.
3. Design an exception-management workflow for a high-value serialized item that is physically found in the wrong location during picking. Specify containment, system status, authorization, investigation, customer impact and corrective action.

Multiple Choice Questions with Answers

Question 1

Which WMS inventory status most appropriately represents goods received but awaiting quality approval?

A. Available

B. Quarantined

C. Allocated

D. Loaded

Correct Answer: B. Quarantined

Question 2

What is the primary purpose of task interleaving?

A. To eliminate all inventory counting

B. To reduce empty travel by assigning compatible next tasks

C. To replace location master data

D. To prevent all picking waves

Correct Answer: B. To reduce empty travel by assigning compatible next tasks

Question 3

Which condition is most important for successful cross-docking?

A. Large quantities of unplanned reserve storage

B. Accurate inbound information and synchronized outbound capacity

C. Maximum inspection delay

D. Unrestricted mixing of incompatible products

Correct Answer: B. Accurate inbound information and synchronized outbound capacity

Question 4

If the target maximum is 120 cases and projected forward-location quantity is 70 cases, what is the simple replenishment quantity?

A. 40 cases

B. 50 cases

C. 70 cases

D. 190 cases

Correct Answer: B. 50 cases

Question 5

Which activity belongs primarily to dispatch control?

A. Creating an item barcode standard

B. Assigning a product to a fixed slot

C. Verifying the shipment is loaded onto the correct vehicle

D. Sampling inbound product quality

Correct Answer: C. Verifying the shipment is loaded onto the correct vehicle

Question 6

Why is adjusting a cycle-count variance without investigation inadequate?

A. It always increases physical stock

B. It may correct the record while leaving the process cause unresolved

C. It prevents any future counting

D. It converts all stock to quarantine

Correct Answer: B. It may correct the record while leaving the process cause unresolved

Question 7

Which picking method commonly picks several orders together and sorts them later?

A. Batch picking

B. Discrete picking

C. Single-order picking

D. Reserve put-away

Correct Answer: A. Batch picking

Question 8

Which master-data field is especially important for correct case-level replenishment?

A. Operator birth date

B. Unit-of-measure conversion

C. Trailer paint color

D. Customer website design

Correct Answer: B. Unit-of-measure conversion

Question 9

A positive quantity variance in the equation ∆Q = Q_p - Q_s means that:

A. The system quantity exceeds the physical quantity

B. The physical quantity exceeds the system quantity

C. Both quantities are necessarily zero

D. The item must be damaged

Correct Answer: B. The physical quantity exceeds the system quantity

Question 10

Which governance practice is most appropriate for a high-risk WMS override?

A. Permit anonymous changes without a reason

B. Delete the original transaction

C. Log the user, reason, time and resulting disposition

D. Allow any operator to bypass safety restrictions

Correct Answer: C. Log the user, reason, time and resulting disposition