Facilities Manager in 60 Days: what to do in the first two months

A facilities manager inherits more than a building. They inherit access routes, temporary fixes, contractor activity, maintenance history, emergency readiness, and the small compromises that people stop seeing because they happen every day. The first 60 days matter because a site can look orderly while still depending on shortcuts that only stay harmless when nothing changes.

The practical thesis is simple. Facilities management protects people when the manager owns access, condition, and work priority together, not when they become the person who only closes tickets. Across 25+ years leading EHS in multinational operations, Andreza Araujo has seen that the weak point is rarely the complaint itself. The weak point is the decision that allowed the complaint to repeat without changing the site.

As Andreza Araujo argues in A Ilusão da Conformidade, a place can look compliant and still be unsafe where it matters. That is exactly why the first two months should be spent mapping how people move, where temporary changes live, and which maintenance decisions are hiding behind a clean corridor or a finished work order.

Key Takeaways

• A facilities manager should treat the site as a control system, because access, maintenance, and emergency readiness are linked.
• The first week should expose how workers, contractors, visitors, and emergency teams actually move through the site.
• Temporary lighting, exit routes, first aid access, and maintenance backlogs should be verified in the field, not only in a ticket queue.
• The first 60 days should end with a weekly risk review that forces decisions on open life safety items, temporary changes, and overdue fixes.
• A tidy site is not proof of control if people still depend on memory, detours, or unofficial fixes to do the work.

What should a facilities manager understand before starting?

A facilities manager should understand that the job is not only about service response. The role shapes how a building behaves under pressure, which means access routes, utility rooms, roofs, loading docks, plant rooms, storage areas, and contractor interfaces all belong to the same operating picture. If those pieces are managed separately, the site starts to solve one problem by creating another.

The market often treats facilities work as a queue of requests. A leak is fixed, a light is replaced, a door is adjusted, and the next ticket arrives. That approach can keep the site moving, although it hides the deeper question: which conditions keep forcing the same request to appear? That question matters because repeated requests usually point to a design flaw, a weak owner, or a temporary fix that has quietly become normal.

For a newly appointed facilities manager, the first discipline is to watch the site under real use. Offices, warehouses, contractor corridors, utility spaces, and night shifts behave differently. A corridor that looks fine at 10 a.m. may become a blind route after dark, during deliveries, or when temporary work narrows the path. The manager who sees only the daylight version of the building will miss the way risk actually enters.

This is why control-of-work auditing belongs in facilities thinking. The manager does not need to own every trade, although they do need to know which controls disappear when the work starts moving faster than the plan.

Days 1 to 7: map the site the way workers move through it

The first week should produce a movement map. Walk the paths people actually use, not the paths drawn in a property brochure. Start at the entrance, then go to loading areas, stairs, lifts, plant rooms, roof access, toilets, first aid points, waste areas, contractor gates, and muster points. If a person must detour around a pallet, a parked cart, a locked door, or a dark corridor, the map is not finished.

The map should name the work that happens in each place, the shift that uses it, the person who owns the area, and the change condition that could alter the risk. A route that serves office workers in the morning may carry forklifts, cleaning crews, or maintenance technicians later in the day. That is not a minor detail. It is the difference between a static drawing and a live control map.

Andreza Araujo's work on safety culture keeps returning to the same point. Culture becomes visible in repeated decisions, and repeated decisions usually begin with movement, not with slogans. A facilities manager who learns where people cut through, where they hesitate, and where they cannot see the next step is already learning more than a dashboard would show.

Use temporary lighting inspection logic early if any route depends on lamps, portable fixtures, or work lights. The route is only as safe as the visibility that holds when the building changes shape.

Days 8 to 15: verify exits, egress, lighting, and access routes

By the second week, the manager should verify the routes people would use if the normal plan breaks. That means exits, emergency egress, external assembly areas, door hardware, stair rails, floor level changes, security gates, temporary barriers, access control readers, and any route that becomes narrower after hours or during maintenance.

The question is not whether the route exists. The question is whether a tired person, a contractor with tools, or a visitor who does not know the site can use it without guessing. If the route depends on local knowledge, the site has a hidden failure mode. If the route is blocked by storage or temporary work, the site has already taught people that convenience can outrank escape.

Lighting belongs in the same review because good egress is not only about distance. It is about visibility at the exact point where the person needs to choose direction, open a door, step down, or cross a threshold. A route can be well signed and still fail when shadows hide a change in level or when a lamp turns a safe exit into a glare problem.

That is why the article on temporary lighting safety inspection is a useful companion. A route that only works in daylight is not a route the building can rely on.

Days 16 to 30: clear maintenance drift before it becomes normal

Maintenance drift is what happens when temporary repairs, repeated work orders, patched labels, and blocked access points stay in place long enough to feel harmless. The building still functions, so people stop noticing the compromise. A loose closer, a failing alarm, a leaking valve, or a broken latch starts to look like a local habit instead of a control problem.

