CSV import versus editing shifts in scheduling software

When a supervisor spots a wrong shift, should they edit it in scheduling software or export a new CSV for publication? Both actions can be reasonable, but they solve different problems. Editing changes the proposed or approved plan in its source system. CSV import carries saved data into another workflow for checking and sharing. Confusing the two can leave a worker page and a scheduler showing different “current” answers.

Picture a fictional facilities team planning shifts in a scheduling application. Each Thursday, approved assignments are exported as CSV for the Riverside project roster. On Friday, a supervisor discovers that Amar’s Saturday start moved from 06:00 to 07:00. If the scheduler owns that decision, change and approve it there first. Export the corrected data, review the new import, then publish a replacement. An import preview should not become an unofficial place to redesign Saturday’s shift.

Decide what kind of work needs doing

Situation	Better starting point	Why
A shift is still being allocated	The planner’s workbook or scheduling system	Staffing rules and approval are still in play
A saved export appears to map the wrong date	Compare source and import review	The transfer, not necessarily the plan, is suspect
A manager approves a changed shift	Correct the authoritative planning source	The roster publication should follow the approved decision
An already-approved week needs worker access	Review and publish the export	Workers need a clear project reference

This is not a ranking of products. Some teams plan in Excel; others use a dedicated scheduler and only need an additional publishing step. RosterField accepts CSV and XLSX in the signed-in app, reviews the imported project roster and lets an administrator publish it. It does not create or edit shifts in the planning system, synchronise assignments back into that system, or handle swaps and timesheets.

Set a dependable export contract

CSV is a flat snapshot: specify the column names, meaning of each shift value, date format, identity field, employer and location fields, and approved period. Include a stable employment number for every intended worker. Ask the source owner to say whether “blank” means off duty, unknown or a missing export value. If the scheduling software exports a revised column name, mapping could change even when the visible rows look familiar.

Name each export with project and period, but also record who authorised it. An automatically generated CSV may be technically perfect while containing a draft future allocation. Never infer approval solely from file creation time. If source and published release disagree, agree which one is authoritative for planning and stop distributing an unverified worker instruction until the difference is resolved.

Check whether the export is a complete period or only a list of changed shifts. A partial CSV may be perfectly valid for its original reporting purpose yet unsuitable as a replacement project roster. Ask the scheduler owner for the full approved snapshot before treating it as a new publication source.

Review a new snapshot as a new release

At import, sample start and end dates, a night shift, a person who joined late and one worker who moved locations. Look at skipped identities, repeated employment numbers, unfamiliar codes and the previewed counts. Resolve source-data problems with the scheduler owner, then refresh the preview before publication. A corrected CSV needs another review even when its predecessor imported cleanly.

Once the checked snapshot is published, the project worker link or QR code supports name search without individual login. It is a shareable worker reference, not a live view into the scheduling application’s database. If Amar’s change happens after publication, updating the source alone leaves the old publication in place until the replacement is reviewed and released. Communicate significant changes directly as required; neither system can assume every worker has read a link.

Know when import is the wrong answer

If the primary problem is building complex shifts, optimising allocations, approving swaps or calculating time, choose tools and processes that address those tasks. Repeatedly patching exports to compensate for missing planning controls will create conflicting sources. Conversely, replacing an established scheduler solely to send a checked worker link may be unnecessary.

The CSV-versus-XLSX guide compares file formats, a different question from choosing where edits happen. For the three decision stages read creation, review and publication, and for the live project workflow start with How it works.

Questions people ask

Can I import a CSV containing only the one shift I changed?

Do not assume a change-only export is a complete replacement roster. Ask the planning-system owner what the CSV contains, obtain the full approved project period when a complete release is required, and inspect the previewed people and dates. A technically readable one-row file may omit everyone else from the intended worker reference.

Should I fix an incorrect shift in the import review instead of the scheduler?

If the underlying decision is wrong, fix it in the authoritative planning source and get the required approval there. Use the import review to diagnose how saved assignments were read, not to create an unofficial new plan. Export again, compare the corrected preview and publish the replacement only after the sources agree.