File No Schedule C Construction Industry List In: Fill & Download for Free

Hello,I’m Jerry, co-founder at ArchiSnapper. We provide new articles every week on how you can build and scale your AEC business.Administration tasks are an essential part of running your architecture or construction business.Without a smooth process; mistakes will be made, things will be forgotten, clients will get confused and irritated, and you could risk making big financial or legal mistakes that could jeopardize your business.With the right tools and processes in place—your productivity will increase, you’ll impress your clients, and your business will grow.And when it comes to perfecting processes, a lot has changed in the past 10 years. From Building Information Modeling (BIM) to the Internet of Things (IoT), new tools and online platforms have revolutionized how we handle administrative tasks.From project management tools to saving time on email writing, there are dozens of fantastically helpful tools that can change the way your business operates; helping you save time, optimizing workflows, hitting deadlines, and impressing your clients with your professionalism and expertise.But where to start? What tools are available and what do you need?Let’s look at the 7 most time-consuming administrative tasks you probably have to do each week, and the tools that can help you do them faster and better.1: Project managementA. Project and business management tools built for the AEC industryB. Easy to onboard project management toolsC. Sharing documents and files2: Streamline your financesA. Bookkeeping, tracking your costs, and incomeB. Payroll, time tracking and expenses:C. Generate and track invoices3: Keep your contracts organized4: Creating gorgeous field reports and punch lists5: Communicate more effectively and in a timely mannerA. Manage your inbox more effectivelyB. Schedule meetings more efficientlyC. Flawless grammar and spelling6: Stay top of mind with CRMs and newslettersA. Stay in communication with your clients with a CRMB. Manage your newsletters7: Managing your online presenceA. Website ServicesB. Keep your social media consistentLet’s get started.In More Creativity, less Admin: 50 Apps and Tools that will Save you Time we covered all the details on the following 50 apps and tools that will help you1. Manage your projects:MonographSynergyCoreRapport3Workflow MaxTrelloBasecampAsanaTeamWorkPMGoogle Drive (+ Google Docs)Dropbox2. Streamline your finances:BenchBrightbookWaveTsheetsHarvestHubstaffExpensifyFreshbooksInvoiceraInvoiceNinjaBlinksale3. Keep your bids and contracts organized:ShakeHelloSignSmartbid4. Create gorgeous site reports:ArchiSnapper5. Communicate more efficiently:Superhuman17hatsBoomerangScheduleOnceDoodleCalendlyYouCanBookMeJoin. MeGrammarly6. Stay top of mind with CRMs and newslettersHubSpot CRMZenDesk SellZoho CRMInsightly CRMAgile CRMActiveCampaignMailChimpHubspot Newsletter7. Manage your online presence:WebsWixWordPressWeeblyBufferHootsuiteMeetEdgarI hope this answer was useful.Check out the full article for more details per app or browse our blog for more valuable info on how to build your construction business.Good luck!

