Working Principles
Clarity is not
a style choice.
It is the work.
What follows is an account of how we think about documentation work — not a mission statement, but the reasoning behind the decisions we make in practice.
Foundation
What the work starts from
Japanese railway systems are among the most precisely operated in the world. That precision is embedded in their physical design, their published schedules, their signage logic, and the behaviours they produce in the people moving through them. When someone asks us to document part of that system, they are asking us to capture something that has already been thought through carefully by others — and to render it clearly enough for a third party to understand and use.
That task does not benefit from being rushed, or from starting without a clear sense of what "done" looks like. The foundation of this work is the belief that useful documentation is the product of limited scope, honest method, and a written form that can outlast the moment of its creation.
Limited scope
Less territory covered carefully produces more useful output than more territory covered loosely.
Honest method
What was observed is recorded. What was not observed is not implied. Sources are noted for every claim.
Written form
A document can be shared, filed, and read by people who were not part of the original conversation.
Lasting use
Work structured around a defined corridor or asset ages slowly and can be updated when individual details change.
Philosophy & Vision
What we think good documentation does
There is a version of documentation that captures everything and illuminates nothing — comprehensive archives that require extensive effort to navigate, where the important details are buried under the exhaustive ones. That is not what this work tries to produce.
What we aim for instead is something more modest in ambition but more useful in practice: a document that a professional can read in an hour and come away from with a clear, accurate picture of a specific station, corridor, or infrastructure asset. Not a comprehensive atlas of the entire network. A reliable account of a defined part of it.
That kind of document is useful to an accessibility team assessing platform access, a journalist writing a background piece, a planner modelling transfer flows, or a designer mapping wayfinding. It covers what they need without demanding that they wade through what they do not.
Core Beliefs
The convictions that shape the work
Scope before fieldwork
No useful document begins in the field. It begins with a clear statement of what is being documented and why. Without that, the fieldwork produces noise rather than reference material. Every engagement starts with a written scope note that both parties agree to before any site visit or schedule review begins.
Uncertainty has a place in good writing
A report that hedges nothing is not thorough — it is overconfident. Railway systems change. Observations are taken at a specific point in time. Publicly available documentation contains gaps. When those conditions apply to a finding, the document should say so, clearly and without apology.
Format follows use
A deliverable is not finished when it has been produced. It is finished when the person who receives it can use it for the purpose they had in mind. That means agreeing on format before drafting begins — not deciding at the point of delivery what shape the document will take.
Narrowness is a feature
A well-documented single station is more useful than a loosely-documented twenty. Clients sometimes arrive wanting broad coverage and leave with a tighter scope — not because the broader work is unimportant, but because the narrower work is genuinely usable in a way the broader version would not be.
Fixed fees reduce distortion
When the billing model rewards more hours, there is a structural pressure to use more hours. A fixed fee removes that distortion. The work takes as long as it needs to take, and no more. Efficiency is not penalised.
Japan is specific
Transport systems carry local logic that general frameworks do not capture well. Japanese station conventions, timetable structures, signage systems, and operational culture are not the same as their equivalents elsewhere. Work that treats them as equivalent produces documentation that is accurate in format but unreliable in content.
Principles in Practice
How beliefs translate to how the work is done
The scoping note is a commitment
Every engagement begins with a written note confirming scope, fee, and calendar. This is not boilerplate — it is the document both parties refer to if there is any question about what was agreed.
Site visits are structured, not exploratory
A site visit conducted without a prepared survey guide produces inconsistent results. Photographic survey and observation notes follow a consistent structure so that what is captured is comparable and complete relative to the agreed scope.
Draft review is part of the method
A draft shared before finalisation is not a courtesy — it is a quality check. If a requirement was misread or a detail was missed, the review stage is where that surfaces, before the document is considered complete.
Calendars are set, not suggested
A timeline stated as approximate tends to expand. Each engagement includes specific milestone dates — for fieldwork completion, draft delivery, and final document — that are agreed as part of the scoping note.
Source notes travel with the document
Every report includes a reference section noting the sources consulted: publicly available timetables, operator documents, site observations, or clarifying interviews. The document can be verified and updated by a third party without needing to reconstruct the research.
Out-of-scope requests are declined clearly
When a request falls outside what the available services can deliver well, the scoping note says so directly. Taking on work that exceeds our reliable capacity would produce an inferior document and set unrealistic expectations.
Client-Centred
Starting from what you actually need
The people who commission this work have quite different backgrounds and needs. An accessibility coordinator planning a station renovation has different questions than a journalist writing a feature, or a planning team modelling transfer volumes. What they share is that they need a clear, reliable document — not a demonstration of how much can be known about Japanese railways in general.
The scoping process starts with your project rather than with a menu of standard services. The three available services describe typical shapes of engagement — but within each one, the specific corridor, station, or asset being documented is defined by you. The goal is to produce something that is directly useful to the work you are doing, rather than a comprehensive reference that partially overlaps with it.
If an initial enquiry suggests that none of the current services fits well, that will be said in the scoping response rather than forcing an ill-fitting engagement.
Continuous Improvement
How the method develops
From each engagement
Each project reveals something about where the survey method leaves gaps, or where the report structure could be clearer. Those observations are carried forward into subsequent work. The method is not fixed — it is periodically reviewed.
Balance between depth and speed
Japanese railway systems change — new lines open, stations are reconfigured, timetables shift seasonally. The method tries to record not only what was observed but also the date and conditions, so that the document can be updated efficiently rather than reconstructed.
What does not change
The commitment to scope-before-fieldwork, stated uncertainty, and a single revision round are not aspects of the method that are under review. They are structural. Changes tend to happen at the level of survey guides, report templates, and diagram conventions.
Integrity & Transparency
What we will not do to close an engagement
We will not overstate certainty
If an observation was made on a single visit, on a single day, under specific conditions, the report will note that. It will not present that observation as a settled fact about the station's permanent condition.
We will not accept scope that we cannot serve well
If an enquiry describes something beyond the available services' reliable range — a multi-city study, a real-time operations analysis, or a legal or safety assessment — we will say so in the scoping response rather than taking the work and producing an inferior output.
We will not hide the process
The method used for each service is described openly. If you want to understand how the fieldwork is conducted or how the report is structured before committing to an engagement, that information is available on request.
We will not pad deliverables
A report that is longer than it needs to be is not more thorough — it is harder to use. Deliverables are edited to contain what is needed for the agreed purpose, not expanded to justify the fee.
Collaboration
What the working relationship involves
Documentation work is not done in isolation. The client holds context about the project that shapes what matters — which access routes are in question, which transfer relationships are relevant, which infrastructure assets are under review. Capturing that context is part of the scoping process. Once it is recorded, the fieldwork and writing can proceed with a clear orientation rather than covering everything and hoping the relevant detail is included.
One consultation session is included in the Transit Schedule Analysis service — used to share provisional findings before the written report is drafted.
One structured round of written feedback is included across all services, at the draft stage, before the document is finalised.
Email correspondence throughout each engagement is replied to within two working days during the active project period.
Long-term Thinking
Building something that lasts beyond the engagement
A good piece of documentation should still be useful in two years. That is not always possible — stations are reconfigured, lines are rerouted — but the closer a document's scope is to a defined and stable asset, the longer it holds its value. A written brief on a specific signal block or a specific station's access structure changes only when those things change, not when the wider network evolves around them.
Source notes make updates tractable. If a section of a report becomes outdated because a timetable changed, a reader who has access to the original sources can identify which specific findings need revision and which remain valid. That is a more honest and more useful document than one that presents all findings as equally current.
Narrow scope ages slowly
A focused document on a single corridor or station is much more likely to remain useful than a broad survey of an entire region, which requires wholesale updates when the network shifts.
Dated observations are honest observations
Every report notes when site visits were conducted and which versions of published schedules were consulted. Future readers know exactly what period the observations relate to.
Structured files can be updated selectively
Because the report structure is consistent and sections are labelled clearly, updating a specific element does not require rewriting the entire document.
For You
What to expect if you work with us
A written scope note before any fee is due
You will know exactly what is included, what the timeline looks like, and what the total fee will be before you commit to anything. There is no obligation attached to an initial enquiry.
A draft before the final document
You will have one structured opportunity to review the work and identify anything that needs correction before the document is finalised. That round is built into the timeline and the fee.
A finished document, not a slide deck
The deliverable will be a written document with annotated diagrams, in an agreed format, with source notes. It is designed to be filed and referenced, not to be presented once and then shelved.
A direct answer if the work is not a fit
If your project needs something the available services cannot deliver well, you will be told that in the scoping response — plainly, and early enough to explore other options without having spent time or money on a poor-fit engagement.
Start here
If this approach makes sense for your project
A short description of the station, corridor, or infrastructure asset you have in mind is enough to begin a conversation. No forms — just an email.