Boundary of use: the three scenes below are fictional and involve only record keeping, communication and agreeing a division of work. They do not involve quality verdicts, equipment disposition or safety procedures. Anything touching a verdict or disposition follows company procedure and the person holding that responsibility.
A team can agree on what to document and how much context a later reader will need. Either colleague can spot a missing field or an incomplete explanation.
INFP and ISTJ: before a factory audit, how the data chain and the explanatory page get split
(Fictional scene) A client is coming to audit and wants three months of records traced. The division follows who normally handles the records, who followed those two anomalies, and who knows the procedure revisions — not type. A common arrangement: whoever knows the logbooks builds the three months of sheets into one chain by batch and by procedure revision; whoever was on site writes a page explaining how the two anomalies were found, who was told and what changed afterwards.
Places missing a signature are marked and handled under the applicable records procedure. Where late signing is permitted, the actual signer, date and reason are kept — no back-dating, no signing for someone else; items that cannot be verified are left as they are rather than filled in to look tidy.
Two constraints apply. The explanatory page cannot replace the record: however detailed it is, a missing signature page is still a missing item. Nor can the chain replace the explanation: however complete, it cannot say why those two variations happened — the cause has to be verified separately.
In this fictional audit, the team samples three entries and checks who measured each part, which procedure applied and whether the next team was notified. This checks traceability in those entries. A qualified reviewer would investigate the causes separately using the relevant evidence.
INFP and ISTJ: a cleaning rota in a shared flat
(Fictional scene) Two people share a flat and the living room and kitchen are never cleaned unless someone asks. One proposes a rota: who takes the rubbish out on which day, who mops at the weekend, tick when done. The other hesitates — will a rota turn the flatmate relationship into mutual assessment, with every missed turn recorded.
This is not about who is cleaner, and not a division by type. The one proposing worries that the work will always fall to the same person; the one hesitating worries that a table will fix things in writing and make living together harder later. Both concerns are legitimate.
A workable version splits the table into two columns: what must be done, and what gets done when noticed — only the first gets ticked. One counterexample: the proposer will also cover a flatmate's week during overtime without mentioning it, and the hesitant one will, after two weeks of putting up with it, stick the table on the fridge.
Agree a checkpoint: look at the table together on the last weekend of each month, adjust the division only, do not reopen old grievances. If someone genuinely stops doing their part over a long period, talk to them separately rather than reworking the whole table.
INFP and ISTJ: the record comes back from review
(Fictional scene) The review comment comes back as "remarks too general". The first thing to do has nothing to do with type: establish whether the comment means the facts were unclear, that mandatory fields were missing, or both. Different targets, different fixes.
If the facts were unclear, what gets added is the process at the time: when it was discovered, which values it rested on, who was notified, how it was handled afterwards. If fields were missing, what gets added is the mandatory cells, units, signatures and dates. If both, list what is missing against the comment first, then decide what can be fixed on the spot and what needs verification back on site.
Responding to the same comment, the two may work differently: one more often compares clause by clause against the procedure to confirm the revised version passes the same requirements; the other more often restates the situation first to confirm that a reader will not misread where responsibility lies. Both work; who checks the revision afterwards follows duty, not type.