You can do this with event-based scheduling with File Events. The concept is that you set up file events to look for a file with a specific name in a specific folder - the file doesn't have to have anything in it, it just has to be there. Whatever software is doing the data loads will create the file when it's finished loading data. BOE will look in the folder every couple of minutes (interval determined by settings on the Event Server) to see if the file is there, when it is, BOE kicks off the event and anything that is scheduled based on that event will run. So, you set your reports to run at a specific time based on an event. The schedules will start looking for the event at the time they're scheduled to run but they won't actually run until the event occurs.
The trick with using this technique is that the file has to be deleted from the folder and it needs to be gone for a period that is longer than the interval the Event server uses to poll the folder for the file. For example, if your event server looks at the folder every 2 minutes, the file must be missing from the folder for at least two minutes. If you're data load is always guaranteed to run longer than the Event Server polling interval, you can delete the file as the first step in the data load and then create it as the last step. If it may run shorter than that, you'll probably want to run a .bat file on a scheduler to clear out the files at a specific time that is earlier than the data load is scheduled to run. (You don't want to have the polling interval to be too small because that puts a heavier load on the report server.)
-Dell
A computer only does what you actually told it to do - not what you thought you told it to do.