City Club Group · Shift Report

Where the build stands

Sunday 22 November 2026. Staff can sign in, administrators keep accounts and permissions, and a report can be made, listed, resumed and read. Now: staff pickers, comments, autosave and the offline state, the third of the report renderer's four stages. Four milestones and the first deploy follow.

2 of 7milestones built
9 of 26stages built
18small steps done

The road, in build order

builtin handto build

Seven milestones, the large stops in the shaded boxes, with the small steps done around them.

M1
MilestoneA large piece of the product, such as user management. It takes its number (M1, M2, M3) when it starts.
StageOne part of a milestone, a square in its shaded box. Each stage ends on the test site, ready to be tried.
Small stepOne narrow job outside the milestones: groundwork, a spec, a mend or a tool (S0, S1, and so on).
  1. 15 Nov
    Small steps
    Groundwork
    4 small steps
    S0 to S3: the skeleton, 39 shared pieces, HTTPS
  2. 15 to 16 Nov
    Small steps
    The specs
    5 small steps
    S4 to S8: every milestone specified and approved
  3. M1
    15 to 18 Nov
    Milestone
    User management
    5 of 5 stages
    v0.1.0 · sign-in, accounts, audit log
  4. M2
    17 to 18 Nov
    Milestone
    Permissions
    2 of 2 stages
    v0.2.0 · the matrix, impersonation
  5. 19 to 22 Nov
    Small steps
    Mends and tools
    9 small steps
    S9 to S17 · up to v0.2.3
  6. You are hereStage C of the report renderer
    M3
    Now
    Milestone
    Report renderer
    2 of 4 stages
    Stage C in hand
  7. Next
    Milestone
    Collaboration and submission
    4 stages
    several people finish and submit a report
  8. Later
    Milestone
    Template builder
    4 stages
    administrators change the report themselves
  9. Later
    Milestone
    Follow-ups and the gallery
    3 stages
    what a shift raises is tracked to its end
  10. Last
    Milestone
    Mail, settings, last screens
    4 stages
    word sent off the site; every screen in place
  11. Waits on hosting
    Small step
    First deploy
    1 small step
    placed when the hosting is settled

Built

Merged into main; the local site runs 0.2.3 with Reports home

  • Groundwork and five approved specs

    15 to 16 Nov

    The walking skeleton, the design's 39 shared pieces, the local site over HTTPS, and a spec for every milestone to come.

  • User management

    15 to 18 Nov

    M1, five stages. Sign-in by password or a daily PIN on an enrolled device; accounts, roles and venues; a second factor; the audit log and its export.

  • Permissions

    17 to 18 Nov

    M2, two stages. Seven permissions a role, checked by the server on every request, and an Administrator viewing the app as another user.

  • Mends and tools

    19 to 22 Nov

    Nine small steps: a session's ID stays dead after Sign Out, wording, a page that showed sign-in by mistake, faster and steadier checks.

  • A report from the template

    21 Nov

    M3 Stage A. A report made from the baseline template, shown and saved on a desktop and a phone, with a count of what is left to fill in.

  • Reports home

    22 Nov

    M3 Stage B, accepted by you. The list with a filter and search, the card to resume a draft, "+ New Shift Report" and a read-only view.

  • Hidden fields are refused

    22 Nov

    The server refuses a change to a field the report is hiding and keeps its value; the page orders each save so nothing a person can see is refused.

Happening now

M3 Stage C, people and words

  • 10 of 16 pieces merged

    2 with their agents
    Contract
    1 2
    Backend
    1 2 3 4
    Web
    1 2 3 4 5 4b
    The join
    Join 1 Join 2 Review Gate, local site
  • What the stage gives

    Staff pickers: typing filters by name or role, with a "listed as management" switch a role carries.

    Comments: added to a field and listed oldest first.

    Autosave and offline: a chip says "Saving…" while a save is in flight; when a save cannot reach the server the report says so and keeps the work.

    A session that ends with a report open returns the person to their work after sign-in.

  • With their agents

    Backend 4: the device's word, and people and comments in the seed's 24 sample reports.

    Web 4b: the browser's form of what a device keeps while offline.

  • For your eyeWhat a device keeps needs the browser's storage, and the project's own check refuses any web file that names it. Web 4b narrows the check for that one file, on a merge that can be taken back alone (B-601). It is the first of this stage's decisions made for you to review.

Coming up

The rest of M3, then four milestones

  • Stage C joined

    about 23 Nov

    Two join briefs, the stage's review with planted faults and the full gate. Then it goes to the local site and the work stops for you to try it.

  • Stage D, photos

    about 24 Nov

    Photos added to a report: upload, re-encoding, captions and the venue's logo. Its check and cut are in the plan, from the draft you approved.

  • The shift types' screen

    about 25 Nov

    Where an administrator keeps the shift types. It closes M3.

  • Collaboration and submission

    from about 26 Nov

    The next milestone, four stages. You restored this order on 22 Nov: it comes before the template builder.

  • First deploy to a test site

    waits on you

    Not on the timeline until the hosting is settled (B-001, B-002).

