Boards add a controlled process on top of the records your team already trusts: clear stages, a responsible person or team, due dates, and complete history. Work moves forward without splitting into spreadsheets, side trackers, or disconnected copies.
A board item carries process state and history; the underlying record keeps its own data, access rules, and change history.
One source of truth
The board tracks the process; your record stays the single source of truth, with the same data, access, and history underneath.
Right team by location
Assign each item to a person or team, and use location context to suggest or pick the group that should handle the work.
Kanban or cycles
Run a continuous board, or plan in cycles with rollover for the work that is not finished yet.
//How a board moves work
From intake to done
01
Intake
A record, or a standalone item, enters the board in its starting stage.
02
In progress
Responsible people and teams move it forward along the transitions you allow.
03
Review and blockers
Open child items can keep a parent from closing until they are done, and due dates flag anything that is slipping.
04
Done
The item closes, and the record keeps its full process history.
Built-in controls
Only permitted people can add, move, or close work.
Moves, responsibility changes, and due-date changes are recorded in the work history.
Sensitive records stay masked when a viewer is not allowed to see them.
The hidden cost of copies
When work is copied into a side tracker, the record and the process drift apart. Status lives in one place and the real data in another, and no one is sure which is true. Updates get lost, responsibility blurs, and the proof of what happened breaks.
Where Boards fit
Boards keep the process and the record together. The same object can appear on one board or many, come back for another pass, and still be the one governed record underneath, with its own access, fields, and history intact.
What a board manages
Stages and the allowed moves between them
A person or team for each item and a responsible team for each stage
Due dates with due-soon, overdue, and at-risk signals
Item links, parent and child work, and blockers
Process comments, attachments, and movement history
What stays with the record
Business fields, related records, and relations
Record-level and field-level access rules
Tags and the record's own change history
Reports, maps, and integration events
01
01How Boards work
Everything a process needs, governed by default
A board is more than columns. It carries the rules, people, timing, and evidence that operational work needs to stay accountable.
01
Stages and transitions
Define the stages work moves through and the exact moves allowed between them. No skipping steps unless you decide to allow it.
02
Responsible people and teams
Assign each item to the person or team handling it, and give each stage the team responsible for moving work forward. People can act because they are responsible, without opening the whole board to everyone.
03
Routing by location
When location context is configured, use the work's address or coordinates to suggest or assign the team responsible for that zone or territory.
04
Due dates and signals
Set a deadline per item and turn on due-soon, overdue, and at-risk signals so nothing quietly slips.
05
Cycles and rollover
Plan work in sprints, waves, or operating periods, and roll unfinished items over to the next cycle on your command.
06
Links and blockers
Link related work and parent or child items. A parent cannot close while a child is still open.
02
02Responsibility
Responsibility that can follow the work
Boards make accountability explicit. An item can have a responsible person or team, a stage can have the team that owns that step, and location context can help route work to the group that should handle it.
Location context can help identify the responsible team, so work reaches the right people with a clear history.
01
Person or team responsible
Assign a person or team to an item. Responsibility travels with the work as it moves between stages.
02
Team responsible for a stage
Give a stage a responsible team. That team can act on the work in the stage, and only on that work.
03
Routing by location
When a board has location context, Moltaro can read the work's address or coordinates and suggest or assign the team responsible for that zone.
04
Just-enough access
When someone becomes responsible, a board can grant the contextual access they need, and take it back when they are done.
Run intake, dispatch, field visits, and follow-ups, with territory-based responsibility when location context is available and progress tracked end to end.
Review and approval
Move requests through review, approval, and sign-off, with each stage gated to the people allowed to act on it.
Production and cases
Track production work, quality rework, returns, or case handling across connected stages with blockers and complete history.
04
04Why Boards
Governed, not just another board
Most boards are a wall of sticky notes. Moltaro Boards are an operating layer with permissions, accountability, and proof built in.
