Contractor Reliability and Notification Policy (DRAFT)
Department & Owner: Operations / People Ops
Latest Update: [Date]
Purpose
This policy sets expectations for Independent Contractors regarding reliability and proactive notification when agreed deliverables or deadlines are at risk. It supports client delivery and contractual compliance. It is outcome- and contract-based; it does not govern attendance, hours, or location in the way employee policies do.
Scope
Intended users
- Operations
- People Ops
- Functional leads responsible for contractor oversight
- Independent Contractors (for awareness of expectations)
When to consult
- When a contractor’s unavailability or impediments may affect agreed deliverables or deadlines
- When defining or enforcing notification and reliability expectations
- When assessing whether a failure to deliver or to notify constitutes a contractual issue
Out of scope
- Employment-style attendance, hours, or location requirements
- Legal interpretation of specific contractor agreements
- Detailed step-by-step escalation (see Policy Non-Compliance Escalation Framework for Independent Contractors)
Definitions
- Reliability: Meeting agreed deliverables and deadlines and communicating proactively when they are at risk.
- Notification: Informing the company as soon as practicable (or per project/contract agreement) when the contractor cannot meet a commitment or will be unavailable in a way that affects delivery.
- Failure to deliver / breach: Missing agreed deliverables or deadlines without timely notification, or repeated failure to meet reliability or notification expectations, in a way that constitutes a material breach under the contract.
Notification Standard
Independent Contractors must notify the company as soon as practicable when:
- They cannot meet an agreed deliverable or deadline, or
- Unavailability (e.g., planned or unplanned absence) will affect delivery.
When a project or contract specifies a notification timeline or method, that agreement governs. Otherwise, notification should be given as soon as the contractor knows delivery is at risk.
Method: Use the designated channel (e.g., Slack, email, or as specified in the project or contract). Notify the direct lead, project manager, or Operations as appropriate to the engagement.
Reliability Standard
Expectations are based on results and deadlines per the contract and project agreement:
- Meet agreed deliverables and deadlines.
- Notify proactively when deliverables or deadlines are at risk.
- Use agreed systems and channels for communication and submission (e.g., timesheets, OOO, status updates).
Failure to deliver or to notify in line with this policy is treated as a contractual and reliability issue, not an attendance or no-show issue.
Consequences
Consequences are framed in terms of contract and engagement, not employment discipline. Escalation for non-compliance with this policy follows the Policy Non-Compliance Escalation Framework (Independent Contractors). Do not use employee-style framing such as “warning,” “write-up,” “suspension,” or “disciplinary action.”
Standard escalation sequence
Escalation under this policy starts at the 2nd occurrence (Written Acknowledgment).
| Occurrence | Action | Documentation |
|---|---|---|
| 2nd | Written acknowledgment — Written summary of the requirement that was not met; contractor must acknowledge and confirm commitment to compliance going forward | Log in tracker + store written exchange |
| 3rd | Compliance review — Live conversation; identify barriers; agree on mitigation; state that continued non-compliance may impact continued engagement | Log in tracker + store internal summary |
Escalation based on project importance and impact
Depending on the importance of the project and the severity or impact of the delay, consequences may escalate more quickly or beyond the standard sequence. Decisions on escalation level, engagement impact, or termination of contract for breach may be elevated to the responsible Executive or Manager (e.g., project lead, functional lead, or leadership as defined for the engagement).
- Engagement impact: Repeated or material failure to meet reliability or notification expectations may be considered in decisions regarding contract renewal, assignment to new projects, and client-facing responsibilities.
- Termination of contract for breach: Material or repeated breach of these expectations may result in termination of the contract for breach, in accordance with the terms of the contractor agreement. Such decisions are made at the appropriate level, up to and including Executive/Manager decision.
Resources
- Operations Manual — Canonical location for this and related policies
- Policy Compliance Tracker — Single source of truth for incidents and escalation
- Policy Non-Compliance Escalation Framework (Independent Contractors) — Standard escalation sequence and documentation
- Contractor agreement and project-specific agreements — Govern notification timelines and methods where specified
Guiding Principles
- Expectations are driven by results and deadlines, not hours or location.
- Notification should be as soon as practicable or per project/contract agreement.
- Consequences are contractual (breach, termination of contract, engagement impact), not employment discipline.
- Documentation and escalation follow the same framework as other Independent Contractor policies.
Responsibilities
| Role | Responsibility |
|---|---|
| Operations Lead | Content owner; policy updates and clarity |
| People Ops Lead | Accuracy and review; alignment with contractor agreements |
| Contractors | Meet reliability and notification standards per contract and this policy |
| Operations / People Ops | Apply escalation framework; log incidents in Policy Compliance Tracker |