Test sample data, expected outcomes, interruptions and recovery in one acceptance checklist.
A shared standard is needed to say it works
An automation reads files and creates a quotation table. The developer sees a result on screen and considers the work finished, while the business notices missing rows. Both parties assess the same output differently because acceptance criteria were not agreed at the outset. An acceptance test defines, in a shared and checkable way, which inputs should produce which outputs. The handover discussion can then rest on more than impressions.
Start testing while designing the process, rather than after the software is finished. Create a small sample dataset with the process owner and describe the correct result manually. Specify which fields a quotation calculation should use, when to skip a record and which actions need human approval. Let the developer work with the same examples. It then becomes clearer whether a newly discovered case changes the scope or violates an existing rule.
Choose representative data
Testing only clean records is easy, but everyday work is less tidy. Include empty fields, duplicates, incorrect dates, unexpected characters and different customers with the same name. Explain why each example was chosen. Do not move real personal data into a test environment unnecessarily. Preserve the real system's field lengths and formats when making representative data so that the examples resemble conditions the application will encounter.
A file's row count alone does not establish correctness. Check source-to-target field mapping, how totals are calculated and where invalid records go. If a record is skipped, its reason should be visible. Running a process again should not create the same record twice. You may share some examples with the developer and reserve others for handover checks; all expectations must still follow explicit business rules.
Write down the expected result
Give each test row fields for scenario, input, action, expected output and actual result. For example, a record with an empty product code may need to go to a review list instead of generating a quotation. Include the meaning of any error message in the expected result. Users should understand which field needs correction. Preventing a wrong action is as much part of acceptance testing as producing the correct output file.
Avoid vague wording for rounding, dates and text comparisons. Illustrate the rule accepted by the process owner with a concrete example. A result cannot be assessed until the price source and treatment of different currencies are clear. If the software must stop or refer a decision to an authorized person when it cannot decide, test that behavior separately. Continuing by guessing is not appropriate for every process.
Include failures and interruptions
Describe what should happen if a file is missing, the network disconnects or an external service does not respond. If a process stops halfway, will restarting damage earlier records? Can the user see the error? Does the activity log show which record completed? These questions test behavior that preserves the business's control as well as the successful workflow. Run interruption tests in an environment that cannot create live transactions.
Make recovery concrete too. If an incorrect output is produced, is source data preserved, can the previous output be archived, and which steps can be undone? Consider human approval or a separate checkpoint before automatically performing an irreversible action. Clearly identify test records as representative examples. Sending trial notifications to real customers or initiating real payments is not an appropriate shortcut for acceptance testing.
Test permissions and user flow together
Testing only with an administrator account can hide problems ordinary users face. Check which screens and actions are available to the relevant roles. An unauthorized user must be unable to perform the action, not merely unable to see its button. Record the account role used in the report. If the role that produced a successful outcome is unclear, the same behavior cannot be assumed for other employees.
Follow the user's steps from start to finish: selecting data, preliminary checks, execution, viewing results and resolving exceptions. If another application will consume the automation's output, include that transfer in the test. Creating the file may not be enough. Can the process owner use the result in everyday work and recognize an incorrect outcome? Define the automation workflow around these handover points.
Turn the handover report into a decision record
Separate passed, failed and unexecuted scenarios at the end of testing. For an outstanding issue, describe its impact, workaround and retest condition. Do not count unresolved cases as successes. The report should let the process owner decide whether to accept delivery or request changes. Recording the version, test date and dataset also helps determine which checks need repeating in a new version.
After initial acceptance, a small change may not require retesting everything. Rerun tests tied to the changed rule along with the core workflow. A previous passing result is not evidence for the new version. For data work, consider the scope of bulk data transfer together with record comparisons. A small, clear and repeatable test set can gradually become part of the business's change control.
Caution: a demonstration is not acceptance
A smooth workflow in a prepared video cannot replace an actual acceptance test. The test must be repeatable with an identified version and dataset. If there are performance expectations, describe the environment and measurement method; do not promise unverified timings or success rates. The aim is to make delivery boundaries visible and record which behavior the business accepts, rather than claim perfection.
At completion, keep the example used and the decision taken in the same place. The next colleague should understand why that approach was chosen. Resolve uncertainty with the responsible person instead of hiding it. A small practical trial may reveal more than an impressive but unused document. Improve that trial through regular feedback.
Frequently asked questions
What is the first step?
Choose one real task and a representative example, then describe the expected result.
Who should check it?
The process owner and the person using the application should review it together.
When should it be updated?
Recheck the affected steps whenever the process or application changes.
Is there a job that keeps repeating at your company? Tell us about it and we will build the tool that does it.
Tell us what you needOther articles
Why does the internal guide keep getting postponed?
Start with one task and identify the knowledge owner, review point and update process together.
5 October 2026Read →Whose code should be for the software you print?
Working software is not the same as having another team maintain it. Discuss code, documentation, data and access delivery together at the beginning of the project.
4 October 2026Read →Five questions to ask when choosing a software developer
The lowest bid alone is not the correct selection criterion. Evaluate maintenance, delivery, data, initial release, and training questions through the same sample process.
4 October 2026Read →Data transfer between two systems: integration or manual?
Writing the same information to two applications works for a while. When work is repeated, the decision should be made not only by speed but also by the need for data accuracy, traceability and maintenance.
3 October 2026Read →We have ERP, is there still a need for a special vehicle?
While ERP manages master records, some work may remain in emails and spreadsheets. The specific tool decision is made by first examining the possibilities of the current system and the actual process gap.
3 October 2026Read →Monthly plan or one-off payment?
A lower first quote does not guarantee a lower cost over two years. Compare both options with the same scope, maintenance obligations and exit conditions.
2 October 2026Read →Will AI replace an employee?
An employee’s job contains many different kinds of task. Assess these separately to understand where AI and automation may help.
2 October 2026Read →Customers missing appointments: do reminders help?
A reminder brings a forgotten appointment back into view; it does not guarantee attendance. Collect accurate contact details, send a confirmation and follow up with a short reminder before the appointment. Measure completed appointments, rather than bookings alone.
1 October 2026Read →What happens if your website is hacked, and how can you prepare?
When a change looks suspicious, protect the website and its users, preserve records and establish the scope. Restoring a clean backup is not enough on its own: close the entry point, secure relevant access and test the service again. Regular maintenance supports this preparation.
1 October 2026Read →Who benefits from an appointment system?
An appointment system can help when customers need to reserve a time slot and arranging those slots by phone interrupts your work. First clarify service durations, shared resources and exceptions.
22 September 2026Read →What if AI makes things up?
A fluent answer is not verified information. A business tool needs more than well-written output: it needs a workflow that prevents actions based on incorrect or incomplete information.
22 September 2026Read →Can a spreadsheet with thousands of rows be entered into a system in bulk?
In most cases, yes. The hard part is not the entry itself but getting the data into the shape the system expects and verifying that every row was really saved. If the system offers no bulk route, the work goes through the screen, and that depends on the rules of that system.
21 September 2026Read →Why does preparing a quote take so long?
Writing the quote does not take long; the time goes into hunting for the price, copying and correcting an old quote, and rebuilding the layout every time. Once the price list sits in one place and the rules are written down, a quote comes out in minutes.
21 September 2026Read →Which jobs are suited to automation, and which are not?
The job best suited to automation is one that repeats often, whose rules can be written down and whose data is already digital. Work that needs judgement, is full of exceptions or has its data on paper needs another step first.
18 September 2026Read →What if the AI assistant on your site gives a wrong answer?
The risk is real, but manageable. An assistant's wrong answer usually comes from guessing about something it does not know. The solution is to draw a clear line from the start around what the assistant knows and does not know, and to have it hand over to a person when it does not know.
18 September 2026Read →Is ranking in Google the same as being mentioned by AI?
Partly. Both draw on the same foundation, but they do not reward the same thing: Google ranks a page, while AI reads several sources, writes an answer and decides for itself who to mention in it.
17 September 2026Read →Why doesn't ChatGPT mention my company?
The reason is rarely “the AI does not like us”. Usually it is a technical block, scattered company information, or the company not being mentioned anywhere else online. All three can be fixed.
17 September 2026Read →What should your site have so AI describes you correctly?
When AI describes a company, it uses the clearest sentences it finds on the site. The list below goes page by page through where those sentences should sit, how they should be written and the markup machines will read.
17 September 2026Read →What is GEO? Being visible in AI answers
GEO (Generative Engine Optimization) is the work of making sure that when ChatGPT, Gemini, Perplexity and Google's AI Overviews answer a question, they find your business, describe it correctly and cite it as a source. It does not replace SEO; it builds on top of it.
17 September 2026Read →Will an AI tool learn my company's data?
Short answer: not in a tool running through a commercial API. But that answer depends on how the setup was done, so it is worth knowing what goes where.
16 September 2026Read →When does a spreadsheet stop being enough?
Excel is not a bad tool; it handles most jobs and more. The problem is carrying on with it for months after the point where it stopped being the right fit.
16 September 2026Read →Off-the-shelf software or custom-built?
The right answer depends on how specific the work is to you. Work that everyone does the same way is cheaper off the shelf; work you do your own way is cheaper built for you.
16 September 2026Read →