rail mobility planning discovery and strategy
Delivered through a named service corridor with scope, named owner, constraints, decisions, measures, exceptions and accepted close-out for every service corridor.
Skip to content
01 02 03 04 Note 01 Note 02 Note 03
400 · rail mobility planning platform
Wrenis
rail mobility planning, shaped around connected services, live status and coordinated ownership.
Wrenis is a fictional rail mobility planning platform organisation created as Interlink Apps catalogue design 400. The page architecture translates the organisation's real operating unit — the service corridor — into navigation, evidence, case work, people, questions and conversion rather than relying on decorative hero content alone.
Framed dossier theatre · quiet narrative bands · high-contrast monochrome · quiet scale and settleservice corridor
01 / Offer
Built around the work, not a generic template.
platform implementation and operations
Delivered through a named service corridor with scope, named owner, constraints, decisions, measures, exceptions and accepted close-out for every service corridor.
Governance, exception handling and stakeholder coordination
Delivered through a named service corridor with scope, named owner, constraints, decisions, measures, exceptions and accepted close-out for every service corridor.
Evidence, reporting and continuous improvement
Delivered through a named service corridor with scope, named owner, constraints, decisions, measures, exceptions and accepted close-out for every service corridor.
02 / Method
1
Frame · define purpose, boundaries, risks and ownership
Each stage leaves an explicit decision trail before the next stage begins.
2
Map · translate the operating system into a visible service model
Each stage leaves an explicit decision trail before the next stage begins.
3
Deliver · execute through explicit checks, decisions and handovers
Each stage leaves an explicit decision trail before the next stage begins.
4
Prove · close with evidence, unresolved risks and next actions
Each stage leaves an explicit decision trail before the next stage begins.
03 / Work
Representative engagements
Case 1
Wrenis programme 400-A
A representative rail mobility planning engagement organised one service corridor around a clear brief, accountable roles and evidence that could survive handover.
Case 2
Wrenis operating cycle 400-B
The team tested the platform model under live constraints, recorded exceptions and translated every unresolved issue into a named next action.
Case 3
Evidence release 400-C
A recurring review converted activity into a concise decision record showing outcomes, trade-offs, ownership and what the organisation would change next.
04 / Evidence
99%work items closed with explicit evidence
2dtypical decision-to-owner handover
32representative operating records reviewed
0anonymous claims presented as proof
05 / People
Sipho Osman
Practice lead
Leila Mokoena
Delivery lead
Jonah Dube
Evidence lead
06 / Notes
What credible evidence looks like in rail mobility planning
Why service corridor ownership improves service quality
Designing platform systems around exceptions rather than ideal cases
07 / Questions
Is this a real organisation?
No. Wrenis is a fictional Interlink Apps identity demonstrating a production-grade website for rail mobility planning platform.
How is delivery made measurable?
Every service corridor carries scope, ownership, constraints, decisions, acceptance criteria and close-out evidence from the beginning.
Can this design adapt to another organisation?
Yes. Brand, imagery, terminology, sections and operating records can change while retaining the responsive, accessible information architecture.