A launch film can make a new internal service look fully available when access is staged or capacity is limited. Employees need to know whether it is for them now.
Define eligibility, opening conditions and the first usable action before showcasing the service.
Define the service entrance before the showcase
Ask the service owner who can use the offering at release and what a valid first request looks like. A film that begins with the service’s full future capability may encourage requests the launch team cannot yet accept. The current access boundary should appear before the demonstration, not as a qualification after it.
Use a fictional request that fits the opening scope. Show the information required, the submission route and what the requester should expect next. Avoid a seamless jump from submission to a completed result if a review or eligibility check sits between them.
Keep future phases recognisable
If the film mentions later availability, distinguish an intention from a confirmed opening. Do not place every team on the same access graphic unless that is accurate. A maintained status page can carry changing eligibility, while the film explains the service’s purpose and current entry process.
Confirm the relationship with existing support routes. Employees may otherwise assume the new service replaces an older one immediately. Explain which work should continue through the existing arrangement and how the service owner will communicate a later transition.
The visual demonstration should use the permissions of the intended requester. An administrator’s account may show options that launch users cannot access. Have the system owner test the example from the actual audience’s perspective before production treats it as an available feature.
For acceptance, ask one eligible employee and one employee outside the initial group what they would do. Both should receive a useful answer, even if the second answer is to retain the current route. The resource succeeds when it creates appropriate requests and clear expectations. It should not create demand for an unavailable service merely because the launch treatment makes future capability look current.
Commissioning checks
| Input | Why it changes production |
|---|---|
| Approved service scope | Identify who can use it now |
| Access stages and exclusions | Show the actual entry step |
| Current request route | Keep future availability conditional |
An illustrative application
Imagine a shared design service opens first to selected teams. The film demonstrates a fictional request and identifies the pilot audience. Other teams are directed to the current arrangement rather than encouraged to submit requests that cannot yet be accepted. This example is hypothetical, not a Live Images project.
Check whether a viewer outside the launch group would reasonably assume they already have access. Do not imply a response-time guarantee, unlimited capacity or a replacement service unless those commitments are approved.
Discuss the production brief
Use the completed brief when you enquire with Live Images. Check the current service offering and agree who supplies the relevant subject expertise before committing to production.
Source and scope
Australian Government Style Manual video and audio is relevant background, checked 30 October 2026. This is original commissioning guidance, not legal, employment, safety or regulated professional advice. Prepared with AI assistance for Live Images.