The Early YearsI began with Perl, because my arrogant, smartass, doe-eyed, naive younger self thought rules were for losers, and I wanted to write code like a megaleet superhacker. Perl was the "swiss army chainsaw," and I believed it was the only language I would ever need.I knew small amounts of C++ and Java, but not enough to write anything meaningful. That didn't bother me, because I knew they were for cubicle monkeys with tiny brains. I had heard of C, but figured C++ was basically the latest version of C.I learned a bit about Python from my brother (about Python; not to be confused with learning a bit of Python), but instinctively hated it for being too hand-holdey. I was particularly put off by Python's "there is exactly one correct way to do it" motto, which directly opposed my beloved Perl's TMTOWTDI.I didn't know a thing about functional languages, much less any programming paradigm outside of my little imperative world of scripting and OO languages.I didn't really know how to use third-party libraries in Perl, and I was more or less confined to single-file scripts, but I figured I knew enough to do pretty much anything. Looking back, I'd rate my competence somewhere between a third to a half of an entry-level software developer. If I were to evaluate this past version of myself for a paid internship, I would reject him 10 minutes into the interview.After tooling around with Perl for most of a year, I got an unpaid internship at a graduate school, where the hiring criteria were basically "hire anyone willing to learn, regardless of skill, as an unpaid intern".Thankfully, that work turned out to be primarily Natural Language Processing, which Perl lends itself very well to, so I shined brightly. Just a few months later, I was offered a full-time research position, which I would hold for the next four years. (It was more than the fact that I happened to know some Perl; I was also a clever and crafty little shit.)Within the first few months of using Perl for a serious purpose, I managed to outsmart the ever-loving Christ out of myself. I'd work on some complicated program, set it aside for two or three weeks, and then get bewildered and frustrated by my own super-clever, uncommented Perl. It was an order of magnitude faster to simply rewrite programs from scratch than to understand my own code. And that's when the importance of readable, structured code began to dawn on me.My lab also used a lot of Python, but I had been avoiding it up to this point out of misplaced and totally uninformed hatred. Begrudgingly, I started teaching myself some Python.The more I learned and practiced Python, the more I liked it. It was a humbling experience, as I gradually became more aware of the depths of my ignorance, but Python was patient with me, and I developed a deep appreciation for its simplicity and accessibility to newbies. I realized that I did need to be led by hand through new and increasingly complex programming concepts, and Python was my wise and compassionate sensei.At this stage, my thoughts on various programming languages were roughly as follows:Perl: "I should get better at this. As I master concepts in Python, I'll go back and learn them the Perl way."Python: "A vehicle for building up my skills and learning new concepts. Perl remains the One True Path; Python will accelerate my progress along it."PHP: "Perl for the web -- awesome! I should pick this up at some point."C++, Java: "These obsolete languages are for cubicle monkeys, and should be ignored."Better, Faster, StrongerIn the research lab, I found myself needing to write high-performance code increasingly often, and Python was no longer cutting it. By this point, I understood what "low-level" and "high-level" referred to in the context of programming languages, and I knew what the tradeoffs of moving lower were.I had already taken an introductory C++ course at a community college when I was 12, and I had also recently breezed through another at the university I was attending, so I decided to dive into C++.It didn't take long to become thoroughly sickened by C++. The STL in particular proved to be an inelegant, overcomplicated mess to work with. I hated everything about the usual code, compile, debug cycle.In learning about C++, I got a better understanding of how it related to C. Seeing that all the things I hated about C++ were C++-specific constructs crudely bolted onto a much simpler language, I decided to go back even further and teach myself C, instead.It was in C that I found exactly what I expected and was hoping for in a low-level programming language: I accepted the manual memory management and lack of built-in data structures as a cost of doing business, and the tremendous gains in performance took my breath away. In a frenzy, I rewrote my collection of Python tools in C and stared in wonder at the little reports I generated that compared their performance. I scoured the Internet for more information on high-performance computing, discovered and learned how to use profilers, and continuously tweaked and optimized my code whenever I got the chance. I became a full-blown performance junkie.Now try to imagine my elation at discovering that my lab had a supercomputer at its disposal. My brain just about leapt out of my skull. I attended information sessions on campus about how to use it and the rules to abide by, and pushed its TechOps team into long conversations in person and over email about how it was put together, how the scheduler worked, and how to make the best use of it. Eventually, I was offered administrator powers and duties for the supercomputer, but it was decided that that'd be too much of a distraction from the research I was being paid to do.Around this time, my usual duties were to assist grad students in the AI lab with running their experiments on the supercomputer. I would coordinate with them on the data, the methods, and the results they wanted, write and tweak the C code that made it happen, and obsessively monitored their progress on the supercomputer. I remember watching the status of specific nodes like a vulture and scooping them up for my use the moment they became available. Those were happy times.Throughout this time, I looked in more detail at the "older" languages to see what else I was missing, and learned a great deal about the development of new languages between the 50's and the 80's. I made some cursory investigations into languages like Fortran, Cobol, Algol, Simula, and Ada, but I put enough of a value on practical concerns such as modern-day use and active development that I thought it'd be a better use of my time to continue exploring, i.e. expanding the breadth of my knowledge, in search of interesting things to learn in depth. Those topics tended to be about performance, e.g. assembly code, computer architecture, and distributed computing.I also learned a bit more about modern languages, such as Java and C#, enough to write very basic programs in them. In particular, Ruby struck my fancy as a nifty fusion of Python and Perl. I knew of course that it was abominably slow, but I had the experience to know that I often enough didn't need extreme performance.And so I decided that I would master C and Ruby, using C when performance mattered and Ruby when it didn't, but try to maintain some competence in other languages in case they mattered in ways I didn't understand yet. I ended up paying far more attention to C than to Ruby, and so my Python-fu still prevails over my Ruby and even Perl skills (which have by now heavily deteriorated).At this stage, my thoughts on various programming languages were roughly as follows:Perl: "I've stopped returning its phone calls."Python: "A solid general-purpose language, until extreme performance is necessary."Ruby: "Python, but slicker. Learn more."PHP: "Sounds like Perl for writing web apps. I still don't know much about it, but I'm wary of it."C: "Ugly as sin, but beautifully performant. It doesn't need to look pretty; only the benchmarks do."C++: "Like C, but uglier and more frustrating to work with. Just use C."Java: "It's like C++ got its act together. Accomplishes what C++ was going for much more cleanly, but I don't care much for what C++ was going for, so I don't care about Java. A lot of software companies seem to use it, though, so I might need to be able to use it to get a job."C#: "Microsoft Java. Good to know that it exists, but I still can't bring myself to care."EnlightenmentAs I learned more about the history of computing and the evolution of programming paradigms and languages, I came into contact with some real oddballs. I didn't really know what to make of them at first. Initially, I more or less dismissed them as highly experimental / proof-of-concept / mental masturbation / toy languages. I had a sort of passive academic interest in what on Earth it was they were trying to prove or accomplish, but never put any real priority on finding that out.Then I encountered Lisp. And as anyone who has ever put "lisp" into an online search knows, you can't read about Lisp online without seeing a metric buttload of hipster wankery about the elegance and beauty and perfection of Lisp. Curious as to what all the fuss was about, I decided I wanted to learn some Lisp....and I immediately ran into a brick wall. Anyone who has tried to independently learn Lisp from online sources knows exactly what I'm talking about. It was excruciatingly difficult to find a starting point. I didn't know which incompatible implementation to start with, or whether I should just read the ANSI standard that nobody obeys, and every forum post I read and IRC conversation I started exploded immediately into a flamewar. Questions were answered with questions I didn't know the answer to. I tried following along with some books, but half of them were outdated and the others didn't give enough attention to practical concerns like getting some gorram input or how programs were supposed to be actually run from a shell, which was important to me because I learn best by testing things constantly as I read through learning material.Thankfully, I had by that point seen Scheme mentioned often enough. I downloaded a copy of SICP, got literally the first Scheme implementation that I saw in a Google search (I think it was guile), and got down to business.As I read through SICP, I of course attempted the problem sets with Scheme, but I also tried with imperative languages I knew as well, and it was this that helped me realize the beauty of functional forms, and helped me bridge the gap in my understanding between the realms of programming and mathematics. I recognized the Holy Trinity that is map, filter, and fold as fundamentally important components of virtually every meaningful program I've written. It felt like I was uncovering the primal forces that programs were composed of. It was awe-inspiring how such few and simple mechanics could be composed into arbitrarily complex systems. Complex systems are easier to build, easier to reason about, and are more reliable when assembled by composing simple parts. And so I began to strive for simplicity whenever possible (in my code, anyway).After getting a firm understanding of Scheme, it was easy enough to make the lateral move into Common Lisp. I gradually built up fluency with CLISP and SBCL.Sometime during my quest for enlightenment, a grad student in my lab suggested that I look into Haskell. To put it mildly, it didn't go well. It was too much, too soon for me about purely functional programming. All it did was confuse the heck out of me. Lisp emphasized some critically important functional features, but it still had loops and mutable variables and such. I couldn't comprehend how you were meant to get anything done with a language that lacked these, and I didn't believe that grad student when he told me, excitedly, that I didn't need them and that my code would be better without them (Marco, if you are reading this, I am so, so sorry for ever doubting you on this).While the details now escape me, I remember it was shortly after my failure to learn Haskell that OCaml emerged from the ether and revealed itself to me. And I don't know what it was about it, but OCaml entranced me. I found myself absent-mindedly seeking out more learning material for it, pushing through Project Euler problems just so I could continue writing in it, reading through the source for its standard library, because there was something about OCaml I couldn't quite put my finger on that I just loved. It was through the use of OCaml that I grokked the significance and benefits of immutable data structures and declarative programming in general, and the equivalence of iterative loops and tail recursion.When I finally snapped out of my OCaml trance, I gave Haskell another try, and I took to it like a... weasel to... whatever weasels take very well to. I took to it like I don't take to appropriate similes. It should suffice to say that Haskell and I are now very good friends.In this phase, I ended up learning a little bit of a heck of a lot of other strange languages, because I wanted to see if there were other profound lessons to be learned from them. And that exercise was moderately successful. Probably the most valuable takeaway I got from that was how awesome the Actor model of concurrency is from Erlang (and how I sometimes wish other languages had the same bit pattern matching construct Erlang has, even though it's pretty arcane).At this stage, my thoughts on various programming languages were roughly as follows:Perl, PHP: "Don't speak to me. In fact, stand over there, away from me."Python: "It's a little depressing how much Guido van Rossum has neutered the functional programming features in Python 3. Still a solid language, though, and it's great that it's newbie-friendly."Ruby: "Oh, right, you exist."C++, Java, C#: "Ugh. Writing in these is like filling out paperwork. Kludging in support for lambdas won't save you."OCaml: "Hello, beautiful."Haskell: "Hello, ma'am."F#: "OCaml.NET. Probably my only hope for actually using OCaml in the software industry. At least the CLR means multi-core support for threads."Lisp: "Using you can still be weirdly painful and unnatural for certain tasks, and it'd be great if you were declarative. Also, I can't interact with communities focused on you without wanting to punch neckbeards."The Industrious CostyaBugs suck. They waste time and money, they make you look incompetent, and they undermine customer trust. They are bad for you, your business, your associates, and your customers. The only parties they benefit are your competitors.It is easier to make your programs work reliably when its components act predictably.Practices that let bugs go unnoticed should be avoided and discouraged.With me so far?(Read in your best Hank Hill voice:) Here are some "fun" language "features":Mutable state.Dynamic type systems.Weak type systems.Interpreted languages.These "features" help create and conceal bugs, and are therefore to be avoided and discouraged.I think most people who are aware of my preference for functional languages simply think I'm a hipster, or that I like knowing things that most people find confusing. That may have been true for Early Years Costya and admittedly for Enlightenment Costya, but it's a gross mischaracterization of Industrious Costya. Industrious Costya believes in evangelizing declarative and functional styles of programming, in encouraging their widespread understanding and use, because he well and truly believes it will make the world a better place.Clever hacks and arcane tricks aren't sexy.Predictability and safety are sexy.The "features" listed above offer the developer some convenience, but at the cost of additional responsibility, since permitting them undermines the compiler's ability to detect bugs.Experience has taught Industrious Costya that his brain is not perfect, and that it should not be overburdened with responsibilities that should be the compiler's. Industrious Costya wants to focus on the problem, not on doing the compiler's job for it. Industrious Costya wants to never see a runtime TypeError or NameError in his life.Nonetheless, Industrious Costya understands that he must sometimes suffer one or more of the above "features" to meet business needs (e.g. performance), or when using a library written by some poor Unenlightened sod, or because 95% of developers only know how to write programs that depend on these "features", or to cooperate with a team of developers who apparently love the crap out of fixing bugs or something because they keep using stupid language features that offer some totally negligible convenience at the cost of crashing your program all the gorram time whenever the customers use it. And while Industrious Costya cannot help but wonder if these people are taking this seriously, or if they're masochists or something, he is capable of sucking it up and accepting a paycheck for pretending to be a static type checker. But he will complain a lot.I continue to go after languages that give me practice with paradigms I'm not familiar with, regardless of poisonous unfeatures, because the best practices I've refined over the years are informed by all the lessons I've learned when trying to put new languages to meaningful use. I have used, and forgotten, and re-learned, and re-forgotten more programming languages than I care to count, but the ones that stick with me best are C, Python, and OCaml.My present-day thoughts on various programming languages are roughly as follows:C: "Manual memory management and weak typing are annoying, but C still reigns supreme in the world of high-performance computing."Python: "Interpreted, with dynamic typing. I am so, so sick of NameErrors and TypeErrors. It's still my go-to language for very simple tools, but I'd really like to stop using it professionally."OCaml: "No one loves you like I do. Sure wish you didn't have that GIL, though. And type classes would be nice."F#: "Please don't tell OCaml I've been seeing you."Haskell: "Zygohistomorphic prepromorphism."Perl: "Go away."PHP: "Kill it with fire."C++, Java, C#: "Knowing what I know today, I don't think I'd have the patience to use you for long."Scala: "A little too bureaucratic for my liking, but really cool otherwise. Interop through Scala is pretty much the only way you'll get me to work with Java."JavaScript: "Dynamically and weakly typed, besides clearly having been made by a deranged lunatic. I'll pass."Lisp: "Dynamically typed. Out of touch with reality. Pass."Ruby: "Oh, right, you exist."

