Mid-Year Individual Subcontract Reports

This is a quick reminder for Federal contractors holding a contract that includes a subcontracting plan.  This month the mid-year Individual Subcontract Reports (ISRs) are due for large businesses.  As with previous reports, ISRs are submitted via the Electronic Subcontract Reporting System (eSRS).  You can refer to another article I posted on May 21st 2013, highlighting Small Business Utilization Monitoring and Reporting requirements.

Quick Tips:

  • The ISR reporting period is 1 October 2013 – 31 March 2014 and the project team (or group responsible for managing reporting) should have collected and categorized all of the subcontract awards.
  • Collect and organize all of the subcontract award data (business name, award date, and amount) made during the period sorting by business type, OTSB, WOSB, SDVOSB, etc.  This can be accomplished using Excel, Access, some contract / project management databases, or paper and pencil.
  • Ensure the required self-certification forms, 8(a), and HUBZone certifications are collected and reviewed for accuracy.  Self-certifications are acceptable for: Small Businesses, Small Disadvantaged Businesses, Woman Owned Small Businesses, Veteran Owned Small Businesses, and Service Disabled Veteran Owned Small Businesses.
  • Ensure the correct subcontracting plan goals are entered into the ISR being submitted.
  • Enter the required data in the eSRS ISR reporting tool.  There are several useful step by step guides with detailed instructions (http://www.esrs.gov/).  Of note the ISR tool will calculate the participation rate percentages for you, although I prefer to calculate the small business (SB) participation rates prior to beginning the process.
  • If required, enter an appropriate remark explaining why goals have not been met.  Regardless if the goals are or are not being met, the team buying out the subcontracts should keep detailed notes on the bidding for each bid package.  This is very valuable information to use for remarks in the ISR in addition to any future contract work in the same region.
  • Even if a contractor did not have any subcontracting activity during the reporting period they are still required to submit a report.  See eSRS FAQs for details.

Summary:

  • Don’t procrastinate starting the reporting process and make sure time is left to review the data for accuracy and completeness.
  • If you have delegated the responsibility for data entry of the ISR, make sure you review the material before it is submitted.  Any errors will find their way back to you.
  • Mid-year Summary Subcontract Reports are not required any longer for DoD.

 

Advertisements

Federal Small Business Reporting

tech-ind

Overview

This month Other Than Small Business (OTSB) {also known as a large business (LB)} contractors and subcontractors (those holding a contract or subcontract in excess of $650,000 or $1,500,000 for construction) are required to submit their Individual Subcontract Reports (ISR) and Summary Subcontract Reports (SSR) via the Electronic Subcontract Reporting System (eSRS). For some construction projects this can be a time consuming event given the large number of subcontractors.  My typical client has 30 to 90 subcontractors depending on the size of the project.  On May 21st I authored a piece highlighting Small Business Utilization Monitoring and Reporting requirements.  This post calls into action the tips and techniques covered in that post as 30 September 2013 marked the end of the most recent reporting period.  The ISRs and SSRs are due within 30 days of that date.

Individual Subcontract Plan Reporting

The ISR reporting period is 1 April – 30 September and the project team (or group responsible for managing reporting) should have collected and categorized all of the subcontract awards related to the contract.  It is beneficial to start the reporting process early so it can be broken down into several discreet steps creating a more manageable process reducing interference with regular tasks the project team completes on a daily or weekly basis.  Below is an overview of the basic steps for those reporting on small business to complete:

  • Collect and organize all of the subcontract award data (i.e. business name, award date, and amount) made during the period sorting by business type, OTSB, WOSB, SDVOSB, etc.  This can be accomplished using Excel, Access, certain contract / project management databases, or paper and pencil.
  • Ensure the required self-certifications and HUBZone certifications are collected and reviewed for accuracy.
  • Ensure the correct subcontracting plan goals are entered for the ISR to be submitted.
  • Enter the required data in the eSRS ISR reporting tool.  There are several useful step by step guides with detailed instructions on the eSRS site.  Of note the ISR tool will calculate the participation rate percentages for you, although I prefer to calculate the small business (SB) participation rates prior to beginning the process.
  • If required, enter an appropriate remark explaining why goals have not been met.  Regardless if the goals are or are not being met, the team buying out the subcontracts should keep detailed notes on the bidding for each bid package.  This is very valuable information to use for remarks in the ISR in addition to any future contract work in the same region.

Summary Subcontract Reporting

There are a few differences between the ISR and the SSR in addition to a couple of tips that are worth noting.

  • The SSR is a fiscal year summary of Federal subcontracting activity reported by agency.  The more contracts and agencies a company works with the more complex the process becomes.  A common mistake I see is firms incorrectly totaling all of the ISRs for a particular agency and reporting that number.  ISRs are reports documenting subcontracting activity for the life of a contract.  Using the ISR in this manner will inflate the data in the SSR.
  • SSRs are reported at the agency level which creates one or more confusing aspects of submitting the SSR of “who”  or “where” to send it to from the range of choices available on the drop down menu.  The good thing is most agency personnel are very good at directing reports to the correct destination.
  • Similar to the ISR, there are several guides available on the eSRS site containing detailed instructions.  I recommend using the guides as they are helpful.

DoD Office of Small Business Programs (OSBP) recently updated is policy on SSRs and the Small Disadvantaged Business (SDB) participation report.  Highlights from the notice distributed several weeks ago are included below:

  • Starting in FY 2014 the SSR submission will be submitted once per year matching civilian agency requirements.
  • For FY 2013 reporting, contractors submit their consolidated SSR in eSRS to the Department of Defense (9700) and NOT to the department/agency which administers the majority of their subcontract plans.
  • For FY 2013 contractors should not submit the SDB participation report as they are no longer authorized since 10 U.S.C. 2323 expired.  For further guidance go to: http://www.acq.osd.mil/osbp/sbs/esrs.shtml

Summary:

  • Don’t procrastinate starting the reporting process and make sure time is left to review the data for accuracy and completeness.
  • If you have delegated the responsibility for data entry of the ISR, make sure you review the material before it is submitted.  Any errors will find their way back to you.
  • CEO or Senior VPs are required to sign the SSR, make sure they know the report is being submitted and they are briefed on the contents of the report.  Too often I have seen an electronic signature from the reporting authority used and not back-briefed on the event.

The Value of Developing a Federal Acquisition Regulation (FAR) Matrix Review During Proposal Development

Eagle with flag

Overview

Maintaining a proactive compliance stance in federal contracting is a tedious task requiring constant diligence and regular reviews.  Administrative reporting requirements and critically important performance requirements are sprinkled throughout the typical federal Request for Proposal (RFP).  Therefore, a key step in the proposal process is conducting a complete review of the FAR clauses in the proposal to set the stage for an active contract management and contract compliance stance.  There are numerous items for the home office and project teams to track.  For example, reporting requirements for subcontracts (which are reported on three separate occasions in many instances), small business reporting, improper business practices, annual representation and certification, I-9 verification requirements, cost & pricing certification requirements, and prompt payment issues (withholding procedures).  A detailed review provides several benefits highlighted below in addition to highlighting the previously mentioned requirements.

Benefits

  1. The overall benefit is it establishes the right mindset for a strong compliance program which reduces friction and interference from the contracting office.  Not only are there contractual requirements for completing certain reports, every contractor is required to annually assert they have complied with Previous Contracts and Compliance Reports as stipulated in clause 52.222-22.  Not doing so could expose a firm to problems associated with making a false statement.
  2. It provides an objective estimation of the level of effort the project team and corporate staff will incur as a result of a successful offer (the amount of required reporting increases with the size and complexity of the project).
  3. A review conducted during the proposal stage allows contractors to communicate with the procuring agency to eliminate errant clauses included in the RFP.
  4. Helps identity mandatory versus recommended FAR clauses for flowdown.
  5. Highlights actions required to comply with the various requirements.

Solutions

There are two solutions (actually there are three if you count doing nothing as an option) to conducting a FAR clause review and documenting the outcome.

  • One option is to build a FAR matrix manually using Excel, Word, or another software tool.  This option is the most time intensive since it involves reviewing the RFP, recording the clauses included in the contract, and briefly outlining each clause, its applicability, required reporting, flowdown requirements (mandatory or recommended), and other information your organization deems relevant.  When I used this method several years ago I slowly built a master file of clauses typically found in RFPs based on the procurement to help save time and effort.  An example is included below:

Article 12 FM Image

  • A second option is to use an automated tool that stores and updates all of the FAR and DFAR clauses for you.  Then all that is left is for your compliance team to do is review the RFP, select the clauses from the electronic list of clauses, and print the results.  I have found this option reduces the level of effort substantially.  An automated tool is not free of course, but it quickly makes up for itself in time saved.  Currently, I use a system designed by Wolters Kluwer (I am not affiliated with Wolters Kluwer and this is not a paid endorsement), and included a snapshot below:

Article 12 WK Image

Regardless of the option you select, either method will drive the compliance team to conduct a detailed review of the RFP developing a clear understanding of the contractual requirements upon award.  Also, it provides decision makers with the information needed to staff the project appropriately, identify any required training for the project team, subcontractors, or consultants, and ensure the company is complying with all applicable regulations.

Small Business Utilization Monitoring and Reporting

In previous posts about small business subcontracting I have discussed activities along the small business planning continuum ranging from outreach efforts to putting a subcontracting plan in to action.  After project award the real work of a small business subcontract plan begins and this activity must be documented semi-annually in the Electronic Subcontract Reporting System (eSRS).  This series ends with an article addressing the monitoring and reporting requirements associated with a typical federal construction project.

Monitoring

Typically the Subcontracting Plan is administered by the Administrative Contracting Officer (ACO) for the government and the Small Business Liaison Officer (SBLO) for the prime contractor.  The ACO is responsible for monitoring, evaluating, and documenting contractor performance on behalf of the award agency.  Therefore, establishing an adequate program to monitor your small business program is important so the program is effectively and efficiently run.  Ultimately the success of a company’s small business program is an integral part of a firm’s business development efforts.  Failure to meet small business goals on federal projects can reflect negatively when responding to future proposals.

Feature of an adequate program:

  • Your company has a published policy letter from the Chief Executive Officer supporting the program.
  • The SBLO maintains documentation of meetings with top management on the status of the program.
  • The SBLO reports directly to senior leadership and depicted on the company organizational chart.
  • The small business policies and procedures are published and distributed to project teams.
  • Individuals directly involved with the program have received training on the small business program and the federal requirements.
  • Self-certification are reviewed, tracked to ISRs and SSRs, and retained for compliance reviews.
  • HUBZone Small Business certifications are verified through the SBA (FAR 52.219-8(d)(2).

Reporting

eSRS Home Page

Reporting small business utilization on federal projects is one of several post-award compliance tasks for large businesses (FAR 52.219-9(d)(10)(iii)).  Reporting is accomplished via eSRS.  Two types of reports are required, the Summary Subcontract Report (SSR) and the Individual Subcontract Report (ISR).

The SSRs collects prime and subcontractors award data for a specific agency during the given fiscal year.  Reporting periods:

For Department of Defense (DoD) and NASA:

  • 1 October – 31 March
  • 1 October – 30 September

For Non DoD agencies:

  • 1 October – 30 September

Reports are due 30 days after the reporting period ends.

The ISR collects prime contractor and subcontractor award data on a project basis over the life of the project.  Unlike SSRs the data carries over each year.  Reporting periods:

  • 1 October – 31 March
  • 1 October – 30 September

Reports are due 30 days after the reporting period ends.

Two common techniques to monitor participation include the use of the spreadsheets or a contract management database program.  Either technique is acceptable; the method used is dependent on which is most compatible with the IT maturity of the firm.  Related to my post on 30 January 2013 “Small Business Outreach and Database Management”, the level of effort in fulfilling the reporting requirements is affected by the capabilities, or lack of, with your contract management or small business utilization tracking tool (spreadsheets).

Reporting Tips:

  • A database can reduce the level of effort to complete the reporting requirements.  For example, Primavera Contract Manager and Prolog can both be modified at the company level to facilitate the reporting process.
  • Develop a consistent methodology to help project teams collect, document, and store self-certifications.  Per 13 CFR 121.411(a), a subcontractor must qualify and self-certify as a small business at the time it submits its offer as a small business subcontractor. Do not retroactively apply small business subcontracting accomplishments. (eSRS Quick Reference Guide)
  • Visit the eSRS website, there are numerous guides, step-by-step samples, and instructional videos to assist with the reporting process.
  • Don’t wait until the last minute to start the reporting process.
  • Throughout the reporting period make sure the project team is collecting information on subcontract awards, self-certifications, and the bid history for each subcontract to document good faith efforts.
  • Review self-certification against System for Award Management (SAM) or the SBA Dynamic Small Business Search (DSBS).  Occasionally small businesses will inadvertently check the incorrect subcategory or miss one entirely.  The effort in due diligence will help the large business and the small business.
  • Under current regulations a self-certification form must be collected for each small business for each project. (SBA SBLO Handbook)

Common trends I find during subcontracting programs reviews for clients:

  • Self-certifications are completed incorrectly resulting in missed or inaccurate small business credit for the prime contractor.
  • The tracking tool used has math errors or small businesses are not categorized according to their self-certification.
  • Summary Subcontract Reports (SSRs) contain more than one fiscal year of data.
  • ISRs are not submitted in a timely manner.
  • ISRs contain insufficient information documenting good faith efforts and are rejected by the Contracting Officer or ACO.