When paperwork has to follow a roadside sobriety assessment, the difficult part is often not remembering what happened. It is recording it in a consistent, readable way while the details are still fresh. SFST Report – Unofficial Tool is a business app built around that narrow task: documenting field sobriety testing and DUI-related reporting with an NHTSA-based structure. I found it most useful as a focused report companion rather than as a general police-management system.
The app is developed by Bonsaisoft LLC and is available free of charge, although it includes optional in-app purchases ranging from $1.99 to $29.99 per item. It is rated for Everyone and belongs to the business category, but its practical audience is much more specific: officers, agencies evaluating a documentation aid, instructors, and professionals who need a repeatable way to organize SFST observations. With an average rating of 4.2 from around 35 ratings and over 10K installs, it has a modest footprint, yet enough real-world attention to make it worth examining closely.
From roadside observations to a usable report
Starting with the situation in front of you
The strongest way to understand this app is to picture the starting condition. You have completed, or are in the process of documenting, a standardized field sobriety test. The report needs more than a conclusion. It needs a clear account of what was observed, how the test was conducted, and what happened at each stage. A blank note-taking app can capture words, but it leaves the structure entirely to the user. SFST Report is intended to reduce that problem by giving the documentation a dedicated framework.
That focus matters because a general form builder can be too open-ended. Users may forget a field, mix observations with conclusions, or describe similar tests in noticeably different ways. A specialized report tool encourages a more orderly sequence. In my view, that is the app’s main value: it turns a task that can feel like scattered note-taking into a guided record-building process.
I would not treat it as a replacement for training, departmental policy, legal advice, or an official records system. The word “unofficial” in the app’s name is important. It signals that the tool should be handled as an aid to documentation, not automatically assumed to be an agency-approved form or a substitute for required procedures. Before relying on any generated report in active work, I would compare its workflow with local rules and the exact forms your organization accepts.
Building the report in a deliberate order
The practical workflow begins with entering the relevant case information and then working through the sobriety-test documentation. I prefer this kind of sequence to writing a narrative from memory because it separates basic identification from observations. That separation makes it easier to review the report later and notice whether a key part of the examination has been left vague.
A useful habit is to enter information as close to the event as your circumstances allow, while keeping your attention on safety and the person being assessed. The app can help organize the record, but it should not become a distraction during an active roadside interaction. If I were using it in a real workflow, I would make brief contemporaneous notes when necessary, then complete or verify the structured report at the first appropriate opportunity.
The NHTSA-based orientation gives the app a recognizable purpose. It is not simply a generic incident diary with a sobriety-test label attached. Its value depends on whether its prompts and organization fit the standardized field sobriety testing process you are trained to follow. That makes it more relevant to an SFST workflow than a blank document, while also making it less flexible for unrelated reports.
Why structured entry can improve consistency
One non-obvious benefit of a dedicated form is that it can expose the difference between an observation and an interpretation. For example, “the subject stepped off the line” is an observation, while “the subject was impaired” is a conclusion. A well-organized report encourages the first kind of detail to be captured before the second. That distinction is valuable when another person later reviews the file and needs to understand how the conclusion was reached.
I also see a practical advantage for repeated work. If several reports are completed during a shift or across different days, a consistent structure reduces the mental overhead of deciding what to write next. It can make reports easier to compare internally and easier for a supervisor or records staff member to read. This is not the same as proving accuracy, but it can improve the discipline of the documentation process.
Another useful approach is to treat each section as a checkpoint rather than rushing to the end. If an observation is unclear, it is better to resolve that uncertainty while the context is available than to rely on a polished but incomplete summary later. The app’s value is therefore tied to how carefully the user works through it; it cannot recover details that were never observed or recorded.
A realistic roadside-to-office scenario
Imagine an officer completes an SFST encounter during an evening shift. Once the immediate roadside responsibilities are handled, the officer opens the app and starts a report while the sequence of events is still easy to recall. Basic case details are entered first. The officer then works through the relevant test documentation, recording what was seen instead of jumping directly to a final opinion.
Before handing the report onward, the officer reviews it for internal consistency. Are the observations written in plain, specific language? Does the sequence make sense? Are there unexplained gaps? This review is where a structured app can be more useful than a loose note: the user has a defined record to inspect rather than a page of unorganized text.
The completed report may then be used as part of the agency’s broader documentation process. That handoff is where expectations matter. If a supervisor, prosecutor, records clerk, or another reviewing officer needs a particular official format, the app’s output may require checking, copying, or transferring into an approved system. I would plan for that step rather than assuming that a mobile report automatically becomes the final institutional record.
Handoffs are where good documentation is tested
A report is rarely created only for the person who enters it. Other people may need to read it without being present at the original event. That means clarity at the handoff is just as important as speed during entry. I would use the app to support a concise, chronological account and then verify that the receiving workflow preserves the meaning of the original observations.
This is also where a specialized tool can expose a trade-off. Its focused structure may help the original user remember the expected categories of information, but another reviewer may still need context that does not fit neatly into a form. If the app allows additional explanation, those notes should be precise and relevant. If the approved process requires a separate narrative, the structured report should be treated as a supporting record rather than the entire case file.
For agencies considering adoption, I would test the handoff before encouraging routine use. Have one person complete a sample report, another review it, and a third attempt to place it into the existing records process. That exercise can reveal whether the app saves time or simply moves the work to a later stage. It is a more meaningful test than asking whether the form looks convenient on a phone.
What the finished result is good at
The finished result is most useful when the goal is a focused, repeatable SFST record. It can give the user a clearer path from observations to documentation than a generic notes app, and it keeps the subject matter centered on DUI reporting and field sobriety testing. For an individual who already understands the procedure and wants a dedicated digital aid, that narrowness is a strength.
I would especially consider it for training environments or personal workflow evaluation, where the user can compare the app’s organization with established instruction and local forms. It may also help someone identify which details need closer attention before finalizing a report. The benefit is not that the app makes a judgment for you; the benefit is that it can make the record-building process more deliberate.
The free entry point lowers the barrier to trying it. That is helpful for a user who wants to inspect the workflow before deciding whether optional purchases are worthwhile. Still, “free” should not be confused with “cost-free” for an organization. Time spent validating the form, training users, checking compatibility with policy, and managing the resulting records can matter more than the download price.
Where the workflow breaks down
The first point of friction is the app’s unofficial status. A tool can be well designed and still be unsuitable as an official agency record. If your department requires a specific form, signature process, evidence system, or retention procedure, this app may be only an auxiliary step. In that situation, an approved records platform or agency-issued mobile form is the better choice, even if it feels less convenient.
The second concern is scope. This is not the app I would choose for broad incident management, case collaboration, scheduling, evidence tracking, or a complete law-enforcement records workflow. Its purpose is much narrower. Users looking for one application to manage every part of a DUI case will likely find the experience incomplete and may be better served by a specialized departmental system.
There is also a human-factors limitation. A structured screen can encourage thoroughness, but it can also tempt someone to focus on completing fields instead of observing the situation. The safest workflow keeps the interaction and the user’s training first, with the phone used only when appropriate. No form should encourage hurried entry, divided attention, or filling gaps with assumptions.
Another trade-off is flexibility. A dedicated SFST report can be easier to follow than a blank page, but a blank page can accommodate unusual circumstances more naturally. If an encounter does not fit the expected sequence, the user needs a reliable way to explain that difference. When the app’s structure feels too restrictive, an official narrative process may be more suitable.
Device and version considerations
The current version is 1.11, and the app requires Android 6.0 or later. That makes it accessible to many older Android devices, which may be useful for organizations working with mixed hardware. At the same time, compatibility is only one part of a deployment decision. I would test the exact phones used in the field, especially if reports need to be reviewed or transferred on a different device afterward.
Because this is a mobile documentation tool, practical testing should include screen readability, typing speed, report review, and the transition from the completed form to the next records step. A workflow that feels fine in a quiet office may be less comfortable in a vehicle or under time pressure. The app should be evaluated in the conditions where it will actually be used, without allowing that testing to interfere with real duties.
Who should use it and who should skip it
I think SFST Report is a reasonable fit for a trained user who wants a focused way to organize field sobriety test documentation and understands that the result still needs to fit local procedure. It is also worth considering for someone comparing digital workflows before proposing a broader documentation solution. The narrow purpose makes it easier to judge than a large all-in-one platform.
I would skip it if you need an officially integrated case-management system, a team-based records environment, or a guaranteed replacement for agency forms. I would also avoid treating it as a learning substitute. Someone who has not been trained in SFST procedure should not rely on an app’s prompts to determine how testing is conducted or how impairment is assessed.
The optional purchases deserve a practical look as well. Since individual items range from $1.99 to $29.99, I would first use the free portion to confirm that the workflow matches your needs. For personal use, a purchase may be reasonable if it removes a genuine obstacle. For an agency, the more important question is whether the paid capability improves the complete handoff into approved records, not simply whether it adds convenience inside the app.
My overall experience with the workflow
What I like most is the app’s discipline. It is aimed at one recognizable job and encourages the user to build a report around field sobriety test documentation instead of improvising every time. That can make the input stage more orderly, the review stage more focused, and the conversation with a supervisor or records reviewer easier to follow.
What keeps me from recommending it without qualification is the gap between a useful report aid and an official system. The app can support careful documentation, but it cannot decide whether the document satisfies a particular department, court process, or records policy. The user remains responsible for accurate observations, appropriate procedure, and the final approved handoff.
My recommendation is therefore conditional but positive: try it if you need a dedicated SFST reporting aid and can validate it against your existing workflow. Use it to improve structure, not to replace judgment or training. If the report transfers cleanly into your required process, its focused design may save effort. If it creates duplicate entry or conflicts with official forms, a department-approved alternative will serve you better.
For a free business app with a specific purpose, its 4.2 average and modest install base suggest a tool that has found a practical niche rather than a universal solution. I would approach it as a specialized companion, test the entire journey from observation to handoff, and keep a clear boundary between convenience and compliance. Used that way, it can be genuinely helpful; used as a substitute for an official reporting system, it is the wrong tool for the job.
