SFST Report – Unofficial Tool

Analysis By Mobexer

When an app is meant to document field sobriety testing and DUI-related reports, trust matters more to me than visual polish. SFST Report – Unofficial Tool is a business app from Bonsaisoft LLC built around that practical need, using an NHTSA-based approach to help organize observations and report details. I see it as a focused digital worksheet rather than a complete replacement for official procedures, agency systems, or professional judgment.

That distinction is important from the first use. The app can make a structured report easier to prepare, but it does not turn a phone into a legal authority. Its value depends on careful input, local procedure, and the person completing the documentation. Used with that mindset, it may reduce the friction of keeping field notes consistent. Used as though the app itself validates a stop or test, it becomes the wrong tool.

How the app fits a real reporting workflow

A narrow business tool with a clear purpose

I appreciate that this is not trying to be a general police toolkit, a driving game, or a broad case-management platform. Its purpose is concentrated on SFST report documentation and DUI reporting. That focus can be useful for someone who repeatedly needs a guided place to record observations instead of building a report from a blank document every time.

A realistic scenario would be an officer finishing a standardized field sobriety test and using the app soon afterward to organize the relevant observations while the sequence is still fresh. Rather than relying on scattered handwritten notes and later reconstructing the order of events, the user can work through the reporting process in a more deliberate way. The benefit is not dramatic automation; it is the reduction of small omissions and inconsistent formatting.

I would still treat the finished report as a working document that needs review. A structured screen can encourage completeness, but it cannot know whether an observation was accurate, whether a test was administered correctly, or whether a local policy requires wording that differs from the app’s approach. Those checks remain the user’s responsibility.

What “unofficial” should mean in practice

The word “Unofficial” in the app’s name is more than a minor label for me. It sets the right expectation: this is a convenience tool, not a government-issued record system. Even if its workflow follows familiar NHTSA-based concepts, I would not assume that every jurisdiction treats its output as an accepted official form.

Before using it in active work, I would compare its sections with the forms, policies, and evidence requirements used by the relevant department or court. That comparison is especially worthwhile if reports may later be reviewed by supervisors, attorneys, or a judge. The app can support documentation, but a department’s approved process should remain the controlling reference.

Where it is stronger than a blank notes app

The usual alternative is a notes application, a paper form, or a general document editor. Those options are flexible, but flexibility can become a weakness when the same details must be captured repeatedly. A blank note does not remind me how I want to organize a sequence, and a paper form can be difficult to correct, search, or preserve neatly.

This tool’s advantage is its subject-specific purpose. It gives the user a starting structure designed around field sobriety reporting rather than asking them to invent one. That makes it more practical for repeated, similar documentation than a generic notes page. The trade-off is equally clear: a general document editor is better when the report needs extensive custom narrative, attachments, agency-specific language, or a workflow outside the app’s intended scope.

Learning the workflow before relying on it

I would not wait until a demanding field situation to discover how the screens are arranged. A short practice session can reveal whether the sequence feels natural, whether the available fields match the user’s normal report style, and how much typing is required. This is one of the less obvious ways to get value from a specialized reporting app: test the workflow in a calm setting, then decide which parts genuinely save time.

That practice also helps separate app friction from procedural friction. If a report feels slow because the underlying event requires careful documentation, no app can remove that responsibility. If the problem is repeated navigation or unclear field order, knowing that in advance lets the user prepare a backup method instead of discovering the limitation during a live case.

Device and version considerations

The current version is 1.11, and the app requires Android 6.0 or newer. That makes it suitable for many older Android devices, which may matter in workplaces where phones are not replaced frequently. I would still test it on the exact device intended for field use, because screen size, keyboard behavior, battery condition, and handling with gloves can affect the experience more than the version number suggests.

The app is free to install, while in-app purchases range from $1.99 to $29.99 per item. I would check the purchase prompts carefully before building a department-wide workflow around it. A free starting point is useful for evaluation, but the total cost of the functions a user actually needs should be understood before treating it as a long-term operational solution.

Trust, controls, and handling sensitive reports

What I can responsibly expect from the visible product description

The app’s stated purpose tells me what it is designed to do, but it does not by itself answer every privacy question I would ask before entering sensitive information. Reports connected with DUI investigations can contain personal details, observations, locations, and legally important narratives. I would therefore avoid assuming anything about storage, encryption, cloud synchronization, account access, sharing, retention, or deletion unless those controls are clearly shown inside the app or in its current privacy materials.

This is not a criticism of one particular design choice; it is a practical boundary for responsible use. A reporting tool can be helpful while still requiring the user to understand where information goes and who can access it. If those answers are not clear during setup or review, I would use the app only for limited evaluation and keep official records in the approved system.

Permissions deserve a deliberate check

On Android, I would inspect the permissions requested during installation and first use rather than approving every prompt automatically. The relevant question is not whether a permission sounds convenient, but whether it is necessary for the exact workflow I intend to use. A documentation app should earn access to sensitive device functions through a clear explanation of how those functions support reporting.