In the context of a legal agreement—which is what a term sheet is—a “schedule” is a list of things that are referenced in the agreement. Often, for complex agreements, there are many things that need to be listed. Examples might be:Names and salaries of employeesNames and ownership interests of shareholdersSoftware licensesPatents and intellectual propertyComputers and other owned equipmentLeases the company has signedEtc.Instead of putting all this directly into the agreement, they will instead be listed separately and attached to the end, with the agreement itself just saying something like “the employees as listed in Schedule A”.There is no particular order in which schedules are attached, although it is typically in the order in which they are referenced in the document. And for purposes of clarity, each schedule is numbered (or, more often, lettered, starting with “Schedule A”.)To give you an idea of the kind of schedules you might find in the actual closing documents of an investment (although likely not the term sheet), take a look at this typical due diligence list:A. Organization of the Company1. Describe the corporate or other structure of the legal entities that comprise the Company. Include any helpful diagrams or charts. Provide a list of the officers and directors of the Company and a brief description of their duties.2. Long-form certificate of good standing and articles or certificate of incorporation from Secretary of State or other appropriate official in the Company's jurisdiction of incorporation, listing all documents on file with respect to the Company, and a copy of all documents listed therein.3. Current by-laws of the Company.4. List of all jurisdictions in which the Company is qualified to do business and list of all other jurisdictions in which the Company owns or leases real property or maintains an office and a description of business in each such jurisdiction. Copies of the certificate of authority, good standing certificates and tax status certificates from all jurisdictions in which the Company is qualified to do business.5. All minutes for meetings of the Company's board of directors, board committees and stockholders for the last five years, and all written actions or consents in lieu of meetings thereof.6. List of all subsidiaries and other entities (including partnerships) in which the Company has an equity interest; organizational chart showing ownership of such entities; and any agreements relating to the Company's interest in any such entity.B. Ownership and Control of the Company1. Capitalization of the Company, including all outstanding capital stock, convertible securities, options, warrants and similar instruments.2. List of securityholders of the Company (including option and warrant holders), setting forth class and number of securities held.3. Copies of any voting agreements, stockholder agreements, proxies, transfer restriction agreements, rights of first offer or refusal, preemptive rights, registration agreements or other agreements regarding the ownership or control of the Company.C. Assets and Operations1. Annual financial statements with notes thereto for the past three fiscal years of the Company, and the latest interim financial statements since the end of the last fiscal year and product sales and cost of sales (including royalties) analysis for each product which is part of assets to be sold.2. All current budgets and projections including projections for product sales and cost of sales.3. Any auditors (internal and external) letters and reports to management for the past five years (and management's responses thereto).4. Provide a detailed breakdown of the basis for the allowance for doubtful accounts.5. Inventory valuation, including turnover rates and statistics, gross profit percentages and obsolescence analyses including inventory of each product which is part of assets to be sold.6. Letters to auditors from outside counsel.7. Description of any real estate owned by the Company and copies of related deeds, surveys, title insurance policies (and all documents referred to therein), title opinions, certificates of occupancy, easements, zoning variances, condemnation or eminent domain orders or proceedings, deeds of trust, mortgages and fixture lien filings.8. Schedule of significant fixed assets, owned or used by the Company, including the identification of the person holding title to such assets and any material liens or restrictions on such assets.9. Without duplication from Section D below, or separate intellectual property due diligence checklist, schedule of all intangible assets (including customer lists and goodwill) and proprietary or intellectual properties owned or used in the Company, including a statement as to the entity holding title or right to such assets and any material liens or restrictions on such assets. Include on and off balance sheet items.D. Intellectual PropertyList of all patents, trademarks, tradenames, service marks and copyrights owned or used by the Company, all applications therefor and copies thereof, search reports related thereto and information about any liens or other restrictions and agreements on or related to any of the foregoing (without duplication from attached intellectual property due diligence checklist).E. Reports1. Copies of any studies, appraisals, reports, analyses or memoranda within the last three years relating to the Company (i.e., competition, products, pricing, technological developments, software developments, etc.).2. Current descriptions of the Company that may have been prepared for any purpose, including any brochures used in soliciting or advertising.3. Descriptions of any customer quality awards, plant qualification/certification distinctions, ISO certifications or other awards or certificates viewed by the Company as significant or reflective of superior performance.4. Copies of any analyst or other market reports concerning the Company known to have been issued within the last three years.5. Copies of any studies prepared by the Company regarding the Company's insurance currently in effect and self-insurance program (if any), together with information on the claim and loss experience thereunder.6. Any of the following documents filed by the Company or affiliates of the Company and which contain information concerning the Company: annual reports on SEC Form 10-K; quarterly reports on SEC Form 10-Q; current reports on SEC Form 8-K.F. Compliance with Laws1. Copies of all licenses, permits, certificates, authorizations, registrations, concessions, approvals, exemptions and other operating authorities from all governmental authorities and any applications therefor, and a description of any pending contemplated or threatened changes in the foregoing.2. A description of any pending or threatened proceedings or investigations before any court or any regulatory authority.3. Describe any circumstance where the Company has been or may be accused of violating any law or failing to possess any material license, permit or other authorization. List all citations and notices from governmental or regulatory authorities.4. Schedule of the latest dates of inspection of the Company's facilities by each regulatory authority that has inspected such facilities.5. Description of the potential effect on the Company of any pending or proposed regulatory changes of which the Company is aware.6. Copies of any information requests from, correspondence with, reports of or to, filings with or other material information with respect to any regulatory bodies which regulate a material portion of the Company's business. Limit response to the last five years unless an older document has a continuing impact on the Company.7. Copies of all other studies, surveys, memoranda or other data on regulatory compliance including: spill control, environmental clean-up or environmental preventive or remedial matters, employee safety compliance, import or export licenses, common carrier licenses, problems, potential violations, expenditures, etc.8. State whether any consent is necessary from any governmental authority to embark upon or consummate the proposed transaction.9. Schedule of any significant U.S. import or export restrictions that relate to the Company's operations.10. List of any export, import or customs permits or authorizations, certificates, registrations, concessions, exemptions, etc., that are required in order for the Company to conduct its business and copies of all approvals, etc. granted to the Company that are currently in effect or pending renewal.11. Any correspondence with or complaints from third parties relating to the marketing, sales or promotion practices of the Company.G. Environmental Matters1. A list of facilities or other properties currently or formerly owned, leased, or operated by the Company and its predecessors, if any.2. Reports of environmental audits or site assessments in the possession of the Company, including any Phase I or Phase II assessments or asbestos surveys, relating to any such facilities or properties.3. Copies of any inspection reports prepared by any governmental agency or insurance carrier in connection with environmental or workplace safety and health regulations relating to any such facilities or properties.4. Copies of all environmental and workplace safety and health notices of violations, complaints, consent decrees, and other documents indicating noncompliance with environmental or workplace safety and health laws or regulations, received by the Company from local, state, or federal governmental authorities. If available, include documentation indicating how such situations were resolved.5. Copies of any private party complaints, claims, lawsuits or other documents relating to potential environmental liability of the Company to private parties.6. Listing of underground storage tanks currently or previously present at the properties and facilities listed in response to Item 1 above, copies of permits, licenses or registrations relating to such tanks, and documentation of underground storage tank removals and any associated remediation work.7. Descriptions of any release of hazardous substances or petroleum known by the Company to have occurred at the properties and facilities listed in response to Item 1, if such release has not otherwise been described in the documents provided in response to Items 1-6 above.8. Copies of any information requests, PRP notices, "106 orders," or other notices received by the Company pursuant to CERCLA or similar state or foreign laws relating to liability for hazardous substance releases at off-site facilities.9. Copies of any notices or requests described in Item 8 above, relating to potential liability for hazardous substance releases at any properties or facilities described in response to Item 1.10. Copies of material correspondence or other documents (including any relating to the Company's share of liability) with respect to any matters identified in response to Items 8 and 9.11. Copies of any written analyses conducted by the Company or an outside consultant relating to future environmental activities (i.e., upgrades to control equipment, improvements in waste disposal practices, materials substitution) for which expenditure of funds greater than $10,000 is either certain or reasonably anticipated within the next five years and an estimate of the costs associated with such activities.12. Description of the workplace safety and health programs currently in place for the Company's business, with particular emphasis on chemical handling practices.H. Litigation1. List of all litigation, arbitration and governmental proceedings relating to the Company to which the Company or any of its directors, officers or employees is or has been a party, or which is threatened against any of them, indicating the name of the court, agency or other body before whom pending, date instituted, amount involved, insurance coverage and current status. Also describe any similar matters which were material to the Company and which were adjudicated or settled in the last ten years.2. Information as to any past or present governmental investigation of or proceeding involving the Company or the Company's directors, officers or employees.3. Copies of all attorneys' responses to audit inquiries.4. Copies of any consent decrees, orders (including applicable injunctions) or similar documents to which the Company is a party, and a brief description of the circumstances surrounding such document.5. Copies of all letters of counsel to independent public accountants concerning pending or threatened litigation.6. Any reports or correspondence related to the infringement by the Company or a third party of intellectual property rights.I. Significant Contracts and Commitments1. Contracts relating to any completed (during the past 10 years) or proposed reorganization, acquisition, merger, or purchase or sale of substantial assets (including all agreements relating to the sale, proposed acquisition or disposition of any and all divisions, subsidiaries or businesses) of or with respect to the Company.2. All joint venture and partnership agreements to which the Company is a party.3. All material agreements encumbering real or personal property owned by the Company including mortgages, pledges, security agreements or financing statements.4. Copies of all real property leases relating to the Company (whether the Company is lessor or lessee), and all leasehold title insurance policies (if any).5. Copies of all leases of personal property and fixtures relating to the Company (whether the Company is lessor or lessee), including, without limitation, all equipment rental agreements.6. Guarantees or similar commitments by or on behalf of the Company, other than endorsements for collection in the ordinary course and consistent with past practice.7. Indemnification contracts or arrangements insuring or indemnifying any director, officer, employee or agent against any liability incurred in such capacity.8. Loan agreements, notes, industrial revenue bonds, compensating balance arrangements, lines of credit, lease financing arrangements, installment purchases, etc. relating to the Company or its assets and copies of any security interests or other liens securing such obligations.9. No-default certificates and similar documents delivered to lenders for the last five (or shorter period, if applicable) years evidencing compliance with financing agreements.10. Documentation used internally for the last five years (or shorter time period, if applicable) to monitor compliance with financial covenants contained in financing agreements.11. Any correspondence or documentation for the last five years (or shorter period, if applicable) relating to any defaults or potential defaults under financing agreements.12. Contracts involving cooperation with other companies or restricting competition.13. Contracts relating to other material business relationships, including:a. any current service, operation or maintenance contracts;b. any current contracts with customers;c. any current contracts for the purchase of fixed assets; andd. any franchise, distributor or agency contracts.14. Without duplicating Section D above or the intellectual property due diligence schedule hereto, contracts involving licensing, know-how or technical assistance arrangements including contracts relating to any patent, trademark, service mark and copyright registrations or other proprietary rights used by the Company and any other agreement under which royalties are to be paid or received.15. Description of any circumstances under which the Company may be required to repurchase or repossess assets or properties previously sold.16. Data processing agreements relating to the Company.17. Copies of any contract by which any broker or finder is entitled to a fee for facilitating the proposed transaction or any other transactions involving the Company or its properties or assets.18. Management, service or support agreements relating to the Company, or any power of attorney with respect to any material assets or aspects of the Company.19. List of significant vendor and service providers (if any) who, for whatever reason, expressly decline to do business with the Company.20. Samples of all forms, including purchase orders, invoices, supply agreements, etc.21. Any agreements or arrangements relating to any other transactions between the Company and any director, officer, stockholder or affiliate of the Company (collectively, "Related Persons"), including but not limited to:a. Contracts or understandings between the Company and any Related Person regarding the sharing of assets, liabilities, services, employee benefits, insurance, data processing, third-party consulting, professional services or intellectual property.b. Contracts or understandings between Related Persons and third parties who supply inventory or services through Related Persons to the Company.c. Contracts or understandings between the Company and any Related Person that contemplate favorable pricing or terms to such parties.d. Contracts or understandings between the Company and any Related Person regarding the use of hardware or software.e. Contracts or understandings regarding the maintenance of equipment of any Related Person that is either sold, rented, leased or used by the Company.f. Description of the percentage of business done by the Company with Related Persons.g. Covenants not to compete and confidentiality agreements between the Company and a Related Person.h. List of all accounts receivable, loans and other obligations owing to or by the Company from or to a Related Person, together with any agreements relating thereto.22. Copies of all insurance and indemnity policies and coverages carried by the Company including policies or coverages for products, properties, business risk, casualty and workers compensation. A description of any self-insurance or retro-premium plan or policy, together with the costs thereof for the last five years. A summary of all material claims for the last five years as well as aggregate claims experience data and studies.23. List of any other agreements or group of related agreements with the same party or group of affiliated parties continuing over a period of more than six months from the date or dates thereof, not terminable by the Company on 30 days' notice.24. Copies of all supply agreements relating to the Company and a description of any supply arrangements.25. Copies of all contracts relating to marketing and advertising.26. Copies of all construction agreements and performance guarantees.27. Copies of all secrecy, confidentiality and nondisclosure agreements.28. Copies of all agreements related to the development or acquisition of technology.29. Copies of all agreements outside the ordinary course of business.30. Copies of all warranties offered by the Company with respect to its product or services.31. List of all major contracts or understandings not otherwise previously disclosed under this section, indicating the material terms and parties.32. For any contract listed in this Section I, state whether any party is in default or claimed to be in default.33. For any contract listed in this Section I, state whether the contract requires the consent of any person to assign such contract or collaterally assign such contract to any lender.NOTE: Remember to include all amendments, schedules, exhibits and side letters. Also include brief description of any oral contract listed in this Section I.J. Employees, Benefits and Contracts1. Copies of the Company's employee benefit plans as most recently amended, including all pension, profit sharing, thrift, stock bonus, ESOPs, health and welfare plans (including retiree health), bonus, stock option plans, direct or deferred compensation plans and severance plans, together with the following documents:a. all applicable trust agreements for the foregoing plans;b. copies of all IRS determination letters for the foregoing qualified plans;c. latest IRS forms for the foregoing qualified plans, including all annual reports, schedules and attachments;d. latest copies of all summary plan descriptions, including modifications, for the foregoing plans;e. latest actuarial evaluations with respect to the foregoing defined benefit plans; andf. schedule of fund assets and unfunded liabilities under applicable plans.2. Copies of all employment contracts, consulting agreements, severance agreements, independent contractor agreements, non-disclosure agreements and non-compete agreements relating to any employees of the Company.3. Copies of any collective bargaining agreements and related plans and trusts relating to the Company (if any). Description of labor disputes relating to the Company within the last three years. List of current organizational efforts and projected schedule of future collective bargaining negotiations (if any).4. Copies of all employee handbooks and policy manuals (including affirmative action plans).5. Copies of all OSHA examinations, reports or complaints.6. The results of any formal employee surveys.K. Tax Matters1. Copies of returns for the three prior closed tax years and all open tax years for the Company (including all federal and state consolidated returns) together with a work paper therefor wherein each item is detailed and documented that reconciles net income as specified in the applicable financial statement with taxable income for the related period.2. Audit and revenue agents reports for the Company; audit adjustments proposed by the Internal Revenue Service for any audited tax year of the Company or by any other taxing authority; or protests filed by the Company.3. Settlement documents and correspondence for last six years involving the Company.4. Agreements waiving statute of limitations or extending time involving the Company.5. Description of accrued federal, state and local withholding taxes and FICA for the Company.6. List of all state, local and foreign jurisdictions in which the Company pays taxes or collects sales taxes from its retail customers (specifying which taxes are paid or collected in each jurisdiction).L. Miscellaneous1. Information regarding any material contingent liabilities and material unasserted claims and information regarding any asserted or unasserted violation of any employee safety and environmental laws and any asserted or unasserted pollution clean-up liability.2. List of the ten largest customers and suppliers for each product or service of the Company.3. List of major competitors for each business segment or product line.4. Any plan or arrangement filed or confirmed under the federal bankruptcy laws, if any.5. A list of all officers, directors and stockholders of the Company.6. All annual and interim reports to stockholders and any other communications with securityholders.7. Description of principal banking and credit relationships (excluding payroll matters), including the names of each bank or other financial institution, the nature, limit and current status of any outstanding indebtedness, loan or credit commitment and other financing arrangements.8. Summary and description of all product, property, business risk, employee health, group life and key-man insurance.9. Copies of any UCC or other lien, judgment or suit searches or filings related to the Company in relevant states conducted in the past three years.10. Copies of all filings with the Securities and Exchange Commission, state blue sky authorities or foreign security regulators or exchanges.11. All other information material to the financial condition, businesses, assets, prospects or commercial relations of the Company.