Keeping a Published Map Current

The launch meeting ends with a link and a sense of completion. The first correction arrives four days later.

A path is closed. A tenant has moved. The parking entrance is on the other street now. The map that was correct on launch day is already a little wrong, and the reader who finds the old answer does not know it is old.

A published map is a living document. The difference between a map that stays useful and one that quietly rots is rarely the drawing. It is the ownership.

Name the person who fixes it

The most useful question after launch is not "who built this" but "who changes it in April."

If the answer is nobody, the honest options are to publish a snapshot and accept that it is a snapshot, or to keep the map small enough that being wrong costs little. A trail map with a closed loop is a nuisance. A hospital map with a closed entrance is a different kind of problem.

If the answer is a name, three things follow. That person needs access to the source list that feeds the map. The list needs a review date. The map needs an address that does not change, so a correction reaches the reader who bookmarked it.

Separate the source from the drawing

The drawing is the last step. The source is the list of places, routes, areas, and notes that the map is built from.

For a business directory, the source is the membership list. For a campus, it is the building and room list. For a trail network, it is the trail inventory and the closure log. For an event, it is the programme and the site plan.

When the source and the drawing live in the same file, every correction requires someone who can edit the map. When they are separate, a staff member can fix the source and hand it to the map owner. The handoff is cheaper and the correction is faster.

Tasmap imports a spreadsheet, a CSV, a PDF, a Markdown file, or a block of pasted text and shows the parsed rows before anything reaches the map. That preview is the moment to catch a name that is spelled three ways or an address that is missing a city. Spreadsheet to interactive map covers the column layout that makes the import predictable.

Keep the link stable

A QR code on a sign is a small commitment. It is printed, laminated, and installed. If the map moves to a new address, the sign has to be replaced.

A stable public address is therefore part of the map's design. Save the map, share the same address, and let the content change. A reader who scanned the sign last month gets the current version. A reader who bookmarked the page gets the current version. A reader who saved a screenshot gets the version from the day they saved it, and there is nothing the map can do about that.

The stable link also makes the correction cheap. The owner edits the map, saves, and the next visitor sees the change. There is no export, no upload, and no new URL to distribute.

Know which version the public sees

The editor and the public map are not always looking at the same thing.

Preview uses the content that is currently being edited, including changes that have not been saved. The public link, the QR code, and the embed use the last saved version. If the team previews a correction and then shares the link before saving, the reader sees the old map.

Tasmap shows unsaved, saving, and saved states separately. The saved state is the one that matters for the public. The habit that prevents most confusion is simple: save, then open the public link, then check the change.

Autosave can help, but it does not remove the need for a final check. A map that saves every few seconds is still a map that can be saved with the wrong label.

Put review dates in the content

A map does not need a version number in the corner. It needs a date the reader can trust.

The article can carry a line such as "Reviewed 12 September 2026" and the map can carry a short note in the same article. The date tells the reader how current the answer is, and it tells the owner when the next review is due.

The review can be seasonal. A botanical garden reviews before the spring display and after the autumn clear-up. A downtown district reviews before the holiday season and after the January vacancy list. A conference center reviews before the first event of the year. A trail network reviews before the hunting season and after the first storm.

The date is also a useful alarm. A map with a review date from two years ago is a map that has lost its owner.

Event maps are copies, not edits

The year-round map should not be overwritten for a single event. The event has its own labels, its own closures, and its own date. When the event ends, the year-round map should return unchanged.

Tasmap can duplicate a map, which makes the event version a separate document. Publish the event copy at its own address, keep the year-round map at the main address, and let the event copy become a record after the event. The next event starts from the same base.

This is the cheapest form of version control for a small team. It does not require a repository or a release process. It requires the discipline to copy before editing.

The maintenance test

Open the public link on a phone. Check the three things a visitor is most likely to need this week: the entrance, the main destination, and the thing that changed most recently. If any of them is wrong, the map is not current.

A visitor who gets the current answer from a link printed two years ago has used the map correctly. Tasmap keeps the source list, the published map, and the stable link in one place, so the correction is a save, not a relaunch.