Describe the workload in operating language
A compute brief becomes easier to discuss when it starts with the work people recognise. A continuously available information service, a scheduled image-production run and an occasional analytical exercise have different patterns of demand. The brief should identify users, processing windows, information location and acceptable waiting time. Those details give technical specialists something concrete to interpret and help a commercial sponsor understand why infrastructure choices cannot be reduced to a list of machines.
Make the uncertainty part of the brief
Early demand estimates often contain several kinds of uncertainty: how many people will use a service, how often they will return and what tasks they will attempt. A useful profile separates known behaviour from a future planning assumption. It also identifies what would change the next decision. If an interactive task becomes scheduled processing, for example, the acceptable operating conditions may shift. The team can then direct early investigation toward assumptions that genuinely influence the options.
Compare environments using a shared reference
CAMPUS uses a concept workload profile to compare site, power, cooling, connectivity and support considerations. Each candidate option answers the same brief, making differences easier to inspect. A spatial drawing can explain where equipment and service areas might sit, while the assumptions register explains what remains to be established. Commercial and technical readers can then discuss the same proposal without assuming that a clear drawing means every underlying condition has already been verified.
End with a decision and the material it requires
The first advisory pack can be compact: a workload profile, candidate options, an assumptions register and a next-stage information list. Its purpose is to establish a useful decision sequence. One question may require site investigation, another a discussion with an information owner, and another a resource partner. Assigning each question gives the project a practical route forward. Detailed engineering follows the needs and conditions established through that route, with the reasons behind its choices remaining readable.
Editorial draft prepared for the BGX concept preview. This is not a regulatory announcement or evidence of a deployed client project.