Coordinating sign deliveries

Delivery coordinators are the regional leads who keep lawn-sign deliveries moving. The coordinator page shows every delivery request in Alberta at once — who is holding each one, how long they have had it, and which ones have gone quiet — and lets you act without waiting for the volunteer.

You reach it from the sidebar: Lawn signs → Delivery coordinator. If you do not see that entry, you do not hold the coordinator role yet; an administrator grants it.

What the page shows

The page has three tabs: Requests, Applications and Volunteers. The number beside Applications is how many people are waiting to be approved, and it stays visible on every tab so you do not have to go looking.

Requests

Every delivery request in the province, whatever state it is in. Each row shows the area code and city, when it was requested, who is holding it, and how far through their week they are — Day 4 of 7, and so on.

Claimed requests with a problem reported come first, so you can get to them without pressing Load more. That includes a problem an earlier volunteer reported on the same request. Everything else follows, and each group runs oldest request first. A problem note stays on the request after the problem is dealt with, so the request stays at the top for as long as somebody holds it.

Use the buttons above the list to narrow it down:

• All — everything.
• Open — nobody has claimed it.
• Claimed — somebody is holding it right now.
• Nudged — somebody is holding it and has already had the day-five reminder. These are the ones worth a phone call.

Type an area code such as T2K in the Area code box to see only that area. It stays applied when you switch tabs.

Switch between List and Map with the toggle on the right. The map plots every request that matches your filters, not just the first page. To zoom in on it from a computer, roll the mouse wheel or pinch the trackpad with the pointer over the map — the same as pinching it on a phone.

Each request is one pin, where the public site places it: the pin the supporter dropped on their home, or, if they did not drop one, the spot the site found for their address. The pin's colour is its state — Open, Claimed, Delivered or Closed, the same four words the rows in the list use — and the colour key is under the map. The label on a pin is the last three characters of the request's postal code, so 0L7 on a request in T2R is T2R 0L7. A finished request has no postal code on its pin, so its label is the area code alone. Choose a pin to see the request's state and who is holding it (and, for a claim, when it is due), and choose Open in that box to open the request's panel.

A pin with a dashed edge has no map location: the public site never had a position for that request, could not find its address, or has erased it, or Team could not reach the site just now. The map draws it somewhere inside its postal area. Do not read its position; open the request for the address. Where two requests are at the same address, or next door, their pins are moved a few tens of metres apart, so that when you zoom in close you can choose each one; a pin can sit a little to one side of its house.

If the map says the pin positions could not load, it is drawing every request inside its postal area for now. It does the same without saying so when Team cannot reach the public site, and then every pin has a dashed edge. The list is not affected. Reload the page to try again.

Rows that came back on their own say Returned automatically; rows a volunteer handed back say Handed back. That difference is worth knowing, because one means somebody made a decision and the other means a week ran out.

Applications

People who have asked to join the delivery pool, with the town each one lives in. Approve puts them in the pool; Decline asks for an optional reason and tells them.

You cannot decide your own application. If you have applied, the buttons on your own row are switched off and somebody else has to approve you.

Volunteers

Everyone in the pool, the town each lives in, the areas each has chosen, and how many deliveries they are holding and have finished. The card at the top says how many active volunteers there are and which areas nobody covers.

The town is the answer to "is anybody near this request?" — an area code such as T0J can cover a dozen towns, so the areas alone cannot tell you. People you have invited show their town too. If someone's profile has no home town, the card says so rather than leaving it blank.

The areas shown here are read-only. Volunteers choose their own delivery areas, and there is no way for a coordinator to set them on someone's behalf.

Acting on a delivery somebody else is holding

Choose any row to open it. The panel shows the supporter's address, the claim, its history, and three things you can do:

• Hand back to the pool — returns the request so other volunteers are offered it again. Use this when somebody has gone quiet.
• Mark delivered — records the delivery when the volunteer has done it but not said so. The delivery stays credited to them, not to you.
• Note a problem — attaches a note to the request and moves it to the top of the list. It does not hand the claim back.

