A very relevant article at present Steve. Just a few things to add:
Firstly, have the contact details for the site services people on the list, along with contact numbers for power and telecoms providers in case of building damage or power loss. If the utilities can provide direct line numbers even better, as the public numbers tend to get hit hard during natural disasters. Also arrange for key people to use alternative entrances to the building - a power failure can often leave electrically operated security doors unusable.
In a big organisation, it's a good idea to lodge the primary contact sheet with a trusted member of staff, maybe someone from IT security. It should be kept in a sealed envelope, preferably in a fireproof and waterproof safe. This not only protects the contents from disaster, but also prevents people being contacted in non-emergency situations by management.
Another option to consider is providing emergency laptops with dial-in capability.
These can be useful if roads are taken out or weather conditions are severe, and also allow people with long commutes to be useful without being present. All laptops should be tested for connectivity from the staff's home, and all security permissions and expected functionality checked before a disaster. Also ensure that the staff are covered for insurance on the laptops, in case of damage/theft from their home.
Get expenses sheets in with the DR plan, so that people know they're not going to be out of pocket with food and accommodation, and can concentrate on the job. Better still, have someone with a company credit card who's authorised to buy food and accommodation, people feel more comfortable about it than having to reclaim it later.
If you've got an off-site facility that the business can move to, make sure that staff are aware of how to reach it, have contact numbers for it and ideally have them visit the facility before a disaster occurs. Nothing worse than reading a map at night in a storm trying to find an unmarked building !
One final thought : When you've finished the framework, how about adding the collective knowledge into the back of The Best of SQL Server Central Volume 3 as a handy, readily accessible checklist for DBAs?