Voice Typing for Security Guards: Incident Reports and Daily Activity Logs Without the Keyboard

Short answer: Security guards can dictate incident narratives, daily activity report entries and pass-down notes on an iPhone at the post, at speaking pace instead of thumb-typing pace. Speak the chronological narrative while it is fresh, type the identifiers such as times, plates and badge numbers, then proofread before you submit.

Nobody gets into security work for the writing. But ask any officer what takes up the most attention on a quiet post and the answer is paperwork: the daily activity report, the incident report when something happens, the pass-down for the next shift, the visitor log, the note to the site supervisor about the broken gate arm. Most of it gets written on a phone, standing up, often at three in the morning, and often right after an event that has your heart rate up.

That combination is where reports go wrong. Not because officers cannot write, but because thumb-typing a three-hundred-word narrative on a phone screen is slow enough that details get rationed. The description of the subject gets shorter. The exact sequence of who said what gets compressed to "verbal altercation occurred." Two hours later, when a supervisor asks what the individual was wearing, the answer is in your memory but not in the report.

This guide is about using voice typing to close that gap: how to dictate the narrative while it is fresh, what to speak and what to type, how to handle radio traffic and wind and a subject standing ten feet away, and where the line is on what you should never say out loud on a post.

The report is the product

A security officer's incident report is read by people who were not there. The client's facilities manager. The account manager at your company. Possibly a police officer, an insurance adjuster, or an attorney, months later. Every one of them will judge what happened based on what you wrote, and the standard is the same across the industry: chronological, factual, objective, complete. What you saw and heard, in the order you saw and heard it, without opinion.

The saying every training class repeats is that if it is not in the report, it did not happen. That is not quite literally true, but it is how the report will be treated. A narrative that says "subject became aggressive" is nearly useless. A narrative that says the subject stepped within arm's reach, raised his voice, and said a specific sentence is evidence. The difference is detail, and detail is exactly what gets cut when every word costs a thumb-tap.

Officers who write on a phone are competing against their own memory decay. Details you can see clearly in the minutes after an event are gone by the end of the shift. The faster you can get them into text, the more of them survive.

The arithmetic of a phone report

Adults type around 40 words per minute on a full keyboard, and practised typists reach 80 to 100. Thumb-typing on a phone is slower for almost everyone, and slower still with cold hands, gloves, or a radio in the other hand. People speak at roughly 130 to 150 words per minute.

A proper incident narrative runs three to five hundred words. On a phone keyboard that is a long, uncomfortable stretch of standing and tapping, during which you are not watching your area. Spoken, the same narrative is a few minutes. A daily activity report entry of one or two sentences becomes something you can do without breaking stride. The point is not speed for its own sake. It is that when words are cheap, you stop rationing them, and the report gets the detail it was supposed to have.

What officers actually write on a shift

It helps to see how much of the job is text.

• Daily activity report entries. Time-stamped lines through the shift: patrols completed, areas checked, doors found unlocked, lights out, alarms, contacts with the public. Dozens of short entries a night.
• Incident reports. The long-form narrative when something happens: trespass, theft, medical, fire alarm, a dispute, property damage, a suspicious vehicle. Who, what, when, where, and what you did about it.
• Pass-down notes. What the next shift needs to know: an ongoing issue, a contractor expected at six, a door that will not latch, a visitor who was refused entry.
• Visitor and vendor logs. Names, companies, times in and out, who they were visiting, badge numbers.
• Maintenance and hazard observations. The leak in the stairwell, the broken light on level two, the ice by the loading dock. Often an email or a message to the site contact.
• Written statements. After a serious incident, a first-person account that may be handed to police or an insurer.
• Messages to supervisors and clients. Text, email, or a note in the company's reporting app.

Almost all of it goes into a text field on a phone, either in a guard-tour or incident-reporting app your company issues, or in Notes, Mail, or Messages. A voice keyboard works in any of those fields, because it is a keyboard. Wherever your cursor is, that is where the words land.

The rule: speak the narrative, type the identifiers

This is the single most important habit, and it is what separates a usable dictated report from a risky one.

Narrative is what voice is good at. Descriptions of people and clothing. The sequence of events. What you observed. What was said. What you did in response. Dictate all of that in full sentences, in order, and you will get a better narrative than you would ever type with your thumbs.

Identifiers are different. A licence plate, a badge number, a unit number, a time, a door number, a spelling of a surname. Speech recognition, from any provider, can mishear a letter or a digit, and it will do so silently: the text looks confident and plausible. A plate that reads one character wrong is worse than no plate, because someone will act on it. So type those, or dictate them slowly and deliberately and then check each character before you move on.

A practical pattern: dictate the sentence with a placeholder, then go back and fill in the exact value by hand. "At approximately [time] I observed a grey sedan, plate [plate], parked in the fire lane at the north entrance." Then tap into each bracket and type it. Voice Keyboard Pro's Voice Edit also lets you speak a change to fix text, which is handy for a misheard word, but for plates and badge numbers, use your thumbs. The stakes justify the ten seconds.

