What does day-to-day maintenance consist of? Who's responsible for the day-to-day maintenance of an organization? What do you actually have to do to maintain an organization from day to day? Imagine visiting a community organization for the first time. A program is scheduled to begin, but no one knows whether the assigned staff member is coming. The online calendar shows a different time from the public website. A participant has been waiting for an answer that should have been provided several days ago. An invoice requiring approval is overdue, and the employee responsible for the organization's primary software account is unexpectedly out. None of these problems by itself defines the organization. Together, however, they suggest that the organization lacks reliable day-to-day operating systems. A management plan establishes how an organization intends to operate. Day-to-day management puts that plan into practice. The goal is not for one director to personally monitor every detail. It is to create reliable systems, clear ownership, appropriate controls, backup capacity, and communication that allow necessary work to continue even when circumstances change. What does day-to-day maintenance consist of? Nearly every part of organizational management requires recurring attention. Some tasks truly happen every day. Others may occur weekly, monthly, quarterly, annually, or when a particular event triggers them. A useful operating system identifies the appropriate cadence rather than treating every responsibility as an informal daily concern. The work of the organization Programs, services, advocacy, outreach, and other mission-related work need enough staffing, scheduling, information, authority, and resources to operate reliably. The organization should know: What work is essential Who owns each responsibility Who provides backup coverage What information or systems the work depends on What quality or safety requirements apply What happens when normal operations are disrupted Financial management Financial work includes more than paying bills and monitoring a bank balance. Organizations may need recurring processes for: Recording transactions Accounts payable and receivable Payroll Cash-flow forecasting Bank and account reconciliation Grant and contract tracking Restricted and unrestricted funds Purchasing Vendor payments Expense reimbursement Internal controls Financial reporting People and workforce management Staff and volunteer management requires recurring attention to: Staffing and coverage Supervision Workload Performance Scheduling and leave Training and development Accessibility and accommodations Safety Workplace concerns Role changes and transitions The organization's responsibility is not to keep everyone continuously enthusiastic or happy. It is to maintain fair, safe, workable conditions and clear expectations. Governance support The Board or other governing body needs enough information to carry out its oversight responsibilities without becoming the manager of everyday operations. Recurring governance support may include: Preparing accurate financial information Reporting major organizational developments Preparing agendas and Board materials Recording decisions and minutes Tracking Board actions Supporting committee work Monitoring governance deadlines and requirements Community and external relationships Community organizations operate within networks of residents, participants, partner organizations, funders, public agencies, vendors, advocates, media, and other stakeholders. Maintaining these relationships may involve: Community engagement Participant communication Referral partnerships Funder reporting Government or public-agency coordination Advocacy where appropriate Public and media communication The objective is not simply to keep the organization's profile high. Relationships should support the organization's mission, accountability, coordination, and community responsibilities. Facilities, technology, and logistics The organization also needs the physical and digital infrastructure required for its work. This may include: Facilities Cleaning and sanitation Physical security Equipment Vehicles Inventory and supplies Computers and mobile devices Networks and internet service Software and cloud systems Access control Vendors and service providers Information, records, privacy, and cybersecurity Organizations depend on information. Recurring management includes: Keeping necessary records current Protecting confidential information Managing access to systems Maintaining backups Applying software and security updates Responding to suspicious messages or account activity Managing records retention and destruction Removing access when people leave or change roles Safety, risk, and continuity Organizations should continually pay attention to conditions that could interrupt essential work or harm people. This includes: Workplace hazards Emergency procedures Financial risks Staffing dependencies Facility risks Cybersecurity risks Vendor dependencies Legal or compliance concerns Organizational culture and sustainability Daily management also shapes organizational culture. Culture develops through ordinary practices such as: How decisions are explained How people are treated How concerns are handled Whether commitments are kept Whether workload is sustainable Whether mistakes can be discussed honestly Whether organizational values are reflected in everyday behavior Who's responsible for the day-to-day maintenance of an organization? Responsibility depends on the organization's size, structure, programs, staffing, geography, governance, and resources. In a very small organization, one person may perform several functions. Even then, important responsibilities should not exist only in that person's memory. Larger organizations should distribute operating responsibilities among appropriate roles rather than expecting the executive director or another senior leader to personally oversee every transaction, supply order, personnel question, technology problem, and community relationship. Assign ownership For important recurring functions, identify: Owner: Who is responsible for making sure the work happens? Backup: Who can perform or coordinate the work if the owner is unavailable? Decision authority: Who approves significant decisions? Escalation route: Where does the issue go when the normal process cannot resolve it? One person may hold more than one of these roles in a small organization, but the arrangement should still be clear. Use appropriate expertise Some functions may appropriately be handled by outside specialists. Depending on organizational needs, these may include: Accountants or bookkeepers Payroll providers Attorneys Information-technology or cybersecurity providers Human-resources advisers Cleaning or facility services Insurance professionals Specialized consultants Outsourcing work does not eliminate organizational accountability. Someone inside the organization should still own the vendor relationship and monitor whether the required work is being performed. Distribute work fairly Shared responsibilities should be assigned according to role, workload, skill, safety, accessibility, and organizational need. Do not repeatedly assign undesirable administrative or housekeeping work to the same people simply because they are dependable or have less formal authority. Likewise, don't require employees to perform additional uncompensated work or treat after-hours cleanup as a team-building activity. Use volunteers appropriately Volunteers can make valuable contributions when their roles are clearly defined, appropriate, safe, and genuinely voluntary. Do not assume that an unpaid volunteer can simply substitute for an absent employee. Consider: Whether the work should appropriately be compensated Whether specialized training or credentials are required Whether the volunteer has accepted that responsibility Whether supervision is available Whether confidentiality or safety issues are involved Build backup capacity Essential work should not depend entirely on one person. Depending on the function, backup capacity may include: Cross-training Alternate approvers Substitute staff Documented procedures Shared access to necessary records Vendor support Emergency succession arrangements Access should still follow appropriate security and confidentiality controls. What do you actually have to do to carry out the day-to-day maintenance of an organization, and how do you do it? Reliable operations depend on systems. Some can be simple: an inventory item reaches a defined reorder point, a responsible employee receives an alert, and the authorized purchaser places an order. Other functions need policies, workflow systems, approvals, controls, training, and documentation. The goal is to prevent predictable problems from becoming emergencies while still allowing the organization to respond when conditions change. The work of the organization Make sure essential work is covered Maintain current schedules, staffing assignments, contact information, backup arrangements, and responsibility for opening, closing, or operating services. When someone will be absent, people should know: Who must be notified How coverage will be arranged What participants or partners need to know Who can authorize a cancellation or change Use approved communication channels rather than relying entirely on informal phone trees or one person's memory. Identify essential functions Decide which organizational functions must continue during disruption and which can temporarily be delayed. Identify the dependencies for each essential function: People Technology Facilities Vendors Data and records Equipment Funding External partners Maintain records Define what information needs to be recorded, who records it, when it must be entered, who reviews it, and how it is protected. Records may support: Program operations Participant services Financial management Grants and contracts Evaluation Safety Legal or regulatory requirements Organizational continuity Collect only information the organization legitimately needs. Use appropriate confidentiality, access, retention, and destruction practices. Use meetings when interaction is needed Meetings can support coordination, problem-solving, decision-making, and shared learning. Not every recurring update requires a meeting. For useful meetings: Define the purpose Share an agenda Provide relevant information in advance Include remote participation where appropriate Use accessible materials and technology Record decisions Assign action items, owners, and deadlines Support learning and information-sharing Staff and volunteers may need ongoing access to changing evidence, policy, community information, professional standards, and technical knowledge. Learning may occur through: Training Coaching Peer learning Shared knowledge bases Communities of practice Conferences or professional education Someone should own the process of identifying significant learning needs and making appropriate opportunities available. Improve programs deliberately Programs should be reviewed and improved when evidence, participant feedback, operational experience, or changing conditions indicate a need. Not every process needs continuous change. Before changing an established practice, consider: What problem the change is intended to solve What evidence supports it Who may be affected What resources are required Whether safety, privacy, accessibility, or compliance are affected Whether a pilot would be useful Maintain appropriate outreach and recruitment People need to know how to access programs and services that are intended for them. Outreach may include: Community partnerships Direct outreach Websites and digital communication Social media Public information Referral networks Media communication when useful Use methods appropriate to the audience and evaluate whether outreach actually reaches the people the organization intends to serve. Financial management Keep accounting records current Financial transactions should be recorded accurately and within an appropriate timeframe. The required cadence depends on transaction volume, organizational complexity, risk, and reporting needs. Maintain reliable records for: Income Expenses Assets and liabilities Grants and contracts Restricted funds Payroll Accounts payable and receivable Monitor cash flow A balanced annual budget does not guarantee that cash will be available when bills and payroll are due. Monitor: Current cash Expected receipts Upcoming payroll Vendor obligations Grant reimbursement timing Restricted versus available funds Reserve levels Use short-term cash-flow forecasts so financial problems become visible before a payment deadline is missed. Maintain internal controls Financial responsibilities should include checks and balances. Depending on organizational size, separate or independently review functions such as: Initiating a purchase Approving the purchase Making the payment Recording the transaction Reconciling the account Reviewing financial reports A small organization may not have enough employees to separate every function. In that situation, use compensating controls such as independent Board review, outside bookkeeping, or periodic review by someone who did not initiate the transaction. Process payroll, invoices, and receivables reliably Establish recurring schedules and clear ownership. Use systems that account for: Holidays Leave New hires and separations Changes in compensation Vendor due dates Contract billing requirements Payroll and other legally or contractually required payments should not depend on one person's availability. Track grants and contracts For each award or contract, know: Budget Spending to date Restricted categories Required match or cost sharing Billing schedule Reporting deadlines Program deliverables Required documentation Keep source documentation in systems that are organized, secure, and accessible to authorized people who need it. Manage purchasing and inventory Critical materials should have defined reorder levels and responsible owners. Purchasing processes should address: Budget availability Spending authority Procurement thresholds Vendor selection Conflicts of interest Contract terms Delivery and receipt Inventory records where needed High-risk purchases may require stronger review than routine low-cost supplies. Manage banking and electronic payments securely Establish: Authorized users Approval limits Multi-factor authentication Transaction alerts Procedures for ACH, wires, cards, and checks Independent reconciliation Verification procedures for vendor payment changes Limit financial-system access according to role and remove access promptly when responsibilities change. People and workforce management Maintain supervision and role clarity Staff and volunteers should know: Their responsibilities Who supervises or supports them What decisions they can make Where to ask questions Where to report a concern Address workload and coverage Monitor whether staffing is sufficient for the work. Chronic overtime, canceled leave, repeated emergency coverage, or continued dependence on one employee may indicate an operational problem rather than exceptional commitment. Consider: Staffing levels Schedule design Cross-training Temporary help Prioritization Reducing lower-priority work Address performance and conduct appropriately Ordinary performance problems should be addressed through clear expectations, specific examples, feedback, appropriate resources, documentation, and follow-up. Other concerns may require different processes, including: Harassment or discrimination Retaliation Workplace violence Safeguarding concerns Fraud Serious safety violations Staff should have a reporting route outside the immediate supervisor when the supervisor is part of the concern. Support accessibility and accommodations Make sure people know how to request needed workplace or communication adjustments through the appropriate process. Include accessibility in facilities, technology, meetings, emergency procedures, and everyday work design. Maintain professional relationships without intruding into personal lives Informal conversation can strengthen working relationships. It should not become a way for managers to gather unnecessary personal information. If someone's personal circumstances affect work, focus on appropriate organizational responses such as leave, flexibility, workload adjustment, benefits, or accommodations rather than expecting detailed disclosure. Recognize contributions appropriately Give specific credit and appreciation for meaningful work. Recognition may be public or private depending on the person's preferences and the situation. Recognition should not substitute for appropriate compensation, manageable workload, development opportunities, or fair treatment. Governance support The Board needs timely, accurate information sufficient to carry out governance and oversight. Depending on the organization, this may include: Financial statements Significant program information Strategic progress Significant risks Major legal or compliance matters Executive leadership information Important organizational changes The Board should not need to manage ordinary operational details in order to exercise effective oversight. Support Board meetings and follow-through Maintain: An annual meeting calendar Clear agendas Useful pre-meeting information Accurate minutes Committee responsibilities Records of Board decisions Follow-up on assigned actions Support Board learning Board members may need orientation or continuing education about: Governance responsibilities Financial statements Programs and community context Legal and ethical responsibilities Conflicts of interest Strategic issues Learning needs should be based on role and experience rather than assumptions about a person's background or community identity. Community and external relationships Organizations should maintain relationships that support community accountability, coordination, access, and mission-related work. Maintain community engagement Use appropriate methods to understand community priorities and experiences, communicate about the organization's work, and invite participation where it can genuinely influence decisions. Maintain partnerships For important partner relationships, clarify: Purpose Responsibilities Referral or service processes Data-sharing rules Decision authority Communication contacts Manage funder relationships professionally Maintain accurate reporting, meet deadlines, communicate material problems, and clarify expectations. Funder relationships should not depend mainly on personal friendship. Manage public and media communication Identify who may speak officially for the organization. Provide accurate information, protect confidential information, and coordinate responses during significant incidents. Staff, volunteers, Board members, and participants should understand when they are authorized to speak on behalf of the organization and when they are speaking only for themselves. Facilities, technology, and logistics Maintain clean, safe, and accessible facilities Assign responsibility for: Cleaning and sanitation Repairs Opening and closing procedures Keys, badges, and physical access Accessibility Building systems Waste and hazardous materials where relevant Use qualified staff or vendors for work requiring specialized skill or safety procedures. Maintain equipment proactively Keep an inventory of significant equipment and technology where appropriate. Track: Responsible owner Condition Warranty or service contract Maintenance schedule Replacement timeline Preventive maintenance can be less disruptive and less expensive than waiting for critical equipment to fail. Manage vendors and service providers Important vendors should have an organizational owner. Monitor: Contracts Renewal dates Costs Performance Service levels Access to facilities or information Insurance or other requirements where relevant Cybersecurity and information systems Control access Give people access to the systems and information required for their roles and no more than necessary. Review and change access when: Someone joins Responsibilities change Someone leaves A vendor relationship ends Use basic security protections Depending on the organization's systems, practices may include: Multi-factor authentication Strong account-management procedures Timely security updates Endpoint protection Secure remote access Phishing awareness Restricted administrative privileges Back up critical information Maintain appropriate backups of critical data and system configurations. Backups should be protected from the same event that could damage the primary system and should be tested periodically to confirm that important information can actually be restored. Prepare for technology incidents Staff should know how to report: Suspicious messages Compromised accounts Lost or stolen devices Unusual payment requests System outages Suspected data exposure Identify who coordinates the technical and organizational response. Safety, emergencies, and continuity The appropriate emergency procedures depend on the organization's work and workplace. Plans may need to address: Fire Severe weather Medical emergencies Workplace violence Hazardous materials Facility loss Technology outage Cybersecurity incidents People should know: How to report an emergency Who has authority to respond When and how to evacuate or shelter Where to obtain reliable updates How people will be accounted for where appropriate Include disability access and other individual safety needs in emergency planning. Organizational culture and sustainability Organizations benefit from a clear sense of purpose, but daily functioning should not depend on one leader continually generating enthusiasm. Leaders and managers can contribute to a healthy culture by: Communicating priorities clearly Acting consistently with organizational values Responding constructively to concerns Sharing information appropriately Recognizing good work Maintaining reasonable boundaries Addressing chronic workload problems Admitting mistakes Supporting psychological safety Sustainable organizations allow people to take leave, change roles, and eventually leave without the work collapsing. Develop backup and succession capacity Identify responsibilities that would become vulnerable if a particular person left unexpectedly. Use: Documentation Cross-training Delegation Backup authority Succession planning Leadership development can be part of this process without assuming that every employee or volunteer wants to become a manager. Keep sight of the whole organization Individual systems can function reasonably well while the organization as a whole develops serious problems. Leaders and governing bodies therefore need organization-wide visibility. Useful information may include: Financial reports Cash-flow projections Program performance Staffing and vacancy information Workload Safety incidents Participant and community feedback Compliance deadlines Technology and cybersecurity incidents Vendor performance Major organizational risks Use indicators and escalation thresholds Leaders do not need to manually inspect every routine transaction. Instead, identify indicators that require attention. Examples might include: Cash falling below a defined operating threshold A critical vacancy remaining open Repeated missed service targets Significant overtime or workload growth An overdue grant report A safety incident A critical system outage A vendor failing an important service obligation Define who receives the alert and what action is expected. Maintain a risk view Periodically ask: What could interrupt our essential work? Which responsibilities depend on one person? Which vendors or systems are critical? Where do we lack backup coverage? What financial risks are increasing? What legal, safety, privacy, or cybersecurity risks need attention? What would be difficult to recover if it were lost? Assign significant risks to responsible owners and review them at an appropriate cadence. Use professional judgment together with evidence Experienced leaders may notice early signs that something deserves attention. Treat that instinct as a reason to ask questions and gather information rather than as proof that something is wrong. Good daily management combines professional judgment with data, direct observation, feedback, policies, financial information, and other evidence. Review operations and improve them Periodically examine: Which routines work reliably Which tasks repeatedly become urgent Where information gets lost Where approvals create unnecessary delay Which responsibilities lack backup coverage Which systems create excessive manual work Which controls are no longer adequate Improve systems rather than depending on individual heroics to compensate for recurring weaknesses. In Summary A management plan has value only when the organization can carry out its responsibilities reliably. Day-to-day management includes mission-related work, finances, staffing and supervision, governance support, community relationships, facilities, technology, records, cybersecurity, vendors, safety, and continuity. These responsibilities should not depend on one director personally remembering and overseeing everything. Assign ownership, decision authority, backup coverage, and escalation routes. Document recurring processes where failure would have meaningful consequences. Financial operations should include appropriate internal controls, current records, cash-flow monitoring, secure payment processes, grant tracking, purchasing controls, and independent review. Operational systems should also protect people and information through workplace safety, accessibility, cybersecurity, privacy, emergency planning, and continuity arrangements. Strong daily management does not require constant expansion, forced optimism, unpaid extra work, or one unusually dedicated leader holding the organization together. The goal is a resilient operating system in which routine responsibilities are clear, important risks become visible early, essential work can continue through disruption, and leaders can focus their attention where judgment and action are actually needed. Resources Online Resources The Center for Nonprofit Management: consultants on management issues (they charge fees). The Frances Hesselbein Leadership Institute: links, readings, information, Fellowships, etc. in nonprofit management. A free management library from the Management Assistance Center for Nonprofits - 69 basic topics, broken down into 675 more specific subtopics. A wealth of information, of varying depth. National Center for Charitable Statistics is a great links page from the Urban Institute. Nonprofit Charitable Organizations provides links to many nonprofit topics, including management and Boards. The Nonprofit Expert provides articles, ideas, and links to management topics, including an on-line Compendium of Federal and State Regulations for US Nonprofit Organizations. The Nonprofit Genie home page: links and information of all kinds for nonprofits. An extremely useful site. Nonprofit Nuts and Bolts, a magazine offering practical tips for nonprofits. Nonprofit Support Center provides leadership, consulting and training to help nonprofits do their work better. "Open House" by Mark Henricks, from Entrepreneur, May, 1995. An article about a technique that could be useful in daily management.
