The Time Bank Ledger That Shows Who Gives Hours and Who Only Spends Them

On a coordinator’s desk in a shared office, a laptop is open to a member’s account. The balance reads minus forty-two. The member has received forty-two hours of rides, meals, and help with paperwork, and has logged two hours of giving back. The coordinator is not looking at the number to decide whether the member is good or bad. She is looking at it to decide whether to pick up the phone.

That distinction is the whole argument of this piece. A time bank ledger looks like an accounting document. It has columns, balances, debits, and credits. But the organizations that run time banks describe it as something closer to a reputation system, and the numbers are meant to start conversations rather than end them. Read the ledger as a verdict and you will misread almost everyone in it.

What the ledger actually records

Time banking rests on a simple rule: one hour given earns one hour received, and every hour is valued equally regardless of the skill involved. TimeBanks.Org, the national support organization, puts it plainly: “Each hour you give earns an hour you can receive, and every exchange builds a stronger, more inclusive community where everyone’s time and talents matter.”

That equality is deliberate. The Bay Area Community Exchange (BACE) explains in its FAQ why web design and weed-pulling earn the same credit: “Putting a price on people’s time separates us by making some people more valuable than others. Time credits excel in building relationships because they place an equal value on everyone’s time and relationships above profit.”

So the ledger records hours, not dollar value. Each row is a transfer: one member’s account is debited, another’s is credited. Over time, the columns show who has given a lot, who has received a lot, and where the two are out of step. That is the document a coordinator reads.

The balance is a prompt, not a score

The most useful sentence in BACE’s FAQ is not about accounting at all. It is about what the system is for:

“Our system functions a bit more like a reputation system than a normal accounting system. You can see how much other members have both given and received and others comments about them, as well as profile information that may help you determine who you would like to exchange with.”

That framing matters because it changes what a negative balance means. In a bank, a negative balance is a failure state. In a time bank, it is a normal part of participation. BACE says so directly:

“Having a negative balance is not a big deal in a time dollar account. After all, people have to receive in order for others to give and everyone needs to be cared for sometimes. Currently, we have set the limit around 50 hours. Reaching the limit triggers an administrator to contact you to help you spend or earn more hours.”

Read that carefully. The limit is not a penalty. It is a trigger for contact. The system is designed so that a member who has received far more than they have given does not simply drift. Someone reaches out, and the conversation is about how to help the member spend or earn more hours, not about shame.

Timebanking UK’s member handbook takes the same position from the other direction. Asked whether members must earn credit before receiving help, the handbook answers:

“No, you can ask for help straight away. As long as you intend to earn some credits in the future we are happy for you to have spent more hours than you have earned.”

The intention is the thing being tracked, not the balance alone. A member who has spent more than they have earned but who intends to give back is not a problem in the ledger. They are a member.

Why transparency does the work

If the ledger is a reputation document, its honesty depends on visibility. BACE’s FAQ explains the mechanism:

“Whenever one person earns time dollars, there is a corresponding debit for the same amount in someone else’s account. No one is anonymous in a timebank and transactions are transparent. This makes it pretty easy to know whether transactions are honest or not. There is not much incentive to cheat because the system is inherently abundant and is based more on reputation than anything else.”

This is the part that distinguishes a time bank ledger from a private bank statement. Every credit has a matching debit, and members can see each other’s giving and receiving. The record is not a secret held by an institution. It is a shared account of who has done what for whom.

That transparency is also a limitation. A member who has spent forty hours and earned two may look one-sided in the ledger, but the ledger cannot see the caregiving they do outside the exchange, the hours they spend looking after a relative, or the help they give neighbors who never joined. The document records only what passes through it. A coordinator who treats the ledger as complete will mistake a partial record for a whole person.

Reciprocity is the expectation, not the entry requirement

hOur Exchange in Portland opens its orientation with a correction that applies to every time bank:

“Timebanking is not barter. We don’t swap anything. You help me out then log your hour(s). Later, someone else does something for you and you ‘pay’ them with your hours.”

This is why a one-sided balance is not automatically a failure. In barter, two people trade directly and the exchange closes when both sides are satisfied. In time banking, the exchange is spread across a network and across time. A member who receives today may give next month, or next year, or to a different member entirely. The ledger tracks the network’s reciprocity, not each pair’s.

Timebanking UK’s code of conduct adds a practical note that coordinators see constantly: “There is no limit to the number of hours (or time credits) a person can accrue. However, spending hours is dependent on the services offered by time bank.” A member can build a large positive balance and still struggle to spend it if no one is offering the help they need. The imbalance can run in either direction, and the ledger alone will not tell you which kind you are looking at.

What a coordinator should ask, in order

The temptation, looking at a ledger, is to ask “who owes hours?” That question turns a reputation document into a debt collection sheet. A better sequence, drawn from how these organizations describe their own practice, runs like this:

1. Is the imbalance reciprocal somewhere else in the system? A member’s negative balance is another member’s positive one. Check whether the giving and receiving are distributed across the network before treating one account as a problem.
2. Has a stated limit been crossed? BACE sets its limit around fifty hours and treats reaching it as a trigger for contact. A limit that produces a phone call is doing its job. A limit that produces a suspension is a different policy, and members should know which one they joined.
3. Has a person been in touch? The ledger cannot make the call. The coordinator can. The question is whether the follow-up happened, not whether the number is embarrassing.

Consider a hypothetical member — call her a composite, not a real account — who has spent forty hours and earned two. The ledger shows a lopsided account. But the member may be caring for a parent, may have joined during an illness, or may simply not yet know what she can offer. The coordinator’s call is the actual instrument of accountability here. The number on the screen is only the reason to make it.

The ledger’s blind spots

Honesty about the document means naming what it cannot show. It cannot show the help members give outside the system. It cannot show the member who would give more but cannot afford the time. It cannot show the member whose offers go unanswered because the network lacks the skills they need. And it cannot show whether a member’s low giving reflects choice, capacity, or exclusion.

That is why the organizations that run time banks describe the ledger in relational terms. BACE calls its system “a bit more like a reputation system than a normal accounting system.” The reputation is built from visible transactions and comments, not from a single balance. A coordinator who reads only the balance is reading the least informative part of the document.

A transferable practice for reading any mutual-aid ledger

The same discipline applies to any record a mutual-aid group keeps — a tool library’s checkout log, a community fridge’s intake sheet, a ride schedule. Before treating a number as a judgment, run this short check:

• Check reciprocity across the whole record, not one account. Is the imbalance matched somewhere else in the system?
• Check the stated limit and what happens when it is reached. Does crossing it trigger contact, or punishment? Members should be able to find the answer in writing.
• Check who follows up. A ledger without a person assigned to read it is an archive, not infrastructure.
• Check whether members can see the record. Transparency is what makes the numbers trustworthy; opacity turns them into gossip.
• Check what the record cannot see. Ask what happens outside the system before concluding anything about the people inside it.

The coordinator’s laptop is still open. The balance still reads minus forty-two. But the next entry in the log will not be a number. It will be a note that someone called, and what the member said, and what the two of them decided to try next. That note is the part of the ledger that actually holds the neighborhood together.