The milestones to come, stage by stage

Each stage ends on the local site for you to try. Every spec below is approved; the dates are estimates from the pace so far.

Next · 4 stages26 to 29 Nov

Collaboration and submission

Several people finish one report without losing each other's work, then it is reviewed and submitted.

  1. A
    People in a reportcontributors, and who may remove them
  2. B
    Statuses and submissionthe readiness checks, Review & Submit, Final Submit
  3. C
    Review and Reports homethe review queue, reopening, archiving
  4. D
    The outputs and the seedCSV, the print layout, a report by email
Then · 4 stages1 to 4 Dec

The template builder

Template Studio: administrators change the report without a developer, and written reports keep their version.

  1. A
    Several templatesand who is offered each
  2. B
    Drafts, publishing and historyevery publish makes a new version
  3. C
    The Studio's canvassections, controls and the field toolbar
  4. D
    The library and the old formready-made sections, the old app's form rebuilt
Then · 3 stages6 to 8 Dec

Follow-ups and the evidence gallery

What a shift raises is tracked until it closes, and the photos reports hold can be found.

  1. A
    A follow-upa record with a priority, a due date and an assignee
  2. B
    Follow-ups and reportsraised from a report's tick, and withdrawn
  3. C
    The evidence gallerythe photos, with flags and filters
Last · 4 stages10 to 13 Dec

Mail, the settings and the last screens

Word sent off the site safely. When it is done, every screen of the design exists.

  1. A
    Somewhere to senda person's confirmed address, the mail settings
  2. B
    What is sentnotices and a report by email
  3. C
    The sign-in screens and PINswording an administrator can edit
  4. D
    The manualthe user manual and the Technical Document

Estimated timeline

builtin handestimate, one box a stagea day for your run and mends

Dates after today are estimates, not promises. They assume the pace so far holds: one stage a day, work on every day, and one day between milestones.

Job
Stages
Days
Built NOW Estimate Mon16 Nov Mon23 Nov Mon30 Nov Mon7 Dec Mon14 Dec

Built

2 milestones · 18 small steps
Groundwork and the specsS0 to S8
9 steps
2
15 to 16 Nov
User managementM1 · v0.1.0
5 of 5
3
15 to 18 Nov
PermissionsM2 · v0.2.0
2 of 2
2
17 to 18 Nov
Mends and toolsS9 to S17 · v0.2.1 to v0.2.3
9 steps
4
19 to 22 Nov

The report renderer

M3 · 2 of 4 stages built
Stage A, a report from the template
built
1
21 Nov
Stage B, Reports home
built
1
22 Nov
Stage C, people and words10 of 16 pieces merged
now
about 2
to about 23 Nov
Stage D, photos
to do
about 1
24 Nov
The shift types' screen
to do
about 1
25 Nov

To come

4 milestones · 15 stages
Collaboration and submission
0 of 4
about 4
26 to 29 Nov
The template builder
0 of 4
about 4
1 to 4 Dec
Follow-ups and the evidence gallery
0 of 3
about 3
6 to 8 Dec
Mail, the settings and the last screens
0 of 4
about 4
10 to 13 Dec
Every screen of the design builtthe first deploy is not placed: it waits on the hosting
about 14 Dec
9 stages in 8 daysThe pace so far, 15 to 22 Nov, with commits on every one of those days and 18 small steps beside them.
About 14 DecemberEvery screen built if that pace holds: 18 stage-days and 4 days between milestones, counted from 23 Nov.
Early JanuaryThe same work at half the pace, for example if stages wait on reviews or the weekends are not worked.

Asked of you

Nothing here stops the work today

  • Look over one decision of Stage C: the check narrowed for one file so a device can keep work while offline (B-601, P1). It can be taken back alone.
  • Try Stage C on the local site when it lands, on a desktop and a phone. The work stops there for you.
  • The phone part of M1's run: the second factor with a phone and an authenticator app (B-245, P1). The rest of M1 is run and greenlit by you.
  • Trust the local site's certificate on your desktop browser and phone, so it opens there over HTTPS (B-020).
  • Settle the hosting (B-001, B-002). This places the first deploy on the timeline.

By the numbers

Review, the merge gate and the backlog

Planted faults caught in Stage C's reviews93 of 107
Eight briefs counted. Every brief is reviewed with faults planted on purpose; each miss was mended or made a test.
The full gate, just ci, last run1,092 s
Against its line of 1,200 seconds (22 Nov, at S17's merge). The run before took 1,032.
Backlog rows open272 of 527
Open: 3 P1, 57 P2 and 212 P3, most of them small. Closed: 247. Accepted or deferred: 8.