Other tables and charts pull their data and calculations from that table.
I used this “one big table” concept for the reason that, should you intend to add new features like detailed tracking of replenishments, it’s difficult not to have a complete overview of what’s going on in each of a particular item’s attributes when playing with values.
The medical staff working on the ambulance have the Coda mobile app installed on their smartphones (most EMS organisations have their staff equipped with work mobiles), alternatively a Coda website link on the smartphone home screen to ensure they immediately land on the right page.
If desired and feasible, each ambulance team could use its own Coda account for the sake of better traceability.
Following an emergency response, whenever the staff replenish an item from the inventory, they search the according item in the app, do a right swipe and press the red button. So a single use of that item is recorded.
The staff could also be encouraged to report any inconsistencies they discover.
page, one or several users working as stock controllers can be enlisted and set as active during the time they are in charge.
Whenever an item’s stock gets low as defined per the selectable threshold, a Coda notification for the currently active controller(s) is triggered. The message contains the affected item and its current stock.
For this to work well and swiftly, encouraging the stock controller to have the Coda app installed on their smartphone would be reasonable.
Similarly, on 1st of every month Coda notifications are triggered in case of an item’s upcoming expiration date (i.e. in the current month).
Generelly, this Doc will work on a free Coda plan with limited object and automation quotas.
It stays below the 50 objects that are allowed in the free tier.
Also, automations will not reach their monthly quota limit since they only affect the quota if they are actually executed.
An obstacle concerning the 1000-rows-limit in the free plan may be the