Manual audit packet

Manual Titan Map audit packet.

A printable worksheet for running real contractor audits before ServiceTitan API access exists: capture evidence, score mapping coverage, log artifacts, record drift findings, and collect customer signoff.

Produce a defensible before/after audit that shows how the current website maps to ServiceTitan job types, business units, campaigns, service areas, offers, memberships, booking paths, and proof workflows.
Audit packet summary
6
sections
5
artifacts
5
findings
4
required
4
signoffs
7
print checks
No ServiceTitan credentials, tokens, app keys, client secrets, or admin logins are requested for this audit.

Audit sections

Website inventory

required

List every public page, form, CTA, phone number, scheduler embed, campaign page, offer page, and service-area page that affects demand.

Evidence to capture
  • - URL
  • - Page type
  • - Primary CTA
  • - Phone/form/scheduler path
  • - Visible offer or campaign
  • - Owner notes
Scoring questions
  • - Does every important service have a current page?
  • - Are stale or low-priority services still promoted?
  • - Do forms and CTAs preserve source and service context?
Output: Current website inventory with unmapped, stale, duplicate, and missing page flags.

ServiceTitan operating taxonomy

required

Capture the customer-reviewed job types, business units, service areas/zones, campaigns, memberships, and pricebook intent that the site should reflect.

Evidence to capture
  • - Job type
  • - Business unit
  • - Zone or city
  • - Campaign/source
  • - Membership/offer
  • - Active/paused status
Scoring questions
  • - Can each priority page map to an active job type or business unit?
  • - Are served areas clear enough to publish service-area pages?
  • - Are offers, memberships, and campaigns active and approved?
Output: Reviewed taxonomy table that becomes the manual Titan Map source of truth.

Page-to-ServiceTitan bindings

required

Map each launch page or campaign page to the ServiceTitan concepts it depends on, even when that mapping is manual.

Evidence to capture
  • - Page URL
  • - Mapped job type
  • - Business unit
  • - Zone
  • - Campaign/source
  • - Offer/membership
  • - Confidence
Scoring questions
  • - Which pages have complete bindings?
  • - Which pages require customer review before launch?
  • - Which high-value services have no page yet?
Output: Titan Map coverage score and prioritized mapping gap list.

Booking and CTA routing

required

Confirm how each important page should route visitors: phone-first, request form, Scheduling Pro, emergency path, or manual review.

Evidence to capture
  • - Page or service
  • - CTA rule
  • - After-hours rule
  • - Emergency rule
  • - Fallback recipient
  • - Scheduling Pro status
Scoring questions
  • - Is there a safe booking path for every mapped page?
  • - Are emergency and after-hours rules explicit?
  • - Does the fallback work without ServiceTitan access?
Output: Booking-path decision table for launch packet and support handoff.

Drift findings

recommended

Document current mismatch between the public website and the reviewed ServiceTitan operating model.

Evidence to capture
  • - Finding
  • - Affected URL
  • - ServiceTitan object
  • - Severity
  • - Recommended fix
  • - Owner
  • - Due date
Scoring questions
  • - Which pages promote inactive services, paused zones, or expired offers?
  • - Which campaigns lack source bindings?
  • - Which ServiceTitan objects need new or updated pages?
Output: Prioritized drift finding list for the 30-day review and Operations Monitor offer.

Proof and outcome readiness

recommended

Identify which lead, booking, job, campaign, or revenue proof can be reviewed manually without claiming closed-loop API attribution.

Evidence to capture
  • - Available export
  • - Date range
  • - Source owner
  • - Redaction status
  • - Match quality
  • - Excluded records
Scoring questions
  • - Can the customer provide safe aggregate or redacted proof inputs?
  • - Which claims are supported by evidence?
  • - Which revenue or booking claims must remain excluded?
Output: Manual proof plan with match-quality labels and excluded claim list.

Artifact log

Owner: PageToJob

Current website URL inventory

