Konetic One Australian Community Services Management Platform Logo
Live feeds

Publish once, governed all the way through

Menus, events, news and service hours, drafted by your team, approved before they go out, and live on the client portal and the branded app within seconds.

koneticone.com/erp/live-feeds
Client portal and branded app
Publishing activity, last 12 weeks
last 12 weeks
Active feeds
9
+2
Items published
128
+14
Pending approval
3
queue
Median approval time
22m
-9m
Feed types in use
  • Meal menus3 feeds
  • Events2 feeds
  • News3 feeds
  • Service hours1 feed
This week
  • Items drafted17
  • Items rejected1
  • Reached app subscribers412
Why it matters

Built on the Konetic One ERP, this module shares one record across the whole org. No duplicate data entry, no third-party tools to stitch together, and no version-control surprises at audit time.

Community services providers publish a constant stream of small, time-sensitive content.

This week's meal menu, an upcoming social outing, a change to service hours over a public holiday, a news update about a program change. Handled by email and noticeboard, that content is stale by the time it reaches a client or family member.

Konetic One's live feeds module gives your team a structured place to draft that content, route it through an approval step, and publish it straight to the client portal and your branded mobile app. A feed is a channel with a content type, menu, event, news or hours, and every item drafted against it carries its own publish and expiry window.

Nothing goes live without someone approving it, and every submission, approval and rejection is written to a permanent audit trail, so the person who asks why a menu changed gets an answer instead of a guess.

4
Content types supported
Always
Approval before publish
Portal + app
Publish destinations
Every action
Audit trail
Three things to know

The thinking behind the module

Outcome-first design. Every interaction is in service of a measurable result.

Draft where the work already happens

Menus, events, news and hours are drafted inside the ERP by the people who own that content, not emailed to someone else to publish.

Nothing goes live unapproved

Every item moves through a submit and approve step before it reaches a client, so a typo or an unconfirmed change never reaches a family member first.

One publish, two destinations

An approved item pushes to the client portal and the branded mobile app together, so there is never a version mismatch between the two.

How it flows

The path through the work

A typical end-to-end flow inside the module.

01
Create the feed

Name, slug and content type set once.

02
Draft the item

Title, details, publish and expiry window.

03
Submit for approval

Item enters the shared approvals queue.

04
Reviewer decides

Approve to publish, or reject with a reason.

05
Publish live

Pushed to the portal and the branded app.

06
Trail retained

Who drafted, approved and when.

The publishing surface

Drafting, approval and reach, rendered live

What a week of publishing looks like from draft to the client portal and the app.

Governance

From draft to published, with an approval gate that cannot be skipped

Every item passes through the same four stages, regardless of content type.

Drafted
Title, details and publish window set by the content owner.
done
Submitted
Item enters the shared approvals queue.
done
Reviewed
A second person approves or rejects with a reason.
active
Published
Live on the portal and branded app together.
pending
Reach and evidence

Where it lands, and who touched it along the way

The same publish action reaches every destination, and the trail behind it is permanent.

Publishes to
Client portal
Published instantly
Branded app
Push to subscribers
News feed
3 active channels
Menu feed
Weekly cadence
Audit trail
  1. Menu drafted, week of 14 Jul
    K. Nguyen, kitchen coordinator · Mon 8:12am
  2. Submitted for approval
    K. Nguyen · Mon 8:20am
  3. Approved and published
    R. Aziz, clinical manager · Mon 9:01am
  4. Viewed by 214 portal accounts
    Client portal · Mon, ongoing
Approval before reach

No item is visible to a client or family member until a second person has approved it.

Full audit trail

Every draft, submission, approval and rejection is retained with who and when.

One publish, every surface

The client portal and your branded app always show the same approved version.

Deep dive

Why teams pick this

Why governed publishing matters for regulated providers

A menu, an outing or a change in service hours looks like low-stakes content, until a family member acts on the wrong version and a provider has to explain the gap. Live feeds treats publishing as a controlled workflow rather than a casual update.

Every item is drafted, submitted, and either approved or rejected with a reason, and none of those states can be skipped from the client-facing side. That is the same discipline providers already apply to clinical documentation, applied to the content that clients and families actually read day to day.

When a regulator or a quality committee asks how a menu change was communicated, the answer is a timestamped record, not a recollection of who sent what email.

One publish, no version drift between the portal and the app

Providers that maintain a website, a portal and a mobile app separately inevitably end up with content drifting between them, an outing listed on the app but missing from the portal, or a menu updated in one place and not the other. Konetic One's live feeds publish to the client portal and the branded mobile app from the one approved item, so there is exactly one version of the truth at any moment.

Publish and expiry windows are set on the item itself, so time-sensitive content, this week's menu, a one-off event, a temporary change in hours, retires itself without anyone having to remember to take it down. The feed becomes the single channel your organisation uses to talk to clients and families, with governance built into how it gets there rather than bolted on afterwards.

In practice

What it looks like across sectors

Three real-world examples drawn from Konetic One customer setups.

Residential aged care, catering

This week's menu, approved before it reaches a resident's family

The kitchen coordinator drafts the week's menu against the meals feed. A clinical manager reviews it for dietary flags before approving, and the approved menu appears in the client portal and the branded app at the same moment, replacing last week's version everywhere at once.

  • Dietary review before publish
  • One version live everywhere
  • Full history of past menus retained
Community and social programs

An outing announced once, seen everywhere

A program coordinator drafts an upcoming social outing as an event item with a start time and RSVP note. Once approved, it appears in the app for subscribed families and on the client portal, without a second copy being typed into a newsletter or noticeboard.

  • Event content type with start and end time
  • Approval catches date or venue errors early
  • Retired automatically after the expiry window
Multi-site provider

Public holiday hours communicated consistently

A single hours feed is updated ahead of a public holiday and approved by an operations lead. Every site's clients see the same change in the portal and the app, removing the risk of one site publishing an update that another site forgets.

  • One feed, one source of truth
  • Approval reduces publishing errors
  • Change visible in the audit trail
Integrations

Plays nicely with your stack

Native to Konetic One, open to everything else.

Client portalKonetic One branded mobile appCommunications moduleDocument storagePush notification deliveryRole-based approval routingCompliance evidence retentionRuby AI assistant
FAQ

Frequently asked

Menus, events, news and service hours, each with fields suited to that content, service date and dietary notes for menus, start and end time for events, and so on.

See it on your data

Ready to see live feeds on your live data?

Sign in Book demo