The control panel is part of the design work
Your client judges the site every day through an interface most studios never look at.
A studio presents the site. The client approves it. Everyone moves on.
Then the client spends the next four years not really looking at the site at all. They look at the admin. That's where they experience the thing you made — several times a week, for as long as it lives, usually while trying to get something done before a meeting.
Almost nobody designs it. It gets treated as plumbing, assembled in whatever order the fields happened to be created in, and handed over with a twenty-minute screen recording that gets watched once.
Field labels are copy, and they're read more often than the website
Hero Image (1440x600) is a note a developer left for themselves. Banner image — sits behind the page title is written for the person who has to use it. Same field, entirely different experience, about eleven seconds of difference to produce.
The test is whether someone who wasn't in any of the meetings could fill the field in correctly on their first attempt. Dimensions in a label are a symptom: if the crop matters that much, the field should enforce it rather than describe it and hope.
Field order is hierarchy
Fields should appear in the order the person thinks about them, which for most page types is roughly the order things appear on the page. Instead they frequently appear in creation order, which is why the SEO description so often sits between the headline and the body — that's simply when somebody remembered to add it.
Grouping matters as much as order. The three fields that make up the hero belong together and visibly apart from the four that control the footer CTA. Craft gives you tabs and field layouts to do this. Using them costs a few minutes at build time.
Delete the fields nobody uses
Every build accumulates at least one field that made sense in week two and has been permanently blank ever since. Leaving it costs nothing technically. It costs something every single time a new person joins the client's team, sees it, wonders whether they're supposed to fill it in, and asks a colleague who doesn't know either.
An empty field is a question with no answer, sitting in the interface indefinitely. Remove them before handover, and remove them again a year later when you've seen what actually gets used.
An orphan field is a question your client will ask a colleague, who won't know either.
Entry titles should be findable
A section listing forty entries all called Untitled, or all beginning with the same six words, is unusable. Titles want to be distinguishable at a glance in a list, which is a different requirement from reading well on the page.
Where the on-page heading and the useful admin title genuinely differ, that's two fields, and it's worth the extra one. Nobody minds typing a short internal name. Everybody minds scrolling a list of near-identical entries trying to find the right one.
Show them what they're making
Live preview costs very little to configure and changes the entire relationship between a client and their website. Editing with preview is composing — you see the effect of a decision as you make it. Editing without it is filling in a form and hoping, then saving, then opening a new tab, then discovering the heading was too long.
One of those makes people confident enough to keep the site current. The other makes them cautious, then infrequent, then absent — and a site nobody updates is a site that looks worse every month regardless of how well it was designed.
Write instructions where they're needed, not in a document
A handover PDF is read once, by one person, who then leaves. A single line of instruction attached to the field itself is read by everyone, at the exact moment they need it, for the life of the site.
One sentence per block or field group. What it's for, where it appears, and any constraint that isn't obvious. It's the highest-return writing on the whole project and it takes about half an hour.
Why this is the studio's problem, not just ours
Because the client will not blame the developer. They'll say the website is difficult to update, and the website has your name on it. The control panel is the part of the project the studio never sees and the client sees constantly, which makes it the single largest gap between how good a project is and how good it feels.
It is also the cheapest goodwill available on any build. Nobody expects a CMS to be pleasant. The bar for exceeding expectations is unusually, almost embarrassingly low — and clearing it is most of what makes a client renew a hosting arrangement without thinking about it.