The official Blackhawk Rescue Mission 5 page describes the headquarters as upgradeable, capable of earning money while you are offline, and able to unlock advanced gear through research. Community references describe departments, staff, resources, and upgrade chains, but numeric tables can become stale. Use the live headquarters screen as the source for every cost and prerequisite.
Inspect before upgrading
Open each current department and note its level, next benefit, resource cost, staff requirement, time, and dependencies. Check whether an upgrade unlocks a function, increases capacity, improves income, enables research, or only advances toward a later prerequisite.
Do not buy from the first panel you open. Compare the next useful upgrade across departments and identify which one removes a real blocker.
Trace dependencies backward
Start at the desired outcome—income, research node, equipment, capacity, or another displayed feature—and follow every prerequisite backward. Write the first unmet step. If the interface shows multiple requirements, confirm all of them before spending.
A cheap node can be expensive when it starts a long chain. Compare total visible requirements with the benefit at the end.
Assign staff deliberately
If the current system requires staff, check whether assignment changes speed, capacity, output, or eligibility. Do not assume a staff member works across every department simultaneously. Confirm whether moving staff interrupts progress or reduces another function.
Before logging out, verify that the intended staff and task are active. A configured-looking panel may still be waiting for a confirmation.
Handle offline income correctly
The official listing confirms offline income, but collection limits, timing, upgrades, and claim behavior can change. Open the relevant headquarters panel after returning, read the accumulated state, and claim through the current interface.
Upgrade offline income only when it supports your play pattern and does not delay a more important operational or research unlock. Players who log in often may value capacity differently from players who return after longer gaps.
Protect an operating reserve
Do not spend every resource on the headquarters. Keep enough cash and supplies for the missions that feed future upgrades. If an HQ purchase prevents you from running the reliable operation that funds it, the timing is wrong.
Use the Money Guide to set a reserve based on current mission expenses rather than a fixed historical number.
Verify completion and benefits
After starting an upgrade, check its active status, remaining requirement or time, and any assigned staff. After completion, reopen the department and confirm the promised feature or capacity is visible. Do not assume the next research node automatically starts.
If the benefit does not appear, check prerequisites, claim buttons, staffing, and server refresh before purchasing something else.
HQ decision card
Income upgrade
Compare current yield, capacity, claim pattern, cost, and how often you realistically return.
Research access
Trace the target item backward through facility, department, staff, resource, and earlier-node requirements.
Capacity or efficiency
Confirm the live before-and-after value and whether it removes a current bottleneck.
Specialist branch
Delay it until the related role is useful and the complete chain leaves an operating reserve.
Recheck after a major update
Operation Typhoon introduced or expanded the headquarters loop. Future revisions can rebalance costs, benefits, staff, research, or offline systems. After a change, reopen every dependency in the planned path and confirm the end benefit still matches the role you want.
Screenshots and tables from community sites are helpful orientation, not purchasing authority. Record the date when sharing numeric advice.
Run an HQ inspection routine
At the start of a session, check claimable income, completed work, active work, staffing, capacity, and the next dependency. Claim or confirm completed output before starting something new. At the end of the session, return to the same panels and verify that the intended long-running state is actually active.
If two upgrades compete for resources, write the operational benefit of each in one sentence. Choose the one that removes the current blocker and delay the other. This prevents a bright notification or inexpensive first level from replacing the progression plan.
Evidence status
The headquarters, upgrades, offline income, and research role are official. Department names, level caps, costs, staff behavior, timers, yields, claim limits, resources, and dependencies are community documented and version-sensitive. Verify them in the live HQ interface.