1SecondCopy / People / System 03 of 09
2023Recorded work
Founder
Hiring & paid trials
Review applications consistently, invite selected writers to a paid trial and return their submissions to the same hiring record for a person to assess.
- Noah’s contribution
- Process design, form mapping and reviewer coordination
- Historical stage
- Configured intake and human review; payment intake partial
- Part of the business
- 1SecondCopy overview ↗
- ClickUp
- Typeform
- Make
- Indeed
- Slack
Inside this system
- Workflow
- Key records
- A repeatable process for a writing business
- One intake structure across recruitment channels
- Review gates before spending on a trial
- A trial invitation that preserved the applicant record
- Mapping and maintenance were part of the implementation
- What the historical evidence establishes
- Connected systems
The workflow
How the system
connects.
Follow the main path and its branches. Select a step for context, or switch to the technical map for implementation detail.
- One application form
Recruitment links carry source and location context into the same application structure. - Shared applicant record
ClickUp stores portfolio links, tool experience, rate, availability and review status. - Route by writing role
Rough-draft and final-draft applicants enter different reviewer assignments. - Rough-draft review
The first reviewer checks writing examples, fit, availability and start date. - Final-draft review
Final-draft applicants start with the corresponding senior reviewer. - Second review gate
Selected portfolios pass to a second reviewer before the agency pays for a trial. - Unqualified applicants
Low-rated applicants leave the trial route rather than receiving an automatic invitation. - Request Trial status
The status triggers a personalized invitation confirming the proposed rate and weekly hours. - Paid assignment
The candidate completes the timed assignment and submits through a record-linked form. - Update the same applicant
The form parameter joins the submission to the original record and sets Review Trial. - Notify the hiring channel
The submission alerts the team that the trial is ready for review. - Human trial decision
A reviewer evaluates the work and decides whether to move forward.
Key records
The information
that carries forward.
| Record | Information | Purpose |
|---|---|---|
| Applicant record | ClickUp record ID and application answers | Keep the review history together |
| Trial URL | A parameter identifying the applicant record | Return the submission to the existing applicant |
| Review stage | Reviewed, request trial and review trial | Control invitations and human evaluation handoffs |
Implementation / 01
A repeatable process for a writing business
1SecondCopy needed a way to review writers consistently before investing in a paid assignment and longer onboarding. A portfolio could establish relevant writing experience, but it could not show how a candidate would handle the agency’s actual briefs, tools and time constraints. Noah helped turn that sequence into a shared hiring pipeline: collect the same information, review the work, invite selected applicants to a paid trial, then return the submission to a human reviewer.
The system supported an agency co-founded by Noah and a partner. Noah’s recordings show him changing application settings, explaining the workflow to reviewers, diagnosing form mappings and documenting the trial process. Other team members evaluated portfolios and trial articles. The work therefore combined process design and automation with delegated human judgment; the hiring decision was not an automatic conclusion from form answers.
Implementation / 02
One intake structure across recruitment channels
Job posts directed candidates to an application form rather than leaving information scattered across platform-specific applications. Source, location and country travelled as URL parameters, pre-filling context in the form. The resulting ClickUp record included application answers, portfolio and profile links, tool experience, start date, availability and requested rate. Local-currency input was retained alongside a USD conversion for internal comparison.
One recorded revision corrected posts that had been marked as in-person to remote work and changed the application route to a shared URL. Country-aware form logic adjusted the displayed information. Those were concrete configuration changes; the speaker’s expectations of lower recruitment costs or more applicants were hypotheses, rather than measured results that can be attributed to the automation.
Implementation / 03
Review gates before spending on a trial
The operational guide described a first review followed by a second reviewer before a trial invitation. Reviewers examined actual writing examples, relevant tool familiarity, stated availability and start date. The record moved through reviewed and request-trial stages, with assignments shifting between people. An earlier handoff also asked a reviewer to rate a sample of applicants so Noah could calibrate the ratings before delegating more of the work.
This distinction matters because the process evolved. In the earlier handoff, the automated writing-test email still needed to be built. A later operational guide described request trial sending the email, and the March 2023 walkthrough explained the downstream form and status updates. These recordings document different historical states of a system, rather than one finished implementation present from the beginning.
Implementation / 04
A trial invitation that preserved the applicant record
Moving a selected applicant to request trial triggered a personalized email. It restated the candidate’s proposed hourly rate and weekly availability before linking to the paid assignment. Noah explained that this confirmation addressed cases where people later said they had meant a different rate or fewer available hours. The brief included time constraints and instructions intended to resemble the complexity of ordinary production work.
The trial link carried another URL parameter tying the submission to the existing ClickUp record. That join let the workflow update the same applicant instead of relying on a reviewer to reconcile a separate document or email by name. After the trial form was submitted, the record moved to review trial and the hiring channel was notified. A person still examined the work and determined whether to continue.
Implementation / 05
Mapping and maintenance were part of the implementation
A separate Make troubleshooting recording shows Noah retrieving a recent Typeform response to expose a field that a collaborator could not map. He distinguished the returned response answers from the ClickUp custom-field refresh, and used a lightweight module to inspect the available variable. It is evidence of practical integration debugging, rather than proof that a successful test hire ran through every branch.
Payment-information collection was an adjacent workstream. Noah revised a collaborator’s form to share universal identity fields and branch by payment method and hidden currency context. He also drew the decision flow so collaborators could understand the conditional questions. The recording explicitly left parts of that logic for later configuration. It supports the design of trial-payment intake, but does not establish a completed recipient-creation or payment execution path.
Implementation / 06
What the historical evidence establishes
The recorded process provides identifiable intake fields, review stages, trial-record relationships and team notifications. It also preserves the human decision about whether to continue with an applicant.
The hiring workflow organized applications, paid trials, reviewer decisions and follow-up around a repeatable process.
Within 1SecondCopy
The work around
this system.
Historical project account synthesized from Noah Edis’s experience records and recorded walkthroughs. Public diagrams and descriptions omit private account screens, client records, personnel details and source recordings.