Model both demand and access population
Prepare two estimates: who needs access over the project period and how many will work simultaneously at the busiest point. Include teaching peaks and overlapping research deadlines. The manufacturer’s permitted client scope and seat conditions still apply; a concurrency estimate is not a promise that any number of people can share the arrangement.
Identify the operating responsibilities
Name the team that will operate the license service, install clients and handle user access problems. Record the devices and campus network environment. Ask who will check connectivity and maintain the setup during the term. A procurement approval without an operational owner can leave researchers unable to use the purchased access.
Plan remote access explicitly
Describe researchers working off campus, shared facilities and any institution-managed connection method. Ask IT to verify the proposed configuration against the current manufacturer requirements. Do not assume that an existing campus setup automatically covers every remote device or that offline use is available under all arrangements.
Run an institutional acceptance check
Before wider rollout, verify access from representative approved devices and the relevant connection locations. Include a realistic simultaneous-use scenario and a process for reporting access issues. Keep research content separate from licensing tests; private interviews or participant records are unnecessary for checking license availability.
Different server-license populations
MAXQDA distinguishes Network for a defined group, Free-Floating for a wider institutional population within a quota, and Campus/Site scope. State both the eligible population and simultaneous demand. The server environment and permitted client access must match the selected model, rather than treating every server license as interchangeable.
Plan your purchase
- Peak simultaneous usage
- Responsible IT administrator
- Remote access and device requirements