Capital Room Intake Gate
A capital request for a conference room usually reaches IT after the stack is already chosen. This brief is the six questions to attach before the PO, so the room is supportable once the truck leaves.
Why this exists
Capital buys rooms on a cycle that does not wait for IT. The integrator fills the hole with last year's leftover stack or their default kit. Helpdesk meets that room for the first time when an executive cannot start the call. This gate is the page you clip to the request so support is specified before anyone orders hardware.
The six gates, in short
| # | Gate | Plain meaning |
|---|---|---|
| 1 | Platform you already run | Spec against the platform you run — not leftover kit |
| 2 | Network path, identity, monitoring | Written before the codec is ordered |
| 3 | Named owner after go-live | Weekday and after 5 |
| 4 | First-touch script | Night shift can follow without sitting in the room |
| 5 | Remote reachability | If the building will be empty |
| 6 | Exceptions named + dated | Silence is not an exception |
What is in the PDF
Page 1 is the form to clip to the capital packet: six gates, write-in lines, initials. The pages after that are why each gate fails and what to refuse.
Frequently Asked Questions
When should IT attach this gate?
Attach it before the PO, while the capital packet is still open to change.
What if the PO is already live and three gates fail?
Bring that packet on a twenty-minute call. We mark the three things to refuse.
Does this replace an integrator submittal?
No. This is the owner-side gate IT attaches so the submittal has to answer supportability before money moves.
Do you sell the hardware on the form?
No. We do not sell hardware and we do not install.
Bring us the room.
If a room on a live PO already fails three of these gates, bring that packet. We will mark the three things you should refuse.
Book a 20-min call