A fictional Albany wholesale nursery has stock lists, order emails and delivery notes spread across several services. The owner wants specialist help but is unsure whether the problem is software, record design or unclear responsibilities. This scenario shows how the business could prepare a better set of questions before paying for a solution. It does not describe an actual nursery, consultant or completed project.
The first question becomes more precise
In the scenario, the initial request is to “put everything in one place”. Staff then point out that the same item can appear under different descriptions, and an order may change after a delivery list has been prepared. Moving the files together would not necessarily resolve those differences.
The owner would revise the brief: the business needs to identify the current accepted order and understand how changes reach the people preparing it. That question connects information management with a real task. A specialist could then investigate the records required rather than begin with a preferred application.
A small sample exposes the information problem
The team would select a limited, authorised example and remove details not needed for the consultation. It would show the original enquiry, accepted order, amendment and delivery record. Each document would be labelled with its source and date so the specialist can see the sequence.
The NSW Government’s systems information guidance discusses understanding business information needs, integration accuracy and documentation. Written for government recordkeeping, it offers useful planning questions here without imposing a system requirement on a private WA nursery. The fictional team would use those questions to explain what each record means.
They would avoid silently correcting the sample before presenting it. A difference between records is evidence of the problem to investigate. The owner would distinguish a factual discrepancy from a staff member’s theory about why it occurred.
The team asks about authoritative information
The specialist would be asked which record should carry the accepted arrangement, who may change it and how earlier versions remain understandable. An item description, unit of sale and requested quantity would need consistent meaning. The business would not assume that matching a name proves two entries refer to the same thing.
- Which record is authoritative at each stage?
- How is a change distinguished from a new request?
- Which identifiers should connect related records?
- Who checks conflicting information before work proceeds?
- How can another staff member reconstruct what happened?
Those questions do not require the owner to decide the technical design in advance. They help the specialist understand the operating consequence of an information gap. A proposed solution could then be tested against the task instead of judged only by how many files it can store.
Retention and access receive their own questions
The owner would ask what must remain available after an order is completed and who should be able to access it. Staff preparing a delivery may need current instructions without unrestricted access to unrelated financial or customer records. The appropriate permissions would depend on duties and the actual system.
The government’s record keeping guidance identifies different business record categories and recommends checking applicable requirements. In the scenario, the owner would seek appropriately qualified advice about retention obligations rather than assume a software consultant determines every legal or tax requirement. No blanket deletion period would be built into the brief.
The business would also ask how useful records can be retrieved if a supplier relationship ends. An export should be inspected for meaning, attachments and links between records. A download containing rows of unexplained values would not necessarily support the work the business needs to continue.
The proposed solution is tested through the same example
After the specialist explains an approach, the team would ask how it handles the sample order and amendment. They would test a normal case, a duplicate and a missing piece of information through a safe arrangement. They would also check who receives an exception when a connection between systems fails.
The review would include the work required to prepare and maintain the information. A new structure can require data cleaning, staff training and continuing ownership. The team would ask which tasks the specialist performs, which remain internal and what evidence will show that handover is complete.
The consultation ends with a reviewable decision
The owner would retain a brief summary of the problem, options, assumptions and unanswered questions. A proposal should identify its scope and limits, including any specialist advice still required. The team could then choose a bounded next step rather than commit to a broad migration without understanding the records.
For an Albany business, preparing better questions means making the information problem visible. This fictional nursery’s useful starting point is not a complete technical specification. It is a clear task, a small traceable example and an honest account of what the business cannot yet explain.