Desk reference · roster imports

Check the file. Check the source.

Use these checks before applying a roster. RelayWorks and its rules are fictional and specific to this practice.

Start with: the approved people-data source and the requested change instructions.

Use this sequence before applying an import

  1. Use the approved source. Confirm exact values there; never guess a missing or uncertain value.
  2. Check the file’s shape. Required columns: Employee_ID, Display_Name, Work_Email, Team_Code. Every cell must be present. Email needs non-space text, @, a domain, and a dot; this does not check deliverability.
  3. Correct fields from the source, then validate. Employee_ID is exactly six digits stored as text; leading zeroes matter. Do not guess or pad an ID. Allowed team codes are OPS, ENG, SUP. Missing values, invalid values or duplicate IDs block the whole import; no partial updates apply.
  4. Compare the preview with the approved change. Employee_ID is the match key: an existing ID updates; a new ID adds. Name or email changes do not create a person. Validation checks structure, not authorization.
  5. Confirm only a reviewed preview. Rows absent from the file remain unchanged. Preserve display names, including spaces and accents, as supplied. After any edit, validate and review again because readiness clears.

Team-code directory

OPS
Operations
ENG
Engineering
SUP
Support

Verify allowed values against the approved source

Example row: 007305 | Rosa Álvarez | rosa.a@example.com | SUP. If the approved source says Rosa’s email changes but her team remains OPS, retain OPS. SUP is an allowed code, but that does not authorize the assignment.