sift
Sign inStart free
engineering

Deployment Request

Deployment requests arrive as Slack messages, emails, or PR descriptions with varying detail. This template captures the service and version being deployed, target environment, required dependencies, pre-deployment checks, deployment window, and whether required approvals are in place, standardising your release process.

See it in action

What users type

Ready to push extraction-service v2.14.0 (commit abc8f3e) to production. This includes the batch processing optimisation and the new confidence scoring model. Depends on the ML model registry update that Kai deployed yesterday to staging (model-registry v1.8.2 needs to be in prod first). Staging tests all green. I got sign-off from Jenn (engineering lead) and Priya (product). Planning to deploy during low-traffic window tonight between 11pm and midnight PT. Requested by Amir Hassan.

What you get

Requester

Amir Hassan

99%
Service Name

extraction-service

99%
Version / Commit

v2.14.0 (abc8f3e)

99%
Target Environment

Production

99%
Dependencies

model-registry v1.8.2 must be deployed to production first (currently in staging)

95%
Deployment Window

Tonight 11:00pm - 12:00am PT

97%
Approval Obtained

Yes

96%

Extracted fields

FieldTypeRequired
RequestertextRequired
Service NametextRequired
Version / CommittextRequired
Target EnvironmentselectRequired
DependenciestextOptional
Deployment WindowtextRequired
Approval ObtainedbooleanRequired

Use this template

Sign up and select “Deployment Request” from the template gallery. Customise any field before going live.

Start with this template — free

Related