Ask yourself the difference in the context of FAR Part 44? In the D-B-B world, the government, as the designer of the recordings, is fully responsible for the accuracy, suitability and resulting responsibility for the design of the facility. The government is responsible for maintaining the integrity of design and design through construction and acceptance and beyond. With this responsibility comes the “control” by the ultimate “approval” of the project as well as for many critical construction requests (I will not discuss here who is contractually responsible for compliance with the bid). So there`s a very ingrained sense of “consent” in our organization, even though most people have no idea why, just that “that`s how we`ve always done it.” Is there a contractual meaning between consent and authorization? My dictionary seems to treat them interchangeably: allow – to give consent, approval – to give consent – I think the differences are more than subtle and you see why you want to allow a purchasing system (accept that the system meets certain standards) and “consent”, but not “approve” a subcontract. Think about the possible situation where subcontractors` performance is poor and the government has “approved” outsourcing. So, no – I don`t think “authorization” is synonymous with acceptance, at least as far as design construction is concerned. In the context of FAR Part 44, I don`t think there is any significant difference. Part 44 uses the authorization for the review of procurement systems for contractors and the agreement for the review of subcontracts. The Government Contract Reference Book defines authorization as “the written notification of a contractor to a contractor that the government agrees with proposed conduct” and approval of subcontracting as “the written agreement of the contractor to enter into a given subcontract.” In the D-B world, we hire a designer to employ or set the “Designer of Record”. Thus, the design builder assumes responsibility for DOR contractually and largely related to liability. . . .