Write down what each post requires
Picture a security company covering a few dozen posts: a warehouse gate overnight, a medical office building lobby on weekdays, a retail center on weekends, and a handful of special events each month. The schedule lives in a spreadsheet, credentials live in a filing cabinet, and site requirements live in the operations manager's memory. On a Friday night, an officer calls out. The supervisor finds someone free and sends them to the post. On Monday, someone notices that the replacement's license renewal date passed last week, and that the client's contract asks for an officer with a specific site training the replacement never took.
That scene is an original illustration, not a TwoQM client and not a measured result. It describes a common gap in guard companies: the schedule and the credential records are kept in different places, so the person filling a shift at night cannot see whether the officer is actually cleared for that post.
This article is about connecting the post schedule to your own credential and training records, so the scheduler sees problems before a shift is assigned. It is not about which licenses, registrations, or trainings the law requires. Your state rules, your contracts, and your compliance person decide that list. The software only enforces what you put in it.
Start with the posts, not the people. For each post, record the requirements your company and your client agreed on:
Credential types. The license or registration level your company requires for that post, entered as a category, not as free text.
Site trainings. Client orientation, site walk-through, or equipment training the contract calls for.
Other conditions. Language needs, such as a bilingual officer at a front desk, or a minimum number of shifts already worked at that site.
Who approves exceptions. The manager allowed to override a rule, and how that override is recorded.
When the requirements are written per post, a supervisor at 2 AM does not have to remember that one client's lobby needs a bilingual officer with a completed site orientation.
Keep one credential record per officer
Each officer gets a record with every credential and training your company tracks: the type, the number if you record one, the issue date, the expiration date, and a copy of the document. Add a status that someone updates when a renewal is submitted, approved, or still pending.
Expiration dates entered as dates, not as notes, let the system do the counting. Contractors use the same idea to keep subcontractor insurance and W-9 files current before the first invoice: the document has a date, and the date drives the reminder.
Check requirements at the moment of assignment
This is the core change. When a scheduler puts an officer on a post, the system compares the officer's record with the post's requirements and the shift date:
Clear. Everything the post requires is current through the end of the shift.
Warning. Something expires soon after the shift, or a renewal is pending. The scheduler can assign, and the officer and manager get a reminder.
Blocked. A required credential or training is missing or expired on the shift date. The assignment does not save unless an approved manager overrides it with a reason.
Checking against the shift date matters. An officer who is current today may not be current for a shift three weeks out. Restaurants face a similar coverage scramble with shift call-outs, but in a guard company the question is not only "who is free" but "who is cleared for this post on this date."
Turn expirations into a weekly list, not a surprise
A short weekly list shows every credential and training expiring in the coming weeks, grouped by officer and by the posts they usually work. The operations manager can schedule renewals and site trainings before they block a shift. Officers can see their own upcoming dates, in English or Spanish, so nobody learns about an expiration from a blocked schedule.
When officers can see next week's assignments and their own reminders in one place, fewer people find out by text message. HVAC companies apply a related idea with on-call rotations technicians can see in advance.
Where TwoQM fits
Custom software can provide the post requirements, the officer credential records, and the check at the moment of assignment when your current scheduling tool cannot enforce rules the way your company works. Connected systems can link that check to the scheduling, timekeeping, or payroll tools you already use, so a blocked assignment is blocked everywhere. Business automation can send the weekly expiration list and the reminders to officers and managers. What fits your company is confirmed during scoping.
Where AI helps, and where it stops
AI can read an uploaded credential or training certificate and suggest the type and dates for a person to confirm, list officers who are cleared and available for an open post, and draft a reminder in English or Spanish for a manager to review. Drafts follow the same rule as AI-drafted follow-ups with human send approval.
AI never decides that a credential is valid, never approves an override, never assigns an officer to a post, and never sends anything without a person approving it. Those decisions belong to your supervisors and your compliance staff.
Where to start this week
Pick your five busiest posts. For each one, write down what an officer needs to be cleared for it. Then look at last month's call-out replacements and check how many of those officers met every requirement on the shift date. The answer shows whether a check at assignment would help first.
TwoQM builds custom software, automation, and connected systems for small businesses in the Rio Grande Valley and beyond. This article describes operational workflow only. It is not legal, licensing, or compliance advice. Pricing explains how business apps, systems, and custom software are scoped.
Describe Your Post Scheduling Workflow · Explore TwoQM Custom Software