Offense Conduct Sample Clauses

Offense Conduct. The parties stipulate that the following facts are true and correct. The parties recognize that the following facts do not represent the entirety of the government’s evidence against LL. Had the matter proceeded to trial, the United States would have proven the following facts beyond a reasonable doubt: At all times relevant to this matter, LL purchased flooring that contained oak harvested in Far East Russia. Certain LL employees were aware that purchasing oak harvested in Far East Russia posed a significant compliance risk. LL’s internal guidance listed “Russian oak” in the highest category of product risk; certain LL employees possessed NGO and governmental reports documenting illegal harvesting in Far East Russia; and an internal LL training from June 14, 2013, described Far East Russia as an area of high risk. Despite LL’s internal guidance and certain employeesknowledge of the risk associated with Russian oak, LL increased its purchases of Russian oak until around the time of the government’s execution of search warrants at LL’s Virginia offices on September 26, 2013. See Graph of LL Purchases from Russia, Appx. at 1. In the first quarter of 2011, LL imported two purchase orders of flooring made of Russian oak. By the third quarter of 2013, LL was importing nearly 60 purchase orders of Russian oak.
AutoNDA by SimpleDocs
Offense Conduct. The defendant stipulates and agrees that if this case proceeded to trial, the government would prove the following facts beyond a reasonable doubt: Since 2004, defendant Winefield has been licensed by the New Hampshire Real Estate Commission as a "real estate salesperson." During the course of his work in that field, he became acquainted with persons who, since about March 2005, were operating the scheme described in the Information. In or about the fall of 2006, defendant joined in conducting, aiding and abetting the conduct of that scheme, continuing to do so at least until the last transaction conducted as part of the scheme in October 2007. The scheme included two principal phases. First, participants in the scheme identified homeowners in New Hampshire who were having difficulty making their mortgage loan payments, some of whom were in danger of imminent foreclosure. They did so through mass marketing, including bulk mailings sent through the U.S. mails, and telemarketing. Once the scheme participants identified homeowners who were in jeopardy of losing their homes, scheme participants then enticed those homeowners to deed their properties to one of the participants or an entity controlled by them. The participants represented that they would take care of the mortgage payments for the homeowners, while the homeowners "got back on their feet" financially. During that time, the homeowners would remain in their homes as rent-paying tenants of the scheme participants, with the option to buy back the properties after two years at a set price that was substantially higher than the price at which they sold to the participants. Second, following such a sale by a homeowner in financial difficulty, rather than continuing to hold onto the property themselves, the participants engineered a sham sale to a person who agreed to act as a proxy for them, commonly referred to as a "straw" buyer or borrower. Initially, straws used by the participants in the scheme were their relatives and friends. Later the participants advertised in newspapers to obtain straws, whom they termed "investors." Typically, the participants would set a sale price for a sham transaction, and obtain an appraisal in the approximate range of the price. The straws' identities were then used to complete an application for a mortgage loan or a combination of a mortgage loan and a home equity line of credit ("HELOC"). Such a loan or combination loan/HELOC usually totaled close or equal to 100% of th...
Offense Conduct. Pursuant to Guideline Section 1B1.2(d), a conviction on a count charging a conspiracy to commit more than one offense shall be treated as if the defendant had been convicted on a separate count of conspiracy for each offense that the defendant conspired to commit.
Offense Conduct. The defendant stipulates and agrees that if this case proceeded to trial, the government would prove the following facts beyond a reasonable doubt: Xxxxxx Xxxxx, a legal permanent resident of the United States, is the owner of IOSE Limited ("IOSE"), a corporation organized under the laws of the Republic of Ireland, and Xxxxx Property, a nominee entity formed in Belize. From 2005 through 2008, Xxxxx was the beneficial owner of accounts held in the names of XXXX and Xxxxx Property at UBS AG in Switzerland. In each year, those accounts held over $10,000. Hoess deposited lOSE's business receipts into the account at UBS. He periodically transferred a portion of the profit made by XXXX into the Xxxxx Property account. Some of the funds in the Xxxxx Property account were used to pay Xxxxx's personal expenses. From 2005 through 2008, Xxxxx willfully failed to file FBARs with the Treasury reporting his beneficial ownership of the IOSE and Xxxxx Property accounts. Case 1:11-cr-00154-SM Document 44 Filed 11/10/11 Page 3 of 14
Offense Conduct. (1) Count One, Coercion and Enticement of a Child:

