Skip to main content

Three Letters that Cost Government Millions

Federal, state and local governments waste millions or perhaps billions of dollars by making requests for proposals too vague, and hedging their bets with language which forces contractors to pad their estimates in order to reduce the risk of misunderstanding requirements and scope creep.

Just three letters -- "etc" -- account for significant waste.  We often see "etc." added to the end of a long list of requirements as if to protect the writer of the solicitation from an inadvertent omission. Other phrases are sometimes used in place of "etc." such as "including but not limited to."

Bidders have two options in handling ambiguous requests.   One is to bid low, hoping either that the unknown requirements will not be large and sink their project or planning to use change orders to cover the revelation of the unknown with additional funding.  The other option is to bid high, conservatively adding time and dollars to a bid to cover even what has not been revealed.

Neither approach is in the interest of the government customer.   A simple search for "etc" in a solicitation before it is published could save millions in tax dollars.

Popular posts from this blog

The DATA Act Driving Grant Management Automation

The Digital Accountability and Transparency Act enacted in May 2014 calls for making spending data available in open, standardized formats to be published online.  It is a continuation of transparency initiatives and lessons learned with experiences such as grants.gov, the 2009 economic stimulus under the Recovery Act and the spending site USASpending.gov.

Government grantees will have significant new administrative responsibilities.  Many organizations that were tracking grants in spreadsheets or documents will have to adopt more sophisticated automated grant management systems such as Microsoft Grants Manager to keep up with reporting rules.

For profit companies will lose some privacy as a result of this law.  Grant recipients will be required to disclose information including officer salaries.

Continued improvements to publishing grant opportunities such as grants.gov may make it easier to find grants. These reforms together are designed to improve the effectiveness of grant prog…

Dynamics 365 for Government Contractors (GovCon) Frequently Asked Questions (FAQ)

One of InfoStrat's most popular solutions is Dynamics 365 for Government Contractors (GovCon).



Here are some answers to frequently asked question on this solution:
Can I add new fields to the solution?  -- Yes, the solution is fully customizable and you can add your own new fields to any form, view or report.Does Dynamics 365 for GovCon work on mobile devices?  -- Yes, Microsoft offers mobile apps for all the most popular platforms including iPhone, iPad, and Android phone and tablets.Does Dynamics 365 connect with bid data systems such as Deltek and Onvia?  -- Some information services, such as Onvia, offer integration with Dynamics 365.  Others require third party solutions such as the InfoStrat integration with Deltek GovWin IQ.What do customers typically customize for their unique requirements? -- Not all contractors follow the same steps in the capture process.  Most clients will tailor the business process to add or remove steps in order to match their sales methodology.  Of…

Getting the Most from Dynamics CRM Online -- Synchronous v Asynchronous Workflows

This video shows highlights from the InfoStrat March 2015 seminar "Getting the Most Out of Dynamics CRM Online" presented by Dmitri Riz, the leader of the InfoStrat Dynamics CRM practice.  This is the second part of a series of blog posts.  The first is Benefits and Cloud Thinking.



In order to make your CRM workflows perform best, you need to understand the difference between synchronous and asynchronous workflows so you can choose which is appropriate for your applications.



Synchronous workflows are a new feature that was introduced in Dynamics CRM 2013.  Unlike asynchronous workflows which are sent to a queue, synchronous workflows execute in a single transaction. 

This means you can eliminate the need for many plug-ins which were created for previous versions of Dynamics CRM.

You may want to disable synchronous workflows during import operations, because they will could be triggered by each new record and significantly slow down the import process.