Skip to content
Kaarne Superstore⌕
Small Business Life

Give the Next Web Coordinator a Map of Open Decisions

A folder of feedback does not explain what is still undecided. Make the page, question, authority and next action visible in one handover row.

Coordinator follows a map from unresolved page questions to separate decision routes.

The outgoing web coordinator leaves a folder of screenshots and a long feedback thread. The replacement can find the page. What they cannot find is whether “remove this section” was a decision, a suggestion or a question still waiting for the offer owner.

Hand over the present decision state

Imagine a fictional membership organisation replacing its web coordinator halfway through an enrolment-page revision. There are three unresolved issues: which eligibility statement is correct, whether a quotation may be published and when the old form should be retired. These are different decisions with different authorities.

A general list of tasks would flatten those differences. Instead, make a map of open decisions attached to the exact pages or sections they concern. The map should tell the next coordinator how to continue the work without reconstructing the entire project history.

Use one row per unresolved question

A practical row contains the page, current version, question, known evidence, decision authority and next agreed action. Add the consequence of waiting when it changes what can safely proceed. Avoid turning the map into a copy of every comment.

  • Page and location: enrolment page, eligibility section, review version dated 18 November.
  • Question: does the new intake include part-time members?
  • Current state: two drafts disagree; neither is treated as approved.
  • Evidence: link to the current programme policy and the relevant discussion.
  • Decision authority: programme owner, with a named cover contact.
  • Next action: coordinator requests a confirmed sentence before the page release decision.

This example does not answer the eligibility question. It preserves its uncertainty and gives that uncertainty a route. The replacement should not have to choose the most polished draft as a substitute for an authorised answer.

Distinguish discussion from a settled instruction

Read the last useful exchange for each row. “Could we say this?” is a proposal. “Use this approved wording” is a different statement. Record the status you can establish and identify what still needs confirmation. Do not upgrade an old suggestion merely because it is the only comment with a date.

Where a decision has been made, retain a concise reason and the relevant evidence rather than relisting it as open work. Where a changed brief may have invalidated an earlier decision, say so explicitly. The map should reflect the page being handed over, not a tidier version of its history.

Show what can proceed while an answer waits

An unanswered eligibility question need not stop every activity. The coordinator might continue checking image descriptions or a layout issue while leaving the disputed statement out of the release decision. State the actual dependency instead of marking the whole project “blocked.”

For the quotation, the next action may be confirming publication permission with the responsible person. For the old form, it may be agreeing the cutover with the team receiving submissions. Different questions should not share a vague next step such as “follow up with stakeholders.”

Test the map with the person taking over

Ask the replacement to choose one row and explain what they would do next, whom they would ask and which version they would avoid publishing. Let them follow the evidence links through their own authorised account. If access fails, record that as a separate handover issue; do not copy private material into a broader folder merely to remove the obstacle.

Revise the row where they need your memory to continue. Finish by identifying who maintains the map after the handover and where newly settled decisions will be recorded. The outgoing coordinator’s availability should be helpful background, not the system’s only navigation method.

Hand over the unresolved decisions together with the page and discussion they concern. A review history is useful when a new coordinator can understand it without the previous owner explaining every item.

The next coordinator may also benefit from giving reviewers specific questions and mapping the access each review participant needs.

0

Discussion 0

What did this article make you think about?

Join the conversation

Your email address will not be published. Required fields are marked *

Saved articles

Saved in this browser.