One job. One connected record.
Job details, inventory, documents, crew hours, and billing around a shared operational record for moving, storage, and logistics. Agent interfaces and visual intake remain in engineering.
Current scope
The operational foundation is implemented. Agent interfaces and assisted intake build on that foundation; they are not a fully autonomous operation available today.
Implemented foundation
- Jobs and dispatch
- Job records, planning views, and readiness checks connect the work that needs to happen with the information needed to start it.
- Bills of Lading
- Pickup, delivery, shuttle, return, and direct BOL workflows include controlled transitions, signatures, and item records.
- Inventory and condition
- QR-based item workflows and condition photos support warehouse receiving, dispatch, and delivery records.
- Hours, payroll, and invoicing
- Crew time entries, payroll periods and approvals, and invoice workflows connect operational records to close-out.
Plan, carry out the work, close the record.
Plan
Organize the job, people, route, and documents. Readiness checks expose missing information before the next operational step.
Carry out the work
Capture item movements, condition records, signatures, and crew hours through the enabled workflows.
Close out
Review completed work, approve relevant time and payroll records, and continue into invoicing with the job context attached.
Where it fits
For moving companies, storage operators, and logistics teams whose jobs cross dispatch, warehouse, crew, and billing responsibilities.
- Your operation
- Defines job types, facilities, roles, handoffs, and the approvals people remain responsible for.
- Atlas
- Provides the shared operational record and scoped workflows. Module availability and access depend on configuration and roles.
- External systems and agents
- Accounting, messaging, and agent connections need an explicit integration scope. MCP scaffolding is not a ready-to-use connector.
Atlas focuses on moving, storage, and logistics. Dispatch, payroll, and compliance decisions retain their human responsibilities. Hoogalabs experimentation and engineering work has a broader scope.
Bring one job from intake to close-out.
Use a real workflow to discuss early access. Identify where its context is lost and which enabled Atlas workflows would need to carry it.
- The job lifecycle
- Bring the steps, documents, item movements, and handoffs involved in a representative job.
- The operating context
- Identify the crews, facilities, access roles, existing tools, and integrations involved.
- The acceptance criteria
- Define the records, approvals, and exception cases that must be checked before changing how the operation works.
Before you begin
Does early access mean everything on the roadmap is available?
No. The implemented foundation and work in engineering are listed separately. Access, enabled modules, and deployment readiness need confirmation for the proposed workflow.
Can external AI agents use Atlas through MCP today?
The MCP server entry point is currently a scaffold. It is part of the engineering direction, not a complete production-ready interface offered by this page.
Is visual intake available?
Visual intake remains in engineering. Assisted volume estimation and inventory drafting should not be treated as enabled features without explicit confirmation.
Does Atlas require Operations Messaging?
They are separate products. Any integration between Atlas, Operations Messaging, or another agent system needs its own scope and verification; this page does not promise a bundled integration.