Interviews are schedulable. Writing is not. That asymmetry shapes every journalist's week: sources have windows, you take them, and the calendar fills with reporting. The draft accumulates pressure invisibly until Wednesday becomes Thursday and Thursday becomes a 1am filing. The same pattern, every time — because the calendar never showed the imbalance until it was already a crisis.
Tempo analyzes reporting, writing, research, and admin as distinct layers. You see exactly how many hours are going to writing versus everything else — and SIGNAL alerts you when reporting is consuming the time a draft needs before Friday.
A story due Friday looks identical to a coffee chat on Thursday. No visual gradient of urgency. The pressure builds silently as the week fills with interviews, and by Wednesday the remaining writing time has been scheduled away. The same crisis, the same pattern, every time — because the calendar never showed it coming.
A source opens at 2pm. You take it. Another at 4pm. The day becomes a reporting day — and the draft that needed three uninterrupted hours gets pushed to tomorrow, which already has three interviews. Writing time cannot defend itself in a generic calendar. It needs its own layer.
A journalist who logged 30 hours might have spent 4 of them writing. The other 26 went to interviews, research, editorial calls, and pitch revisions. Without separating those categories, there is no way to see whether the calendar is producing publishable output — or just sustained activity.
Reporting, Writing, Research, and Admin each get their own layer. Tempo tracks how hours are actually distributed across input and output work — so you can see whether writing time exists in the week before a deadline makes the question urgent.
Source interviews, press conferences, on-the-record calls, background conversations, and in-person reporting. Input — essential, but it should be proportional to the output time available. Its own layer makes the ratio between gathering and writing immediately legible.
Drafting, revision, and final polish. The output layer — the only one that produces published work. Writing loses to everything schedulable because it cannot book itself into a meeting slot. As its own layer, Tempo shows at a glance whether real writing time exists or has been crowded out.
Document review, database searches, background reading, and verification. The connective tissue between reporting and writing — often invisible on a generic calendar, but with real time requirements that compound as deadlines approach. Its own layer makes the investment visible.
Pitch writing, editorial emails, expense reports, contract reviews, and publication admin. Non-writing overhead that is necessary but must not dominate. SIGNAL monitors this layer and alerts when admin time is consuming hours that should be protected for drafting.
Reporting and Interviews at 58%. Writing at 9%. Deadline Friday. The implication is immediate — the story is not getting written this week. That signal only surfaces when the two categories are distinct and visible. On a generic calendar, both look like calendar events with no indication that one is consuming the other.
SIGNAL watches your layer ratios relative to deadlines in the calendar. When writing time is below what a piece requires and the deadline is approaching, it surfaces the gap in your weekly PULSE — before it becomes a Thursday night problem that everybody could have seen coming and nobody did.
Connect your calendars in under two minutes. Reporting, Writing, Research, and Admin in separate layers. SIGNAL watching the ratio before deadlines arrive. PULSE showing the honest picture of your week — so the imbalance is visible on Monday, not Thursday night when the draft is due in eight hours.