How we take a requirement through to a working system.

• Consolidate the operating record into one system of record with clear module boundaries.
• Model roles first, so reporting and data access follow the organization chart.
• Ship module by module rather than as a single large release.

• Modular application layer over a relational system of record.
• Role-based access enforced server-side at the data layer.
• Reporting views derived from the same source of truth as operational screens.

• Web application
• Relational database
• Role-based access control
• Reporting layer

• Server-side authorization for every data path.
• Least-privilege roles per module.
• Change history retained for operational records.

• Module-by-module rollout with the operating team using each module before the next was built.
• Reporting added after the underlying records were stable.

Live and in continuous use, with modular expansion and an AI insights layer planned.

Status reflects OMS IT™ internal use of the system. No external client metrics are claimed.

• Map the newsroom workflow end to end before introducing any AI assistance.
• Use AI to assist editorial steps — drafting support, verification prompts, summarisation — with journalists retaining the decision.
• Keep publishing authority with named human editors.

• Editorial workflow application with staged review.
• Assistive AI layer invoked per editorial step, not as an autonomous publisher.
• Distribution and audience data reported back into the same workflow.

• Web application
• Content workflow model
• LLM-assisted editorial tooling

• Editorial roles and publishing permissions separated.
• Human approval required before publication.

• Newsroom pilot first, with a narrow set of assisted steps.
• Wider syndication and creator tooling deferred until the pilot workflow is proven.

In development — newsroom pilot stage.

Status is self-reported project maturity. No audience, revenue or performance figures are claimed.