Concept

What anti-template means in Rose Rocket: your box, not ours

Anti-template means Rose Rocket starts from your own objects, boards and rules, not a fixed form, so the system matches how your operation already works.

Published September 22, 2026Verified on release 2026.9
Object BuilderBoard BuilderRocket EngineOrdersCustomersInvoicesBoardsCustom objects
A brokerage's own lanes table floated over a forest road: Lane, Mode, Rate and Status columns, with Dallas, TX to Pittsburgh, PA FTL at $3,850 Active, New York, NY to Austin, TX LTL at $1,200 Active and Los Angeles, CA to Seattle, WA LTL at $2,450 Inactive
On this page3 sections
  1. What it is
  2. Why a template fails a trucking operation
  3. What starting from your objects looks like
  4. Where you meet it in Rose Rocket
  5. Go deeper

What it is

A template is someone else’s box; Rose Rocket starts from your own objects, boards and rules so the system matches how you already work.

A template is a fixed order form, a fixed board and a fixed set of rules, decided before anyone at your company saw it. For example, a brokerage runs dedicated lanes, bills a tarping charge and a lumper fee to some customers only, and has one customer that wants its own PO number and a signed BOL before any invoice goes out. A fixed order form has no place for the lane, the accessorials or the paperwork rule, so the desk keeps them somewhere else. In Rose Rocket that brokerage adds those fields to its Order object, filters a board to the lanes it runs, and writes a rule that holds the invoice until the BOL is attached.

Why a template fails a trucking operation

Every operation books, moves and bills differently. One carrier quotes by the mile and another by the pallet; one brokerage needs a carrier’s insurance date on every load and another never asks. A fixed form fits none of them exactly, and the gap does not close on its own. People fill it with a spreadsheet beside the software, a note in the free-text box and whatever the senior dispatcher keeps in their head. The real information about the operation then lives outside the system, where a board cannot filter it, a rule cannot check it and a new hire cannot find it. Out-of-the-box software is out of someone else’s box: its shape was chosen before your operation was in the room.

What starting from your objects looks like

Instead of a form to adapt, you start with the things your operation already tracks. An object is one kind of thing, such as Order or Customer, and you add the fields your desk collects, for example a tarping charge or a required BOL. A board lists the records of an object, and a view is a saved tab of that board with its own filters and columns, so dispatch, billing and sales each see the orders their desk works. A workflow is one of your rules written into the system, for example holding an invoice until the BOL is attached. The system ends up shaped like the operation because it was built from the operation’s own nouns.

Builders call the result configuration.

Where you meet it in Rose Rocket

  • Object Builder (Settings › Builders › Objects, then an object such as Order) → the object’s field list, with a Custom pill on each field your team added → the order form is your own, not a template’s; see Object Builder.
  • Configure on the Orders board (Operations › Orders) → Configure View with the view’s filter, sort, grouping and columns → a board shaped to one desk; see Board views.
  • Workflows table (Settings › Builders › Rocket Engine) → a row per rule with its object, event, condition and action → your rules, written where the system reads them; see Platform basics.

Go deeper

More on Orders, Customers, Invoices, Boards, Custom objects