Hammertech
Send Evercam images to HammerTech
Turn any Evercam camera image into a HammerTech observation without leaving Evercam. Mark up the image, pick a HammerTech project, fill in the observation details, and send — the marked-up photo is attached automatically, and HammerTech stays your safety system of record.
5 steps: capture → send
Works from: Recordings, Live View, 360°, Drone and Automations
Before you start: connect your HammerTech account once
The connection is set up at the account level. Enter your HammerTech sign-in details along with your tenant and region — after that, HammerTech appears as a destination everywhere you can Send.
Field | What to enter |
|---|---|
Your HammerTech username | |
Password | Your HammerTech password |
Tenant (TNAT) | Your HammerTech tenant identifier |
Region | The region your tenant is hosted in |
You can reconnect or revoke the connection at any time. Access tokens refresh automatically, so you don't need to sign in again for each send.
The walkthrough
Step 1 — Open an image and mark it up
Start from any Evercam surface that offers Send — a recording or live snapshot, a 360° capture, a drone image, or an Automation. When the source is an image, you can annotate it with shapes or text, and crop, redact or resize it before sending.
When the image is ready, click Send in the top-right of the markup workspace.

The Evercam markup workspace on CPAC – Kishoge 1. Annotate, then click Send (top right).
Step 2 — Pick HammerTech from the Send menu
The Send menu lists every destination you've connected. Choose HammerTech. Your other destinations — such as Procore, Aconex, Autodesk or Email — stay available from the same menu.

Select HammerTech from the list of connected destinations.
Step 3 — Select the target HammerTech project
The Send To HammerTech dialog opens on Project Details. Search your connected HammerTech account and choose the project that should own the observation, then click Next.

Step 1 of 2 — search and select the HammerTech project (here, "z Training – Demo Project").
Step 4 — Complete the observation details
Evercam loads the observation types and rules configured in HammerTech for that project. Choose an Observation Type, write a clear description, and set the classification, location, sub type, priority and due date. The Photo for fix required toggle and any project-specific custom fields appear here too.
The fields you see — and which are required — depend on the HammerTech observation type and classification you pick (see Good to know below). When everything looks right, click Send.

Step 2 of 2 — an illustrative observation: Reality Capture – Flagged, Negative, High priority, with a close-out photo required.
Step 5 — What happens on send
Evercam creates a HammerTech observation against the project and observation type you chose, with the marked-up JPEG attached. Files referenced by supported custom fields are uploaded too. From here, HammerTech owns the observation's workflow, close-out and reporting.
The new observation arrives Unassigned — open it in HammerTech to assign the responsible person (see the note below).

The observation as it lands in HammerTech — image attached, details carried over, status Unassigned.
Good to know
Observations arrive unassigned. Evercam can't pull your company's HammerTech user list, so it doesn't set an assignee. Create the observation from Evercam, then assign the responsible person inside HammerTech.
Types bring their own fields. Each observation type can carry custom fields configured in HammerTech — dropdowns, checkboxes, a sub type, and image, file or signature uploads. Evercam shows them in the form automatically.
How classification changes required fields
The classification you choose in Step 4 decides whether a priority and due date are mandatory.
Classification | Priority & due date | What it means |
|---|---|---|
Negative | Required | A resolution is expected — set priority and due date. |
Neutral | Required | Also requires priority and due date. |
Positive | Not required | No resolution needed — the section is hidden. |