State
Every project has a defined current condition rather than a vague label such as in progress.
Operating System // Web Production
Move website work through controlled states.
The Raptor Web Production System defines how a request enters production, who owns it, what must be checked, when it can move forward, and what evidence is required before closure.
RAPTOR // PRODUCTION STATECONTROLLED
CURRENT STATE05 // QUALITY CONTROL TWOCorrections verified. Technical setup under review.
OWNERAssigned
GATEOpen
DEPENDENCIESClear
EVIDENCEPending
NEXT TRANSITIONClient Review // requires QC approval
SYSTEM RULEA project moves when the gate is satisfied, not when the calendar becomes uncomfortable.
Purpose // Why the System Exists
Replace memory and urgency with visible control.
Production failures often begin before the build. Missing access, unclear ownership, undocumented instructions, hidden dependencies, and rushed review create problems that surface at launch. The system makes those conditions visible early.
Owner
Responsibility for the current task and next transition is explicit.
Gate
Required checks must pass before work advances into the next state.
Evidence
Completion is supported by inspection, records, or live verification.
Lifecycle // Eight Controlled States
From intake through verified production.
The stages create a common operating language. A project can pause, return for correction, or enter exception handling, but it should never lose its state, owner, or next required gate.
01INTAKE
Intake and Context
Record the request, business purpose, priority, scope, special instructions, and acceptance conditions.
GATE // Request is complete enough to assess.02DEPENDENCIES
Access and Dependencies
Confirm domains, hosting, platform access, content, assets, integrations, and external dependencies.
GATE // Required inputs and blockers are visible.03ASSIGNMENT
Production Assignment
Assign ownership, define the current state, and move approved requirements into implementation.
GATE // Owner accepts the production brief.04QC ROUND ONE
Quality Control One
Inspect structure, content, responsive behavior, functionality, and adherence to the production brief.
GATE // Defects are recorded and routed.05QC ROUND TWO
Quality Control Two
Recheck corrections, technical setup, special instructions, and readiness for client review.
GATE // Corrections pass independent reinspection.06REVIEW
Client Review
Collect decisions and revisions without allowing feedback to become untracked production work.
GATE // Approval or defined revisions recorded.07DEPLOYMENT
Launch Control
Coordinate DNS, deployment, redirects, analytics, tag management, sitemaps, and search connections.
GATE // Launch checklist completed.08VERIFICATION
Post-Launch Verification
Inspect the live site, confirm tracking and search access, record issues, and close only after evidence exists.
GATE // Live result verified and documented.Quality Control // Two Different Questions
The second review should not repeat the first.
Quality Control One identifies defects and deviations. Quality Control Two verifies the corrections and tests whether the site is ready to enter client review.
Separating the rounds prevents a correction list from being mistaken for proof that the work was corrected.
QC // 01
Inspect the buildStructure, content, mobile behavior, functions, links, instructions, and visible defects.
↓ CORRECT AND RECORD
QC // 02
Verify the correctionsReproduce prior issues, inspect technical setup, and confirm client-review readiness.
OUTPUTApproved for review or returned with evidence.
Exception Handling // Keep the State Honest
Blocked work needs a controlled route.
A dependency failure, infrastructure outage, missing client decision, or urgent request should change the production record. It should not disappear into messages or remain falsely marked in progress.
01
Identify the exceptionName the blocker, affected work, and operating consequence.
02
Change the stateMark the project blocked, escalated, or returned for input.
03
Assign the responseSet the owner, required action, and decision deadline.
04
Re-enter through a gateResume only when the missing requirement is verified.
Applied Evidence // Production at Volume
The method grew from real delivery pressure.
The system reflects prior operating experience coordinating higher-touch and special-project work inside a broader environment that could move roughly 30 websites per week during urgency periods.
That figure describes the broader production environment, not an individual output claim or a current Raptor throughput guarantee.
CONTEXTHigh-volume agency production
DIRECT ROLEHigher-touch projects, escalation, and QC support
CONTROLTwo review rounds plus client approval
EVIDENCE CLASSPrior operating experience
Raptor // Control the Work
Need a production process your team can actually inspect?
Call or email Raptor directly. We can start with the current workflow, failure points, ownership gaps, and the gates needed to move work safely.