Related to Offense Conduct

  • Criminal Convictions Grantee certifies that neither it nor any officer, director, partner or other managerial agent of Grantee has been convicted of a felony under the Xxxxxxxx-Xxxxx Act of 2002, nor a Class 3 or Class 2 felony under Illinois Securities Law of 1953, or that at least five (5) years have passed since the date of the conviction. Grantee further certifies that it is not barred from receiving an Award under 30 ILCS 500/50-10.5, and acknowledges that Grantor shall declare the Agreement void if this certification is false (30 ILCS 500/50-10.5).

  • Serious Misconduct In the case of serious misconduct, or for disqualifying crimes as defined in statutes applied to the licensed provision of home care services, each Employer may in its sole discretion, for reasonable cause, bypass any one or all of the steps of progressive discipline. In the case of any form of discipline less than termination, the employee’s disciplinary action shall include a description of the conduct that is the basis for the disciplinary action(s). Each Employer will strive to identify specific corrective action(s) that the employee is expected to take to improve his/her performance.

  • No Felony Criminal Convictions Contractor represents that neither Contractor nor any of its employees, agents, or representatives, including any subcontractors and employees, agents, or representative of such subcontractors, have been convicted of a felony criminal offense or that if such a conviction has occurred Contractor has fully advised System Agency in writing of the facts and circumstances surrounding the convictions.

  • Business Conduct Merger Sub was formed on December 3, 2020. Since its inception, Merger Sub has not engaged in any activity, other than such actions in connection with (a) its organization and (b) the preparation, negotiation and execution of this Agreement and the Transactions. Merger Sub has no operations, has not generated any revenues and has no liabilities other than those incurred in connection with the foregoing and in association with the Merger as provided in this Agreement.

  • Disorderly Conduct The Contractor shall at all times take all reasonable precautions to prevent any unlawful, riotous or disorderly conduct by or amongst its personnel, and to preserve peace and protection of people and property in the neighbourhood of the Works.

  • Business Conducted Borrower shall continue in the business currently conducted by it using its best efforts to maintain its customers and goodwill. Borrower shall not engage, directly or indirectly, in any line of business substantially different from the business conducted by it immediately before the Closing Date, or engage in business or lines of business which are not reasonably related thereto.

  • Conducts activities regulated by (a) a Board member, or (b) an employee or by the Board member or another employee directing that employee;

  • ETHICAL CONDUCT Seller's employees shall comply with the BorgWarner Supplier Code of Conduct articulated within the BorgWarner Supplier Manual. Compliance with these standards is a mandatory component of Buyer's purchase contracts worldwide and must also apply to Seller subcontractors. Both, the BorgWarner Supplier Code of Conduct and the BorgWarner Supplier Manual are incorporated by reference as part of the Purchase Order, are binding on the Seller, and Seller explicitly verifies to have read and accepted the BorgWarner Supplier Code of Conduct and the BorgWarner Supplier Manual.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Student Conduct Students are required to adhere to School District and College policies, procedures, and regulations regarding facilities and equipment usage and both School District and College codes of student conduct as well as the Alamo Colleges District Student Responsibility for Success Policy. All disciplinary action, including suspension and dismissal from the College, shall be in conformity with the Codes of student conduct of the Parties. All Students will be provided access to the Alamo Colleges District eCatalog, Student Code of Conduct, Student Handbook, and Title IX / Clery Act materials in the same manner as all other students enrolled in the College. For additional information on the College student conduct policies, please refer to the College’s Catalog at xxxxx://xxxxxxxxxxxx.xxxxx.xxx/content.php?catoid=175&navoid=10909. In the event of a conflict between the policies of School District and College, the Parties will collaborate to resolve any conflict. The School District and the College will inform one another of complaints against a Student. The party which receives a complaint of non-academic misconduct may investigate the complaint and reach a decision on responsibility for violations of the applicable student code of conduct, but must notify the other party of sanctions before they are issued. Students who are in violation of policies and codes of conduct will, where appropriate, return to the School District’s high school, if any, and will not be allowed to return to any College facility. The Parties will cooperate fully with each other in any investigation involving student misconduct or conduct that threatens or potentially threatens the safety of others and the college campus. The Parties will cooperate fully with each other as necessary in all matters pertaining to complaints, grievances and appeals regarding student conduct issues. The definition of “cooperation” includes providing access to students or other persons who may be witnesses or persons with knowledge of relevant facts. Students may be sanctioned the same as other post-secondary College students and may be subject to exclusion from the College campus and College properties. The Alamo Colleges District board policy F.4.5 states that Students who violate federal or state statutes, the Student Code of Conduct, Alamo Colleges District policy, or other applicable requirements related to alcohol and drug use shall be subject to appropriate disciplinary action. Such disciplinary action may include referral to drug and alcohol counseling or rehabilitation programs or student assistance programs, suspension, expulsion, and referral to appropriate law enforcement officials for prosecution.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!