what your team can
actually do in tally.

Six workflows teams run every single week. Find a part, log the movement, move between shelves, approve a transfer, pack for competition, and keep the budget honest. No manual required.

fuzzy search
V5 Smart Motor
Bin A3 · qty 4 · last moved 14m ago
fuzzy hit
location
Workshop / Shelf A / Bin A3
next move
Withdraw from result card
what the team learns
Search tells you the part, where it lives, how many remain, and how recently it moved.
01  /  fuzzy search

Search by the way people actually talk.

Students type partial names, wrong spellings, or whatever label is on the bin. Tally still gets them to the right part — name, SKU, location, or typo. Every result shows quantity, bin, and last movement side by side.

  • +Fuzzy match handles typos like v5 moter without missing a beat.
  • +See qty, bin, and last-moved timestamp inside the result card.
  • +Jump from a search hit straight into a withdraw or deposit.
part card · actions
V5 Smart Motor
Bin A3 · 11W · stored at Workshop / Shelf A
Withdraw
qty 4 → 3
Deposit
qty 3 → 5
Trade
to Team 1234B
audit trail
Every action writes to inventory_adjustments. No silent mutations.
02  /  three-button actions

Withdraw, deposit, trade. Every tap writes audit history.

Every part card has three buttons and only three buttons. No silent mutations, no spreadsheet fudge. Every tap creates an inventory_adjustments row with who, what, when, and why.

  • +Withdraw, deposit, and trade share one consistent flow.
  • +Undo toast for destructive actions — no orphan changes.
  • +Server-side checks enforce approval before trades commit.
location hierarchy
Workshop
214 parts · 5 shelves
Shelf A — Motion
94 parts · 8 bins
Bin A1 — V5 Motors
12 parts · updated 14m ago
Robot Bay
89 parts · active build
Competition Crate
44 parts · sealed for transport
parts in this location
Workshop
214 parts · 5 shelves
Shelf A — Motionqty 94
Shelf B — Structureqty 62
Shelf C — Electronicsqty 38
Drawers 1-4 — Fastenersqty 20
03  /  location hierarchy

Workshop, shelf, bin. The tree matches your room.

Build a hierarchy that mirrors the physical shop — rooms, shelves, bins, drawers. Drill down to see exactly what lives where and let students navigate their way to the right spot.

  • +Nested locations — workshop to shelf to bin to drawer.
  • +Direct location links for fast drilldown.
  • +Each level shows the parts and sub-locations inside it.
intra-org transfer
team A · 1234A
has 2 / needs 4
V5 Smart Motors
team B · 1234B
has 6 spare
can lend
1
A requests 2 motors from B
server holds stock pending
2
notification to org owner
approval required · RLS enforced
3
owner clicks approve
transfer commits atomically
4
audit trail written
inventory_adjustments · both teams
04  /  intra-org transfers

Loans and trades between teams, with real approval.

Multiple teams share one shop. Transfers exist to make borrowing explicit and reversible — request, approve, reconcile. The server enforces approval so a student can't just move parts without sign-off.

  • +Create loans with due dates or permanent transfers.
  • +Owner approval enforced server-side via RLS.
  • +Returns reconcile quantities automatically on both sides.
packing list · event kit
competition load-out
Saturday event kit
0/4
battery cart
waiting
driver spares
waiting
hex keys
waiting
pit box
waiting
05  /  packing lists

Pack from a list. Check the same list back in.

Competition prep isn't about loading the robot. It's about making sure the spares, batteries, tools, and pit materials leave with you and come back with you. Packing lists cover the trip out and the trip home.

  • +Build event kits from real inventory, not memory.
  • +Check items out as the van loads.
  • +Return scan flags anything that didn't come home.
season budget · live
spent
$3,200
of budget
$5,000
36% remaining · $1,800 left
recent purchase requests
4× Flex wheels (4in)
$120
pending
Battery cart restock
$240
pending
Pneumatics bundle
$480
pending
06  /  budget & purchasing

Purchase requests meet the budget in one place.

Track purchase requests from submit to receive, watch the budget gauge update as approvals land, and keep the cost data owner-only when you need to. Your sponsors get numbers they can trust.

  • +Submit → approve → receive, all in one log.
  • +Budget gauge updates live as requests commit.
  • +Cost visibility gated by financial_visibility_for_admins.

Learn the workflow, then try it on your own parts.

Open the app, add a few bins, search a real part, and run the whole workflow yourself. That's the fastest way to tell if it fits your team.

open the appread the docs
copyright 2026 consul | tally | all systems operational