Almost like Bob described, some years ago I designed an Excel solution for technologists, where every technologist had his/her own workbook, where info about production orders given him/her was entered, and head of department had his own (main) workbook, where registers of technologists and work orders, etc. were maintained. Technologists workbooks read registers (into hidden sheets) from main workbook using ODBC connections, and main workbook read production orders info from technologists workbooks into specified ranges of it's own hidden sheet using linked formulas. And the main workbook consolidated then all production orders info into separate table using an ODBC query with hidden sheet as source. And finally, the main workbook had various report sheets for department head to use.

The main condition for such design to work is, every user edits only his/her own data (technologists can enter appointed work order details, but can't register new orders, or new technologists, or enter any info for orders appointed for other technologists, and department head can register new technologists, or new work orders, etc., and appoint orders to technologists, but can't enter any order details) - all other data is read-only.