Daily operational checks

Prerequisites and authority

Assign an operator and an authorized technical owner. Data-replacing recovery and updates require a maintenance window, preserved recovery point and known target.

Operate a live installation

The operator's job is to keep customer access, payments and maintenance work consistent. A working dashboard is only one signal. Review customer service, router state, background work and recovery readiness together.

Start of shift

Check for open incidents and planned work. Record the current release and any overnight changes. Review API/application availability, license warnings, failed operations, routers without recent contact and the last backup. Check host disk headroom before jobs fill storage.

Open representative records rather than relying only on totals. Confirm successful payments are linked to the intended subscriptions, active entitlements have successful provisioning and queued purchases are waiting for valid reasons. Investigate exceptions through the corresponding troubleshooting article.

Handle a customer request

Identify the customer through the approved account lookup. Establish whether the request concerns application login, payment, entitlement, hotspot login or a device. These are different layers.

Review current subscription and payment references before assigning another plan. Ordinary purchases stack; creating a replacement subscription can hide a failed provisioning operation and misstate paid time. Use supported retry/repair actions when appropriate and verify actual access afterward.

For device complaints, distinguish registered devices from simultaneous connections. Inspect all applicable routers before deciding the concurrency limit was breached. A device block must follow the approved immediate-disconnect target after implementation is verified.

Monitor the network

Review router reachability, desired-configuration state and failed operations independently. A source outage can affect one site while the central system remains healthy. A management-only outage can leave customer internet working.

Record the outage and follow Router offline recovery and reconciliation rather than suspending customers indiscriminately. After recovery, inspect expiry enforcement, late operations, device blocks and accounting gaps.

Review payments

Use references to compare provider outcomes with BryanNet records. Preserve successful transactions even when provisioning fails. Do not delete financial records or create manual payments merely to make a status screen agree.

Use sandbox records for integration tests. Live corrective actions need a documented reason, authorized operator and post-action verification. Complimentary/imported grants must remain distinguishable from collected revenue.

Maintain operational evidence

Record unresolved errors with timestamps and identifiers. Capture bounded logs before restart where practical. Keep credentials and unrelated personal information out of shared incident records. A service restart is an intervention, not a root-cause explanation.

Use the smallest suitable action: supported application repair, dependency correction, controlled service restart or escalation. Database writes and restoration belong to advanced recovery, not normal shift support.

End of shift

Confirm critical jobs and backups completed, or hand over their failure explicitly. List affected customers/sites, actions already taken, pending work and the next verification step. Include when the next operator should check a delayed event.

Leave update approvals and restore decisions with the designated owner. Do not begin a migration just before handover without a maintenance window and recovery plan.

Use Daily weekly and monthly operator checklists's printable schedules and the incident template to make these routines repeatable. The named worker schedules and exposed health metrics must be verified against the release before this handbook is operationally signed off.