List, board, and map show the same task

When the team says “Trello for the board, a map for the field, a sheet for reports,” three statuses appear in three days. The office card says “doing,” the field Excel says “done,” the report sees neither. The villain is not people — it is the second database. In Ontra a view is a lens. List sorting does not delete the record. Board columns are generated from the custom status record. Map pins come from the task location field.

This model keeps field and office in the same sentence. A technician opens the card on mobile; photo and location write to the record, not to chat. The office sees it on the same card the next morning. No separate gallery app, GIS, or “field Excel” is born. If signal drops, the card is opened ahead of time, the photo stays local, and it writes with the same task id when the link returns.

Save the filter you reuse. “Late this week”, “my open work”, “client X folder” open in one click. A personal shortcut does not rewrite someone else’s board. A shared saved view is a team contract: “late items” means the same thing for everyone. Do not mix the two. Ten shortcuts are clutter again. Three are enough: today, late, waiting on approval. Drag to change pin order.

On day three a new member should see the three shared views and build their own pins. Do not force “the same desktop for everyone.” The ritual is shared; the shortcut is personal. A filter does not rewrite the project record; it changes the lens. That is why the fear “you broke my board” is misplaced — what broke is an unsaved temporary sort.

“Doing / done” is not enough for every team. “Review” means code review to one person and client approval to another. Name the status and bind who may move it to a role. If internal review and client approval share a column, the sprint lies as “stuck in review.” Two statuses, two roles, two report filters. You mark which statuses count as done; close speed does not break. A new column does not need a new tool.

A technician does not need every project. List and map show only assigned work. If location lives in a separate GIS tool, status scatters again. The pin sits on the task card. The office plan does not force a milestone onto the field — linked tasks are already visible. That is not condescension; it is fine-grained access in the field.

The office opens “late today” on the list. The field sees the same card’s pin on the map. Management reads the column on the board. Three sentences are one record. If one marks “done,” all three are done. A separate GIS, Trello, and Excel turn three sentences into three truths. Ontra changes the lens, not the database. List sorting does not delete. Board columns come from the status record. Pins come from the location field.

A saved view is a contract. “Late” means the same for everyone. A personal pin does not rewrite someone else’s board. Three shortcuts are enough: today, late, waiting on approval. Field may add a fourth “near me.” A fifth is noise. On day three a new member sees the three shared views and builds their own pins. Do not force the same desktop on everyone.

Mobile opens the same record. Photos land on the card, not a gallery app. When signal drops the card is opened ahead of time and writes with the same id. “I’ll put it in Excel tonight” is hidden delay in the field. The evening row contradicts the morning board. One record kills that contradiction. Field access is narrow: `tasks.assigned_only`. A technician does not browse the whole project.

The office opens late-today on the list. The field sees the same pin on the map. Management reads the column on the board. If one marks done, all three are done. A separate GIS, Trello, Excel turn them into three truths. Ontra changes the lens, not the database. Sorting does not delete. Columns come from the status record. Pins come from the location field. Mobile opens the same record. Photos land on the card. When signal drops, writes return with the same id. Evening Excel is hidden delay.

A saved view is a contract. Late means the same for everyone. A personal pin does not rewrite someone else’s board. Three shortcuts: today, late, waiting on approval. Field may have a fourth near-me. A fifth is noise. The shortcut sits on the server. A different board on mobile is a second truth. On day three a new member sees the three shared views. Do not force the same desktop. Ritual shared, shortcut personal.

Field access is narrow: assigned_only. A technician does not browse the whole project. The office does not force a milestone. Wrong site is born of a wide role. A field vocabulary can be planned, on the way, on site, done. The board generates columns from that record. No new tool. A filter does not rewrite the record. You broke my board is an unsaved sort.

Three lenses are one sentence. If that sentence breaks, report, board, and map each want their own meeting. Ontra turns the meeting into a report because the record is one. A view does not clone. A clone is a second database. A lens is enough.

Do not let a field photo land in a separate gallery app. Ontra mobile opens the card; photo and location write to the record, not to a chat. The office sees it on the same card the next morning.

A shared “late this week” view carries the same definition for everyone. A personal shortcut does not rewrite anyone’s board. Do not mix the two.