Self Employed / HHG
CAREER & BUSINESS
Two routes. One weekly review.
days since 28 August 2026
Tracker snapshot · Monday review at 8am UK
This week at a glance
Employed
End goal: a suitable employed role
The 31 October traction checkpoint has passed. The next evidence gateways are 30 November and 6 December, before the Christmas and January-strategy decision. Applications create opportunities; interviews and a suitable offer show progress. An offer target is not a prediction.
Are inputs producing results?
Last four calendar weeks through the reconciliation cutoff. Each bar shows recorded activity, not an estimate of unlogged activity.
Applications submitted each week
Recorded applications 5 per week target
Recruitment outcomes each week
First screen / interview / offer responses with a date. Later interviews may be missing from the current workbook structure.
Networking target: 2 meaningful actions per week. Actions are counted only when a dated networking or recruiter / agency row is recorded in the master.
Recorded progress towards an offer
No combined completion percentage: submitting more applications does not make a job offer certain.
Inputs
Targets retained: 5 strong applications and 2 meaningful contact actions per week. Networking and recruiter / agency actions are shown separately.
Outcomes recorded
Only explicit screening, interview or offer stages count. Automated receipts do not count as progress.
Application funnel
Cohort: applications submitted in the selected period, with progress recorded by the snapshot. Later stages are included in earlier funnel stages.
What the evidence says
- Check the method when consistent activity produces little interview progress.
- Prioritise strong-fit applications and useful conversations over volume alone.
- Keep submission dates, substantive responses and interview stages current in the employed master; automated receipts remain confirmation only.
The employed master remains private and authoritative; it is not embedded or linked from this read-only summary.
End goal: enough suitable work at a worthwhile rate
Test demand and earnings together at 15, 20 and 25 total working hours a week. Enquiries alone do not establish a sustainable business.
Is there enough work coming through?
New enquiries each week
Completed jobs each week
Last four calendar weeks. Completed work may still await payment. Jobs without completion dates are shown separately, not assigned to a week.
Workload against the three scenarios
Total working time includes visits, messages, travel, loading, purchasing, admin and on-site work. Missing activity hours prevent a reliable utilisation percentage. The 15/20/25-hour scenarios are capacity comparisons, not confirmed demand.
Inputs recorded
Customer-facing actions come only from explicit dated follow-up records. Messenger, offline and other unlogged activity remains unknown, not zero.
Outcomes recorded
Enquiry to paid work
Unique lead IDs in the selected enquiry cohort. Accepted, completed and paid jobs establish earlier quote stages. Potential duplicate leads remain separate pending confirmation.
Project economics
| Project | Status | Received | Known direct costs | All-in hours | Effective / h |
|---|
Effective earnings use received income less known direct job costs across complete working time. Where direct-cost allocation or travel, loading, admin or on-site time is incomplete, the rate remains unavailable.
Lead sources
| Source | Leads | Won | Paid | Won % |
|---|
Won means an accepted job, including completed or invoiced work. Paid means a confirmed receipt. Cash amounts are not used as a proxy for lead quality.
Types of work
| Project type | Leads | Won | Declined |
|---|
Categories inferred from the requested work. Compare customer fit, effort and repeat potential alongside conversion. Mixed jobs may need a category review.
15 / 20 / 25-hour annual comparison
Use an effective rate after direct costs and across all working time. No measured all-in effective rate is available yet, so the comparison remains unavailable until a clearly labelled scenario rate is entered.
| Total working hours / week | 15 hours | 20 hours | 25 hours |
|---|
Annual income at this effective rate
Annual amount = effective hourly rate × total weekly hours × 46 working weeks, less annual overheads. This is an indicator, not a forecast. Compare with an employed gross annual salary at 37.5 hours/week with paid holiday. It is a before-tax income comparison, not a take-home or total-benefits equivalent.
The 46-week assumption allows six non-working weeks; do not deduct holidays a second time. Scenario inputs are temporary and do not change either tracker. No unknown rate, hour or cost is treated as zero.
Missing facts to reconcile
The HHG master remains private and authoritative; it is not embedded or linked from this read-only summary.
Milestones
Decision rules and income bridge
Review each Monday. Judge activity against the weekly targets and outcomes over at least four weeks. Missing records mean “not assessed”, not a red or green verdict.
If activity is sustained but outcomes remain weak, change the method. At the late-November checkpoint, prepare temporary local work as an income bridge if neither main route provides sufficient traction. On 6 December choose the January strategy: employed, business, a combination, or an income bridge alongside the search.
One update, two sources
The Monday review reconciles the employed and HHG masters. This dashboard is generated from those files. There are no activity or outcome fields to maintain here.
Automatic website publishing is not connected. This prepared snapshot must be deployed before it changes career.functionalform.uk. The existing Monday review remains active.
Data and previous reviews
Sources: Employed_Job_Search_Tracker.xlsx and HHG_Business_Tracker.xlsx. Figures are calculated from underlying rows, not cached summary cells. Unknown dates are excluded from dated periods and shown separately. A zero means zero matching records, not proof that no activity occurred.
Older browser reviews are preserved under the original storage key. They are not mixed into tracker totals.