A shortlist for digital operations should reflect how your Albany business receives work, makes decisions and checks results. Use the steps below to compare a manageable set of options against one operational task. The example is recording an incoming delivery and passing a discrepancy to the appropriate person, rather than replacing every business system at once.
Step 1: choose the task boundary
Write down what starts the process and what counts as a useful finish. For a delivery record, arrival might start it, while an accepted record of received quantities and unresolved discrepancies ends the chosen task. Payment approval and supplier negotiation can remain separate processes.
Keep that boundary consistent while comparing options. Otherwise, one supplier may demonstrate only data entry while another includes checking and follow-up, making their prices and apparent speed difficult to assess fairly.
Step 2: observe the existing handover
Ask the person receiving deliveries to show how quantities, item identifiers and damage concerns are recorded. Ask the next person what information they need. Use a suitable example with unnecessary personal or commercial details removed from the planning copy.
Record where information is entered again, where clarification is needed and who makes each decision. A gap in your own approval rule will not necessarily be fixed by another application. Resolve the rule separately from selecting software to support it.
Step 3: write essential requirements in task language
The government’s digital tools guidance recommends separating necessary and optional features. Translate that distinction into actions, such as recording a discrepancy against the correct delivery, rather than vague requirements for an advanced dashboard.
- Identify the delivery and relevant items.
- Keep received quantities separate from expected quantities.
- Make an unresolved discrepancy visible.
- Preserve the reason for a later correction.
- Provide the next authorised person with usable context.
An optional feature can remain on the list without becoming a deciding factor. Explain why each essential requirement matters so a supplier can respond to the operational need rather than guess what the business means.
Step 4: identify the required permissions
Receiving an item, changing an approved stock record and authorising payment are different actions. The ASD’s access control guidance recommends permissions aligned with duties and reviews when roles change. Ask which roles the proposed tool can support.
Do not test only through the owner’s account. Prepare a demonstration for the ordinary receiver and the person reviewing a discrepancy. Note any action that requires a broader permission than the role should reasonably have.
Step 5: give candidates a common example
Create an invented delivery containing an expected item, a short quantity and a damaged item. Include a later correction to the initial record. Give each candidate the same explanation of the task and the same information.
Ask staff to follow the record into the next stage. Can the reviewer distinguish a missing item from a changed expectation? Record what was demonstrated, what was only promised and what depends on additional configuration.
Step 6: compare the complete commitment
Include setup, record preparation, staff practice, support and ongoing charges. Ask what happens when an item identifier changes or the business adds another receiving person. Mark estimates and unresolved pricing questions rather than filling them with invented figures.
Consider staff coordination as well as subscription costs. A tool that removes one paper form but requires repeated checking in another system may shift work rather than reduce it. Measure the full boundary you defined at the start.
Step 7: check useful record transfer
Inspect a sample export with the person who would receive the information. It should preserve enough meaning to connect the delivery, items, status and correction history needed for your task. A successful download does not demonstrate a complete migration.
Ask who assists with transfer, what it costs and how access changes when the service ends. Check your actual recordkeeping obligations independently instead of assuming the supplier’s default storage period is sufficient.
Step 8: record the shortlist decision
Keep a brief, dated comparison for the receiving team showing demonstrated requirements, limitations and open questions. Do not rank a candidate as capable merely because the feature name appears in its brochure. Seek clarification for any essential action staff could not complete.
Include the attachments in that decision. If staff use a photograph to explain damage, establish how it remains connected to the correct delivery and who can view it. A file stored in a separate message thread may be difficult for the reviewer to find. Test the connection and ask what happens when an attachment is replaced or removed under your approved process.
Choose the next step deliberately: a supervised trial, another demonstration or a pause while you resolve a business rule. Assign an owner and review date. Your shortlist should leave the Albany team able to explain the choice and the work still required before regular use.