Tech Mode Log: Control Admin Access
Tech Mode Log: Control Admin Access in Your Club
Section titled “Tech Mode Log: Control Admin Access in Your Club”The Tech Mode Log in IZI CRM is a tab inside Suspicious Activity that records every entry into tech mode — the elevated-privilege state that lets admins manually close sessions, adjust client balances, and perform non-standard device operations. To open it: Analytics → Suspicious Activity → Tech Mode Log. Set a date range, and each row in the table corresponds to one tech mode entry: staff member, device, start time, end time, and duration. The core principle is straightforward — using tech mode is not a violation, but every entry should be explainable by a real operational need. The log makes that verification possible.
What Tech Mode Is and Why It Needs a Separate Log
Section titled “What Tech Mode Is and Why It Needs a Separate Log”Tech mode is not a debug feature reserved for IT staff. It is a standard operational tool that every admin may legitimately need in the course of a shift:
- Manually closing a stuck session after a client has already left
- Taking a PC offline for maintenance (game updates, hardware swap)
- Correcting a client balance after an operator error
- Resolving a non-standard payment situation
The issue is not with tech mode itself — it is with what it enables. When a PC is in tech mode it generates no billing revenue, and certain operations (balance adjustments, session termination) are available that bypass the normal billing flow. That is why IZI logs every tech mode event separately and surfaces it in Suspicious Activity.
Revenue Impact While a PC Is in Tech Mode
Section titled “Revenue Impact While a PC Is in Tech Mode”Every hour a PC spends in tech mode during peak hours is an hour it is not generating revenue. You can estimate the cost parametrically:
Tech mode revenue loss = Hours in tech mode during peak × Average revenue per PC per hourAverage revenue per PC per hour ≈ AOV ÷ average session length (hours) × utilization rate. If your AOV is X and the average session is Y hours, each peak-hour PC downtime costs roughly X / Y. Multiply by the number of tech mode hours in a month to get a lower-bound estimate of indirect losses.
Note: some of these losses are unavoidable and justified — maintenance is necessary. The log’s job is to confirm that tech mode runs only as long and as often as genuinely needed.
What the Log Records and How to Read It
Section titled “What the Log Records and How to Read It”Each entry in the Tech Mode Log contains a consistent set of fields that together give you the context to assess the event.
| Field | What it shows | What to watch for |
|---|---|---|
| Staff member | Who entered tech mode | Cross-check with the shift schedule |
| Device | Which PC was placed in tech mode | Unfamiliar device for this admin? |
| Start time | When tech mode was activated | Working hours or off-hours? |
| End time | When tech mode was exited | Calculate the duration |
| Duration | Total time the PC was in tech mode | Minutes = normal; hours during peak = flag |
Primary Signals to Check First
Section titled “Primary Signals to Check First”Time of day. Tech mode entries outside normal shift hours need an explanation. Overnight maintenance can be legitimate in 24-hour clubs, but those sessions should correspond to known scheduled work.
Duration. A typical tech mode entry for a specific task takes a few minutes. A session lasting an hour or more during peak hours is either a serious technical problem — which should be on record — or a signal worth investigating.
Frequency per staff member. Multiple entries within one shift are not a problem if each is justified. A recurring pattern of “many short entries” by the same admin, shift after shift, is worth a follow-up conversation.
Device–admin pairing. An entry on a PC not normally associated with that admin, or outside their usual zone, is an atypical event worth clarifying.
Business Meaning: Tech Mode as Tool and Risk
Section titled “Business Meaning: Tech Mode as Tool and Risk”Legitimate Use
Section titled “Legitimate Use”Tech mode is a standard part of club operations. Without it, normal hardware maintenance is impossible. Admins need it, and most log entries will be routine operational events. The goal of the log is transparency, not a presumption of wrongdoing.
How Tech Mode Can Become a Source of Losses
Section titled “How Tech Mode Can Become a Source of Losses”If an admin spends time in tech mode on a PC instead of performing actual maintenance, that PC sits idle with no revenue. In a systematic pattern this accumulates into meaningful losses.
Parametric risk estimate:
Monthly risk = Average "excess" tech mode hours per day × Working days × AOV ÷ Average session length“Excess” hours here is the difference between actual tech mode time and justified time (for example, if standard maintenance takes 15 minutes per PC per week, but actual logs show 2 hours). Plug in your own numbers — you will quickly see whether the pattern warrants deeper investigation.
The Preventive Effect
Section titled “The Preventive Effect”When staff know that every tech mode entry is logged and visible in the CRM, they use it precisely when needed. This is one of the core mechanisms behind the Suspicious Activity section as a whole: transparency changes behavior before any investigation is necessary.
How to Work With the Log Regularly
Section titled “How to Work With the Log Regularly”Weekly Planned Review
Section titled “Weekly Planned Review”Include the Tech Mode Log in your weekly Suspicious Activity check. Set a 7-day filter, spend 5–10 minutes:
- Any entries outside shift hours or off-schedule?
- Any long sessions during peak hours (evenings, weekends)?
- Any single staff member with an unusually high entry count for the period?
If all three answers are “no,” you are done — everything looks normal.
When a Cash Discrepancy or Low AOV Appears
Section titled “When a Cash Discrepancy or Low AOV Appears”If your shift report shows a discrepancy, or a specific admin’s AOV for a shift is anomalously low, check the Tech Mode Log for that same window:
- Were there tech mode entries during that shift?
- How many devices, and for how long?
- Do the timestamps overlap with the low-sales period?
This adds context for a conversation with the admin: it either explains the anomaly (a PC was in maintenance) or adds a data point to the picture.
Step-by-Step for a Suspicious Entry
Section titled “Step-by-Step for a Suspicious Entry”- Record the event details: staff member, device, time, duration
- Cross-check with the shift schedule — was this admin on duty at that time?
- Ask the admin for context: what required tech mode at that moment?
- Review the session report for that device over the same period — what happened before and after?
- If the situation remains unclear, check the Employees tab for the same period
How the Tech Mode Log Connects to Other Analytics
Section titled “How the Tech Mode Log Connects to Other Analytics”The Tech Mode Log is one part of a broader control system. It works alongside other IZI tabs and reports.
| Question | Where to go |
|---|---|
| Cash discrepancy — where to start? | Shift Report → then Tech Mode Log |
| Which staff member has anomalous AOV? | Employees tab |
| Which balance operations look non-standard? | Balance Operations |
| What tariffs were sold during the shift for comparison? | Tariff Sales |
| Overview of all suspicious activity vectors | Suspicious Activity — overview |
Frequently Asked Questions
Section titled “Frequently Asked Questions”Do I need to approve every tech mode entry in advance?
Section titled “Do I need to approve every tech mode entry in advance?”That depends on your internal club policy. IZI does not require pre-approval — it logs the event. Many owners implement a simple rule: any non-obvious tech mode entry (not routine maintenance) gets a brief note in the team chat. This is not bureaucracy; it means that if an entry later appears in the log, the admin already has context documented.
Can I restrict tech mode access for some staff?
Section titled “Can I restrict tech mode access for some staff?”Tech mode access rights are configured through the IZI CRM role system. If certain admins should not be able to place devices in tech mode independently, that is handled at the role-settings level, not in the log itself.
What is the difference between the Tech Mode Log and the Employees tab?
Section titled “What is the difference between the Tech Mode Log and the Employees tab?”The Employees tab aggregates all types of anomalous events per staff member into a single profile. The Tech Mode Log is a specialized record of one specific event type: tech mode entries. Think of Employees as the person-level anomaly summary, and the Tech Mode Log as a deep-drill into one specific vector.
What should I do if the log shows a large number of events?
Section titled “What should I do if the log shows a large number of events?”Start by checking whether all of them map to known operational situations: scheduled maintenance, hardware upgrades, unusual client scenarios during that period. If most entries are explained, that is fine. If a significant portion is not, identify the pattern — who, when, how often — and begin with a direct conversation with that admin, referencing the specific dates from the log.
Do I need to check the Tech Mode Log every day?
Section titled “Do I need to check the Tech Mode Log every day?”No. A weekly review within your regular Suspicious Activity cycle is enough. Daily checks only make sense during an active investigation of a specific incident, or after a confirmed systematic pattern has been identified.
Frequently asked questions
What is the Tech Mode Log in IZI CRM?
The Tech Mode Log is a tab inside the Suspicious Activity section that records every time a staff member enters tech mode — an elevated-privilege state that allows manual session closure, balance adjustments, and non-standard device operations. Each record shows who entered tech mode, on which device, the start and end times, and the total duration.
What is tech mode in a gaming club?
Tech mode is a built-in operational status that gives an admin expanded rights: manually closing stuck sessions, correcting client balances, and performing non-standard device operations. It is a legitimate tool for edge cases, but because it allows operations that bypass the standard billing flow, all tech mode events are logged separately.
Why does tech mode need its own log?
Tech mode is a valid instrument, but it also enables operations that do not pass through standard billing. The log lets you verify that every session was justified by a real operational need — not an opportunity for off-the-books activity. Regular log reviews are part of sound club operations.
How do I open the Tech Mode Log in IZI?
Navigate to Analytics → Suspicious Activity → Tech Mode Log tab. Set a date filter for the period you want to review. Each row represents one tech mode entry event: staff member, device, start time, end time, and duration.
What signals are suspicious in the Tech Mode Log?
Key red flags: tech mode entries during off-hours or outside the staff member's shift, unusually long sessions during peak hours, the same employee entering tech mode repeatedly within a single shift with no apparent reason, and entries on devices not normally associated with that admin.
Can a tech mode entry be a normal work action?
Yes — in the vast majority of cases it is routine. Admins enter tech mode to handle stuck sessions, run maintenance, install updates, or resolve a client payment issue. The log is not about presuming guilt; it is about making sure every entry has a traceable operational reason behind it.
How does tech mode affect club revenue?
While a PC is in tech mode it is unavailable to paying clients. Planned maintenance during off-peak hours is acceptable. But if a machine regularly enters tech mode during peak hours, the revenue impact accumulates. Estimated loss per hour equals approximately (AOV ÷ average session length) multiplied by peak utilization rate.
How does the Tech Mode Log relate to other Suspicious Activity tabs?
The Tech Mode Log complements the Employees tab. If Employees shows an anomaly for a specific admin, the Tech Mode Log lets you check whether concurrent tech mode sessions explain the anomaly — or deepen it.
How often should I review the Tech Mode Log?
A weekly planned review alongside other Suspicious Activity tabs is sufficient for routine monitoring. Review it immediately whenever a shift report shows a cash discrepancy or an unusually low AOV for a specific shift.