Frequently Asked Questions

No. F2 Core is an operational layer that connects work, vendors, approvals, and evidence. It can start standalone and integrate with maintenance or ERP systems when ready.

Yes. F2 Core launches with native assets, tickets, vendors, dashboards, documents, and routing rules. Integrations can be added when the customer is ready.

Access is role-based: site managers, GMs, finance, compliance, vendors, and leadership all see different views of the same operating record.

Workflows use rules, thresholds, ownership, vendor contracts, approval limits, and escalation timers — configured per customer during implementation.

No. F2 Core supports environmental workflows, organization, documentation, and evidence readiness. It is not a substitute for legal advice or a qualified environmental compliance review.

Yes. Labels and QR codes are tied to tank and container records with state-aware templates and a print/order workflow.

Pickups are routed through a shared workflow with the tank context, vendor route, schedule, documents, and reconciliation.

Yes. Authorized vendors can attach documents and notes that retain on the asset record.

No. Energy Management features help identify runtime patterns, exceptions, and opportunities for action. Actual savings depend on site conditions, equipment, usage, tariffs, and implementation.

HVAC, compressors, dryers, lifts, garage doors, lighting circuits, pumps, exhaust systems, and other current-monitored equipment.

Yes. Energy alerts can route into tickets, vendor workflows, or PM tasks based on policy.

Yes. Energy partners receive service requests with full asset and signal context.

SpendGuard does not replace AP. It gives AP operational evidence: approved quote, contract terms, work completion, pickup records, manifests, and credits.

SpendGuard supports professional, evidence-backed conversations. Disputes are approval-controlled and source-cited.

No. AI can answer questions and draft recommendations, but authorized users make final financial decisions.

Phase 1 is standalone. ERP integration is future enrichment, not a dependency.

SpendGuard separates potential, accepted, validated, realized, and sustained savings.

Extracted contract terms and rate cards require human review and approval before compliance rules activate.

Start with duplicate invoices, over-quote invoices, missing used-oil credits, unauthorized surcharges, and missing manifests.

Correct — SpendGuard does not create dealership revenue. It is designed to reduce leakage, prevent avoidable overpayment, recover missing credits, and give leadership spend control.

Yes. Start with one or two categories such as used oil, facility repairs, HVAC, lifts, doors, or recurring vendor services. Vendor alias cleanup and contract / rate-card setup improve matching over time.