I would also revisit permissions after updates. A change in version can alter the way an app requests access, and a permission that was irrelevant to my original test may become visible later. This is a simple habit, but it is particularly important when the phone is used for professional records rather than casual personal notes.

Account controls and the boundary of user agency

Before entering identifying information, I would look for clear controls around accounts, sign-in, report ownership, export, deletion, and sharing. The practical concern is not just whether I can create a report; it is whether I can control the report afterward. A user should know how to correct an entry, preserve a final copy, remove a draft, and prevent accidental disclosure.

If the app does not make those choices obvious, I would keep the content minimal during testing. For example, I could use a fictional scenario to learn the form flow instead of entering a real person’s name or case details. That approach gives me useful hands-on knowledge without exposing sensitive information while I am still deciding whether the tool belongs in a professional process.

Three moments when data handling matters most

The first sensitive moment is initial entry. Field reports may combine personal identifiers with observations that could affect a legal case. I would avoid typing more detail than the workflow requires and would not treat a phone screen as a secure place simply because it is password protected.

The second is the period between saving and finalizing. Drafts can remain on a device, appear in recent-app views, or be visible to someone who picks up an unlocked phone. I would lock the device promptly, avoid leaving a report open in public, and check whether the app offers a clear way to distinguish unfinished work from a completed record.

The third is export or transfer. Moving a report to email, messaging, cloud storage, or another system can create additional copies. I would use only an approved destination and confirm the recipient before sending anything. If the app’s output is intended to support an official record, I would preserve the original workflow required by the relevant organization rather than relying on an informal share.

Why a paper form can still be the better choice

Paper is not automatically safer or better, but it can be preferable when a department already has a controlled form, when device use is impractical, or when connectivity and battery concerns make digital entry unreliable. A general notes app may also be a better fit for a user who needs extensive narrative and already has a secure, approved records process.

On the other hand, paper introduces its own risks: handwriting can be unclear, pages can be misplaced, and later transcription can create errors. My choice would depend on the surrounding controls, not on the app alone. SFST Report makes the most sense when its structured workflow fits an existing process and the user has a clear, authorized method for preserving the result.

Who should consider it, and who should skip it

I can see this app helping a user who regularly documents standardized field sobriety observations and wants a dedicated Android workflow for organizing those reports. It may also be useful for training or internal evaluation, provided that fictional or non-sensitive information is used until the organization approves the process.

I would skip it as a primary solution if I needed a full records-management system, department-specific approval chains, extensive evidence handling, or a guaranteed official submission path. I would also avoid depending on it if the user cannot verify its data practices and permissions to the standard required for sensitive case information. In those situations, an approved agency platform or controlled form is the more responsible option.

What the adoption numbers suggest, and what they do not

The app has passed 10K+ installs, with an average rating of 4.2 from 35 ratings and 14 reviews. Those figures suggest that people have found enough value to try and rate it, but they are not a substitute for testing it against a real organization’s requirements. A small review base can provide useful signals while still leaving many device types, workflows, and professional expectations unrepresented.

Its content rating is Everyone, which describes the age suitability of the app rather than the sensitivity of the reports a user may enter. I would not confuse an Everyone label with a promise that professional case information is appropriate to store without additional safeguards. The responsibility comes from the content being entered and the system surrounding the app.

My practical setup recommendations

My first step would be to install it on a test device or use a fictional case. I would walk through a complete report, note which fields are mandatory or easy to overlook, and see how corrections work. I would then compare the resulting document with the organization’s required format before considering real use.

Next, I would record the app’s visible permission requests and review its account and data controls. I would decide in advance where completed reports may be stored and who may receive them. This avoids the common mistake of finishing a sensitive report and only then improvising a transfer method.

Finally, I would create a short backup plan. If the phone fails, the battery runs low, or the app cannot accommodate an unusual situation, the user should still be able to document events through an approved alternative. A specialized app should reduce routine friction, not become a single point of failure.

My cautious verdict

I find SFST Report useful in concept because it addresses a specific documentation problem instead of pretending to solve every part of DUI casework. Its NHTSA-based focus and dedicated reporting purpose give it a clearer role than a blank notes page, especially for repeated field sobriety documentation. The app is free to start, runs on Android 6.0 or newer, and comes from Bonsaisoft LLC, but the in-app purchase range means I would examine the actual cost of the required workflow before wider adoption.

My recommendation is conditional rather than automatic. I would suggest it to someone who wants to evaluate a focused reporting aid, understands that it is unofficial, and can verify that its permissions, storage behavior, account controls, and output fit an approved process. I would not recommend placing sensitive case information into it casually or treating its report as a replacement for official documentation.

The best reason to try it is structure; the best reason to be careful is control. If the app helps you capture observations consistently while leaving your organization’s privacy and records requirements firmly in charge, it can be a worthwhile companion. If those requirements cannot be checked clearly, a trusted official system or established paper workflow is the better choice.

FAQ