In a modern organization, IT infrastructure is never static. Employees join, teams relocate, applications change, devices are replaced, and networks are continuously adjusted to support new business requirements. Moves, Adds, and Changes, commonly known as MAC, is the structured discipline used to manage these everyday infrastructure adjustments without disrupting operations, weakening security, or losing control of assets.
TLDR: Moves, Adds, and Changes are routine IT activities that involve relocating users or equipment, adding new services or assets, and modifying existing systems. A disciplined MAC process helps organizations reduce downtime, maintain security, control costs, and keep accurate infrastructure records. Effective MAC management depends on clear procedures, documentation, approvals, communication, and post implementation verification.
What Are Moves, Adds, and Changes?
Moves, Adds, and Changes refers to a broad category of IT service requests and operational tasks that modify the technology environment. These changes may involve physical infrastructure, such as desks, phones, access points, cabling, and network switches, or logical infrastructure, such as user accounts, permissions, software licenses, cloud services, and configuration settings.
A move typically occurs when an employee, device, department, or service is relocated. This might mean transferring a workstation from one office to another, moving a server workload to a different environment, or reassigning network ports after an office redesign.
An add involves introducing something new into the infrastructure. Examples include provisioning a new employee account, installing additional monitors, adding a phone extension, deploying a new printer, or assigning a cloud application license.
A change modifies an existing service, configuration, or asset. This may include updating access permissions, changing a user’s department profile, altering firewall rules, upgrading hardware, or modifying a network configuration.
Although many MAC tasks appear routine, they can have significant consequences if handled poorly. A minor cable change can disconnect an entire team. A permission update can expose sensitive data. A missed asset record can lead to billing errors, security blind spots, or compliance issues.
Why MAC Management Matters
Organizations often underestimate MAC activity because it is familiar and repetitive. However, the volume of small changes can be substantial. In a growing company, IT teams may process dozens or hundreds of MAC requests each month. Without structure, these requests can become fragmented, undocumented, and difficult to audit.
Effective MAC management provides several important benefits:
- Reduced downtime: Planned and documented changes are less likely to interrupt business operations.
- Improved security: Access rights, devices, and network configurations are reviewed and controlled.
- Better asset visibility: Hardware, software, and licensing records remain accurate.
- Lower operational risk: Standard processes reduce dependency on individual knowledge.
- Faster service delivery: Repeatable workflows help IT teams complete requests more efficiently.
- Stronger compliance: Audit trails demonstrate who requested, approved, implemented, and verified each change.
For regulated industries such as healthcare, finance, government, and legal services, MAC control is especially important. Infrastructure changes can affect data privacy, system availability, and regulatory compliance. A formal process helps ensure that even routine tasks are performed with appropriate oversight.
Common Examples of MAC Requests
MAC requests vary by organization, but most fall into predictable categories. Recognizing these categories helps IT leaders create standard procedures and service catalog items.
Employee and Workspace Moves
When an employee changes desks, offices, floors, or locations, IT may need to move or reconfigure equipment. This can include computers, docking stations, monitors, IP phones, printers, network connections, and access control badges. In hybrid work environments, moves may also involve home office equipment and remote access settings.
New User Adds
Onboarding a new employee is one of the most common add requests. The process may include creating an identity account, assigning email, configuring multifactor authentication, granting application access, issuing hardware, assigning phone numbers, and enrolling devices in endpoint management tools. A reliable workflow ensures new employees are productive from day one.
Hardware and Software Adds
Organizations frequently add laptops, mobile devices, peripherals, servers, virtual machines, storage, SaaS licenses, and collaboration tools. Each addition should be evaluated for business need, budget approval, compatibility, security, and lifecycle management.
Access and Permission Changes
Role changes, transfers, promotions, and project assignments often require access adjustments. These changes must be handled carefully because excessive permissions increase security risk. The principle of least privilege should guide all access-related MAC activity.
Network and Telephony Changes
Network MAC tasks may include activating ports, changing VLAN assignments, updating Wi-Fi access, modifying firewall rules, adding IP phones, changing call routing, or adjusting quality of service settings. Because network changes can affect many users, they should be planned and tested carefully.
The MAC Lifecycle
A complete MAC process follows a defined lifecycle. The goal is not to create unnecessary bureaucracy, but to ensure that each request is understood, approved, implemented, and recorded properly.
- Request submission: A user, manager, or system owner submits a request through an approved channel, such as a service desk portal.
- Classification: IT determines whether the request is a move, add, change, or a more significant change requiring formal change management.
- Assessment: The request is evaluated for technical feasibility, cost, security impact, timing, and dependencies.
- Approval: The appropriate manager, data owner, budget owner, or change authority approves the work.
- Scheduling: IT coordinates timing with affected users and support teams to minimize disruption.
- Implementation: Technicians perform the work according to documented procedures.
- Verification: The requester or technician confirms that the service works as expected.
- Documentation: Asset records, configuration databases, diagrams, licenses, and support notes are updated.
- Closure: The ticket is closed with evidence of completion and any relevant details.
This lifecycle creates accountability. It also helps IT teams identify recurring issues, measure service performance, and improve processes over time.
MAC Versus Formal Change Management
MAC activities are related to change management, but they are not always the same. Many MAC requests are low risk and operationally routine. For example, assigning a standard laptop to a new employee may not require review by a change advisory board. However, some MAC tasks can carry significant risk and should be managed through formal change control.
A useful distinction is based on risk and impact. If a request affects a single user, uses a standard procedure, and has a clear rollback path, it may be handled as a standard MAC request. If it affects multiple departments, critical systems, security boundaries, production networks, or compliance controls, it should be escalated to formal change management.
For example, changing a user’s phone extension is typically a MAC request. Reconfiguring the organization’s call routing architecture is a formal change. Adding a software license for one user is routine. Deploying a new enterprise platform requires broader governance.
Key Roles and Responsibilities
Successful MAC management depends on clear ownership. Confusion over responsibilities leads to delays, incomplete work, and security gaps.
- Requester: Provides accurate details, business justification, required dates, and confirmation after completion.
- Manager or approver: Confirms business need, budget authorization, and access appropriateness.
- Service desk: Receives, categorizes, tracks, and communicates request status.
- IT technician or engineer: Performs the technical work and documents results.
- Security team: Reviews requests involving sensitive access, privileged accounts, or security controls.
- Asset manager: Ensures hardware, software, and license records are updated.
- Facilities team: Coordinates physical space, power, cabling, furniture, and building access where needed.
In many cases, MAC work crosses departmental boundaries. A desk move may require IT, facilities, human resources, security, and telecom support. Clear coordination prevents last minute problems.
Documentation Requirements
Documentation is one of the most important parts of MAC management. The work is not truly complete until records are updated. Poor documentation creates future support problems and can undermine security audits.
Important documentation may include:
- Service desk ticket history and approval records
- Asset tags and device ownership records
- Software license assignments
- Network port and switch documentation
- IP address management records
- User account and group membership records
- Configuration management database entries
- Floor plans, rack diagrams, and cabling maps
For larger organizations, a configuration management database, or CMDB, can be especially valuable. It provides a central view of infrastructure components and their relationships. When MAC activity is reflected accurately in the CMDB, IT teams can troubleshoot faster and assess the impact of future changes more effectively.
Security Considerations for MAC
Every MAC process should include security controls. Routine operational changes are a common source of risk, particularly when approvals are informal or documentation is weak.
Access-related changes should be reviewed carefully. If an employee changes roles, old permissions should be removed before or at the same time new permissions are granted. This prevents privilege accumulation, where users gradually collect access rights they no longer need. Privileged access should require stronger approval and additional monitoring.
Device moves and adds also require attention. New equipment should be encrypted, patched, inventoried, and enrolled in endpoint protection before use. Retired or reassigned devices should be wiped properly. Network changes should be validated to ensure they do not bypass segmentation, expose systems to unnecessary traffic, or violate firewall policy.
Organizations should also maintain audit trails. A trustworthy MAC process records who requested the change, who approved it, who completed it, when it occurred, and what was modified.
Best Practices for Effective MAC Management
MAC management is most effective when it is standardized but flexible enough to support business needs. The following practices help create a reliable operating model:
- Use a central request system: Avoid email-only or verbal requests. A ticketing system provides tracking, reporting, and accountability.
- Create standard service catalog items: Common requests such as new user setup, desk moves, and access changes should have predefined forms.
- Require appropriate approvals: Approval workflows should reflect risk, cost, and data sensitivity.
- Define service level targets: Establish realistic completion timelines for different request types.
- Maintain checklists: Repeatable tasks should follow documented steps to reduce missed actions.
- Coordinate with stakeholders: Notify affected users, managers, facilities, and support teams before work begins.
- Verify after implementation: Confirm that the requested service works and no unintended issues were introduced.
- Review metrics regularly: Track request volume, completion time, rework, delays, and customer satisfaction.
Common MAC Challenges
Even mature IT departments face MAC challenges. One common issue is incomplete request information. If users submit vague requests such as “set up computer” or “change access,” technicians must spend time gathering details. Well designed request forms reduce this problem.
Another challenge is last minute urgency. Business teams may notify IT of office moves, new hires, or role changes too late. This can force rushed implementation and increase the risk of mistakes. Organizations should define lead times for common MAC activities and communicate them clearly.
Shadow IT can also complicate MAC management. If departments purchase software, devices, or cloud services outside official processes, IT may not have accurate visibility. This creates security, licensing, and support risks. A practical approval process and responsive service delivery can reduce the incentive for unofficial workarounds.
Measuring MAC Performance
To improve MAC operations, IT leaders should measure performance. Useful metrics include request volume by category, average completion time, first time completion rate, number of overdue tickets, approval delays, incident rates after changes, and user satisfaction scores.
These metrics help identify bottlenecks. For example, if access changes are frequently delayed by approval waits, the approval workflow may need adjustment. If desk moves often create follow up incidents, checklists or coordination with facilities may require improvement.
Conclusion
Moves, Adds, and Changes are a constant part of IT infrastructure management. Although many MAC tasks are routine, they directly affect productivity, security, cost control, and operational resilience. Treating them casually can lead to downtime, inaccurate records, excessive access rights, and avoidable support issues.
A complete MAC program relies on structured intake, proper approvals, clear responsibilities, accurate documentation, and post implementation verification. When these elements are in place, IT teams can respond quickly to business needs while maintaining control over the infrastructure. In a serious and well governed technology environment, MAC management is not merely administrative work; it is a core discipline for keeping the organization secure, efficient, and ready for change.
