Stop 6 of 9 · Weekly
Survey to proposal
Site survey notes become an engineering brief the shared SE can answer in one sitting, and the design comes back as a proposal with a CFO page whose numbers Wael fills.
Two handoffs, both of which usually leak
A survey happens, Wael writes notes on his phone, the notes sit for three days, the engineer gets a message with half the constraints in it, the design comes back missing a site, and the proposal gets written the night before. Each handoff loses something. This stop closes both.
The artefacts are the engineering brief and the proposal, and your manager reads the CFO page of the proposal.
Survey notes into an engineering brief
The brief has five parts and fits on a page: the sites with addresses and what is physically there, the constraint at each site, the services the customer asked for, the questions only the engineer can answer, and what Wael already checked so the engineer does not repeat it.
Here are my raw site survey notes for nine sites, dictated on the day: [paste the notes]. Turn them into a one-page engineering brief. Table one: site, address, what is in the comms room today, the physical constraint I noted, and the service requested. Table two: the questions only an engineer can answer, each with the site number it belongs to and the reason I cannot answer it myself. Below that, one short list of what I already confirmed on site so he does not check it again. Where my notes are ambiguous about a site, put the site in a third list called unclear rather than guessing. Include no network diagram content and no addresses beyond what is in my notes.
The unclear list is what stops the design coming back wrong. Wael calls the facilities contact, fixes three rows, and sends a brief with nothing missing.
The design back into a proposal
| Proposal section | Source | Numbers |
|---|---|---|
| What we understood | The account plan and survey | None |
| The design in plain words | The engineering response | None |
| Delivery and cutover | The engineering response | Dates only |
| Commercial shape, the CFO page | Wael and the rate tool | All placeholders |
| Terms and next steps | The Carrier Project | None |
Attached: the engineering response and the account plan: [attach both]. Write the proposal in the five sections above, using our template headings. The design section explains the design to a non-engineer in under 300 words with no product name longer than three words. The delivery section carries only dates that appear in the engineering response. The CFO page covers term, what is fixed and what varies, what happens at the end of term, and who carries the risk if a site is late. Every rate, total, monthly charge and saving is a bracketed placeholder, and you list all of them at the end under "Numbers Wael fills". Then list every claim in the proposal that is not supported by the two attachments.
Here is the finished CFO page: [paste the page]. Write the six-sentence note that sits above it in the email. It names the decision I am asking for, the term, the two things that vary, and the date the design expires for engineering reasons. No rates, no savings, no percentages of any kind. If a sentence needs a number, write it as a placeholder and tell me which one.