Why Runlev
Most operations software is a screen your team has to keep filled, and most AI added to it can only answer from what was typed in. Runlev's agents read what your business already produces, keep one current record, and bring forward only what needs a person.
Typical dashboard
New sales order
Not startedWaiting in the inbox
- Confirmation email
- Ticket photo
- Booking notice.pdf
- Material
- Net weight
- Container
- Booking
Someone has to read it, retype it and file it before anyone can see where the order stands.
AI assistant added on
Assistant
Inside the dashboard- Where is Load 2318?
- I can't find Load 2318. It may not have been entered yet.
- Did the buyer confirm the weight?
- I don't have that information. Try checking your email.
Ask anything…
It can only answer from what someone typed in.
Runlev
Order 2318
Zorba · River yard to export buyer
- Material
- Zorba
- Confirmation email
- Net weight
- 22.0 t
- Scale ticket
- Container
- TXGU 418220 4
- Booking notice
- Booking
- Confirmed
- Booking notice
- Documents
- 3 filed
- B/L, ticket, 18 photos
Needs you · The bill of lading shows TGXU 418220 4, not TXGU. Caught before the documents go out.
What's different
Most industry software was built for people to type into, and an assistant added on top can only answer from what someone entered. Rebuilding a large platform around agents means reworking years of screens, through many teams and approvals. Runlev starts from the work as it arrives, and each system is shaped to the business that uses it.
| Typical dashboard | AI assistant added on | Runlev | |
|---|---|---|---|
| Where information comes from | Typed in by your team. | Whatever was typed into the dashboard. | Read from the emails, tickets, photos and documents your business already produces. |
| When the work happens | When someone sits down to update it. | When someone thinks to ask. | All day in the background. Every shipment is re-checked each morning. |
| What you see | What someone has entered so far. | An answer, if the data is there. | The operation as it stands, with what needs you first. |
| When something doesn't match | Found later, often by the customer. | Missed unless someone asks the right question. | Flagged against the record before it leaves your desk. |
| Where it reaches you | Inside the dashboard. | In a chat box inside the dashboard. | In your workspace, and in the chat and email your team already uses. |
| How it changes | On the vendor's release schedule. | On the vendor's release schedule. | Shaped to your operation, and changed as it changes. |
The work behind the screen
Order entry, load scheduling, document checks and keeping every site on the same page. The work is well defined, and it arrives in inboxes and on paper long before it reaches a system. Runlev does it as it arrives, so your people spend their time on customers, exceptions and decisions.
Open role
Order & scheduling administrator
Full time · Responsibilities
How Runlev handles it
01Enter purchase and sales orders
RecordedRead from the confirmation or contract and recorded with its source.
02Schedule loads and match them to bookings
MatchedLoads matched to bookings and carriers. Open slots show before they're missed.
03Check shipping documents against the order
CheckedContainer numbers, weights and booking details checked before documents go out.
04File tickets, photos and paperwork for every load
FiledAttached to the load they belong to, as they arrive.
05Keep everyone updated on every order
Prepared for reviewA morning brief and updates reach your team's phones. Replies are drafted for someone to send.
06Build loading schedules and weekly reports
PreparedWritten from the record, ready to review and send.
The whole operation
Every purchase, sale, load, shipment and document across your sites, current in one record. Routine updates are recorded for you. Anything that doesn't add up comes forward with its evidence, before it reaches a customer.
Operations
All sites · currentSites
- North yard12 loads moving
- River yard9 loads moving
- Processing plant4 runs today
- Trading desk21 open orders
Needs you
3Container number doesn't match the bookingLoad 2318 · River yard
The bill of lading shows TGXU 418220 4. The booking shows TXGU 418220 4.
Bill of lading · Booking noticeCorrect before the documents go out
Buyer weight claimLoad 2290 · North yard
The buyer reports 21.1 t received. The scale ticket shows 22.3 t.
Buyer email · Scale ticket · 18 load photosReview the claim with the load evidence
Agreed adjustment isn't on the orderOrder 1187 · Trading desk
A price adjustment agreed by email on Oct 14 isn't on the order yet.
Email thread, Oct 14Confirm and update the order
Recorded automatically · today
- Order 2331 confirmedFrom the buyer's confirmation email
- Load 2318 weighed · 22.0 tScale ticket attached
- Booking received for Load 2325Booking notice attached
- 18 photos filed to Load 2290Sent from the yard by text
- Documents complete for Load 2304Bill of lading, ticket and photos
Caught before it leaves
Documents are checked against the record, so mismatches surface before a customer finds them.
Filed as it arrives
Emails, tickets, photos and PDFs stay with the load they belong to.
Decisions stay with people
Nothing is agreed, sent or paid without someone on your team.
Alongside what you run
Runlev doesn't ask you to replace your yard, scale or accounting systems. Where they allow it, Runlev reads from them and checks every email and document against what they hold. Where they don't, it works from the exports and paperwork they already produce.
What arrives
- Emails and attachments
- Texts and photos of paper
- Scale tickets
- Contracts, bookings and bills of lading
read and recorded
One current record
Your operation
Purchases · Sales · Loads · Shipments · Documents
A private database for your business
checked against
What you already run
- Yard and scale system
- Accounting
- Spreadsheets and shared drives
How it starts
Begin where the paperwork is heaviest, running alongside how you work today. As it proves itself, extend it to purchasing, production and your other sites.
One desk first
Start with the orders, loads and documents one team handles every day.
Side by side
Run it next to your current process until the record speaks for itself.
Every site, one record
New and acquired sites join the same record instead of learning another system.
