Home Work Services About Blog Contact Start a project
Creator Agency CN Creator App TCN Agent LIVE Games Dentistry Downloads
ENAR

All articles

Agency Import Status: What to Tell Staff

When an agency tool imports data, staff need to know exactly what finished and what still needs attention. Show distinct states, keep the last good data visible, and give a recovery path that does not require guesswork.

Why vague import messages cost time

A spinner that says 'syncing' tells staff nothing about whether yesterday's figures are safe or whether they should wait before editing pay formulas. When an import stalls, people refresh, retry, or start manual work that later conflicts with the import.

The fix is to separate the current attempt from the last known good result. Staff should see both at a glance: what is happening now, and what data is currently usable.

States that match real work

Use a small set of states that map to decisions. Queued means the job is waiting for a worker or a scheduled window; no data has changed yet. Connecting means the tool is authenticating or opening a session; still no data change. Importing means records are arriving; partial results may already be visible.

Partial means some records arrived but the run did not finish cleanly. Complete means the run finished and the expected scope was covered. Attention means the run finished but some records need a human decision, such as a creator who cannot be matched to the roster.

Each state should answer one question: can staff rely on this data right now, and if not, what should they do next?

Last success versus current attempt

Show the timestamp and scope of the last successful import next to the current attempt. If the current attempt is partial or failed, the last success remains the source of truth until someone resolves the issue.

Do not overwrite good data with an incomplete run. Write new records to a staging area, validate them, then merge. If validation fails, keep the previous dataset and mark the new run as attention.

This matters for pay and levels. A half-imported month can silently change a creator's standing. Staff should be able to freeze the month on the last good import while they investigate.

Recovery that respects the roster

Recovery should be specific. If a creator cannot be matched, offer to link them to an existing roster entry or create a new one. If a field is missing, show which field and which record. Avoid a single 'retry' button that reruns everything and hides the cause.

Keep an audit trail of what changed during recovery. Staff need to know whether a manual link will affect future imports or just this run.

Suppose an agency imports daily LIVE figures and one creator appears under a new handle. The tool marks the run as attention and lists the unmatched handle. A staff member links it to the existing creator. The next import should recognize that link and not raise the same attention again.

A concrete pass or fail test

Before shipping, run this test: start an import, interrupt it midway, and then open the staff view. The view must still show the last successful import with its timestamp, must show the interrupted run as partial or attention, and must not present the incomplete data as final. If any of those three conditions fails, the status design is not ready.

Also test the recovery path: resolve one attention item and confirm that the next import does not repeat it. If the same item returns, the link is not being persisted correctly.

Tradeoffs and scope

More states mean more clarity but also more UI to maintain. Start with the six states above and resist adding new ones unless they change a staff decision. If a state does not lead to a different action, merge it into an existing one.

Detailed recovery screens take time to build. A simpler alternative is to export attention items as a list and let staff resolve them outside the tool, but that breaks the audit trail and often leads back to spreadsheets. Choose based on how often imports need human intervention in your agency.

Finally, keep the language neutral. 'Import finished with items to review' is clearer than 'sync error' because it tells staff the data is mostly usable and points to the next step.

Continue reading

A practical next step

Explore the related Devign work, then discuss your requirements before committing to a project scope.

Related Devign work · Discuss your project