T78 Submission decision tracker
Submission decision tracker

Every candidate Copperline Talent has submitted to Varden Pay for the six open platform engineering roles and not yet answered, with its age against the agreed response window of two business days, so each one gets an answer: advance, decline or question. Maintained by Rafael Delaney, senior recruiter at Copperline Talent, for Anders Sundqvist, head of platform engineering at Varden Pay. Issued Thursday, October 1, 2026, from the record of Monday, September 28. The next decisions are taken at the Thursday hiring sync on October 8.
Sample template: the firm, people, clients and figures are fictional, and the embedded view holds synthetic sample records.
Where the 11 submissions stand
Since September 1, Copperline has sent candidates for six roles: senior site reliability engineer, backend engineer (payments), platform engineer (Kubernetes), security engineer, data platform lead and QA automation engineer. On Monday, September 28, eleven submissions were open. Five were inside the window, four were past it, and two were waiting on a question from Varden that Copperline has to answer.
Live example from the Dashboards app, shown with Varden Pay's demo data. Block dates move forward each week, so they can differ from the sample dates on this page.
The chart below splits the same 11 by what Varden has said so far. Read the middle bar first: those are the submissions where the window has closed and nobody has answered.
Live example from the Dashboards app, shown with Varden Pay's demo data.
| Role | Open | Past the window | Inside the window | Question from Varden |
|---|---|---|---|---|
| Senior site reliability engineer | 2 | 1 | 1 | 0 |
| Backend engineer, payments | 3 | 1 | 2 | 0 |
| Platform engineer, Kubernetes | 2 | 1 | 1 | 0 |
| Security engineer | 2 | 1 | 0 | 1 |
| Data platform lead | 1 | 0 | 0 | 1 |
| QA automation engineer | 1 | 0 | 1 | 0 |
| All roles | 11 | 4 | 5 | 2 |
Response window rules
The rules below were agreed in the hiring plan approved on July 13, 2026. They apply to every submission, whichever recruiter sent it.
Open submissions for Varden Pay
The view lists the 11 open Varden Pay submissions, one row per candidate, all at status Submitted. Read the Next step column first: it says whether a submission is inside the window, how far past it, or waiting on a question, and who has to act. Owner is the Copperline recruiter: Rafael Delaney owns six of the 11 and Beatrix Ferraro owns five.
Before you share this page with a client
This view is already filtered to Varden Pay. The database also holds other clients' records, so keep the embed on a view filtered to the client you share the page with, and never switch it to an all-records view.
Past the window: four submissions
Each row names the reviewer who owes the answer. Ages are business days on Monday, September 28.
| Candidate | Role | Owner | Priority | Wait | Reviewer | What is needed |
|---|---|---|---|---|---|---|
| Tarquin Ellsworth | Senior site reliability engineer | Rafael Delaney | Urgent | Reviewer named Sep 24 | Advance, decline or question before Oct 8 | |
| Casimir Novotny | Backend engineer, payments | Beatrix Ferraro | High | Panel lead | The panel lead's answer; Beatrix Ferraro chases | |
| Ravindra Pillai | Platform engineer, Kubernetes | Rafael Delaney | High | Platform engineering manager | Answer on a role that sat in the shared hiring inbox and is now owned | |
| Florian Hesse | Security engineer | Rafael Delaney | High | Platform engineering manager | Answer on a role that sat in the shared hiring inbox and is now owned |
One candidate has already been lost to the wait
A candidate accepted another offer after 12 days without an answer, so that placement is gone. Tarquin Ellsworth is the oldest open wait at 9 business days, and his submission for the senior site reliability engineer role is marked Urgent. Two of the four late submissions, Ravindra Pillai and Florian Hesse, sat in a shared hiring inbox that no Varden reviewer watched, so nobody owned the answer. Anders Sundqvist has named the platform engineering manager as reviewer for those two roles. Consequence: any further wait on Tarquin Ellsworth risks the same outcome.
One reviewer for each role and one decision slot a week. If a submission has no answer, I want to see how old it is, not find out from the candidate.
From send to answer
This is the path of one submission. The same steps apply to all 11.
sequenceDiagram
participant C as Copperline recruiter
participant R as Varden named reviewer
participant A as Anders Sundqvist
C->>R: Day 0, sends the submission with the role criteria
Note over R: Two business days to answer
alt Advance or decline
R->>C: Day 1 or 2, records the answer
C->>A: Answer shown in the view with its age
else Question
R->>C: Records a question
C->>R: Copperline answers and the clock restarts
else No answer by day 2
C->>R: Reminder on the day the window closes
C->>A: Row marked past the window for the Thursday sync
A->>R: Asks for the answer or a named stand-in
end
Answers needed before the Thursday hiring sync on October 8
- Margit Szabo, security engineer: Copperline answers Varden's question on on-call experience. The record showed it due before Sep 30; if it is still open on Oct 1, answer it today. Owner: Beatrix Ferraro.
- Ezra Lindahl, data platform lead: Copperline answers Varden's question on team size managed. The record showed it due before Sep 30; if it is still open on Oct 1, answer it today. Owner: Rafael Delaney.
- Ottilie Brenner, Ondine Garnier, Jovan Markovic, Anouk Visser and Cosima Frei were inside the window on Sep 28, with answers due Sep 28 and 29. Any still unanswered on Thursday, Oct 1 are now past the window and join the past-the-window table. Owners: Rafael Delaney and Beatrix Ferraro.
Rafael Delaney refreshes the view each Monday before the Thursday sync. Reviewed by
How to use this template
Keep one tracker for each client hiring program. Update the view each week from the submission record, mark every submission past the window with its reviewer, and review the page at the weekly decision slot.
| Variable | Meaning | Required |
|---|---|---|
{{client.name}} | Client organization the submissions were sent to | Required |
{{record.as_of_date}} | Date of the record the ages are counted to | Required |
{{window.business_days}} | Agreed response window in business days | Required |
{{submission.open_rows}} | Open submissions with candidate, role, owner, status and age | Required |
{{submission.past_window_rows}} | Submissions past the window with the named reviewer and the next step | Required |
{{reviewer.name}} | Named client reviewer for each role | Required |
{{sync.next_date}} | Date of the next weekly decision slot | Optional |
If a required value is missing, show Needs review in its place and hold the page; never fill it with a guess. If the submission record cannot be read, show Unavailable instead of the counts and ages.
The live Dashboards blocks on this page show the Varden Pay demo profile. Point each block at your own client's profile, or remove it, before you share the page. Filter the embedded view to the same client as well.