What the Studio is
The Studio is focused software used to keep a content item and the decisions around it connected. Working material can move through a deliberate sequence: creation establishes a reviewable version, planning records intended destinations and timing, review produces an explicit decision, and distribution records the outcome of an authorised release attempt.
That sequence matters because content can appear ready while important information is still missing. A date does not prove approval. An approval does not apply to every later edit. A release request does not prove publication. The Studio’s model keeps those states separate.
How the private workflow is organised
Create and organise
Keep assets, copy, source details and version identity together so the current review candidate is clear.
Plan and review
Record proposed destinations, times, conditions and the people responsible for checks and decisions.
Distribute and verify
Where a destination is configured and authorised, submit approved work and record the actual state returned.
Connected-platform boundaries
Connections are not assumed to be permanently available. A third-party destination can expire authorisation, change requirements, delay processing, reject a submission, restrict an account or remove content. Plans and intended times are therefore instructions, not guarantees.
Human review remains part of the publishing decision. The operator is responsible for the intended audience, rights, disclosures, final version, destination and settings.
Access and privacy
Access is limited to the operator and people expressly authorised by the operator. Streamlists does not currently provide public registration, a trial, a subscription, a public login or a public Studio dashboard. The Privacy Notice explains the categories of data that may be handled when a platform is configured.