I would suggest that you have a table for bindery which contains fields JobNumber,Description, and the DateOfJob. then you could perform a find on JobNumber and DateOfJob or just DateOfJob.
Think of it as a many to many relationship:
Employees::__pkEmployeeID = Employee_Task::_fkEmployeeID AND
Employees::cToday = Employee_Task::TaskDate
Enable "Allow Creation of Records via this relationship for Employee_Task in the above relationship.
Tasks::__pkTaskID = Employee_Task::_fkTaskID
cToday is an unstored Calculation field with this expression: Get ( CurrentDate ). If you prefer, you can use a date field instead of the calculation field so that the person assigning tasks can select the date instead of always being locked into today's date.
Now you can use a portal to Employee_Task on the Employee layout to assign daily tasks to an employee. _fkTaskID can be formatted in this portal row with a drop down list of TaskID's and TaskNames from the Tasks table.
Now your report can be generated from a computer based on the Employee_Task table. You can perform a find on this layout for all records of a given date and sort them by Employee or you can find all records with a given date and for a specific employee. Either way, you can get report that is only as long as the assigned tasks for the specified day.
Here's a demo file that illustrates this method and that also demonstrates some more sophisticated methods for working with a many to many relationship: https://www.dropbox.com/s/oyir7cs0yxmbn6i/ManyToManywDemoWExtras.fp7