Consider a fictional small cleaning business in Albany comparing a low-cost online enquiry tool. The business, people and events in this scenario are invented to illustrate task ownership. The example does not describe an actual local operator or offer cleaning, employment or pricing advice.

The owner wants enquiries to reach the right person without repeated copying. A supplier’s offer appears inexpensive, with an online form, a shared list and automatic notifications. The team examines the work behind those features before deciding whether the proposed arrangement is useful.

The first question concerns the task after the notification

In the scenario, a supervisor asks what happens when the form arrives. The owner initially assumes the notification means the enquiry has been handled. Staff explain that someone still has to check the request, ask missing questions and establish whether an assessment is needed.

The team defines enquiry received as a record awaiting review. It does not mean a service has been quoted, accepted or scheduled. That distinction prevents an automatic message from creating a commitment the business has not approved.

The owner records the initial goal: an authorised employee should be able to find the request, recognise its stage and identify the next action. The tool will be assessed against that task rather than the number of features included.

The low price leaves preparation with the business

The proposed supplier scope includes setting up the form. It does not include deciding which questions are necessary, writing the business’s service descriptions or checking existing customer records. Those tasks would remain internal.

Business.gov.au’s supplier guidance recommends documenting responsibilities and looking beyond price. Using that approach, the fictional team asks the provider to identify inclusions, exclusions and work that would require another quote. It does not assume a short setup description covers every practical decision.

The owner also asks who maintains the form when the service changes. A one-off build and a continuing content update are different tasks. They need separate responsibility even if the same person eventually performs both.

A sample request exposes an unclear handover

The demonstration uses fictional details in a safe environment. A request arrives without enough information to assess the work. One employee assumes the supervisor will follow up; the supervisor assumes the person who opened the enquiry will do it.

The team changes the proposed routine so each incomplete item has a named role responsible for clarification. It defines where the response will be recorded and how the next colleague will recognise the current position. A notification alone is not accepted as evidence of ownership.

The practical method reflects official productivity guidance on examining delays, repeated entry and responsibility. No measured improvement is claimed; the exercise has uncovered a question that the team must resolve before live use.

Access decisions reveal another part of the work

The owner asks whether everyone should receive the same permissions to make setup easier. The supervisor distinguishes reading an enquiry from changing service settings or exporting customer details. The intended role needs to complete the task without unnecessary broader authority.

The ASD’s access guidance recommends limiting permissions to duties and reviewing them as roles change. In the scenario, that becomes a question for the supplier about ordinary staff accounts, not a reason to share the owner’s credentials.

The team allocates responsibility for adding and removing access, keeping recovery information current and checking changes. Those continuing tasks are included in the comparison even though they are not extra buttons in the form builder.

The comparison includes staff time and unfinished work

The owner prepares a short scope record:

  • The supplier’s setup and support deliverables.
  • The internal decisions about questions, wording and stages.
  • The role responsible for each enquiry and exception.
  • The training, access and maintenance tasks still required.
  • The evidence needed before the tool is accepted for live use.

Business.gov.au’s digital tools guidance recommends considering full costs and separating essential features from optional ones. The fictional owner therefore compares the proposal with improving the existing shared record, using the same task and internal time assumptions.

For the training check, another employee will follow the instructions without the owner explaining each step. The team will record where assistance is needed and update the authoritative guide. A delivered form and a staff member who can explain an incomplete enquiry are treated as separate acceptance questions.

The next decision remains deliberately limited

The scenario ends with a revised brief and questions for the supplier, rather than an invented purchase success. The business still needs confirmed terms, a safe test and evidence that staff can operate the process. The advertised price has become one part of an understandable scope.

The lesson is to locate the work behind a low-cost offer and give it an owner. A useful tool can support a process, but it cannot decide the business’s responsibilities merely by sending a notification.