Skip to content
RoomAMD

LinkedTracks

LinkedTracks

Work‑train planning for rail construction.

Rail construction and work-train planning software that brings identity, workforce, fleet and project control together around one workflow, from T‑42 weeks to closeout.

Built by RoomAMDOne organisation's process

Build something like this
LinkedTracksDashboard

Waiting on your signature

  • 1 NLR‑W15 · consist
1 to sign

Clashes

No clashes this week
0 clashes

Loading now

  • 1 train loading · NLR‑W14 · Wed
  • 2 cars to certify
2 cars

Maintenance coming up

  • TM-15 in the shop until Fri, Mar 19, 2027
1 unit out

The next ten weeks

  • 4 weekends planned
  • 1 waiting on signatures
  • 0 short of cars
4 weekends

The fleet

  • 9 units ready
  • 1 at the shop
9 of 10 ready

Weekends · next ten weeks

NLR-W14 · North Line km 42–48closure Sat, Mar 13, 2027
Development: doneCorridor lead: doneSupport leads: doneManagers: doneDeparture Board: due within two weeksDeparture Board · Due Fri, Mar 5, 2027 · Every train certified loaded
  1. T-42
  2. T-22
  3. T-12
  4. T-8
  5. T-6
  6. T-4
  7. T+1
ClearedDana Okafor on BR-07✓ Locked · WP-14 v3T-2/1 · certify by Fri, Mar 5, 2027 · 23:59

Interactive demo on invented data. Nothing here connects to a live system. This is the real application's dashboard, weekend list and lifecycle.

The problem

Work trains are planned in fragments

Six spreadsheets, six owners
Consists, crews, machines, routing, materials and sign-offs each live in a different spreadsheet, owned by a different team.
Late changes break approvals
A car swap the week before a closure quietly invalidates paperwork that was signed months earlier.
Readiness is a phone call
On loading night, nobody can see at a glance which trains are certified and which are still waiting.

The lifecycle

T‑42 weeks to closeout.

Every weekend closure runs against the same eight milestones, each due on the Friday of its week. A milestone completes when its facts are true, never because someone ticked it. The loading gate opens fourteen days before the closure.

  1. T-42Draft planEvery train has a consist and a route; requests filed.
  2. T-22HandoverHanded over to the delivery team.
  3. T-12Consist signedConsist and machines signed by both leads.
  4. T-8Machine routingMachine routing signed; track access confirmed.
  5. T-6Train routingTrain routing signed; timings received.
  6. T-4MaterialsMaterials signed by both leads.
  7. T-2/1Certified loadedEvery train certified loaded before departure.
  8. T+1CloseoutEvery train back home.

Inside the platform

Where the four products came from.

RoomAMD Identity
Identity cards with QR verification, live training records, and machine tickets checked against every booking.
RoomAMD Workforce
Operators from several contractors, proposed, asked and confirmed by name for each weekend, with who is on site and cleared.
RoomAMD Fleet
Locomotives, cars and track machines on one timeline; units held from loading to return, with clashes between weekends found and fixed.
RoomAMD Projects
Every weekend against eight T-week milestones that complete from the facts; consists, routing and materials signed by both leads on the exact version.

Also in LinkedTracks: materials (hub stock against demand), photo-based inspections, arrivals and pickups, consist checks for length, tonnage and power, and private document storage.

In the field

The crew carries it.

A phone app for crews and operators: this week's work, their own card and tickets, card scans for supervisors, arrivals to confirm, pickups with photos, and car-by-car checks for the readiness certificate.

What LinkedTracks is, and isn't

LinkedTracks is a planning, coordination and documentation system. It does not control dispatch, signalling, train movement or machinery. It was built around one organisation's real work-train process, and RoomAMD packages its capabilities for others.

See LinkedTracks on your own programme.

We'll walk through a closure from T‑42 to closeout with you, and what configuration your process would need.