How it works
Keep planning in Excel. RosterField gives your project a deliberate review step before workers see a published roster.
Keep planning in Excel. Choose the project and upload its CSV or XLSX roster.
Open flagged sections, confirm unfamiliar labels and resolve corrections. Refresh the preview and check totals before release.
Make the reviewed project roster current; workers can find it through the project link or QR code.
Before release
Upload CSV or XLSX, select the worksheet and check the detected layout. The review starts with personnel, entry counts, the selected date window and actions needing attention. Click an action to open its correction section. Optional settings stay collapsed, with information icons explaining each section.
Before release
Unfamiliar non-empty daily statuses start with the cleaned text from the source cell. Confirm those values or choose meaningful replacements. Leaving a mapping blank keeps the source value, not an empty shift. Time-only values, oversized labels, duplicate records and ambiguous dates still need attention.
Before release
Any review edit makes the preview out of date and disables Publish until it is refreshed. What will be published is collapsed initially and paginates the first 100 sample entries, 10 per page. Compare the total counts, boundaries and source records too; the sample is not the full roster.
After release
When the preview is right, publish it for the project. The current roster is available through the project link or QR code; earlier publications remain in roster history for administrators.
Scope
RosterField publishes a reviewed copy of the roster. It does not plan shifts, calculate payroll or repair a source workbook automatically. Change the source and re-upload when necessary.
Useful answers
No. An administrator checks the selected worksheet, people, dates and statuses in review before choosing to publish. The public demo cannot publish a live project roster.
Yes. RosterField takes a prepared CSV or XLSX through import review and publication. It does not replace the spreadsheet where your team builds the plan.
Do not publish it. Open the flagged action, check the mapping and date window, or correct the source cell or workbook. Refresh the preview after every edit and compare the new counts before release.
Not simply because they are unfamiliar. Their cleaned source text is prefilled and requires confirmation. A blank mapping retains it; clear the source cell deliberately if the value must be removed.
Try a fictional roster in the isolated import sandbox, or upload a small, non-sensitive CSV or XLSX test file. Publishing stays disabled.