Xavier - I really appreciate you taking the time to respond to my question. Let me give a bit more context around my problem in an effort to show why I need to calculate this in hours.
I am an accounting manager at a mid-sized private company. We are implementing QuickBase to manage our month end close process every month. Each month end close checklist should be the same as the prior month, with small changes being made as necessary. You can think of each close as a project with multiple people interacting as process/task owners in that project.
The heavy portion of our month end close project lasts one week and goes from Monday-Friday - we must close on Friday, so our deadlines will never fall on a weekend. You might then ask why I need to exclude weekends from the calculation. Well, we have dependent tasks that occur in the week prior to our heavy week of month end close and those sometimes spill into the heavy week. I want to measure those as being behind schedule but I don't want to take on the weekend hours.
Due to the short period of time, it is really important for our team to be able to manage if dependent tasks are falling behind schedule down to the hour level. Measuring whether something is behind schedule at the day level would not give us the level of detail that we need to monitor the project's status.
Given that, is there a solution to solving for this in hours?
