Documents
Build a document stack for one Fintwist program
Sort general explanations, program instructions, and agreements without mixing their scope.
When several Fintwist or Corpay pages describe a card, the challenge is not collecting more tabs. It is deciding which document answers the question in front of you. A fee schedule supplied for a particular card program and a general product overview answer different questions. The method below is an editorial way to sort them; it is not a provider-issued document hierarchy.
Put each document in a lane
Use three lanes: introduction, program instruction, and applicable terms. An introduction explains the product family. An instruction tells a specified audience how to complete a task. Terms describe conditions within their stated scope. A document may serve more than one purpose, but you should still know which part you are relying on.
Add the audience and date beside each item. “For new hires in this location” is narrower than “for employees.” “Updated this month” is not enough if the document concerns another program. The date helps establish currency; the audience helps establish relevance.
Resolve a mismatch without inventing a hierarchy
Suppose a public overview describes a convenient option while your program materials do not mention it. Do not assume silence means either permission or prohibition. Ask the responsible organization whether the option is included and which current document confirms that answer.
Likewise, an employer’s explanatory email does not automatically replace a card agreement. If documents appear inconsistent, describe the two statements and request clarification through the applicable official channel. This article does not decide which legal document controls a dispute.
Produce a one-page index, not a private archive
The output can be a list of titles, dates, subjects, and verified locations. You do not need to copy full agreements into a public note or retain screenshots containing financial data. Store any necessary personal documents only in a place appropriate for them.
At the end, every open question should point to a missing document or a specific unresolved sentence. “Which fee schedule applies to this card?” is actionable. “The internet says something else” is not. Keeping the stack narrow also makes later updates manageable: replace the superseded reference and retain a note of what question it answered.