Reporting services for public-interest media records
Irvako Newsroom takes on discrete assignments: documenting what aired, mapping likely switching paths, and writing clear, correction-ready reports. Work is scoped, quoted, and delivered with a transparent evidence log.
What we do (and what we do not)
The work is editorial and technical: we treat a broadcast moment as an artefact with edges, timing, and provenance. We do not impersonate broadcasters, we do not run influencer “reaction” campaigns, and we do not publish raw material by default. Deliverables are written to stand up to scrutiny: when something is an inference, it is labelled as an inference.
Commissioned verification memo
A structured memo that answers a narrow question: what likely aired, what is supported by recordings, and where the gaps remain. We anchor claims to observable elements: timecodes, lower-thirds, and the specific on-screen geometry that distinguishes a routed desktop from a graphics template.
- Evidence ledger: capture types, timestamps, and a short integrity note for each artefact
- Cut map: where recap clips diverge from the live segment
- Inference boundary: a plain-language section separating what is known from what is plausible
- Correction path: what additional sources would change the assessment
Timeline reconstruction
We reconstruct the sequence around an on-air anomaly: what was visible, for how long, and what followed. For live panels, the smallest details matter: a half-beat delay, an earpiece cue, or a lower-third refresh that indicates the control room changed states.
Signal-path explanation
A plain-language explanation of plausible routing paths, written for readers who are not engineers. We explain common failure points—mislabelled sources, rehearsal leftovers, or a desktop capture accidentally punched to programme—without turning the write-up into a how-to manual.
Deliverables that travel well
Canadian live panels and recaps
Work is limited to public-interest media moments in Canada: live panels, current-affairs segments, and the official recap ecosystem that follows. We focus on what changed between live and published versions.
No impersonation, no “official” claims
Irvako Newsroom is not a broadcaster and does not represent any network. If an assignment requires access or authority we do not have, we say so and do not take the work.
Publication-ready language
You get writing that reads like a newsroom document, not a marketing deck. We keep a corrections mindset: the wording is chosen so it can be updated without rewriting history.
How commissioned work runs
The process is designed to avoid two predictable failures: treating a single screenshot as definitive, and treating a technical mishap as a moral story. We handle the artefact first, then the meaning.
-
01
Define the question and boundaries
We start with one narrow question: for example, whether an overlay was a graphics template or a routed desktop capture. You tell us what you have. We tell you what else would be useful, and what we will not attempt to infer.
Label: scope and constraints -
02
Collect and triage artefacts
Recordings are logged with a short integrity note. A PVR capture, a phone recording, and a clean HDMI capture each have different strengths. We prioritise material with on-screen graphics intact, because those elements act like a built-in checksum.
Label: capture integrity -
03
Write the memo and evidence ledger
We produce a report that makes its own limits visible. Observable facts are anchored to timecodes. Interpretations are marked as interpretations. If a routing hypothesis depends on missing data, that gap is described, not filled with bravado.
Label: correction-ready language -
04
Hand-off and update window
Deliverables include a short update window, so that late-arriving artefacts can be incorporated. If a revision changes meaning, we add a clear change note rather than silently rewriting.
Label: transparent updates
Pricing and quoting
Quotes are based on complexity, not on drama. The unglamorous variable is the artefact mix: one high-quality capture can settle a question quickly, while several low-quality clips can prolong it. We scope deliverables before we quote, so the cost aligns with the work.
Was it an AI prompt window, or a graphics template?
We look for the tells: window chrome, cursor artefacts, scaling behaviour, and whether the overlay sits “above” the programme output or replaces it. The goal is not to accuse; it is to describe the object accurately.
What changed between live and the official recap?
We produce a cut map: continuity edits, missing seconds, and the placement of jump cuts. Recaps are not inherently suspicious; the question is whether the edit removes a public-interest artefact.
Request commissioned reporting
Use this form to describe the broadcast moment, share timecodes, and explain what deliverable you need. We will reply with clarifying questions only if necessary, then provide a scoped quote.