crawl exportspreadsheetmanual URL list
No special redaction unless forms expose customer data.
Used for
  • - website inventory
  • - page bindings
  • - drift findings
Owner: Customer

Job types and business units

CSV exportspreadsheetredacted screenshotscreen-share notes
Remove customer names, addresses, technician notes, and private dispatch data.
Used for
  • - taxonomy
  • - page bindings
  • - coverage score
Owner: Customer

Service areas, zones, ZIPs, and cities

spreadsheetCSV exportredacted map screenshotscreen-share notes
Remove customer addresses, route history, and technician schedules.
Used for
  • - service-area pages
  • - CTA rules
  • - drift findings
Owner: Shared

Campaign/source/UTM reference

spreadsheetMarketing Pro screenshotad platform exportmanual notes
Remove ad account credentials, payment data, and customer-level identifiers.
Used for
  • - campaign pages
  • - source plan
  • - proof readiness
Owner: Customer

Manual outcome or revenue proof

aggregate reportredacted exportscreen-share notes
Remove customer identifiers, invoice notes, payment details, and private job notes.
Used for
  • - proof plan
  • - outcome report
  • - 30-day review

Finding templates

Inactive or low-priority service promoted

high
Affected URLVisible claimReviewed active statusOwner

Recommended fix: Remove, rewrite, or demote the page until the customer approves the service.

Page lacks Titan Map binding

medium
Affected URLMissing job type/business unit/campaignReviewer

Recommended fix: Assign manual binding or mark the page out of launch scope.

Service-area page promotes unsupported zone

high
Affected city/ZIPReviewed zone statusBooking rule

Recommended fix: Change page copy, route to phone-first, or remove from sitemap until approved.

Expired or unapproved offer promoted

medium
Offer URLExpiration/statusApproval owner

Recommended fix: Replace with approved evergreen offer or remove offer CTA.

Unsupported revenue or attribution claim

medium
ClaimSource reportMatch-quality issueExcluded records

Recommended fix: Relabel as demo/supplied/manual proof or remove the claim until evidence exists.

Print checklist

  1. 1. Record customer name, trade, market, reviewer, date, and audit scope.
  2. 2. Inventory public URLs, forms, CTAs, phone paths, scheduler embeds, offers, and campaign pages.
  3. 3. Capture reviewed job types, business units, zones, campaigns, memberships, and pricebook intent.
  4. 4. Assign page bindings and confidence levels.
  5. 5. Document drift findings with severity, owner, recommended fix, and due date.
  6. 6. Log every artifact with redaction status and source owner.
  7. 7. Collect owner, operations, admin, and PageToJob signoff before launch claims are made.

Signoff gates

Owner

Approve the services, areas, offers, and campaigns included in the audit scope.

Evidence: Written scope notes or approved pilot proposal.

If missing: Keep the audit in discovery mode and do not publish operational changes.
Operations

Approve Titan Map bindings, CTA rules, inactive services, paused zones, and drift fixes.

Evidence: Reviewed binding table and drift findings.

If missing: Use conservative phone-first CTAs and label mapping gaps in the launch packet.
ServiceTitan admin

Confirm manual artifacts are enough now and future API authorization can wait.

Evidence: Admin contact, module inventory, and future access notes.

If missing: Run the audit entirely from screen-share notes and public website evidence.
PageToJob

Confirm every stored artifact is redacted, source-labeled, and tied to a specific use.

Evidence: Artifact log with owner, date, redaction status, and use case.

If missing: Do not store the artifact; use screen-share notes instead.

Audit disclaimers

  • - PageToJob is not affiliated with or endorsed by ServiceTitan.
  • - This audit packet does not request or accept ServiceTitan credentials, tokens, app keys, client secrets, or admin logins.
  • - Manual audit artifacts are customer-supplied review inputs, not live ServiceTitan API authorization.
  • - API-backed imports, sync, webhooks, pricebook writes, and closed-loop revenue attribution remain gated until approved app access, customer authorization, scopes, secure storage, and sandbox validation exist.