Structuring departments and designations as you scale

Published 12 July 2026 · Merik team · 5 min read

At 5 people, everyone just knows who does what. At 25, that informal knowledge breaks down — and the fix is simpler than it sounds: departments and designations, defined once.

Department vs designation

• Department — the function someone belongs to (Sales, Operations, Engineering, Finance).
• Designation — their title or level within it (Executive, Senior Executive, Manager, Lead).

Together, they answer "who does this person report through, and at what level" — the question that gets harder to answer informally as headcount grows.

Keep it simple at first

You don't need five levels per department on day one. Start with broad departments and two or three designation levels, and add structure only when a real need appears — not in anticipation of one.

The goal isn't a perfect org chart — it's that anyone can look up who's in which department and at what level, without asking around.

Why this matters beyond org charts

Payroll and CTC bands

Clear designations make it easier to compare pay fairly within a level and plan hikes consistently — see how CTC translates to pay.

Reporting and headcount

Department structure lets you see cost and headcount by function at a glance, instead of reconstructing it from memory every time someone asks.

Onboarding new hires

A new employee's department and designation should be set the moment they're added — see the onboarding checklist.

How Merik handles it

Merik stores department and designation as core fields on every employee record, so reporting, CTC comparisons and org visibility stay accurate as you scale — no separate spreadsheet to maintain. Explore features.

Create your workspace →

Or talk to us about your team →