Skip to content
DAContactGet a quote

Write to me.

A question, an idea, or something you just want to think out loud about. If something else would serve you better, I'll tell you.

You can also mail me directly at rasmus@tek-aerobic.dk.

The details are used to answer your request. Read about privacy.

All projects

Website Approval

A simpler way to review and approve changes to the website.

No edit goes live until it has been read and approved.

Every edit to the website's pages starts as a proposal in the CMS, the system the pages are edited in. An approver reads the proposal and approves it, or sends it back to be corrected and sent again. Once it is approved, the website updates itself.

Shown with example data from an invented plant nursery.

In and out
In: a proposed edit in the CMS, the system behind the website's pages. Out: the approved edit, online.
People
Propose the edit. An approver reads the proposal and approves it or sends it back.
AI
This workflow does not use AI. Every proposal is read by a person.
Systems
The website and its CMS. The page updates itself once a proposal is approved, and the proposal stays on record, so what changed can be seen later.

Either edits wait in a queue, or mistakes go online.

  • When only a few people have access to edit a website, small fixes wait in a queue.
  • If direct editing is open to everyone, typos and wrong details go online before they have been read through.

Who does what, from proposal to website.

People and systems each have their own lane. The drawing follows an edit from proposal to website. The dashed line is a proposal that is sent back, corrected and sent again.

  1. StartAn edit is proposedThe page online still shows the old text.
  2. 1 · PeopleAn approver reads the proposalThe proposal is approved or sent back.Sent back: corrected and sent again
  3. 2 · SystemsThe page updates itselfOnly once the proposal is approved.
  4. ResultThe edit is onlineThe proposal stays on record and can be seen later.
A drawing of the workflow in two lanes: people and systems. An edit starts as a proposal, and the page online still shows the old text. An approver reads the proposal and approves it or sends it back. A proposal that is sent back does not appear online, and the person who proposed it corrects it and sends it again. Once the proposal is approved, the page updates itself and the edit is online. The proposal stays on record, so what changed can be seen later. A pencil shows where a person writes or corrects a proposal, and a check mark at the dot where a person approves. A dashed line shows the way back. A dot without a mark shows where a system does the step. Dot without a mark: a system does the step.Check mark: a person approves here.Pencil: a person writes or corrects a proposal here.Dashed line: sent back.

What each step looks like.

  1. StartPeople

    An edit is proposed

    The CMS is the system where the website's pages are edited. Every edit there starts as a proposal, and until the proposal is approved, the page online shows the old text.

  2. 1People

    An approver reads the proposal

    An approver reads the proposal. The old text is struck through, with the new text below it. Then it is approved or sent back. A proposal that is sent back does not appear online. The person who proposed it corrects it and sends it again for approval.

  3. 2Systems

    The page updates itself

    Once the proposal is approved, the website updates itself with the new text. The proposal stays on record, so what changed can be seen later.

Only approved edits appear online.

The edit is on the page once an approver says yes. The proposal stays on record, so what changed can be seen later.

What changes in the work

Before

  • Small fixesWait in a queue when only a few people have access to edit.
  • An editGoes online before it has been read through.
  • OnlineTypos and wrong details nobody has read.

After

  • Small fixesStill wait as proposals until an approver has read them.
  • An editStarts as a proposal and is reviewed internally.
  • OnlineOnly edits an approver has approved.

Same steps, other pages.

Three invented examples of the same steps: a proposal, a person who reads and approves it, and then the page updates itself.

  • Opening hours at a swimming pool

    The proposal
    New hours for the school holidays
    Read and approved by
    A department manager
    Online
    The new hours on the page

  • Course dates at a language school

    The proposal
    A corrected start date for a course
    Read and approved by
    A course coordinator
    Online
    The corrected date on the course page

  • Prices at a dental clinic

    The proposal
    A new price for a cleaning
    Read and approved by
    A clinic manager
    Online
    The new price on the price page

A website where edits need reading first?

I'll go through your message, and if the job is not a fit, I'll tell you clearly.

Describe a similar taskAbout workflow automation

Describe your project

What kind of job is it?

Pick the closest one. It can change once things are clear.