The first month should therefore rank the backlog by risk, not by age alone. Items that affect life safety, emergency access, restricted zones, visibility, or the condition of a critical control belong at the front of the queue. Cosmetic work can wait. A broken exit sign cannot. A door that does not latch cannot. A leak that forces people to skirt a route cannot be treated as routine housekeeping.

Across more than 250 cultural transformation projects, Andreza Araujo has observed that leaders often confuse completion with control. During the PepsiCo South America tenure, where the accident ratio fell 50 percent in six months, the point was not to create more paperwork. It was to make the decision line visible enough that weak conditions could not keep repeating under a clean report.

The facilities manager should review recurring work orders with operations and maintenance together, then ask which item keeps returning because the site is working around a design flaw. If a pallet blocks the same panel every week, or a cable runs through the same path every night, the building is not asking for another reminder. It is asking for a decision.

Days 31 to 45: test emergency readiness with real walkthroughs

The third block should move from mapping to proof. Walk the emergency response routes as they really appear after hours, during contractor activity, and when part of the site is being reconfigured. Check first aid access, extinguisher access, spill response access, alarm audibility, muster instructions, room keys, access cards, and the places where people would naturally search for help when something goes wrong.

A good walkthrough is not a presentation. It is a field test. If a responder cannot reach the kit without crossing a hazard, if the alarm is not audible in the far corner, or if a locked gate forces the route to bend, the emergency design needs correction. The issue is not whether the site has a response plan. The issue is whether the plan survives the way the site is actually used.

Use first-aid kit readiness as a simple anchor. If the kit is not reachable in less time than the incident can grow, it is not ready.

Hot work, roof work, and temporary access also belong in this check. The article on hot work fire watch handover is relevant because a building that hosts hot work must know where fire protection, escape, and watch responsibilities actually sit when the task starts.

Days 46 to 60: build a weekly facilities risk review

By day 46, the manager should stop collecting isolated observations and start running a short weekly risk review. The meeting should be small enough to survive pressure and sharp enough to force a decision. Track open life safety items, temporary changes, blocked routes, recurring maintenance failures, contractor exceptions, and any control that depends on memory instead of design.

The review should not become a tour of tickets. It should answer a harder question: which issue can still hurt someone next week if nothing changes? If the answer is unclear, the manager is looking at reporting noise rather than risk. A queue can be long and still miss the few items that matter most.

As described in Safety Culture: From Theory to Practice, safety becomes real when leaders keep making the same kind of correct decision under pressure. The facilities manager needs that rhythm too. If the weekly review only celebrates close rates, the site will learn to finish tasks while leaving exposure behind.

This is also where the article on critical control verification becomes useful. If a control is important, it should be checked often enough that it cannot age quietly between meetings.

Comparison: reactive support vs risk-owning management

The table below shows the difference between a site that reacts to problems and a site that owns the risk behind them. Both can look busy. Only one changes the conditions that keep creating the same trouble.

The point of the comparison is not style. It is control. A reactive site can feel efficient because people solve small problems quickly, but that speed often hides the fact that the same small problem keeps returning. A risk-owning site does the slower work of removing the cause.

Resources to deepen

For a facilities manager, the cleanest grounding comes from Andreza Araujo's books Safety Culture: From Theory to Practice and A Ilusão da Conformidade. The first helps leaders see how repeated decisions shape the site. The second helps them detect when compliance language has become a substitute for field control.

Pair that with the internal guides on control-of-work auditing, temporary lighting inspection, and first-aid kit readiness. Those articles turn the abstract role into practical checks a manager can run in a live facility.

FAQ

What is the first thing a facilities manager should do?

Walk the site as people actually use it. The first week should show where workers move, where they hesitate, where contractors enter, and which routes only work because everyone knows the local workaround.

How does a facilities manager reduce safety risk quickly?

Focus on access routes, emergency exits, temporary lighting, maintenance drift, and the few recurring issues that keep forcing people to improvise. Quick wins matter less than removing the condition that keeps creating the same exposure.

Should maintenance backlog be handled by age or risk?

By risk. An old ticket that affects a cosmetic issue is not the same as a newer ticket that blocks an exit, weakens a control, or creates a detour through traffic or darkness.

Why are temporary changes such a problem?

Because temporary changes often outlast the reason they were approved. If nobody owns the expiry date, the site starts treating the exception as the normal way of working.

What should the weekly facilities review decide?

It should decide what gets removed, repaired, escalated, accepted with a deadline, or redesigned. If the meeting only records status, it has missed the point of the role.

Each week a facilities team treats access, lighting, maintenance drift, or emergency readiness as background noise, the building teaches people to work around the gap instead of removing it.

A strong facilities manager does not wait for a broken route or a failed alarm to define the role. The first 60 days should make the site easier to read, easier to use, and harder to fool.

For more practical safety conversations that connect leadership with field control, follow Headline Podcast.