A Shared Campus Recording Booth Procurement Checklist
Share
A shared campus recording booth needs one specification that teaching staff, student media, facilities, IT and purchasing can all review. Each group sees a different part of the project. A room that fits the equipment may still lack an agreed booking owner, a supported recording workflow or a workable route for installation.
Start with the service the university intends to offer. Then connect each requirement to an owner and evidence. This university recording booth procurement checklist is a planning tool, not an institutional certification or approval for a particular education activity.
Define the service before selecting the enclosure
Describe the initial recording tasks in plain language: course narration, student-produced audio or another institution-approved use. List the expected equipment and operating positions. Separate activities the institution is ready to support at launch from ideas for a later phase.
For each task, identify who sets up, who records, who helps when something fails and what the user should leave with. Do not assume that buying a booth also supplies recording equipment, software support, editing or training.
Write a short launch statement: “This space will support the following approved recording tasks, using this equipment, during these staffed or independently supported hours.” Leave unresolved details visibly pending. That statement gives the procurement group something specific to evaluate.
Give every decision an accountable owner
Invite stakeholders early enough that their requirements can change the specification. One project lead can gather decisions, but that person should not have to guess another department's technical or policy requirements.
| Reviewer | Decision to resolve | Evidence to retain |
|---|---|---|
| Teaching and learning | Supported instructional tasks and training scope | Approved service description and orientation outline |
| Student media or media services | Recording workflow and equipment needs | Equipment list and sample workflow using approved test material |
| Facilities | Location, installation route and building requirements | Survey, drawings and required project reviews |
| Accessibility lead and prospective users | Functional access requirements and review process | Agreed requirements and qualified assessment for the proposed installation |
| IT or audiovisual support | Accounts, software, connections and support boundary | Supported system list and file-handling procedure |
| Service manager | Booking, opening hours, handovers and incident response | Named primary and backup owners |
| Purchasing | Complete supply and service scope | Current quote, exclusions and institutional purchasing review |
These roles may sit in fewer departments on a smaller campus. The important distinction is between gathering a requirement and approving it within the institution's process.
Survey the actual location and delivery route
Document the proposed room, available floor area, ceiling, door approach, nearby equipment and intended component positions. Include the route from the delivery point to the assembly location, including any hallways, stairs or elevators involved. Ask facilities what evidence it needs for floor-load and other building reviews.
Use the LAVB dimension page as a starting reference. Nominal size names are not exact usable interior measurements. Model and acoustic treatment affect the space available inside, and exterior planning must include ventilation and assembly clearance.
Keep the survey separate from approval. A marked floor outline can help the team discuss a layout, but it cannot verify door operation, structural suitability or accessibility. Record the exact drawing revision reviewed and update it if the configuration or location changes.
Specify a supported recording system
List the computer, interface, microphones, monitoring, furniture and other equipment the service will actually provide. Identify what a user may bring and what staff must approve before connection. Assign software licensing, updates and troubleshooting to the appropriate team.
Ask where controls and connections need to be reached in the working layout. A connection available somewhere in the enclosure may be inconvenient behind installed furniture. Review cable routes with the relevant technical staff rather than improvising them after delivery.
For LAVB, Standard provides exterior power access and Premium adds interior power access. The booth is not hardwired and does not include built-in wall outlets. Check the power options and have the appropriate team confirm the actual equipment requirements. A package name is not an electrical design approval.
Decide how users get a session and help
Define who can book, what orientation is required and how the institution handles competing demand. Decide whether bookings include preparation and handover time. Base these choices on the service and staffing plan rather than an assumed universal session length.
Name the person or team that answers a failed-login question, an audio problem and a physical equipment problem. Give users one clear first contact, with an internal escalation route behind it. Confirm what happens when that contact is unavailable.
Before opening, test the booking instructions from the user's perspective. Can someone find the eligibility rules, request needed assistance, understand the equipment provided and learn how to report a problem? Resolve gaps before advertising independent use.
Establish authorized recording and file handling
Have the institution define the activities and recording permissions it allows. Booking a space should not be treated as permission to record another person or use material without the necessary rights. Route project-specific questions through the institution's existing responsible office.
Ask IT and the service owner to agree on approved accounts, storage, export, retention and staff access to files. Explain those arrangements in the orientation. Do not promise that the enclosure itself establishes confidentiality or that recorded material is automatically protected by the room choice.
Keep the procurement worksheet free of student recordings and personal information. The committee can review an equipment demonstration with institution-approved test material. Operational evidence does not need to include someone's real coursework or account details.
Include ongoing care and equipment reset
Assign responsibility for the baseline equipment arrangement, current instructions, consumable supplies and reporting visible damage. Identify who may adjust equipment and who decides when an unresolved fault prevents the next booking.
Use a separate operating reset sheet once the service opens. The procurement document should name its owner and acceptance criteria, without becoming a second, competing checklist. Require current manufacturer-approved care guidance for the booth and each equipment type before setting local procedures.
Include staff time and ongoing support in the project scope. A one-time purchase decision can leave a recurring workload, even when the hardware itself meets the agreed specification.
Request evidence against the exact configuration
Send the supplier a concise requirements packet: proposed location, measured route, intended layout, equipment needs and questions that remain open. Request current drawings, configuration details, delivery responsibilities, available installation services and a quote that separates included and additional costs.
Do not treat “review requested” as “requirement met.” For each open item, record the responsible reviewer, the answer needed and the document that will establish it. A supplier's explanation of a product feature and an institution's approval serve different purposes.
Before committing, check that the quote matches the reviewed configuration. Changes to the model, door position, accessories or room can invalidate earlier assumptions. Keep purchasing and technical reviewers working from the same version.
Include launch readiness in the decision
Create three final lists: requirements resolved, requirements awaiting evidence and work needed before opening. Assign a person and next action to every unresolved item. Keep any affected purchase or launch decision pending until the responsible reviewers resolve it.
After installation, verify the agreed setup, orientation and support route with approved test material before inviting routine bookings. This acceptance exercise checks the campus's actual service; it does not create product certification or replace specialist reviews.
Use the stakeholder checklist to request a project-specific review from LAVB. A clear requirement, a named owner and the right evidence make the next decision easier for everyone involved.