The failed contact load
A retail operations assistant loads two fictional contact rows. Both are rejected because the family-name map points to a nonexistent source column. The source also contains outside spaces and uppercase email.
Read the failed counts, fix the map, add a duplicate control, rerun with stable external IDs, and produce a scoped reconciliation report. The conclusion must distinguish a corrected mapping from a general claim that all source data is clean.
You own the complete import incident handoff described in the brief. The next person needs working configuration and enough evidence to explain its behavior. Start with the business requirement, then keep each completed part while you add the next one. Your own saved state carries between steps.
A later task can expose a mistake that an isolated form would hide. A queue may exist without usable membership, a report may have the right title but the wrong population, and a rule may work for the example while rejecting an allowed record. Test those boundaries as you go. The final step asks for the operational conclusion or completed deliverable, and the checker keeps earlier requirements in scope.
Business requirement → configuration → boundary tests → handoff
Build a connected deliverable and retain its controls.