Skip to main content
Ottili LD3 · Newsroom

A newsroom pipeline for local publishers and content teams

Ottili LD3 Newsroom joins source monitoring, topic queues, fact quality, publishing levels and editorial review into one pilot for local media. It starts from a verified fact base — not the raw source text.

Join the Ottili LD3 newsroom pilot
Source monitoring

Everything the newsroom hears, in one place

Ottili LD3 monitors regional feeds, wires, social channels and tip inboxes with provenance and attribution — no signal arriving through a side door.

Local feeds and wires

Connect municipal RSS, regional newswires, agency feeds and your own CMS. Ottili LD3 keeps the original link and attribution for every ingested item.

Social and tip inboxes

Pull mentions, community tips and press-room inboxes into one monitoring surface so nothing arrives through a side channel.

Editor briefing docs

Drop standing briefs, style guides and embargo notes. Ottili LD3 uses them to weight and label incoming signals instead of guessing your intent.

Freshness and quiet signals

Monitoring tracks how stale a source is and flags when a usual beat goes silent — so an empty desk is visible, not hidden.

Topic queues

Signals become triageable topics

Verified source items land in a shared queue, ranked by relevance and recency. Editors promote, merge or dismiss — duplicates collapse into one thread.

1

Incoming signals land in a queue

Every verified source item becomes a candidate topic in a shared queue, ranked by relevance, recency and your briefs.

2

Editors triage and merge

Editors promote, merge or dismiss topics. Duplicates from multiple feeds collapse into one thread with all source links attached.

3

Topics become assignments

A promoted topic opens an assignment with its fact base, linked sources and a publishing-level target, ready for drafting.

Fact quality

Every claim stays traceable

Extracted facts carry their source link and attribution. Conflicting sources are held for editorial resolution, never silently averaged.

Provenance on every claim

Each extracted fact carries its source link and original attribution, so a draft can always trace a statement back to where it came from.

Conflict detection

When sources disagree, Ottili LD3 holds the claim for editorial resolution instead of silently averaging two contradictory reports.

Structured fact base

Verified material is reduced to entities, dates, figures and quotes — the shared basis every channel package is written from.

Editorial review

Humans and AI review before anything ships

Reviewers see the draft beside its facts, comment, reject or request changes. External posts wait for a named approver before they ship.

Human review with context

Reviewers see the draft beside its source facts and can comment, request changes or reject — no blind approve button.

AI review before publish

Automated checks cover tone, accuracy against the fact base and source alignment, surfacing risks for the editor to confirm.

Approval gates

External posts wait for a named approver. The decision is recorded on the package, matching the Ottili ONE approval system.

Publishing levels

From draft to live, with explicit levels

Each package moves through levels. When a source is unverified or no approver is available, publishing holds rather than shipping unvetted copy.

Draft

Planned

Generated from the fact base, not yet visible to anyone outside the newsroom.

Internal review

Beta

Shared with the editorial desk for comment and AI review checks.

Approved

Beta

A named approver has confirmed the piece and its sources.

Scheduled

Planned

Queued for a publication window across the chosen channels.

Published

Beta

Pushed to the connected channel with delivery status tracked per asset.

Paused / unavailable

Planned

When a source is unverified or an approver is unavailable, publishing holds rather than shipping unvetted copy.

Multi-channel output

One package, every surface

The same verified fact base powers the news site, newsletter and social — each channel gets the right cut, all sharing one approval trail.

News site

Turn a verified topic into an accurate explainer or breaking-news brief with citations and a clear review trail.

  1. 1Promote a topic from the queue
  2. 2Draft from the verified fact base
  3. 3Human + AI review
  4. 4Approve and publish to the news site

Newsletter

Assemble the day's approved packages into a newsletter blurb that stays consistent with the published articles.

  1. 1Pull approved packages
  2. 2Generate a newsletter cutdown
  3. 3Editorial pass for voice
  4. 4Send to the connected list

Social

Cut one package into on-brand posts and threads per network, each held for a named approver before it goes live.

  1. 1Derive post cutdowns from the package
  2. 2Adapt tone per network
  3. 3Hold for named approver
  4. 4Publish to connected accounts
Honest pilot reality

How the pilot handles real newsroom states

A pilot should hide no gap. Here is how Ottili LD3 Newsroom behaves when sources are quiet, conflicting or unavailable.

Empty desk

When no sources are connected or a usual beat goes quiet, the queue shows the gap instead of inventing filler. Editors see what is missing.

Ingest in progress

While feeds are being fetched and verified, items appear as pending with a source count, so the desk knows work is arriving, not stuck.

Conflict or broken source

A conflicting claim or an unreachable source is held for editorial resolution. Ottili LD3 never publishes from an unverified or contradictory input.

Publishing paused

If no approver is available or a channel credential lapses, publishing holds. The package stays in its last safe level until released.

Ready for the pilot?

Use Ottili LD3 Newsroom as a pilot

Ottili LD3 Newsroom is a pilot for invited local publishers and content teams. Request pilot access or explore Ottili LD3 as a standalone product.

Request pilot accessPrivate BetaExplore Ottili LD3