An occupied building has a working day to protect. Someone is taking calls, using a meeting room, checking in visitors or trying to finish a shift. Before counting connections, write down what must keep working while the project happens.
You do not need to design the network yourself. The preparation is about giving the people quoting it enough context to identify the work, the unknowns and the coordination needed.
Mark what happens in each space.
Use a floor plan if you have one; a simple sketch is useful too. Mark current work areas, proposed changes and equipment locations you already know. Include rooms whose use varies. A quiet training room today might be the busiest room in the building on another day.
For each area, list the activities it needs to support: desk work, wireless devices, phone calls, video meetings or another defined use. Note equipment that is staying and equipment still being chosen. “Unknown” is a useful answer when it is visible in the brief.
Keep existing trouble spots separate from new requests. “Calls drop in this room” describes a problem to investigate. “Add a connection on this wall” describes a requested change. Recording both helps avoid assuming the requested change will solve the problem before anyone has assessed it.
Define access and interruption together.
List occupied hours, busy periods, restricted rooms and the person who can arrange access. Explain whether work can move between areas while people remain onsite. If a landlord, facilities team or another contractor must approve access, identify that dependency early.
Be specific about interruptions. Instead of “keep downtime low,” write which activities cannot stop, which could move temporarily and who would approve a planned interruption. Share any required notice period and who will communicate with staff.
For example, a front desk might need to remain usable while a back office can be cleared for a morning. Put those differences in the brief so the proposed schedule accounts for them.
Put a name beside each responsibility.
A network project can involve cabling, internet service, equipment, configuration and applications. Write down who currently looks after each part. Flag gaps before asking bidders to make assumptions.
When cabling work overlaps with meeting-room technology, business phones or IT support, describe the connection in the brief. A room can have its physical connections completed while equipment setup or application access still needs an owner. Make the expected finished state explicit.
Compare what each quote assumes.
Ask each provider to identify included work, exclusions, unresolved site questions and responsibilities assigned to others. Check how access arrangements, equipment setup and any planned interruptions are handled. Two totals are easier to compare when those assumptions are visible.
Agree what completion means: which checks are included, what will be labeled, what documentation will be handed over and who takes responsibility afterward. Testing and documentation requirements belong in the scope conversation; they should not be guessed from a short equipment list.
LVC groups installation work under Building Technology and ongoing business support under IT Support. A project can involve both; the proposal should make each responsibility clear.
To discuss a project with LVC, start with the location, building use, desired timing and what needs to keep working. The site conditions and agreed responsibilities will shape the next step.