The software I am developing is a multi-relational database constructed in Filemaker Pro, as I consider it a rapid development tool. I have been a Filemaker Pro developer for decades and created many large databases. It could easily be ported into C or PHP if necessary.
Input is based on simplicity. Each task that must be recorded, has a simple "form" showing and requesting ONLY the required info to document that task.
Picture an Excel spreadsheet with 50+ tabs, all sharing data with each other, some fields overwrite other fields on other tabs when changed, etc. Consider the potential for error when multiple users make updates, with no change tracking, often in a hurry, or while actually working on a plant. Yucch!
All of that info instead can be stored in true relational databases. For humans to access this database to read info or make changes, they pull up the appropriate form. This form is like a scratch pad. Tasks can easily be entered either per plant, or per group of plants as desired. User can make changes, verify info, and when they think all is well, they click a "Commit" button to publish the info they have entered on the form.
This is where the magic happens. The software checks all necessary info any number of ways, and requests clarification from user if an "issue" is found. i.e. you recorded that you made a cutting from plant with serial number #1234, before committing the information, it must be verified that plant #1234 exists, and is at an appropriate stage for making cuttings. The genetic link must be recorded and maintained (both ways), to allow for easy viewing of crop genetics.
Database tracks inventory of all equipment and inventory owned by the business. You can plant some "pot", if you don't have POTS, and some stuff to put in the pot (or Rockwool) right? I have it printing sticky labels for pots, and sourced a dedicated label printer for under $500 that makes tough labels then laminates them. It contains a format for SOP's and can assist in generating them while minimizing re-typing and copy/pasting.
The "ULTIMATE" goal would be to see growers/workers work carrying a Toughpad and recording their tasks as performed, allowing accurate time stamping. Tasks could alternately be written in traditional paper log, then entered into database via batch mode.
Phew, sorry for long post. This is first time I have posted about this in public. Any questions?