← All field notes

When a small website edit becomes a different request

“Change this heading” can grow into rewriting the whole service page. The work may be worth doing, but the original task no longer explains its scope.

  • Keep the original acceptance condition in the conversation.
  • Describe the additional work and the pages or templates it affects.
  • Separate independent follow-up work instead of quietly extending a finished task.
  • Confirm who approves the revised scope before starting a larger change.

A readable request history should explain why the work changed. It does not need a transcript of every internal thought; it needs the decisions the next operator would otherwise have to guess.

Related guide: Request history.


Have a correction or a workflow we should cover? Tell the IrmaWP team.