Skip to main content
GullySystem

Task and Activity Lists for Each Team Member

Calls, tours, tickets and renewals are gathered into one list per person. Whatever has slipped past its date sits at the top of that list.

Why separate lists fall short

A community manager may keep a notebook, the front desk may keep notes on a monitor, and the owner may send jobs through a group chat. An email thread covers the fit-out. No single list shows what the centre owes people by Friday. Work that lives in six places gets done in the order of who shouted last. A single list lets the quiet jobs, such as a renewal call due next fortnight, stand beside the loud ones. It also makes cover during leave a short handover and not a hunt through pockets and chats.

One list, four sources

Follow-ups on enquiries

The call promised to a prospect arrives on the day it was promised for, in front of the person who made the promise.

Tickets to close

The complaints assigned to this person, oldest first.

Renewals to raise

Terms that are ending soon appear early enough for a proper conversation with the member. Notice is not the first sign.

Tasks somebody assigned

A one-off job from the owner, with a due date.

Activity logged against the record

Calls made, tours run and notes written, so the next person handling the member sees what happened.

What it changes

A short Monday review

Overdue first, then today. The team reads one list together and does not go round the room asking who is doing what.

Cover during leave

When somebody is away, their list stays visible and can be handed over to whoever is in that day.

Nothing writes itself

A call that nobody logs did not happen, as far as the list is concerned. Teams that skip logging end up with a list that is incomplete.

A typical day for a community manager

Think of the hours, not the features. A list helps most when it matches the day, because a manager who must open three screens to find a callback will go back to a notebook. Keep every task one click from the record it belongs to.

Morning

Tickets due today, tours booked, and any member who gave notice this week.

Midday

Calls to prospects who toured yesterday, while the visit is fresh.

Afternoon

Renewal conversations, vendor follow-ups and notes to log.

Before leaving

Anything promised to a member that is still open moves to tomorrow with a reason. Handover notes for the evening shift sit on the same list. Nobody phones the previous person at home.

Agreeing what is worth logging

  • Calls that change a rate, a date or a promise
  • Every tour, even a short one
  • Fixes that needed a vendor
  • Skip routine greetings and small talk
  • Leave out anything the invoice or ticket already shows

Where the tasks originate

Enquiries

Follow-up dates on prospects.

Tickets

Member complaints and who holds them.

Internal jobs

Fit-outs, servicing and vendor work.

Make an informed decision

Agree the evidence before signing off this part.

Use a representative scenario to decide what this part of the system must show and where review is still needed.

Renewals to raise

What happens to existing dues when the next renewal is stopped?

For “Renewals to raise”, test a cancellation near the renewal date. Agree the last service period and how any existing balance is handled before recurring work starts.

Background reading: ERPNext: recurring billing

FAQ

Frequently asked questions

Does every task have to be typed in?

No. Promised calls, open complaints and approaching renewal dates surface from the records behind them. Only a one-off job needs to be typed in by hand.

Can the owner see everyone’s list?

Yes, across centres. A manager sees their own team, which keeps the screen usable.

Is this measuring staff?

Not by design. The list holds what is pending and what has slipped. Read as a scorecard, it can lead people to stop logging things.

What about a task for two people?

Give it one owner and record the second person’s involvement on the task. A task with shared ownership is easily missed.

How do recurring jobs fit in?

Servicing and renewals of annual contracts can be set as repeating tasks. Agree the list of recurring jobs during scoping, so they appear on the right person’s list.

What happens to a task when someone leaves?

Their open items are reassigned in one step, and the history stays on the records they touched.

Can tasks be linked to a member?

Yes. A task raised from a ticket, a renewal or an enquiry stays tied to that record, so the context is a click away.

Talk to us

Tell us what you need.

Share your requirements and one of our engineers will come back to you within one business day.

What happens after you share your requirements

  1. A senior engineer reads your answers. Nobody phones first.
  2. Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
  3. If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
  4. No call is booked and nothing is paid until you have read the note. Your details stay with us.

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.

Share your requirements