A guard notices something worth remembering. A gate that sticks. A visitor who seemed off. A reminder for whoever takes over the post next.

Where does that note actually go? Half the time, nowhere useful. A scrap of paper on a desk, a text to a supervisor that gets buried, a mental note that’s gone by the next shift.

This is the small, unglamorous problem Pocket Book is built to solve. Not incidents, not formal reports. Just the ordinary notes that keep a site running smoothly when they’re written down and quietly cause confusion when they’re not.

What Pocket Book Actually Is

Pocket Book lives inside AVES under Logs & Reference, right next to SOP. Where SOP holds your uploaded documents and procedures. The tool holds the shorter, dated notes guards and managers log day to day.

It’s not an incident report. It’s not an occurrence log. Think of Pocket Book as a proper electronic guard logbook, the digital version of the notebook a guard used to carry, minus the part where that notebook gets lost, left in a shack, or scribbled in handwriting nobody can read a month later.

Some companies still call this kind of tool an e-pocketbook for guards, which is a fitting description. It’s personal, it’s quick to use and it’s meant to be checked constantly, not opened once a week.

How Creating an Entry Actually Works

Here’s exactly what the Pocket Book create flow looks like, based on the real screens, not a guess.

From the Home dashboard, scroll to the Logs & Reference section and tap Pocket Books. From there, tap Create.

The form asks for three things. A Date, picked from a calendar. A Time, picked from a clock selector. And a Message field, where the actual note goes.

Fill those in and tap Submit. That’s the entire entry process. No categories to choose, no severity level, no extra fields to slow a guard down mid-shift.

That simplicity is worth noting on purpose. A digital guard logbook that takes thirty seconds to fill out gets used. One that takes five minutes gets skipped, especially at 3am on a slow night when logging a small observation doesn’t feel urgent enough to justify the effort.

How Reviewing Past Entries Actually Works

Tap Records from that screen and you land on a screen titled Details of Pocket Book. It opens to a full month calendar, with today’s date already selected by default.

Two things stand out here. First, the calendar lets you move month to month using the arrows on either side of the month name, so pulling up an entry from six weeks ago is a couple of taps, not a search through a notebook.

Second, there’s a toggle above the results labeled My Books and Staff Books. My Books shows entries the current user logged. Staff Books shows entries logged by staff. Switching between them is one tap.

If there’s nothing logged for the date you’ve selected, the screen tells you so, though it’s worth knowing the exact wording differs slightly depending on which toggle you’re on. My Books shows “No Data Available.” Staff Books shows “No Data available for the Selected Date.” Small inconsistency, but worth knowing so you’re not confused wondering if it means something different.

Why the “My Books vs Staff Books” Split Matters More Than It Looks

It’s easy to check one Pocket Book toggle, see nothing logged and assume there’s nothing to see. That’s the most common way this feature gets misread.

My Books and Staff Books are genuinely separate views. A supervisor checking only My Books on a given date could easily miss entries their team logged under Staff Books for that same day. If you’re reviewing a date for any real reason, check both toggles, not just one.

What’s Confirmed and What Isn’t Yet

Being straightforward here matters more than sounding polished. The Pocket Book create and records flows above are confirmed directly from real screens. That part isn’t a guess.

What isn’t shown anywhere in the current screens: whether a Pocket Book entry can be edited or deleted after it’s submitted, what exactly determines whose entries show up under Staff Books and whether the Message field has any length limit.

If those details matter for how your team plans to use it, the honest answer is to ask for a live walkthrough of those specific flows before assuming how they work.

Why This Beats a Handwritten Logbook

If your team is still using paper, the case for Pocket Book as a way to replace handwritten security logbook habits comes down to four things paper can’t do well. A digital record can’t be torn out. It can’t go missing with the notebook. It timestamps automatically instead of relying on a guard’s memory of when something happened. And it’s searchable by date instead of flipped through page by page.

None of that requires guards to change what they actually write. It changes what happens to the note after it’s written, which is usually where paper systems fail first.

Getting the Most Out of Pocket Book

Keep each entry to one note. A message field that turns into a running list of five unrelated observations is harder to scan later than five separate entries would be.

Log things close to when they happen, not at the end of a shift from memory. The Date and Time fields exist for a reason.

Check both toggles when reviewing a date for anything that actually matters. It takes one extra tap and avoids the most common way Pocket Book gets misread.

What This Actually Looks Like Across a Real Shift

A day shift guard notices the loading dock gate isn’t latching. Not incident-worthy, but worth the next shift knowing. They open Pocket Book, tap Create and log it in under a minute.

That entry exists whether or not the guard mentions it verbally at handover. The night guard can check Records, filter to today’s date and see it under My Books if they logged it, or Staff Books if a supervisor is reviewing the whole team’s notes.

This is where the two toggles in Pocket Book earn their place. A guard cares about their own notes. A supervisor cares about the wider picture. Same tool, two different views.

Picture a slower shift too, nothing worth a formal report. On paper, that shift often produces nothing written down, since nothing felt urgent enough to bother. With Pocket Book, the bar is lower. A visitor who lingered too long. A flickering light. None of it’s an incident, but all of it becomes searchable history instead of a memory that fades.

That’s really the point. One entry rarely matters. A pattern across two weeks, the same gate mentioned three times, is what a supervisor only catches if the notes exist somewhere searchable. Scattered notebooks can’t show that. A calendar can.

Guards who know their Pocket Book notes get reviewed tend to write better ones. No complicated rollout needed, just the habit and a supervisor who actually checks.

Where to Go From Here

If your team is still relying on scrap paper or memory for the small stuff, that’s exactly the gap Pocket Book is built to close. Simple entry, simple review, one place instead of scattered notes nobody can find later.

If you want to see the edit, delete and permission details that aren’t shown in these screens yet, ask for a walkthrough of those specific flows before rolling Pocket Book out to your team.

A logbook nobody can search isn’t a record. It’s just paper that happens to be digital, waiting for the one day someone actually needs it and finds nothing there

See how Pocket Book actually works. Book a quick walkthrough

CONTACT US

Website : https://www.avessecurity.com

Linkedin: https://www.linkedin.com/company/aves-security-management-system/

Instagram: https://www.instagram.com/avessecurity/