A daily read on the nine roads staff travel to reach the office: which route is hard today, when to leave and when to send people home, which gate to brief, and the patterns underneath. Built for Operations and HR from live driver reports — no staff member or journey is tracked.
Every corridor into the office, ranked by how much attention it needs right now. A route is disrupted when a gateway or a checkpoint on it was reported closed or held in the last 6 hours, and on watch when there is an incident near it or several points reporting delays.
No data is kept as its own answer: it means nobody has reported that road recently, which is not the same as clear.
Staff who do not live in Ramallah reach the office along — road corridors. These are the routes a car actually drives, not straight lines — each one traced through the live road network.
They are not equal journeys: the shortest is —, the longest — — before a single checkpoint is counted.
Along them sit — checkpoints, gates and roadblocks that can stop a journey. Every figure on this page is built from what drivers themselves reported passing them — — reports since —.
For each corridor: the share of all reports along it that said something other than open. This is the plainest measure of how often a member of staff on that road meets an obstacle.
— is the hardest by a clear margin — — of reports on that route are not open, against — on the easiest.
The same corridor is not equally hard all day. This is the share of reports that were not open, hour by hour, in Palestine time — read it as the chance a journey starting then meets something.
The pattern is consistent across corridors: mornings are the clear window, and the evening return is the worst part of the day. Across — the calmest departure hour is —, and the worst is —. The faint lines are the individual corridors — pick a city to bring one forward.
The return leg is the office's own decision, and it is the half of the commute Operations actually control. The calmest hour to release staff on this route is —; the evening peaks at —, and the climb towards it starts well before.
Every corridor against every day of the week. Darker means a larger share of reports that were not open — the days on which staff on that road are most likely to be delayed.
The corridors do not share a bad day, so no single office-wide rule fits them: —
If one day has to bring everyone in — an all-hands, a workshop, a visit — the working week's easiest is —, and its hardest is —.
A corridor is only as open as its narrowest point. These are the individual checkpoints that generate most of the difficulty on — — the ones worth naming in a security brief.
Knowing which gate is the problem is what turns "the road is bad" into a decision: a different route, a different hour, or a day worked from home.
Each city is entered through a small number of gateways. When the primary one closes, there is usually a known alternative — this is the operational knowledge the tracker carries, per city.
Use it the way a driver would: check the primary, and know the detour before setting off.
Live from the collector. A corridor is flagged when any checkpoint on it is currently reported closed or holding an army presence.
— of — corridors carry such a report from the last — hours. Points the crowd has gone quiet about are drawn faintly — a closure reported last month is history, not news, so only recent ones count here.
This report re-reads the wb-alerts collector — crowd reports from public Telegram road channels, parsed continuously and matched to a checkpoint registry — through one question: how hard is it for a member of staff to get to the Ramallah office? Routes are computed on a local routing engine against the real road network; a checkpoint is attached to a corridor when it lies within — of the driven route.
It is a measure of reporting, not of delay. The collector records what drivers said, so a corridor with more traffic produces more reports, and a quiet corridor may be quiet because no one is posting rather than because it is clear. Treat these as relative risk between routes and hours, not as minutes lost. Nothing here is personal data: no staff member, vehicle or journey is identified or tracked.
Head counts stay on your machine. If you enter how many staff travel each road in chapter 01, the numbers are held in this browser's local storage and used only to weight what you see — how many people a closure reaches, and which weekday suits the most staff. They are never transmitted, and clearing them removes them.
—
Keyboard: ← → chapters, T theme.