Skip to content

Risks and known limitations

This page says what the product does not do yet and what it does with a caveat. It is section 12 of the arc42 template. It is written for a company that evaluates Ochema and for the people who build it: both should read the same list.

The words Available, Preview, Planned, Simulator, Not verified and Proposed mean what the overview defines. The state of every single capability is in the capability map, and what comes next is in the roadmap.

  • Real SMS and email need provider accounts. Out of the box the product runs in simulator mode: an SMS is recorded and shown in the conversation but reaches no phone, and an email is written to a local outbox. Sending for real depends on the platform being configured with an SMS provider (Twilio) and an email provider (SMTP or Amazon SES), and on the platform team assigning an SMS number to the company. See Context and scope and Messaging settings.
  • Sending through a real account is Not verified. The adapters of the real providers are written and tested against local stand-ins. No message has been sent through a real account yet, so the first real send may show differences the stand-ins do not have. See ADR-0013.
  • SMS waits for the carrier registration. With a real provider, SMS is held until the registration of the company for business messaging (A2P 10DLC) is marked approved. The platform team makes the registration with the provider, outside Ochema, and records its situation. See Messaging.
  • Calendar sync needs setup by the platform team. Connecting Google Calendar or Microsoft 365 works only after an OAuth application of each provider is saved in the platform panel. The iCalendar feed of a recruiter needs no setup. See Calendars.
  • No voice. A recruiter calls from their own phone and records the outcome in the call list. Ochema does not dial or record calls. Calling from the product, video and AI agents are Planned. See the capability map.
  • No outgoing webhooks. Another system can send leads in through the lead intake API. Ochema does not notify another system when something changes. See Lead API.
  • The compliance rules are a regulatory preview. Every rule, retention period, consent text and legal text ships marked “Regulatory preview” and is shown that way on screen until the platform team validates it. Ochema organizes the file; it does not give legal advice, and the carrier remains responsible for its own compliance. See ADR-0019 and Document types and rules.
  • Screenings are recorded, not ordered. Motor vehicle records, background checks, PSP reports, drug and alcohol tests and Clearinghouse queries are ordered by the company on the site of each provider or agency. Ochema records what to order, the file received, the result, the date and the reviewer. Integration with a screening provider is Planned. See Screenings and exams.
  • The electronic signature is a typed name with its proof. A signer types the full name and confirms; the product records when, from where and on which document, and freezes the content. There is no drawn signature and no certificate-based digital signature. See ADR-0014.
  • Signing by link needs a careers page address. A person outside the company signs on a page under the careers address of the company. A company that has not set that address cannot send a document to be signed by link. See Contracts and signing.
  • Nothing is erased at the end of a retention period. The product shows the files whose retention ended and lets a person keep each one or mark it for deletion. The mark is a decision on record; erasing data for good is not a function of the product. See Archiving.
  • Random testing and training are not built. The selection of drivers for random drug and alcohol testing, and the training library, are Planned. See the capability map.
  • Eligibility does not block a load. A driver file says whether a driver is eligible. Stopping an ineligible driver from being dispatched arrives with dispatch, which is Planned. See Lifecycles.

Ochema is built in the order a carrier needs it: recruiting and compliance first. The other areas exist in the menu and in the data model, and most of what they will do is Planned.

Area Today, and what is Planned
Driver app Today: sign-in and empty screens. Applicants and drivers do what they need on public pages opened by a link, with no app and no password. Planned: the app itself, with schedule, inspections, proof of delivery, documents and pay statements. It is a progressive web app in version 1.0; native apps and background location come after. See ADR-0026.
People Today: the directory of people and the terminals. Planned: schedules, hours of service, performance, safety events and communication with drivers.
Fleet Today: the register of vehicles. Planned: maintenance, inspections, fuel, telematics and ELD integration.
Operations Today: the registers of customers and locations. Planned: orders, loads, dispatch, routing and tracking.
Portals Today: nothing a customer can use. Planned: shipper, receiver and partner carrier portals.
Finance Today: nothing a customer can use. Planned: rates, invoicing, driver pay, settlements and accounting.
Platform Today: accounts, roles, the audit log, search, and integrations for messaging and calendars. Planned: sign-in with a second factor and single sign-on, configurable reports, custom fields, and the brand of the carrier on pages and messages.
  • Spanish is complete for applicants and partial for office users. The careers page, the application, scheduling, signing and the candidate area are fully in English and Spanish, and so are the default message templates. In the office system a user who chooses “Español” sees Spanish in part of Attract and Recruit and English elsewhere. See Internationalization.
  • The office system is designed for a desktop. The pages an applicant sees are built for a phone. The office system is built for a wide screen; on a phone only its top bar is checked. See Quality requirements.
  • No accessibility audit yet. Contrast, keyboard use of the application form and the behaviour of the components are tested. A full audit against WCAG 2 level AA, with a screen reader, has not been made.
  • Tested in one browser. The automated browser tests run in Chromium. Other browsers are not part of the automated checks. See Testing.
  • United States only. Phone numbers, states, time zones and the compliance rules assume the United States. See Introduction and goals.
Limit Detail
Search needs three characters. A search by text needs at least three letters or digits in a row.
Some analytics read a shorter period. “Time in each stage” and the stage moves per recruiter read at most the last 92 days of the chosen period, and the screen says so.
Automatic SMS is limited on purpose. Automatic messages go out only inside the sending window of the company, which is never wider than 8 AM to 9 PM in the time zone of the candidate, and each candidate gets a capped number of automatic SMS per day. A message outside the hours waits; a message over the cap is not sent.
An audit log export has a ceiling. One export holds at most 100,000 rows and a period of 366 days.

The full list, with the values a company can change, is in Limits.

The product runs today in a development environment. The production environment is Proposed: its design is written in the Deployment view, and nothing of it is provisioned. That has direct consequences:

  • No hosting provider is chosen, and there is no release pipeline, monitoring or alerting.
  • No backup and restore procedure exists yet, and no availability objective is set.
  • The measurements in Quality requirements come from a development machine. Response times with many users at once, and running more than one instance of the API or of the worker, are Not verified.

These are consequences of the decisions in Solution strategy, accepted knowingly. Each one says why it is accepted and what limits it.

A query written without care for it can be correct and slow in a large company. It is accepted because isolation between companies is the first quality goal, and the database is the only place that cannot forget a filter. What limits it: the plan of every list, panel and search is checked against a seed of realistic volume, and text search goes through dedicated functions. See ADR-0022.

Section titled “In-house compliance rules and signatures carry legal weight”

A wrong rule or a contested signature is a problem for the carrier, not only for the product. It is accepted because recruiting and compliance must work with no outside account and at no cost per document. What limits it: rules and texts are labelled as a preview until validated, each signature records whether its text was validated, and every change of a driver file is in its history.

A heavy module cannot be scaled alone. It is accepted because one team builds ten business areas that share people, files and messages. What limits it: the API and the worker are already separate processes, and a module can be split out starting from its public interface. See ADR-0001.

Behaviour that only a real provider shows is found late. It is accepted because the whole product must run and be tested with no provider account. What limits it: each adapter is written against the documentation of its provider and tested with the answers that documentation shows. The first real account is the remaining check.

Nothing a company registers is removed. It is accepted because history must stay readable and a mistake must be undoable. What limits it: the largest tables are partitioned by month. Removal after retention is still to be designed. See ADR-0011.

Row level security, definer functions and partitions are features of this database, and they are what makes the isolation enforceable. The schema uses PostgreSQL 18 and five extensions (postgis, pg_trgm, btree_gin, btree_gist, unaccent), which a hosting service must offer. Moving to another database engine is not a goal.