The Friction Tax, Part 2: The Work Beneath the Work
- by Buoyancy Works
- |
- - 9 min read
In This Article:
How Reporting, Duplicated Data, and Underpowered Technology Drain Nonprofit Capacity
Every community organization knows the strange moment when good work becomes difficult to prove.
The team has helped people secure benefits, stabilize housing, replace identification, open bank accounts, complete tax returns, resolve urgent needs, and recover from setbacks.
Staff know the work happened. Clients experienced the difference.
But when reporting time arrives, the organization may have to reconstruct that work from case notes, intake forms, spreadsheets, shared drives, paper records, emails, survey tools, funder portals, and staff memory.
Someone finds the missing forms.
Someone cleans the spreadsheet.
Someone decides which activities fit the funder’s categories.
Someone follows up with frontline staff about incomplete records.
Someone turns a complicated set of human interactions into a clean table of outputs and outcomes.
The report eventually gets submitted.
The hidden work required to produce it usually does not appear in the report.
This is the second layer of the friction tax.
Clients encounter friction when they try to access support. Advocates absorb some of that friction by helping them navigate. Organizations then absorb another layer through documentation, duplicate entry, reconciliation, reporting, and the workarounds needed to hold fragmented systems together.
That work is often treated as administration rather than service delivery.
But it directly affects how much service an organization can deliver.
The Reporting Burden Starts Long Before the Report
Reporting is often discussed as a quarterly or annual responsibility.
In practice, it begins at the frontline.
A funder may ask an organization to report:
- who was served;
- which program they received;
- what activities took place;
- how often they participated;
- which referrals were made;
- which outputs were completed;
- whether circumstances changed;
- how clients rated their progress;
- and how the work connects to the funded agreement.
Each question may be reasonable.
Together, they determine what staff must collect during intake, what they document after each interaction, which categories appear in the database, when surveys are assigned, how referrals are coded, and what managers need to monitor.
The reporting requirement travels backward through the organization.
It moves from the funder agreement to the reporting template, from the reporting template to the data structure, from the data structure to the workflow, and from the workflow to the interaction between a staff member and a client.
This is not necessarily a problem. Organizations need information to learn, improve services, demonstrate accountability, and steward public or charitable funds.
The problem begins when reporting requirements are disconnected from how the work actually happens.
A funder may want a count of “service episodes,” while staff think in terms of visits, calls, actions, referrals, applications, and follow-ups. An organization may deliver flexible, team-based support, while the reporting model assumes a client belongs to one worker and one program. A funder may request a single outcome category even though the result emerged across several services over time.
When categories do not match frontline reality, staff must translate the work into the system after the fact.
That translation is work.
Funder Requirements Cascade Downward
Administrative requirements are rarely contained at the level where they are created.
They cascade.
A funding agreement may require demographics, eligibility evidence, service counts, attendance, pre- and post-program surveys, outcome indicators, financial categories, narratives, and supporting records.
The organization must then create the processes needed to produce those answers.
Managers add fields.
Forms become longer.
Staff receive new documentation instructions.
Spreadsheets gain extra tabs.
A second survey tool is introduced.
Program codes multiply.
Someone creates a guide explaining which service belongs in which category.
Each addition may solve a legitimate reporting problem. But few organizations have a process for assessing the combined burden created by all of them.
Over time, the documentation system becomes a record of accumulated obligations.
This is one reason administrative work can expand without anyone explicitly deciding to make it larger.
Research on public-sector friction distinguishes among administrative burden, red tape, sludge, and other forms of costly process. These concepts are not identical, but they share an important insight: requirements that appear reasonable in isolation can become costly when people experience them as a combined system.
For a community organization, those costs are not paid only by the person completing the report.
They are distributed across the team:
- frontline staff collect additional information;
- supervisors check completeness;
- administrators reconcile categories;
- managers interpret funder definitions;
- analysts clean and aggregate data;
- leaders explain discrepancies;
- and everyone adjusts their work when requirements change.
The burden reaches the frontline even when the frontline worker never sees the final report.
The Technology Gap Becomes a Resource Tax
Many community organizations do not lack technology.
They have a great deal of it.
They may use:
- a legacy client database;
- spreadsheets;
- paper intake forms;
- shared drives;
- online survey tools;
- email;
- calendars;
- accounting software;
- funder portals;
- generic customer relationship systems;
- and local documents created to fill gaps between them.
The problem is often not the absence of tools.
It is that the tools do not form a coherent operating system for the work.
A client may be entered in one database. Household details may live in a spreadsheet. Survey responses may be stored in a separate platform. Referrals may be documented in notes. Follow-ups may sit in a worker’s calendar. Funder outputs may be reconstructed in another workbook.
Staff become the connection between the systems.
They remember where information belongs. They copy it from one place to another. They reconcile records when the same client appears under different names. They maintain local guides, templates, colour codes, naming conventions, and unofficial rules.
Technology has not removed the administrative burden.
It has distributed the burden across screens.
This creates a recurring resource tax:
- staff time is spent moving information rather than using it;
- training must cover both the service model and the workarounds;
- managers cannot easily see current demand or incomplete work;
- reporting depends on manual consolidation;
- and every local fix creates another process that someone must maintain.
The system may technically function. But it functions because people continuously repair its gaps.
Duplication Is Not a Minor Annoyance
Duplicate entry is easy to dismiss as an inconvenience.
Enter the name again.
Copy the address.
Recode the interaction.
Upload the same form to a second location.
Add the survey result to the funder spreadsheet.
Individually, each task may take only a few minutes.
But duplication has compounding effects.
It consumes time
Every repeated entry reduces the time available for service delivery, preparation, follow-up, supervision, and learning.
It creates inconsistent records
When information changes in one system but not another, the organization no longer has a dependable version of the record.
A client’s address, household composition, program status, or referral outcome may differ depending on where someone looks.
It creates reconciliation work
Someone must compare files, resolve discrepancies, remove duplicates, and decide which version is correct.
It delays visibility
Managers may not know what is happening until records are manually combined at the end of the month or quarter.
It weakens trust in the data
When staff repeatedly encounter inaccurate or incomplete records, they are less likely to rely on the system. They may create their own tracking tools, which produces further fragmentation.
It transfers frustration to the client
When information cannot move across workflows, clients may be asked to repeat details or provide documents that the organization already holds.
Duplication is therefore not simply a time cost.
It is a source of delay, error, uncertainty, and avoidable relational friction.
Shahab and Lades connect sludge to several forms of transaction cost, including the effort required to search for information, evaluate options, implement decisions, and manage psychological strain. Their framework helps explain why fragmented administrative processes cost more than the minutes needed to complete each task.
The cost includes finding the right record, deciding which version is correct, understanding how one system maps to another, correcting errors, and recovering confidence after the data fails.
Heroics Hide System Failure
Many organizations make fragmented systems work through expertise, commitment, and persistence.
One staff member knows how the funder categories really work.
Another knows which spreadsheet contains the reliable numbers.
A manager knows how to identify duplicate clients.
Someone else can translate service notes into reportable outputs.
During reporting season, these people perform a familiar rescue.
They find missing data, repair formulas, interpret inconsistent entries, contact staff, rebuild timelines, and make the report coherent.
Their expertise is real and valuable.
It is also a risk.
When an organization depends on one or two people to make its information usable, knowledge has become concentrated in individuals rather than embedded in the operating system.
The process may fail when someone:
- takes leave;
- changes roles;
- leaves the organization;
- becomes overloaded;
- or simply cannot remember how an earlier workaround was built.
Routine heroics can also hide the scale of the problem from leaders and funders.
The report is submitted, so the system appears to have worked.
But the report does not show the evenings spent cleaning data, the services delayed while staff searched for records, or the management attention diverted to reconstruction.
A process that succeeds only because people repeatedly rescue it is not a reliable process.
Data Quality Is a Behavioural and Systems-Design Problem
Organizations often respond to incomplete records by reminding staff to improve data quality.
Sometimes that is appropriate.
But “staff need to enter better data” is rarely a complete diagnosis.
Documentation behaviour is shaped by the environment in which it occurs.
Staff are less likely to complete a field accurately when:
- the category does not match the service they delivered;
- the system is slow;
- the same information must be entered elsewhere;
- the purpose of the field is unclear;
- the correct option is difficult to find;
- the interaction is urgent;
- the worker expects to complete the record later;
- the data produces no visible value for the person entering it;
- or local practice differs from written instructions.
These are not excuses for poor documentation. They are observable design conditions.
A field that is consistently skipped may indicate a training issue. It may also indicate that the field is confusing, badly timed, redundant, or disconnected from the workflow.
A category that is used inconsistently may reflect weak definitions. It may also reflect a service model that is more complex than the available options.
A note completed days later may reflect poor discipline. It may also reflect a system that makes documentation impossible during the interaction and provides no effective prompt afterward.
The practical question is not simply:
Why did the staff member fail to complete the record?
It is:
What conditions make the desired documentation behaviour difficult, ambiguous, or unrewarding?
That shift matters because it changes the response.
Instead of adding another reminder, the organization can examine the task, timing, interface, categories, feedback, and value of the data.
When Administration Becomes Sludge
Administrative work is not automatically waste.
Good documentation can:
- protect clients and staff;
- support continuity;
- make follow-up reliable;
- improve supervision;
- reveal unmet demand;
- support learning;
- strengthen funding applications;
- and demonstrate accountability.
The problem is not administration itself.
The problem is administration that is disconnected from service delivery, duplicated across systems, difficult to interpret, or useful only after extensive manual repair.
That is where administration becomes sludge.
The distinction is important because the goal is not to minimize documentation at any cost. An organization could reduce paperwork and lose essential information, weaken accountability, or make service continuity worse.
The better goal is to ensure that every significant data requirement has a clear purpose and that the information is captured as close as possible to the work that creates it.
A Practical Work-Beneath-the-Work Audit
A team can begin identifying hidden administrative burden without launching a major technology project.
Choose one recurring report, preferably one that requires input from several people.
Then trace each reported number or narrative backward.
For every item, ask:
- Where is this information first created?
Does it arise during intake, an interaction, a referral, a survey, or a follow-up? - Where is it recorded?
Is it entered on paper, in a database, a spreadsheet, a form, an email, or more than one place? - How many times is it handled?
Count every entry, copy, translation, cleanup, approval, and reconciliation step. - Who knows how the process really works?
Identify any step that depends on one person’s memory or unofficial instructions. - When does the information become visible?
Can managers use it while the work is happening, or only after the reporting cycle? - What happens when something is missing or inconsistent?
Is there a clear recovery process, or does someone investigate manually? - Who uses the information afterward?
If nobody uses a field for service, management, learning, compliance, or reporting, ask why it is still being collected.
The output does not need to be a sophisticated process map.
A table with five columns is enough:
| Information required | First captured | Re-entered or transformed | Person responsible | Current failure point |
|---|
The audit often reveals a small number of high-cost problems:
- the same information entered multiple times;
- categories that require interpretation;
- reporting fields collected too late;
- records that cannot be linked reliably;
- surveys stored outside the client journey;
- or one staff member functioning as the organization’s integration layer.
These are useful starting points because they describe work that can be redesigned, not merely endured.
The Work Beneath the Work Is Still Work
Community organizations are often praised for doing more with less.
That praise can hide an uncomfortable reality.
Many teams are not simply delivering services with limited resources. They are also compensating for fragmented funder requirements, poorly fitted technology, disconnected data, and processes that require continuous human repair.
The work beneath the work consumes capacity.
It affects how many people can be served, how quickly staff can follow up, how confidently managers can make decisions, and how accurately leaders can describe what the organization has achieved.
The answer is not to stop measuring or reporting.
It is also not simply to buy more software.
The deeper task is to connect service delivery, documentation, measurement, and reporting so that information becomes useful as the work happens.
That is where technology can either reduce the friction tax—or make it worse.
About Buoyancy Works
Buoyancy Works develops accessible technology for community organizations delivering stabilization, navigation, advocacy, and coaching. Our work focuses on reducing administrative friction, preserving service continuity, and making frontline work easier to coordinate, understand, and sustain.
Learn more at https://buoyancy.works
Acknowledgement
This article was developed using AI-assisted research and drafting. The Buoyancy Works team reviewed the evidence, analysis, and final editorial decisions.
References
Imagine Canada. (2026). The hidden cost of funding: How federal policies and practices affect charities and nonprofits.
https://imaginecanada.ca/en/research/hidden-cost-of-funding
Madsen, J. K., Mikkelsen, K. S., & Moynihan, D. P. (2022). Burdens, sludge, ordeals, red tape, oh my! A user’s guide to the study of frictions. Public Administration, 100(2), 375–393.
https://doi.org/10.1111/padm.12717
Shahab, S., & Lades, L. K. (2024). Sludge and transaction costs. Behavioural Public Policy, 8(2), 327–348.
Recommended for you
