Intake analyst / EXAMPLE DESIGN
Finding a missing file halfway through a job means another round of chasing. See how the Intake Analyst checks a case pack before evidence work begins and names the person who can supply each missing item.
Working browser demonstration · Fictional sources · Local rules, no live agent
The agreed intake list and the files received for one authorised case.
A checklist of received files, missing items and any restricted material to isolate.
The evidence owner accepts completeness and approves requests for more information. The role cannot admit restricted material.
Choose how many of the four required records arrived. Add a restricted attachment to see why an extra file cannot fill a missing requirement. Set the input and select “Prepare this result”. Then read the output before recording a fictional review.
Changing an input starts a fresh example.
Only the case workspace and signed scope; unexpected restricted material stops intake.
PREPARED OUTPUTA checklist of received files, missing items and any restricted material to isolate.
HUMAN REVIEWThe evidence owner accepts completeness and approves requests for more information. The role cannot admit restricted material.
Compare a case pack with four agreed requirements. See which records arrived, what is missing and what belongs outside the case.
Compare a case pack with four agreed requirements. See which records arrived, what is missing and what belongs outside the case.
Local fictional example · 0 recorded events · Revision 1
These fictional originals belong to the selected case. Compare the output with the source, version and allowed use. Showing a source here does not clear missing evidence or grant wider access.
Synthetic source. Case D-01 asks for a one-week role-capacity comparison, not a staffing recommendation or revenue forecast. The target is simulation week 1. There are 6 comparable candidate packs of qualified demand, 40 analyst hours and 8 partner hours. R is available qualified-reviewer hours, a whole number from 4 to 24, default 12.
Use boundary: Synthetic fixture; private review within this fictional case only.
Synthetic source. For simulation week 1 only: analyst availability 40 hours; qualified-reviewer availability R hours; partner availability 8 hours. R comes from the selected fictional allocation scenario. Allocation describes available active effort, not signed client acceptance or bankable revenue.
Use boundary: Synthetic fixture; private review within this fictional case only.
Synthetic source. Per comparable pack, analyst effort is 8 hours and partner effort is 2 hours under both methods. Current reviewer effort = 3 review + 1 correction = 4 hours. Proposed reviewer effort = 2 review + 0.5 correction + 0.5 operating = 3 hours. For each method, whole-pack capacity = min(floor(40/8), floor(R/reviewer hours per pack), floor(8/2), 6 demand). Floor each role before taking the minimum. No client acceptance, quality equivalence or realised gain is established by these assumptions.
Use boundary: Synthetic fixture; private review within this fictional case only.
Synthetic source. The issue draft must show both methods, the original source versions, all role and demand ceilings, review/correction/operating effort and an alternative to changing the method. A qualified reviewer must test quality on comparable packs before issue. Client acceptance, corrections or disputes require their own record; this fixture contains no accepted client pack.
Use boundary: Synthetic fixture; private review within this fictional case only.
Synthetic source. D-01 requires four version-1 records in this order: DEL-SCOPE, DEL-ALLOCATION, DEL-METHOD, DEL-REVIEW. K is the selected whole number of required records received, 0 through 4; exactly the first K arrived. Required gaps = 4 minus K. Allocation uses the original case's default R = 12 hours. The source library holds reference specimens of all four, but a specimen displayed there does not mean it arrived in this intake. The challenge adds one unsolicited attachment outside this list; it never fills a required slot. Received required plus missing required always equals four. An unexpected restricted attachment holds intake for the evidence owner.
Use boundary: Fictional case metadata for this role example only.
Synthetic source. Challenge attachment SIM-EXTRA-01 belongs to a different fictional case, D-OTHER. D-01 has no permission to read or use it. Only this restriction metadata is present; its contents are absent. Keep the attachment isolated and ask the evidence owner to resolve its disposition. Removing a filename or approving this screen grants no case access.
Use boundary: Restriction metadata only; attachment content and use in D-01 are denied.
Run the connected case to see what arrives before this step, who reviews its output and what happens when the next owner returns it.
Bring the task, its current owner and where it gets stuck to a no-fee Workflow Fit Call. If a paid System Blueprint is useful, it measures one service line and fully designs three connected workflows. Roles are chosen for those designs. Installation is separately scoped; pricing is quote-specific.
