The BOINC client knows the deadline, so will report before the deadline if there's an usable network-connection. Any "ready to report" tasks will be reported:

1: Next time asks for more work.
2: If < 24 hours until deadline.
3: If < "Connected..." until deadline.
4: Immediately if user has set <report_results_immediately>.
5: If sends a trickle-up message (projects like CPDN only).
6: If user manually hits "update".
7: If <next_rpc_delay> is over (project asks all clients to re-connect in N seconds).

Rule #2 will make sure all work finished before deadline will be reported before deadline, as long as there's an usable internet-connection.

Oh, and even if you report after the deadline, WCG is AFAIK the only project that has a "grace-period", and will accept all (*) tasks even they're reported upto N days after the deadline. Not sure, but it's maybe 3 days WCG is currently using.

(*) Well, unfortunately it seems beta-tasks doesn't follow the rules, and even if you report before the deadline you'll not always get credited for your beta-work.

Not surprisingly it matches, since once-upon-a-time I added half of the items on the list to the unofficial BOINC-wiki, and the WCG-FAQ has copied this old copy.

Just did an edit of the Wiki, splitting the reasons into two blocks with "common" and "less frequently used (project-specific or config-specific) triggers", and added a bunch of reasons, bringing the total up to 17.

See http://www.boinc-wiki.info/Ready_to_Report

You'll need to update the WCG-FAQ if so desires.

Two wingmen have to wait long, which of the long running type A-inconclusives was the valid one:

BETA_ erag_ a163_ ps0000_ 0-- 607 Valid 6-10-09 20:38:49 10-10-09 03:44:53 60.04 531.8 / 557.5
BETA_ erag_ a163_ ps0000_ 1-- 607 Invalid 6-10-09 20:38:25 9-10-09 11:08:12 59.09 752.3 / 557.5
BETA_ erag_ a163_ ps0000_ 2-- 607 Valid 6-10-09 20:38:08 12-10-09 07:29:13 39.79 583.3 / 557.5 <-- mine

Hmmm,
seems that a further single WU was sent for all WUs with state Inconclusive while singe WUs with Pending Validation (e.g. BETA_erag_a175_ps0005) turned to Too Late.
I have more Inconclusive than PV... :-)

I care about the one I had!

BETA_erag_a003_ps0000 was returned well within time, was siting in PV and now is too late and getting nothing?

If it had failed part way or was returned with invalid results I could accept it, but to turn in a 66.65 hr WU and have it binned without even confirming if the result was valid or not seems a bit harsh when invalid results are getting credit.