Mandatory Office Days: A Contractor’s Productivity Nightmare

by Eric Hanson, Backend Developer at Clean Systems Consulting

“We just need you in the office a few days a week.”
Sounds harmless—until those days quietly become the least productive ones.

It Sounds Reasonable at First

No one introduces it as a problem.

  • “Better collaboration”
  • “Easier communication”
  • “Stronger team alignment”

For full-time employees, that might work.

But for contractors?

It changes how the entire engagement operates.

The Cost of Just Showing Up

Office days aren’t neutral—they come with hidden costs.

  • Time lost commuting
  • Energy drained before real work even begins
  • Context switching between environments

Instead of starting focused, the day begins with friction.

And for contractors, time is the product.

Every hour matters.

The Environment Mismatch

Contractors usually work best in setups they control.

  • Proper tools and configurations
  • Quiet, focused environments
  • Flexible schedules that match their workflow

Office environments often disrupt that.

  • Shared spaces and interruptions
  • Limited or restricted machines
  • Policies that slow things down

You’re taking a high-performance setup and replacing it with constraints.

Presence Over Performance

Mandatory office days shift the focus.

  • Being physically present becomes the expectation
  • Visibility starts to matter more than output
  • Work gets shaped around schedules, not results

That’s the opposite of how contractors deliver value.

They’re not there to “be seen”—they’re there to get things done.

The Control Trap

Why do companies push for this?

  • It feels easier to manage people in person
  • There’s a sense of control and oversight
  • It mirrors how employees are managed

But contractors aren’t employees.

Applying employee rules to contractors creates friction without adding value.

A Better Way to Work Together

If productivity is the goal, the approach needs to shift.

  • Focus on deliverables, not location
  • Keep meetings intentional and minimal
  • Let contractors work where they perform best

Trust doesn’t mean losing control—it means setting clear expectations.

And then letting people meet them in the most effective way.


Mandatory office days might look like structure,
but for contractors, they’re often just productivity in disguise—quietly slipping away.

Scale Your Backend - Need an Experienced Backend Developer?

We provide backend engineers who join your team as contractors to help build, improve, and scale your backend systems.

We focus on clean backend design, clear documentation, and systems that remain reliable as products grow. Our goal is to strengthen your team and deliver backend systems that are easy to operate and maintain.

We work from our own development environments and support teams across US, EU, and APAC timezones. Our workflow emphasizes documentation and asynchronous collaboration to keep development efficient and focused.

  • Production Backend Experience. Experience building and maintaining backend systems, APIs, and databases used in production.
  • Scalable Architecture. Design backend systems that stay reliable as your product and traffic grow.
  • Contractor Friendly. Flexible engagement for short projects, long-term support, or extra help during releases.
  • Focus on Backend Reliability. Improve API performance, database stability, and overall backend reliability.
  • Documentation-Driven Development. Development guided by clear documentation so teams stay aligned and work efficiently.
  • Domain-Driven Design. Design backend systems around real business processes and product needs.

Tell us about your project

Our offices

  • Copenhagen
    1 Carlsberg Gate
    1260, København, Denmark
  • Magelang
    12 Jalan Bligo
    56485, Magelang, Indonesia

More articles

When Laptops Are Domain-Locked and Developers Can’t Install Tools

Nothing kills momentum faster than a laptop you can’t fully control. As contractors, working on a domain-locked machine is often a recipe for frustration.

Read more

How San Francisco Founders Cut Backend Burn Rate by 60% Without Sacrificing Code Quality

Your backend team costs $80K a month fully loaded. The output is good. The question is whether you need $80K a month of permanent cost to get it.

Read more

N+1 Queries in Rails — How I Find and Fix Them for Good

N+1 queries are the most common Rails performance problem and the most consistently underestimated. Here is a systematic approach to finding them, fixing them correctly, and preventing them from coming back.

Read more

The Strategy Pattern in Java — Replacing Conditional Dispatch With Polymorphism

Conditional dispatch — switching on a type or status to select behavior — is the most common source of rigid code in Java applications. The strategy pattern replaces the switch with polymorphism, but the right implementation depends on what varies and how often it changes.

Read more