What site maintenance includes, and what is already a new task

Everyone reads the word "maintenance" differently. The client sees every marketing request in it. The contractor sees updates and an hour a month. The argument starts on the third task, when "fix the text" has become a new calculator. The boundary is dull and useful.

Usually inside the pack

• Platform and module updates in an agreed order, with a copy taken before the work.
• Small fixes to text, contacts, a banner, inside a block that already exists.
• A watch on the form: a test lead if something goes silent.
• A watch on copies, and on the certificate and domain not expiring quietly.
• A reply on business hours within the named time.

Usually already a separate task

• A new section, an account area, an integration, a platform change.
• A night incident, if a night channel was not bought separately.
• Texts and photos that do not exist yet. Support does not write the proposal for you.

Hours in the pack make sense only if there is a queue and one person who files tasks. A chat with no owner eats the hours on clarifications. Lexora writes this boundary into maintenance for our own sites and for others', after a short look at what the project is built on.