The guide to voice typing for police officers makes the same argument for a report that gets read in court, and the reasoning carries over directly. Security reports are less often litigated, but when they are, the same standard applies.

What a dictated narrative sounds like

Here is an illustrative example of the kind of narrative that dictates cleanly. It is invented for this article, not a real report, and the details are placeholders.

At approximately [time], while conducting a foot patrol of the east parking structure, I observed a male subject on level two attempting to open the driver's door of a dark blue SUV, plate [plate]. The subject was approximately six feet tall, wearing a black hooded sweatshirt, grey sweatpants and white trainers. I announced myself as security from approximately twenty feet away. The subject looked toward me, released the door handle, and walked quickly toward the level two stairwell without responding. I did not pursue. I notified dispatch by radio at approximately [time] and requested that the vehicle owner be contacted. I remained in the area and observed no further activity. No damage to the vehicle was visible from the exterior. Camera coverage of level two should be reviewed for the period [time] to [time].

Notice what is there and what is not. There is a description specific enough to be useful. There is a sequence. There is a distinction between what was observed and what was done. There is no speculation about the subject's intent, no adjectives about his character, and every identifier is a bracket to be typed. Spoken, that narrative takes about a minute and a half. On a phone keyboard, most officers would take ten minutes and cut half the detail.

The setup on post: your iPhone

For most officers, the phone is the whole toolkit. Voice Keyboard Pro is a custom iPhone keyboard with a built-in mic button for dictation in any iOS app. Switch to it with the globe key, tap the mic, speak, and the text appears in whatever field is active: your company's reporting app, Apple Notes, Mail, or a message to your supervisor. It handles punctuation and capitalisation as you speak, so the narrative comes out as sentences rather than a wall of lowercase.

Three features earn their place on a post.

• Voice Edit. Say a correction and the text updates. "Change trainers to sneakers." "Change north entrance to northeast entrance." Faster than selecting and retyping with one hand while holding a radio in the other.
• Two-way translation while dictating. Security teams are often multilingual, and so are the people you deal with. The keyboard covers 24 languages, so a pass-down note can be dictated in one language and land in another, or you can compose a message to a contractor in theirs. Read the translated text before you send anything that matters. Machine translation is good, not infallible.
• Swipe typing. For the short stuff, when speaking would be inappropriate or a single word needs adding.

The keyboard needs Full Access to reach the network for transcription, and it needs a data connection. A basement post with no signal is a keyboard-only post; dictate the narrative in Notes when you reach coverage, then paste it into the report.

Voice Keyboard Pro is free with daily limits, and Pro is $4.99 a month or $34.99 a year. Many officers will find the free tier covers a normal shift, and the ones writing multiple long incident reports a night will know quickly whether Pro is worth it.

The setup at the desk: if it is a Mac

Guard desks are more often company PCs than Macs, and the Mac app is for Mac. But plenty of officers write up longer reports at home, and supervisors and site managers writing up their own summaries frequently do it on a Mac. For them, the menu bar app is the better tool.

Hold a hotkey, speak, release, and the text appears at the cursor in whatever app is in front: a browser-based reporting portal, a Word document, an email. Two Mac features matter here.

Smart Vocabulary is a personal dictionary with replacement rules. Every site has its own names: post designations, building codes, client company names, the surnames of regular contractors, the shorthand your team uses on the radio. Add them once and they come out spelled correctly every time, and a replacement rule can expand a spoken shorthand into the full phrase your reports are supposed to use.

Meeting Mode with speaker detection and AI notes suits the guard mount at the start of shift, a post-incident debrief, or a client review meeting. It picks up scheduled meetings from the calendar, records with speaker labels, and produces notes you can share. Use it for internal briefings where everyone in the room knows it is running. Do not use it to record members of the public, subjects, or client staff without their knowledge; that is a legal question that varies by jurisdiction and a trust question that does not.

Night shifts, fatigue, and the report you write at four in the morning

The quality of a report written at 04:00 by someone eight hours into a twelve-hour shift is not the quality of a report written at noon. Fatigue shows up in writing as omission: sentences get shorter and the narrative gets vaguer. Speaking is more forgiving of tiredness than typing. You can talk through an event coherently long after your thumbs have stopped cooperating.

A useful habit is to dictate a rough narrative into Notes immediately after any event, even before you open the formal report, while the sequence is still sharp. Then clean it up. The guide to voice typing for night shift workers covers the broader approach to writing when you are running on the wrong side of your body clock.

Noise, radios, and wind

Posts are noisy in ways offices are not. Traffic, HVAC plant, a parking structure that echoes, a radio that talks over you mid-sentence, wind at a perimeter gate.

