Common questions, organized by audience.

ARWIX is designed around three principles that distinguish it from most platforms: governance as a platform foundation (not a feature), configuration instead of customization, and a dedicated workspace for every participant type. Most platforms build governance features onto a system that wasn't designed with governance in mind. ARWIX treats auditability, role-based access, and policy enforcement as core platform architecture.

Yes. ARWIX is designed to support organizations with multiple policy frameworks — domestic and international, grade-based and lump-sum, managed and flexible. Each framework is configured separately within the platform and applied based on the employee's situation. A coordinator managing a domestic corporate relocation and a CONUS-to-OCONUS move for the same organization operates within the same platform but with framework-appropriate rules applied to each case.

No. ARWIX is designed as the relocation lifecycle management layer — the platform that coordinates the workflow, participants, documents, and decisions specific to a relocation. It is designed to complement, not replace, HR information systems. Data exchange between ARWIX and existing HR systems is handled through defined integration contracts, not open-ended file transfers.

Yes. Approval tiers, authority thresholds, routing logic, and escalation paths are all configurable. Organizations define who can approve what, up to what amount, and what happens when a case falls outside standard parameters. Configured approval workflows are enforced by the platform — not dependent on individual coordinator judgment.

Both program models are supported within ARWIX's configurable framework. Lump-sum programs are configured with their specific parameters — payment structure, employee entitlements, and documentation requirements. Managed programs are configured with service structures, entitlement rules, and approval workflows. Each operates within the same governed platform.

Yes. ARWIX includes a dedicated employee workspace — My Relocation — where employees can view their entitlements, complete guided questionnaires, access and sign documents, track their move status, and submit expenses and vouchers. The employee experience is policy-aware and calibrated to each employee's specific situation.

Yes. ARWIX is designed to support relocation programs governed by the Federal Travel Regulation, including the entitlement structures, authorization workflows, and documentation requirements that federal civilian programs apply. The platform is configurable to reflect agency-specific policy interpretations and operating procedures.

Agency policy is configured as a platform construct — applied consistently to every case, every participant, every entitlement determination. When policy changes, the configuration is updated centrally rather than communicated to individual coordinators and applied case by case. Consistency is enforced by the platform, not dependent on coordinator interpretation.

Yes. ARWIX supports the full authorization-through-voucher workflow — from initial travel authority issuance through expense submission, review, and settlement. E-signature support is included for all required documents, in compliance with the ESIGN Act. Audit documentation is captured at every step.

ARWIX is designed to support records-retention requirements by maintaining case documentation, decision logs, and audit evidence as part of the platform architecture. Specific retention configuration depends on agency requirements. Organizations are responsible for configuring and validating retention parameters appropriate to their applicable schedules.

No. ARWIX is a commercial platform designed to support governed, policy-driven relocation operations. ARWIX does not hold FedRAMP authorization, DoD authorization, or any government security accreditation. Organizations operating under specific security or regulatory frameworks should evaluate ARWIX against their applicable requirements.

ARWIX is designed to provide the governance infrastructure — approval workflows, audit trails, cost documentation, and exception records — that FAR-governed relocation programs require. It does not provide regulatory interpretation or cost-allowability determinations. Organizations are responsible for evaluating their obligations under FAR Part 31 and configuring ARWIX to reflect their approved policies.

Yes. Every approval, authorization, exception, and case action in ARWIX is logged with timestamp, actor identity, applicable rule, and decision basis. This documentation is designed to respond to program audits without reconstruction — the record exists within the case history, not in reconstructed email threads.

Yes. ARWIX is designed to support organizations operating under multiple contracts, each with distinct relocation rules, approval structures, and documentation requirements. Each client context can be configured separately within the platform.

Exceptions are routed through configured approval workflows — not handled informally. When a case falls outside standard parameters, the exception is flagged, the applicable rule is identified, and the approval is routed to the authorized authority. The exception, the approval decision, and the basis for the decision are all documented in the case record.

