SWAP

Survey Work Allocation Portal

Organisation logo goes here.

Duty Planner

Drag a duty onto a team member’s day to allocate it.

Phase 2 screen — the most complex surface in the project. One screen, but roughly four or five screens' worth of build.
Shift Early · 07:00–15:00 Mid · 09:00–17:00 Late · 13:00–21:00 Not rostered Cell shading shows the team member's rostered shift that day — a duty can only be dropped on a matching shift. A team member can take duties from up to 3 projects on the same day.

20–26 Jul 2026

Team Member
Mon 20
Tue 21
Wed 22
Thu 23
Fri 24
Sat 25
Sun 26
Alice Johnson
7034/11
Bob Wilson
7034/127040/05
David Martinez
7034/13
Emily Clark
7034/14
Jane Smith
7034/15
John Doe
Kevin Thompson
7034/16
Lisa Anderson
7034/17
Michael Brown
Rachel White
Sarah Davis
7034/18

Duty Details

Project—
Duty Time—
Team Member—
First Journey—
Days Operable—
Break Duration—
Duty Status—
Final Journey—
Number of Journeys—
Date—
Task Status—

Allocation warnings

Every duty carries its own date, set on Add Duty, so it can only be dropped in that date’s column — the column lights up as you start dragging. Changing the date is an edit to the duty, not a planner action. A shift mismatch is blocked outright; a date whose weekday falls outside the duty’s Days Operable is allowed but flagged here, as is any overlap in a team member’s times. Auto-allocate walks the unallocated list one duty at a time and gives it to the first team member who is rostered for that duty’s shift (Reference Data › Member Shifts), has no clashing times, and is under the limit of 3 projects that day. A duty whose shift nobody free can work is left unallocated and reported here.

Work Monitor

—

Manual entry only — no field feed in Phase 1Custom
0
Total
0
Active
0
Complete
0
Pending
0
Journeys In
0 / 0
Actual vs Anticipated

Duties

—
DutyTeam MemberDaysShift TimesFirst StopLast StopJnysProgressStatus

—

Team Member
—
Days Operable
—
Project Type
—
Duty Status
—
Task Status
—
Duty Start
—
First Journey
—
Final Journey
—
Duty End
—
Break
—
Journeys
—
Progress
—

Journeys

Projects

—

Custom
Work TypeProject No.YearOperatorDescriptionTarget StartTarget EndDaysJourneysStatusActions

Click a row to see the project's details.

All Duties

—

⚠ Open Item 5 — Task StatusCustom
Duty No.TypeShiftTeam MemberFirst StopFinal StopJnysBreakDuty StatusTask StatusDaysActions

Shift is the duty’s sign on – sign off time. Break is the total of the lunch and break events on the duty.

Import Timetable

Greater Manchester bus timetable · TransXChange format, loaded as published

Custom

Load the public-domain Greater Manchester bus timetable in TransXChange format, exactly as published — no pre-processing. Each service is split into the timetable variants it actually runs (up to six: Mon–Fri, Saturday and Sunday, each Outbound and Inbound), and the operator running it is stored with its reference and short name for filtering.

Imports are all-or-nothing. A file that fails validation cancels the whole import and nothing is written. Records that already exist are updated; new records are created.

Drop a TransXChange file here
or — .xml, or a .zip of .xml files
No file selected

Last import — result

Accepted
Filetfgm_txc_2026-10-01.zip
Operators created / updated2 / 9
Services created / updated4 / 212
Timetable variants1,143
Journeys48,906
Stops12,480
Files rejected0

Example of a rejected import

Cancelled

Nothing was written. Fix the file and upload again.

SVC_590.xml — not valid TransXChange (schema 2.4)Error
SVC_X12.xml — operator reference NST has no Operator recordError
SVC_33.xml — journey pattern references unknown stop 1800BSTN04Error

Stages View

One timetable at a time — pick the operator, service, day and direction

Custom

All Journeys

—

⚠ Open Item 11 — rejection codesCustom · Phase 2
DutyTeam MemberDaysSvcJourneyDirBoard StopDepAlight StopArrStatusReview

Every journey on every duty. Change a journey’s status from the dropdown. A journey comes in from the TS App as Complete, is then Approved for export or Rejected with a reason code from the Review button — a rejected journey goes back into the pool to be added to another duty.

—

—

Admin-generated
Standard generated CRUD — list, filter, create, edit, delete. Layout is the framework's, not bespoke.
—