CubeSats are deceptively simple. The form factor is standardized — 1U is 10x10x10 cm with a 1.33 kg mass limit, 3U is 10x10x30 cm with a 4 kg limit, 6U is 10x20x30 cm with an 8 kg limit. These constraints look generous on paper. They are not. Most first-mission CubeSat teams spend the back half of their schedule fighting mass and power problems they could have predicted at SRR.
Start with the mass budget. For a 3U CubeSat with a 4 kg launch mass limit, allocate roughly 40% to structure (chassis, panels, brackets, fasteners), 25% to ADCS and reaction wheels, 15% to power (battery, EPS, solar panels), 10% to comms and antennas, 5% to OBC and harness, and 5% to payload. That leaves you with zero margin if you start with a 4 kg target. The honest planning number for a 3U is 3.0-3.2 kg dry mass with the remaining 0.8-1.0 kg as margin and growth.
The structure number surprises most first-time CubeSat designers. A 3U COTS chassis is typically 350-450 grams. Add internal panels, deployable solar wing brackets, antenna mounting hardware, and structural fasteners and you are at 500-700 grams of "just structure" before any subsystem is installed. Then add MLI, kapton tape, ground straps, and harness clips and you are over 800 grams. The 40% structure allocation is not pessimistic — it is realistic.
For 6U CubeSats the picture is slightly better but the same pattern holds. An 8 kg 6U should be planned at 6.0-6.5 kg dry with 1.5-2.0 kg of margin. Programs that try to use more than 80% of the launch mass at PDR usually end up reclassifying components or downgrading payload at CDR.
Power budgets are where most CubeSat missions fail to close on first analysis. A typical 3U body-mounted solar configuration generates about 2-3 watts orbit-average power at end of life on a non-pointing spacecraft. A 3U with deployable wings can reach 8-12 watts. A 6U with deployable wings reaches 15-25 watts. These are end-of-life, eclipse-included, beta-angle-averaged numbers — not the peak-of-day, pointing-perfect, beginning-of-life numbers from the solar panel datasheet.
Eclipse fraction matters more than most teams realize. A typical LEO orbit at 500 km has 35-40% eclipse fraction, depending on beta angle. The spacecraft must run on battery during eclipse, then recharge plus support its operating power during the sun half. If your orbit-average power generation is 6 watts and your eclipse fraction is 35%, your maximum sustainable continuous load is around 3.5-4 watts after recharge inefficiency. Anything more and the battery slowly drains over multiple orbits.
Battery sizing is driven by depth-of-discharge limits, not capacity alone. CubeSat lithium-ion batteries should be sized for 20-25% maximum DoD per orbit to achieve a 2-3 year operational life. A 20 Wh battery sized for 25% DoD gives you about 5 Wh of usable energy per eclipse. At a 4 W eclipse load and a 35-minute eclipse, that is 2.3 Wh consumed — comfortably within the 5 Wh budget. Tighter DoD targets are better for life but cost mass.
The mass-power coupling is what catches teams. Adding a payload that draws 5 watts may force you to add a deployable solar wing (200-300 g of mass), a larger battery (100-150 g), and more harness (30-50 g). A 5 W payload addition can easily cost 400-500 g of dry mass before anyone has touched a structural element. The mass and power budgets need to be analyzed together, not in isolation.
Common CubeSat budget pitfalls: underestimating ADCS power (a 3-axis stabilized 3U with reaction wheels can draw 3-5 W in fine pointing mode, not the 1 W often assumed); ignoring harness mass (3-5% of dry mass for a 3U, more for a 6U with multiple instruments); forgetting standoffs and brackets (the unglamorous mechanical parts add up); using BOL solar power instead of EOL (15-25% degradation over a 3-year mission is typical for COTS panels).
COTS subsystem datasheets are usually optimistic. Solar panel current is reported at 28°C in 1-sun illumination, which is rarely the operating condition. Reaction wheel mass excludes mounting hardware. Battery capacity is reported at room temperature and beginning of life. Read every datasheet with the assumption that your operating conditions are 10-20% worse than the specified test conditions, and budget accordingly.
Plan for ConOps power modes early. Most CubeSats have at least four modes: safe mode (low power, sun-pointing), nominal (operational power, attitude control on), payload (peak power, all subsystems active), and downlink (high transmit power, pointing). Each mode has a different power balance, and the worst-case mode usually drives the array sizing. Build a power-vs-mode table at SRR and update it through CDR.
CubeSat schedule is short, which compounds the budget problem. Most CubeSat programs run 12-24 months from kickoff to delivery. Major design changes after PDR are nearly impossible to absorb. The teams that ship on schedule are the ones that lock in conservative budgets at SRR and resist the urge to backfill margin with optimism.
SMAD Portal's mass and power budget modules are designed for tight-margin missions like CubeSats. Component-level allocations, maturity codes, growth-adjusted totals, and ConOps power mode tracking are all built in. The Solar Array Sizing and Battery Sizing calculators help you converge on a realistic configuration at SRR — before you commit to a payload that the bus cannot support.