Yes. ARWIX is designed to support structured relocation environments governed by the JTR, including grade-based entitlement resolution, HHG weight tracking, travel authorization workflows, and voucher processing. The platform is configurable to reflect the specific provisions and implementing instructions applicable to your program.

Yes. ARWIX includes HHG coordination capabilities — carrier assignment, weight entitlement tracking, SIT authorization, NTS management, and milestone documentation — connected to the relocation case record.

No. ARWIX is a commercial relocation platform designed to support structured operational models. It does not hold DoD Authorization to Operate, FedRAMP authorization, IL5 accreditation, or any government security certification. Organizations operating under DoD security requirements should evaluate ARWIX against their applicable standards and operating environment.

Yes. ARWIX's configurable framework supports different entitlement structures, policy provisions, and workflow requirements for different employee populations within the same platform.

ARWIX includes e-signature workflows for repayment agreements and other required documents — supporting draw, type, upload, and mobile signing options in compliance with the ESIGN Act. Signed documents are timestamped, hashed, and retained as part of the case record.

Yes. ARWIX is designed to support RMCs managing multiple clients simultaneously — each with their own policy framework, approval structure, and operational preferences — within a single governed platform. Each client's operating model is respected through configuration, not through separate platform instances.

ARWIX is not a replacement for RMC expertise or operational methodology. It provides the case management, carrier coordination, policy application, and governance infrastructure that supports complex multi-client operations. RMCs configure the platform to reflect their preferred workflows and client requirements.

Yes. ARWIX provides work queues, status visibility, priority indicators, and actionable case lists designed for coordinators managing large caseloads. Case status is visible at a glance without requiring per-case inquiry.

Carriers and service providers participate in the case through ARWIX's carrier workspace — receiving service assignments, accessing scoped documentation, documenting milestones, and submitting for assessorial approvals. The coordination is structured and documented, reducing the manual overhead that currently characterizes many carrier relationships.

Yes. Client-specific workflows, approval structures, policy rules, and operational preferences are configured per client within the platform. A coordinator working on a DoD client's cases and a corporate client's cases in the same session operates within the appropriate framework for each.

Carriers participate through a dedicated Carrier Operations workspace — receiving service assignments, accessing authorization documents scoped to their shipments, documenting milestones, and participating in coordination workflows. Carriers do not have access to the full case record — only the information relevant to their services.

No. Carrier access is scoped to the specific shipments and services they are responsible for. Role-based access controls ensure carriers see what they need to perform their services — and nothing more.

Yes. Parent carriers can manage their local agent relationships within the platform, with scoped visibility that gives agents access to the shipment information relevant to their services.

ARWIX is designed to provide carriers with structured, complete information at the time they need it — authorization documents, contact details, scheduling requirements — through the platform rather than through email requests. When information arrives structured and on time, carriers can schedule and execute services without the coordination overhead that currently delays many moves.

Employees access ARWIX through the My Relocation workspace — a guided, policy-aware experience designed to reduce the uncertainty and complexity of a relocation. In their workspace, employees can view their entitlements and authorized services, complete guided questionnaires, access and sign documents electronically, track their move status, and submit expenses and vouchers.

Yes. The ARWIX employee workspace is scoped to your specific relocation — you see your own information, your own documents, and your own move status. Your information is accessible only to you and to the coordinators and approvers authorized to manage your case.

Yes. ARWIX supports electronic signatures through draw, type, upload, and mobile QR signing options. The mobile signing option generates a QR code that you scan with your phone — allowing you to sign on any device without installing an application.

Yes. The ARWIX employee workspace is designed to surface the entitlements and information that apply to your specific situation — based on your organization's policy, your role, and your relocation parameters. You will not receive a generic list of all possible benefits; you will see what applies to you.

ARWIX provides visibility and guidance throughout your relocation — but your primary point of contact for specific questions about your case is your relocation coordinator or HR contact. ARWIX is the platform that supports the process; the people managing your relocation are your direct resource for case-specific questions.