Keep the lesson for the next incident
Document field semantics
Record each source column's meaning, units, type, optionality, destination field, transformation, default, and rejection rule. Name positional or version-specific behavior explicitly. Include a small mapping table with distinct examples so similar labels cannot be interpreted by guesswork.
Retain import fixtures
Keep labeled rows for reordered headers, omitted columns, duplicate names, empty and zero values, malformed types, and defaults where relevant. Assert destination fields and error outcomes. Preserve source format versions so a fixture continues to explain the boundary that failed.
Review source changes
Assign owners for source schema changes, mapping revisions, and historical repair decisions. Review new headers, changed types, and unexpected default or rejection rates on a defined cadence. Reopen investigation for a new misroute or unexplained field distribution shift.
What to carry forward
Close the learning record with field semantics, mapping revisions, labeled fixtures, owners, and a recurrence trigger for misrouted or newly defaulted values. Keep ambiguous source meaning visible as follow-up. The durable result is a reviewable import contract that makes future changes easier to assess.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow