Hiring Pipeline Board for Nextcloud Deck
as a normal Nextcloud Deck board.
A hiring board for small teams without an applicant tracking system. It runs from a written role through screening, interviews, decision, and offer to a reply for every candidate.
Last verified
Board preview
Hiring Pipeline
Sourced1
Write the role before you open it
If you cannot describe what good looks like, you cannot recognise it in an interview.
- List what the person will do in the first 90 days
- Separate the requirements from the nice-to-haves
- Agree the salary range before the first call
- Decide who is on the interview panel
Screening1
Screen against the written criteria
Score against the list you wrote, not against how the conversation felt.
- Use the same screening questions for everyone
- Write the score down before discussing it
- Record the one thing that would change your mind
Interview1
Ask every candidate the same core questions
Comparable answers are the only way to compare candidates fairly.
Decision1
Decide within two days of the last interview
Good candidates have other offers. A slow decision is usually a lost one.
Offer1
Put the whole offer in writing
Salary, start date, working pattern, and probation. Verbal offers create disputes.
Closed1
Reply to everyone, including rejections
Silence after an interview is the thing candidates remember and tell others about.
View the portable v1 template JSON
{
"schema": "deckloud-template-v1",
"schemaVersion": 1,
"slug": "hiring-pipeline-nextcloud-deck",
"locale": "en",
"title": "Hiring Pipeline Board for Nextcloud Deck",
"description": "A pipeline from written role to signed offer, with the same questions for every candidate and a reply for everyone.",
"category": "work-teams",
"tags": [
"hiring",
"recruiting",
"interviews"
],
"quickCreateStackKey": "sourced",
"compatibility": {
"requiresBoardCreate": true,
"includesAttachments": false,
"includesComments": false
},
"board": {
"title": "Hiring Pipeline",
"color": "2563EB"
},
"labels": [
{
"key": "strong",
"title": "Strong",
"color": "10B981"
},
{
"key": "maybe",
"title": "Maybe",
"color": "F59E0B"
},
{
"key": "needs-scheduling",
"title": "Needs Scheduling",
"color": "8B5CF6"
},
{
"key": "rejected",
"title": "Rejected",
"color": "64748B"
}
],
"stacks": [
{
"key": "sourced",
"title": "Sourced",
"order": 1
},
{
"key": "screening",
"title": "Screening",
"order": 2
},
{
"key": "interview",
"title": "Interview",
"order": 3
},
{
"key": "decision",
"title": "Decision",
"order": 4
},
{
"key": "offer",
"title": "Offer",
"order": 5
},
{
"key": "closed",
"title": "Closed",
"order": 6
}
],
"cards": [
{
"stack": "sourced",
"title": "Write the role before you open it",
"description": "If you cannot describe what good looks like, you cannot recognise it in an interview.\n\n- [ ] List what the person will do in the first 90 days\n- [ ] Separate the requirements from the nice-to-haves\n- [ ] Agree the salary range before the first call\n- [ ] Decide who is on the interview panel",
"labels": [
"needs-scheduling"
]
},
{
"stack": "screening",
"title": "Screen against the written criteria",
"description": "Score against the list you wrote, not against how the conversation felt.\n\n- [ ] Use the same screening questions for everyone\n- [ ] Write the score down before discussing it\n- [ ] Record the one thing that would change your mind",
"labels": [
"maybe"
]
},
{
"stack": "interview",
"title": "Ask every candidate the same core questions",
"description": "Comparable answers are the only way to compare candidates fairly.",
"labels": [
"needs-scheduling"
],
"dueOffsetDays": 7
},
{
"stack": "decision",
"title": "Decide within two days of the last interview",
"description": "Good candidates have other offers. A slow decision is usually a lost one.",
"labels": [
"strong",
"maybe"
],
"dueOffsetDays": 2
},
{
"stack": "offer",
"title": "Put the whole offer in writing",
"description": "Salary, start date, working pattern, and probation. Verbal offers create disputes.",
"labels": [
"strong"
]
},
{
"stack": "closed",
"title": "Reply to everyone, including rejections",
"description": "Silence after an interview is the thing candidates remember and tell others about.",
"labels": [
"rejected"
],
"dueOffsetDays": 3
}
]
}
01
When to use this board
For small teams hiring without an applicant tracking system. The board enforces the parts that make hiring fair and fast: the role written down before it opens, the same core questions for every candidate, a decision within two days, and a reply to everyone including rejections.
02
How to run this board
Write the role and criteria before you open it.
Describe what good looks like on the first card, then screen every candidate against that list.
Ask the same core questions.
Use one question set for every interview and decide within two days of the last one.
Offer in writing and reply to everyone.
Put salary, start date, and probation in the offer, and send every other candidate a reply.
03
What this creates
6 stacks, 4 board labels, and 6 starter cards carrying 7 checklist steps. Attachments and comments are intentionally omitted so the template stays portable.
04
Why it fits Deckloud
The template is just a recipe for standard Deck objects. No hosted workflow account, no relay backend, and no Deckloud-only object model.
05
Safe import rules
IDs are not stored. Stack and label keys are remapped at creation time, due dates use relative offsets instead of stale fixed dates, and checklists are written into the card description as ordinary Markdown task lists.
FAQ
Practical questions
Does this change my Nextcloud server schema?
No. It creates ordinary boards, stacks, labels, and cards through the normal Deck model.
Does the template include comments or attachments?
No. V1 templates are text-only because comments imply authorship and attachments vary by server/version.
Can I edit the board after creating it?
Yes. After creation it is just a normal Nextcloud Deck board.
Should candidate names and notes live on this board?
Only if the board has appropriate access control and you have a retention policy. Interview notes are personal data and should not be kept indefinitely.
Why insist on the same questions for everyone?
Comparable answers are the only basis for comparing candidates. Different questions produce impressions, and impressions are where bias enters.
Related
Nextcloud Deck templates, made for real boards.
Free Nextcloud Deck board templates with starter cards and checklists: kanban, GTD, releases, bug triage, incidents, hiring, events, study, and more.
OpenBuild a Nextcloud Deck template without sending server data anywhere.
Build a simple Deckloud template JSON in your browser for a Nextcloud Deck board. No account, no upload, no server credentials.
OpenCreate templates that stay portable.
Create portable Nextcloud Deck board templates with stack keys, label keys, starter cards, and relative due dates.
Open