The road, in build order
Seven milestones, the large stops in the shaded boxes, with the small steps done around them.
-
15 NovSmall stepsGroundwork4 small stepsS0 to S3: the skeleton, 39 shared pieces, HTTPS
-
15 to 16 NovSmall stepsThe specs5 small stepsS4 to S8: every milestone specified and approved
-
M115 to 18 NovMilestoneUser management5 of 5 stagesv0.1.0 · sign-in, accounts, audit log
-
M217 to 18 NovMilestonePermissions2 of 2 stagesv0.2.0 · the matrix, impersonation
-
19 to 22 NovSmall stepsMends and tools9 small stepsS9 to S17 · up to v0.2.3
-
You are hereStage C of the report rendererM3NowMilestoneReport renderer2 of 4 stagesStage C in hand
-
NextMilestoneCollaboration and submission4 stagesseveral people finish and submit a report
-
LaterMilestoneTemplate builder4 stagesadministrators change the report themselves
-
LaterMilestoneFollow-ups and the gallery3 stageswhat a shift raises is tracked to its end
-
LastMilestoneMail, settings, last screens4 stagesword sent off the site; every screen in place
-
Waits on hostingSmall stepFirst deploy1 small stepplaced 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 NovThe 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 NovM1, 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 NovM2, 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 NovNine 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 NovM3 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 NovM3 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 NovThe 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 agentsContract1 2Backend1 2 3 4Web1 2 3 4 5 4bThe joinJoin 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 NovTwo 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 NovPhotos 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 NovWhere an administrator keeps the shift types. It closes M3.
Collaboration and submission
from about 26 NovThe 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 youNot 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.
Collaboration and submission
Several people finish one report without losing each other's work, then it is reviewed and submitted.
- APeople in a reportcontributors, and who may remove them
- BStatuses and submissionthe readiness checks, Review & Submit, Final Submit
- CReview and Reports homethe review queue, reopening, archiving
- DThe outputs and the seedCSV, the print layout, a report by email
The template builder
Template Studio: administrators change the report without a developer, and written reports keep their version.
- ASeveral templatesand who is offered each
- BDrafts, publishing and historyevery publish makes a new version
- CThe Studio's canvassections, controls and the field toolbar
- DThe library and the old formready-made sections, the old app's form rebuilt
Follow-ups and the evidence gallery
What a shift raises is tracked until it closes, and the photos reports hold can be found.
- AA follow-upa record with a priority, a due date and an assignee
- BFollow-ups and reportsraised from a report's tick, and withdrawn
- CThe evidence gallerythe photos, with flags and filters
Mail, the settings and the last screens
Word sent off the site safely. When it is done, every screen of the design exists.
- ASomewhere to senda person's confirmed address, the mail settings
- BWhat is sentnotices and a report by email
- CThe sign-in screens and PINswording an administrator can edit
- DThe manualthe user manual and the Technical Document
Estimated timeline
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.
Built
The report renderer
To come
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