I suspect this won;'t come across well, but...better to have it right, than fast. Expediency is an operational consideration, but since the premise is we're doing 'science', then inconveniences on doing it right trump the 'gains' in getting 'a result' quickly. Personally, I;'d rather have the r9ight result, than the 'fast result'. In a perfect worlkd, they're the same.
This is, of course, a huge issue at the moment. Our capacity to 'construct' a model, and 'derive estimates' from it has in many instance exceeded our capqability to assess fit of the model to the data in the first place. Sometimes, the problem is conceptual -- a saturated model isn't always defined. In such cases, unclear how to proceed. In other cases, there are numerically intensive resampling approaches which may be the best you can do (the median c-hat,in MARK, derived from some early suggestions by eorge Sevber, is an example of same). The problems with GOF testing are many -- is the lack of fit due to structural incomaptability of the model with the 'true' structure of the data, or is it because of poorly beaving 'animals' who don't understand that they should all flip completely independent multinomial coins for various life events. In my experience, there is a subtle but important conflict between the two -- in the latter case, most folks seem content with estimate some sort of measure of lack of fit (the ubiquitous c-hat), used in some sort of quasi-likelihood adjustment to model selection (via AIC or otherwise). The estimation of c-hat becomes an estimation problem. But, the estimation is not informative -- it doesn't give any clues as to 'why' there is a lack of fit, merely, it estimates the magnitude of the lack of fit. Without knowing why there might be lack of fit, its hard to know if the model structure, given the data, is flawed from the outset. In other words, there is information in lack of fit that might be important (i.e., it isn't like all due to extra-binomial noise).
So, what to do? In the absence of a reasonable abiulity to estimate/parse lack of fit (note: because it might take a long time on a computer does *not* constitute reasonable -- compute time is cheap, realtive to the cost of collecting the data. If it takes hours -> days to run a model, so what, other than the risk that your system crashes before its done), what I've often suggested, which is admitedly ad hoc, but which at least has some conceptual basis, is to evaluate the 'sensitivity' of the model selection criterion (say, randkings based on AIC) to different values of c-hat. Default is 1. Then, you try 1.1, 1.2...2.0 or so. If the basic rank order of models stays more or less constant, you're probably fine/safe. If, on the other hand, you get 'big' jumps in rank order, especially for c-hat in the 1.0 -> 2.0 range, then I'd be pretty suspicious. I did a fairly large simulation experiement at one point that showed that big jumps in rankings often strongly indicated basic structural causes for lack of fit.
As a (somewhat) related aside -- as c-hat goes up, various 'rules of thumb' for using relative normalized AIC weights as the basis for model selection require more thought (since everything gets 'more conservative'). This is treated in some detail in Edwards 'likelihood' book, and in precis form in the MARK book in a couple of places.
At any rate...