Each asks you to confirm first, and the confirmation names the volunteer, so you can see whose delivery you are about to change.

If somebody else changed the same delivery while you had the panel open, we tell you what is true now instead of quietly doing it twice.

To go back to the list, choose the X in the panel's top corner. On a phone the panel fills the screen, so the X is the way out.

Messaging a supporter

You can write to the supporter of any request that is still in play — including one nobody has claimed, which is often exactly the one that needs a question answered ("would you collect it from Brooks?"). Open the request and choose Message the supporter in the panel. Write your message, up to 2,000 characters, and choose Send.

The supporter gets it by email, from your first name followed by "Forever Canadian sign coordinator", and answers by replying. Their reply comes to you by email and appears in the panel. Once you have written, the panel uses their first name. Neither of you ever sees the other's email address.

A request with a reply you have not read yet shows as new in the list until you open it or answer it.

Everyone else who has a conversation with this supporter about this request is listed under Other conversations with this supporter — including the volunteer holding it, who has one from the moment they claim, because the supporter can answer the email that tells them a volunteer is coming. You see who (and their role, once they have written), how many messages, when the last one was, and whose turn it is — but never what was said.

A conversation is read by the people in it. An administrator can open any conversation in full, and close it for good. Closing ends that one person's conversation; it does not stop another coordinator, or a later volunteer, from writing to the same supporter.

You can send 10 messages a day to one supporter, and 30 a day across all your conversations. A conversation closes a week after the sign is delivered, and when the request is closed on the public site. Messages are deleted 30 days after the request closes; a reply that arrives later is deleted 30 days after it arrives.

If a request has no messages section at all, supporter messaging has not been switched on yet. On a request that was closed on the public site, or delivered more than a week ago, the section says you can no longer write to the supporter.

Sharing what you are looking at

Everything on the page — the tab, the list-or-map choice, the filter, the area code, and any request you have open — is in the address bar. Copy the address and send it to the other coordinator, and they will open exactly what you were looking at.

The supporter's address

Open a request and the panel shows the supporter's full address under the area and town at the top: the street, then the unit on a line of its own in bold, then the city and postal code. You see it for every request, whatever state it is in, so you can help when a delivery runs into trouble.

A unit made up of numbers and single letters, such as 103, 12B or B, is labelled — Unit 103, Unit 12B, Unit B — so it cannot be mistaken for part of the street. A unit with a word or an abbreviation in it, such as Apt 12, Main Floor or PH2, is shown exactly as the supporter wrote it. If there is no unit, the address stays on one line.

Team reads the address from the public site each time you open the panel and does not keep a copy. When the panel shows you the address, that is recorded on the request: the History says Address opened, with your name and when, the next time the panel loads. Reopening the same request within the hour does not normally add another entry.

Sometimes there is no address to show, and the panel says so in a line, not an error:

• Address no longer available — the public site no longer has it. It erases addresses 30 days after a request closes.
• Address unavailable right now — the public site could not be reached. Close the panel and open it again in a moment.

What the page will not show you

The street address appears in that panel and nowhere else on this page. The rows in the list place a request by area code and city only. The map draws each pin where the public site places the request, so it shows you where requests are, but it never writes an address: a pin is labelled with a postal code and not a street number, and choosing one gives you the request's state and holder, not its address. To read the address you open the request. There is no list or download of addresses, and that is deliberate — the address is here so you can help with the delivery in front of you, and a province-wide list of every address is a different thing entirely.

You never see a supporter's email address or phone number, or what their delivery notes say. The list shows only that a request has notes, with delivery notes ✓. Volunteers' email addresses are not here either, and a volunteer's home is shown as a town only — never a street or postal code. Messaging a supporter does not change any of this: you never see their email address, which Team reads from the public site only to send each message, and your messages reach them through Team.

Getting the daily email back

You will not. The daily delivery summary that used to arrive by email has been retired — this page replaced it, and it is always current, which an overnight email never was.