Sample Timesheet for Consultants

STANDARD OPERATING PROCEDURE: Consultant Timekeeping and Billing Telemetry Protocol

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the mandatory engineering standards, data schemas, and lifecycle workflows for consultant timekeeping and billing telemetry within Template Registry infrastructure projects. Accurate timekeeping is treated as a critical logging subsystem; unlogged hours represent unrecorded system liabilities, billing leakage, and compliance vulnerabilities.

The purpose of this document is to eliminate ambiguity in hour allocation, ensure immutable audit trails for client invoicing, and enforce deterministic mapping of engineering effort to specific cost centers and Work Breakdown Structure (WBS) codes.

---

2. Scope & Prerequisites

Scope

This procedure applies to all external consultants, independent contractors, professional services vendors, and internal engineering resources billing time against client or internal capital expenditure (CapEx) accounts under Template Registry governance.

Prerequisites & Required Tooling

• Time-Tracking Subsystem: Active account in the enterprise instance of Harvest/Deel/Tempo (Access requested via IT Service Desk ticket REQ-INF-ACCESS).
• Authentication: Multi-Factor Authentication (MFA) enabled via Okta corporate identity provider.
• Project Context: Assigned Work Breakdown Structure (WBS) codes and Jira Epic links provided in the onboarding manifest.
• Hardware: Corporate-provisioned or verified BYOD workstation with TLS 1.3-compliant browser tooling.

---

3. Roles & Responsibilities

• Responsible (R): Executes the time-logging procedure and maintains ledger hygiene.
• Accountable (A): Validates and approves timesheet submissions prior to billing cycles.
• Consulted (C): Provides clarification on WBS mapping and dispute resolution.
• Informed (I): Receives finalized financial telemetry and audit logs.

---

4. Step-by-Step Procedure

Phase 1: Pre-Iteration Setup & WBS Verification

• Log in to the corporate timekeeping portal using SSO credentials.
• Verify active project assignments against the current Statement of Work (SOW) or Jira sprint board.
• Confirm alignment of assigned Work Breakdown Structure (WBS) codes with the following standard schema: [Client-ID]-[Project-Phase]-[WBS-Code] (e.g., TR-PH2-ENG-04).

Phase 2: Real-Time Telemetry Logging (Daily Cadence)

• Log hours accrued on a daily basis; batch entry at the end of a sprint or billing cycle is strictly prohibited.
• Input time entries with a resolution of no less than 0.25 hours (15-minute increments).
• Append descriptive, immutable notes to every time entry using the mandatory format: [Jira-Ticket-ID] - Brief technical summary of architectural or engineering deliverable. (Example: TR-1042 - Refactored Terraform state locking mechanism for multi-region deploy).
• Categorize billable versus non-billable (internal R&D, administrative overhead) flags accurately.

Phase 3: Weekly Reconciliation & Submission

• Review all daily entries for the active work week (Monday 00:00 UTC through Sunday 23:59 UTC).
• Reconcile logged hours against Jira commit logs, pull request timestamps, and calendar invites to ensure structural integrity.
• Submit the timesheet for managerial review no later than Monday at 10:00 UTC following the close of the reporting period.

---

5. Quality Assurance & Pro-Tips

Best Practices (Pro-Tips)

• Granular Telemetry: Avoid vague descriptions such as "Meetings" or "Development." Always link context directly to a ticket, design doc, or repository commit.
• Proactive Blockers: If a WBS code is missing or deactivated mid-sprint, immediately flag the Engagement Manager via Slack channel #ops-billing-alerts rather than guessing a fallback code.

Common Pitfalls

• Late Submissions: Timesheets submitted past the Monday 10:00 UTC hard cutoff are automatically quarantined to the subsequent billing cycle, delaying consultant cash flow by 30 days.
• Orphaned Hours: Logging time against closed Jira epics will trigger an automated parsing exception in the Finance ingestion pipeline.

Metric Thresholds

• Timesheet Compliance Target: $\ge 99.5%$ on-time submission rate per reporting period.
• Description Audit Metric: 100% of entries must contain a valid, resolvable Jira ticket reference.

---

6. Frequently Asked Questions (FAQ)

Q: What should I do if I exceed the weekly cap defined in my SOW?

A: Do not log hours exceeding your contracted cap without explicit written authorization (Change Order or approved Jira Service Desk ticket) from the Engagement Manager. Unauthorized hours are automatically scrubbed by the billing ingestion script.

Q: How do I correct an error in a previously submitted and approved timesheet?

A: Submit a formal correction ticket to Finance Ops (finance-ops@templateregistry.internal) detailing the Date, WBS Code, original hours, and corrected hours. The Engagement Manager must explicitly re-approve the delta adjustment in the portal.