Hold the phone closer to your mouth than feels natural, speak at a steady pace, and release the mic while the radio is talking rather than trying to dictate over it. If your radio is on a shoulder mic, turn your head away from it when you speak. Constant background noise, like a generator, transcribes better than sudden noise, like a door slamming, so pause for the slams. Speaking in a low, clear voice beats shouting, which distorts. The guides to fixing dictation in background noise and speaking clearly for dictation go deeper on technique.

Mobile patrol: parked only

If you drive a patrol route, the temptation is to dictate the last stop's notes while rolling to the next one. Do not. Dictation still requires you to look at the screen to start it, check it, and stop it, and the report can wait the two minutes until you are stationary. Pull in, put the vehicle in park, dictate the entry, move on. That is the same position we take in the guide to voice notes while driving, and it applies with more force when the vehicle has a company name on the door.

What not to dictate out loud

Voice typing has one obvious limit that typing does not: other people can hear you. On a security post that matters more than in an office.

• Not in earshot of the subject. Never dictate a description of someone while they can hear you doing it. Step away, or type, or wait.
• Not in earshot of the public or client staff. A lobby full of employees does not need to hear the details of the medical incident on the fourth floor. Move to the desk or the guard room.
• Not anything confidential to the client. Access codes, alarm procedures, the client's internal disputes. If it should not be overheard, it should not be spoken.
• Not on a post where phones are prohibited. Some sites forbid personal phones on post entirely, and some prohibit third-party keyboards on company devices. Your post orders and your company's device policy win. Check before you rely on any tool.

Also check whether your company has a position on third-party tools being used to write company reports. Most will not have thought about it. Some, especially on government or critical-infrastructure contracts, will have a policy, and it may be strict. Ask before, not after.

Privacy: what happens to your words

Incident reports contain names, descriptions, and sometimes medical details. It is reasonable to ask where the audio goes. Voice Keyboard Pro's transcription engine processes the audio to produce text, and the server stores only operational pings. No audio is kept and no transcript content is kept. The report exists in the app you dictated it into and nowhere else on our side.

That is our position. Your company's reporting app has its own, and the client may have requirements on top. Know all three.

A realistic shift

An evening-to-morning shift at a commercial property might look like this once dictation is part of the routine.

• 18:00. Guard mount. If the supervisor runs it on a Mac, Meeting Mode produces notes so nobody has to write them by hand.
• 18:30 to 22:00. Foot patrols. Each daily activity report entry is one dictated sentence at the end of each patrol, typed times, thirty seconds each.
• 22:40. A door found propped open at the loading dock. Dictate the entry, type the door number, photograph, send the maintenance note to the site contact from Mail, dictated.
• 01:15. A confrontation with an intoxicated individual in the lobby. Handle it. Once the individual has left and the area is clear, step behind the desk and dictate the rough narrative into Notes while it is fresh. Type the times. Then open the formal report, dictate the clean version, proofread every sentence, submit.
• 05:30. Pass-down for the day shift. Dictated, sent, done before the relief arrives.

The difference is not that the shift is shorter. It is that the 01:15 report contains the detail it should have, and that you spent the quiet hours watching the property instead of hunched over a phone.

How you know it is working

The test is not that reports get written faster, although they will. The test is that they get longer where they should: more specific descriptions, more complete sequences, more of what was actually said. If your supervisor stops asking follow-up questions because the answers are already in the report, the tool is doing its job. If a report ever goes to police or an insurer and stands on its own, that is the standard met.

Officers in adjacent roles will recognise much of this. The field service technicians guide covers the same on-site, standing-up, phone-in-hand documentation problem, and the property managers guide covers the other side of many of the same incidents.

Frequently asked questions

Does voice typing work inside our company's guard-tour or incident-reporting app?

If the app has a standard text field, yes, because Voice Keyboard Pro is a keyboard and works wherever the iOS keyboard appears. A small number of apps use custom input fields that behave differently; if the mic does not respond in one, dictate in Notes and paste. Check with your company whether third-party keyboards are permitted on the device.

Is it accurate enough for an incident report?

For the narrative, yes. For identifiers such as plates, badge numbers and times, type them or check them character by character. Proofread every report before you submit it, exactly as you would a typed one. Dictation removes the typing, not the responsibility.

Will it add punctuation and capital letters?

Yes. Speak in normal sentences and the text arrives punctuated and capitalised. You do not have to say "period" after every sentence.

What about names and site-specific terms?

On the Mac, add them to Smart Vocabulary once and they come out right every time. On the iPhone, use Voice Edit to fix a misheard name by saying what to change, or type it.

Does it work without a signal?

No. Transcription needs a data connection. On a dead-zone post, dictate when you have coverage and paste the text where it belongs.

Can I record a subject or a member of the public with Meeting Mode?

Do not. Meeting Mode is for meetings where participants know they are being recorded, such as a guard mount or a debrief. Recording the public or a subject without their knowledge raises legal issues that vary by jurisdiction and will not help your report or your employer.

Is my report content stored anywhere by Voice Keyboard Pro?

No. The server stores only operational pings. No audio and no transcript content is retained. The text exists only in the app you dictated it into.