Download signNow app
4.7 / 5 rating on

Attachment No 2 Non Collusion Certificate Bformb 512

Use a Attachment No 2 Non Collusion Certificate BFormb 512 2013 template to make your document workflow more streamlined.

What this non-collusion certificate does

Attachment No 2 Non Collusion Certificate Bformb 512 is a procurement document used to record a bidder’s certification that its offer was prepared without collusion. It identifies the submitting business and responsible signatory, captures the required declaration, and creates a dated record for the purchasing authority. The exact fields, instructions, and submission requirements come from the solicitation or issuing authority, so users should compare the completed certificate with those materials before signing. signNow can convert the supplied document into a fillable workflow, route it to the authorized signer, and preserve the completed record with an audit trail.

Who uses this certificate

Public procurement

Government procurement offices use the certificate to collect a bidder’s non-collusion representation with the related bid package and signing record.

Bidders and suppliers

Contractors and suppliers complete the certificate when a solicitation, agency instruction, or purchasing policy requires a signed non-collusion statement.

Key features for this certificate

signNow connects the approved certificate, authorized signer, signature event, and retained audit evidence in one controlled workflow.

Fillable workflow

Upload the approved attachment and review detected fields before assigning the authorized bidder signatory.

Signer routing

Route the declaration to the person authorized to certify the bidder’s submission.

Audit trail

Capture signature, date, and transaction events in one completion record.

Access control

Use controlled permissions for procurement staff, signers, and reviewers handling the bid package.

Record export

Export the completed certificate and audit trail for the bid file.

Reusable template

Use templates when the same approved certificate is required across procurement submissions.

Complete the certificate in signNow

Use the issuing authority’s approved attachment and complete each required declaration before routing it to the authorized bidder signatory.

  • Upload certificate:

    Upload the approved certificate PDF.
  • Check fields:

    Review detected fields and add missing entries.
  • Assign signer:

    Assign the authorized bidder signatory.
  • Send document:

    Send the certificate for signature.
  • Store records:

    Download the signed certificate and audit trail.
be ready to get more
Get legally-binding signatures now!
  • Best ROI. Our customers achieve an average 7x ROI within the first six months.
  • Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
  • Intuitive UI and API. Sign and send documents from your apps in minutes.

How the certificate audit trail works

The audit trail connects each Attachment No 2 Non Collusion Certificate Bformb 512 action to a retrievable record of signer activity.

01

Signer authentication:

Records the signer’s email or configured authentication event.
02

Timestamp capture:

Captures the exact date and time of each action.
03

Document hashing:

Associates the signed certificate with document integrity data.
04

Tamper-evident sealing:

Preserves completed pages against later alteration.
05

Event logging:

Logs views, signatures, declines, and completed actions.
06

Audit export:

Allows authorized users to retrieve or export the audit trail.

Recommended certificate workflow setup

Configure the workflow around the solicitation, authorized signer, required authentication, and procurement record schedule.

SettingRecommendation
Authentication and provisioningVerified email with administrator-controlled access
Signature typeTyped or drawn electronic signature
Audit trailEnable completion certificate and event history
Document retentionFollow the issuing authority’s schedule
EncryptionTLS 1.2/1.3 and AES-256 protection

Find and fill out the correct attachment no 2 non collusion certificate bformb 512

airSlate SignNow helps you fill in and sign documents in minutes, error-free. Choose the correct version of the editable PDF form from the list and get started filling it out.

VersionsForm popularityFillable & printable
2013 MD Cumberland Housing Form 512 [2013-04-17] 20164.8 Satisfied (8521 Votes)
2013 MD Cumberland Housing Form 512 [2013-04-17] 20134.8 Satisfied (194 Votes)

Platform requirements for this certificate

Complete Attachment No 2 Non Collusion Certificate Bformb 512 using Chrome, Edge, or Safari on supported desktop operating systems.

  • Desktop browsers Chrome and Edge on Windows 10 or later
  • Apple computers Safari on macOS 12 or later
  • Android devices Chrome on Android 11 or later

For managed procurement workflows, administrators should confirm browser updates, device access, and identity controls before sending this certificate. Configure signNow access through organizational policies when multiple bidders, contractors, or reviewers need a controlled signing process.

Security controls for certificate records

Transport encryption:

Encrypted in transit with TLS 1.2/1.3

Stored encryption:

Encrypted at rest with AES-256

Security certification:

Certified under SOC 2 Type II

Management standard:

Certified under ISO 27001

Signature compliance:

ESIGN and UETA compliant

Health data control:

HIPAA compliant with BAA required

Integrations for procurement records

Connect the signed certificate with procurement, collaboration, and storage tools used to organize bid submissions and supporting records.

Salesforce
Procore
Zapier
Microsoft Teams
Hub spot
Box
Microsoft

Best practices for certificate records

Use the solicitation and the applicable public-records or procurement schedule as the controlling source for handling this certificate.

Match the certificate to the solicitation

Confirm the solicitation identifies Attachment No 2 Non Collusion Certificate Bformb 512 as a required attachment. Compare every field, defined term, signature instruction, and submission condition against the issuing authority’s bid documents before preparing the signNow workflow.

Preserve the signed record and audit trail

Export the completed certificate and its audit trail after every approved signing event. Preserve the original file, final PDF, completion record, and transmission evidence together so reviewers can connect the signer’s declaration with the submitted bid.

Limit access to procurement records

Restrict access to procurement staff, authorized signers, and reviewers with a documented business need. Use role-based permissions and secure archival controls to reduce disclosure of bidder information contained in the attachment.

Follow the governing retention schedule

Apply the retention period required by the purchasing authority, contract, grant, or state records schedule. No universal federal retention period is established here for this certificate, so obtain the applicable rule before deleting records.

Document exclusions and state rules

Notarization rules

May be rejected when required notarization is missing.

Wills excluded

Electronic signing does not replace will formalities.

Family law

Family law decrees remain outside ESIGN coverage.

Real-estate deeds

Deed acceptance depends on state recording requirements.

Troubleshooting certificate workflows

Resolve field, signer, authenticity, and retention questions by checking the solicitation first, then reviewing the signNow transaction record.

Upload the issuing authority’s original Attachment No 2 Non Collusion Certificate Bformb 512 rather than recreating its language. In signNow, review auto-detected fields after upload and add missing signature, date, or required text fields manually before sending.

The Business plan includes templates and audit trails, while Business Premium adds bulk send. For one certificate, prepare the document individually; for repeated procurement packages, verify that the selected plan supports the required sending volume and workflow.

ESIGN and UETA generally recognize electronic signatures when intent, consent, attribution, and record reproducibility are established. Confirm the solicitation and applicable state procurement rules accept electronic execution before relying on an electronic certificate.

Use signNow’s signer authentication options when the purchasing authority requires stronger identity evidence. Email delivery alone may not satisfy a solicitation requiring identity verification, SMS authentication, or another specified control.

The completed certificate and audit trail should be stored together with the bid record. signNow supports audit-trail retrieval and export; apply the issuing authority’s procurement retention schedule because this form has no universal period identified here.

Do not alter the certificate after signing or substitute a different attachment without approval. If the solicitation changes, create a new signNow transaction from the approved source document and retain the earlier record according to the governing procurement schedule.

ROI at a Glance

Key performance indicators that demonstrate SignNow's proven track record.

28M+Documents signed
13+Years in business
4.6/5Average G2 rating

BE READY TO GET MORE

Get this form now!

If you believe that this page should be taken down, please follow our DMCA take-down process.