A small pilot can show whether tracking online enquiries helps an Albany business follow work through to a clear next step. The idea might be a shared queue, a simple status record or an improved handover. Avoid these mistakes when planning the pilot, so it tests a useful operating question instead of creating a second set of records staff must maintain indefinitely.
Mistake 1: tracking everything before defining the purpose
A spreadsheet with many columns can look thorough while leaving the team unsure what decision it supports. Start with a specific gap, such as enquiries without an assigned owner or requests waiting for clarification. Define the task the pilot should make easier to understand.
The government’s digital performance guidance recommends starting with goals before selecting measures. Apply that to enquiry tracking: choose information because it supports the task, not because a platform can export it. A total message count alone does not show whether customers received a useful response.
Mistake 2: confusing an enquiry with a confirmed order
A customer asking about a service has not necessarily accepted a quote or secured a booking. If the pilot merges those stages, the report can overstate completed work or send an inappropriate confirmation. Staff need a shared understanding of what each status means.
Use a small set of clear stages, such as received, clarification needed, assessed and next step communicated. Adapt them to the actual workflow. Keep an unknown or conflicting status visible for review rather than forcing the record into a completed category to tidy the queue.
Mistake 3: creating a parallel record with no authority rule
If the existing system and pilot record can be changed independently, staff may not know which one is current. A request amended by telephone might update one place and remain unchanged in another. The pilot then creates the discrepancy it was intended to reduce.
Decide where the authoritative information belongs and how the pilot refers to it. Use a reference rather than copying the full conversation where possible. Explain who updates a status and what evidence supports the update. Keep the established operating process available until the proposed arrangement has been checked.
Mistake 4: collecting more customer information than needed
A review may need the enquiry category, current stage and next owner without needing photographs, full contact details or private history. Copying everything into another shared file adds access and maintenance responsibilities. Choose the minimum information appropriate to the question and protect it.
Use sample or appropriately authorised records during testing. Confirm any safe demonstration method before a tool can send real messages or create live bookings. Explain the exercise to staff and keep test entries distinguishable from genuine work, including how they will be handled afterwards.
- What does the record need to show?
- Which source contains the supporting detail?
- Who can view or change the pilot record?
- How are duplicates and test entries identified?
- What happens to the pilot information when the exercise ends?
Mistake 5: testing only the easiest path
An ordinary complete enquiry may move through the system easily while an amendment or missing detail reveals a gap. Include those cases and a handover to another authorised staff member. Observe what happens without coaching every action, and record any help needed.
The Digital Transformation Agency’s research guidance discusses task-based testing and revising prototypes. It is government service guidance, but its distinction between testing a task and collecting preferences is useful here. A small business pilot does not establish universal usability or compliance.
Mistake 6: counting faster entry as less administration
Staff may enter a request quickly while spending more time clarifying, correcting or reconciling it later. Include the whole task and any new work the pilot creates. Ask whether the record actually helps the next person act, not only whether the form is convenient to complete.
Record the period and conditions checked. Different enquiry types, staffing or workload can affect a comparison. Keep estimates separate from observations and avoid turning a short exercise into a precise annual saving or a claim about every Albany customer.
Keep a dated note of changes to the pilot’s fields or status definitions. Otherwise two reporting periods can appear comparable even though staff were recording different information or interpreting completion differently.
Mistake 7: keeping the pilot without reviewing it
Set a decision date and define what evidence to bring. Summarise the original gap, cases tested, findings and unresolved questions. Decide whether to adopt, revise or stop. If continuing, assign ownership, access review and maintenance rather than leaving the creator responsible by default.
For an Albany business, a useful enquiry tracking pilot makes responsibility and next actions clearer. The result may be a simple shared record or a better use of an existing service. Its value is the evidence it provides for that decision, with the limits of the trial and the continuing work stated honestly.